Hi,
So far, most containers have allowed developers to continue to require
opensocial-0.7 even after 0.8 support has been released. I see no
reason to believe this trend will not continue for 0.9. When checking
for the availability of OpenSocial, you'd want to check for the same
version you've included in the require tag of your XML.
If trying to detect the presence of social features in a locale where
they are never available, the exact solution depends on whether or not
gadgets.* is available. I believe gadgets.* will roll out before
social, in which case you'd just use the above hasFeature code to
check for availability and render a modified gadget. If gadgets.* is
not available, you'd need to check the availability of that API first.
This (untested) code, might work:
gadgets = gadgets || false;
if(gadgets && gadgets.util.hasFeature("opensocial-0.8")) {
// do opensocial version
} else {
// do non-social version
}
I hope this helps.
Dan
On Jan 24, 12:07 pm, poncz <[email protected]> wrote:
> Hi,
>
> In one of the recent blog post (http://igoogledeveloper.blogspot.com/
> 2009/01/new-acls-on-social-features.html) I saw a suggestion to use
> gadgets.util.hasFeature("opensocial-0.8") to check if the user allows
> the gadget to use the social features. But what if opensocial-0.9 or 1
> will be introduced? will this still work?
>
> As much as I understand not all iGoogle locals will support opensocial
> gadgets on launch. However the gadget xml is the same for all local.
> So if I create an open social gadget what will the users in non
> opensocial supported local see?
>
> Thanks,
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"iGoogle Developer Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Gadgets-API?hl=en
-~----------~----~----~----~------~----~------~--~---
