Hi Waldemar,

Actually 'OpenSocial' doesn't use any external javascript libraries like
prototype or jQuery.

The container (the website surrounding the gadget) can of course use some
library, but since the gadget resides in an iframe this doesn't affect the
gadget at all.

If you want to create your own social site (and not a gadget) then you could
implement the gadget <> container RPC calls however you like, using any
library you like, as long as you register your RPC hooks using:
gadgets.rpc.register('resize_iframe', mySetHeight);
gadgets.rpc.register('set_pref', mySetUserPref);
gadgets.rpc.register('set_title', mySetTitle);
gadgets.rpc.register('requestNavigateTo', myRequestNavigateTo);


On Mon, Jan 5, 2009 at 6:36 PM, Waldemar <[email protected]> wrote:

>
> Hi again...
> We are currently implementing an opensocial container, our site uses
> jquery and has been using it for quite some time before starting any
> development with opensocial. I'm not completely sure, but is seems
> like opensocial heavily relies on prototype javascript library for its
> implementation. I've just checked partuza's and orkut's
> implementations and both have the "$" as a prototype environment
> variable.
>
> Since jQuery also uses "$" as its environment variable there is a
> conflict between these two after rewriting each other's property.
> jQuery could be referenced by using "jQuery" environment variable or
> using an alias, thus causing no conflict... although that would
> require some code rewriting which we are trying to avoid.
>
> Do gadgets.js, rpc.js and other files need prototype as part of the
> standard or is there another path?
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Implementing OpenSocial Containers" 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/opensocial-container?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to