Hi
rpc.js has a bug related to returning the window for container -> gadget
channel communication
Original code
function getTargetWin(id) {
if (typeof id === "undefined" ||
id === "..") {
return window.parent;
}
// Cast to a String to avoid an index lookup.
id =
Will this framework be taking advantage of the features framework where views
would be appropriately expanded, etc?
Also, has there been any effort to expand gadgets.rpc so that gadget <-> gadget
or gadget broadcast would allow gadgets
to communicate with one another?
Finally is the new js tak
A JS loader that has the capability to load other javascript and their
transitive closures shouldn't reinvent the wheel,
or use a loader that is only specific to opensocial or a vendor's extension of
opensocial, but rather use commonjs's require
or ECMAScript's 'Simple Modules' which includes th
SM seems better but requires browser
> support.
>
> What are your thoughts on what we might do now to fill the need during
> transition?
>
> --j
>
> On Mon, Jun 21, 2010 at 7:12 PM, Kam Kasravi wrote:
>
>> A JS loader that has the capability to load other javas
We (yahoo) took the original pubsub and extended it, but it would certainly be
worth exploring openajax's pubsub.
I had used their hub 1.0 implementation sometime back and thought it was well
implemented. Hub2.0 has
many more features.
kam
On Jun 25, 2010, at 3:17 AM, Shtein, Ilya wrote:
> Ar
makeRequest is reserved for requests that are backend bound. Although I haven't
looked at the documentation,
perhaps this is a request to route to another gadget via the container. This
type of functionality would certainly
be needed.
kam
On Jul 2, 2010, at 4:51 AM, Justin Wyllie wrote:
>
>
As far as I know, myspace has done this correctly - they've extended the
opensocial schema and
apis. Probably going thru their documentation would be the quickest way to get
an understanding of
how this is done from both the data model and javascript perspectives.
kam
On Jul 2, 2010, at 7:02
Actually just setting the iframe's parent to point to the container will allow
the 2 calls below to work.
That is the iframe's src should contain a parent parameter that is the same as
the parent.
kam
On Jul 7, 2010, at 8:31 AM, John Hjelmstad wrote:
> Hi Randy:
>
> What's the top-level page,
