How it works is that:
- the requestNavigateTo function puts the <myVarName>=<uri encoded
( json encoded ( opt_params ))> in the container url, for example:
http://my.container.com/application?foo=bar&view-params={foo:bar}
- your container page picks this up, and puts this directly on the
gadget iframe url using &view-params={foo:bar} as format
- The javascript in the gadget take care of the rest for you..
Took me a bit to figure out too, container implementation details
aren't very documented at the moment
-- Chris
On Jun 5, 2008, at 11:47 AM, Pieter De Schepper wrote:
Hi all,
I'm currently implementing the requestNavigateTo-function in
gadgets.js on our Netlog-implementation of Shindig.
This function has an argument opt_params which, according to the
specs, are passed to the gadget after it has been navigated to on
the surface.
How should this be passed to the gadget? How does the gadget
accesses these opt_params?
I can't find it in the documentation, so can anyone shed some light
on this matter?
Regards,
Pieter De Schepper
Junior Web Developer
NETLOG NV
Emile Braunplein 18
B-9000 Gent
http://www.netlog.com
[EMAIL PROTECTED]
Tel +32 2 400 43 21
Fax +32 2 400 43 20
GSM +32 485 85 52 24
