I'm wondering if an API like this would supplant URL style gadgets in a
way? Probably not, but something to think about since a UrlSite and a URL
style Gadget accomplish about the same thing.
Matt Marum
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------|
|Ryan J Baxter/Westford/IBM@Lotus
|
>--------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------|
|[email protected]
|
>--------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------|
|04/27/2011 03:31 PM
|
>--------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------|
|Allowing The Common Container To Render URLs in Sites
|
>--------------------------------------------------------------------------------------------------------------------------------------------|
We have a few use cases in some of the proposals out there for OpenSocial
2.0 where the container would be responsible for rendering URLs in
iFrames. (You can check out the proposals here,
http://docs.opensocial.org/display/OSD/Embedded+Experiences and
http://docs.opensocial.org/display/OSD/View+Enhancements+To+Support+Opening
+Of+Gadgets+and+URLs
.) The URL can be anything, for example http://www.google.com or
http://example.com/mypic.png. In my mind the best way to do this is to
have something similar to the common container classes GadgetSite and
GadgetHolder for URLs....something like UrlSite and UrlHolder. Then we
can add the corresponding methods to the container to render these URLs in
their sites. I was thinking something like
osapi.container.Container.newUrlSite(urlEl)
osapi.container.Container.navigateUrl(....)
osapi.container.Container.closeUrl(site)
Anyone have any thoughts or objections to this?
-Ryan
Email: [email protected]
Phone: 978-899-3041
developerWorks Profile
