| Post a Reply |
| Weblog: |
|
Enterprise Services and Widgets: A Recipe for Information Access |
| Subject: | Rooftop vs. Enterprise Widget Framework | |
| Date: | 2008-05-15 23:30:53 | |
| From: | Richard HirschBusiness Card | |
|
|
||
|
Hi Dan,
|
||
|
|
Next Message |
| Showing messages 1 through 2 of 2. | ||
|
|
||
| Titles Only | Main Topics | Oldest First |
I'd like to see a more thorough explanation too.
regards, anton
I asked Alexander Dreiling to confirm my understanding of the AJAX-based nature of the Rooftop platform. He said that the front-end used to created widgets is an AJAX-based web application. AJAX was used to power the development platform to make it as easy as possible for end users who wanted to create widgets. They just need a link, a browser and that’s it. Once the application is loaded users have a range of services to choose from and to combine in whatever way they would like. They then can save their work or deploy it as a Yahoo widget or as a Windows Vista Gadget (in addition to these three more formats are supported). Hence, the application provides a full-blown secure Web Service Infrastructure, Mashup facilities and the facilities to create fully functional widgets / gadgets.
So, the widgets are widgets, not AJAX-based widgets. I suppose that the right language would be as follows:
Rooftop has an AJAX-based development environment for creating widgets that can be deployed in standard widget frameworks.
I am still working on getting an answer about when Rooftop would is recommended as opposed to the Eclipse-based environment.
Cheers,
-Dan Woods
| Showing messages 1 through 2 of 2. |
SAP, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product, service names, trademarks and registered trademarks mentioned are the trademarks of their respective owners.