The "typical" user experience would not involve opening the containers preferences UI. The gadget would display its own UI allowing the user to set the values and then call the set prefs APIs to tell the container about the new preference values. If the user then went to the container preferences UI the new values would be displayed there. What you trying to accomplish is not wrong in any way but Shindig doesn't have a default way to accomplish it. What you are doing with the RPC handler seems like the best approach. Although I would probably not hook into existing RPC APIs but instead create my own that just opens the preferences UI in the container. You could then take it one step further and wrap this in a feature for the gadgets of your container to use. That way they can mark the feature optional and fall back to the traditional way of setting preferences if they are not rendered in your container.
On Tue, Nov 12, 2013 at 1:50 PM, Darren Bond <[email protected]> wrote: > Dear All, > > > > Our gadgets have an "Edit Settings" menu item, accessible via each gadget's > title bar, which displays the gadget's UserPrefs dialog (typical iGoogle > style behaviour). This functionality is working well. > > > > Now we have developed a Weather gadget, who's initial state displays a "Set > Up" button within the gadget's window. > > > > The question is how can we enable this button to display the gadget's > UserPrefs dialog when clicked? Does Shindig have a kind of event that could > be published outside so that a gadget's container (our website) can catch it > and handle it as required? > > > > The required action is shown in this image - > http://download.globalcad.com/Weather_Gadget_Button_UserPrefs.png > > > > The current logic we use to enable the gadget title bar's "Edit Settings" > menu item is via the Shindig 'set' and 'setArray' methods... > > http://opensocial-resources.googlecode.com/svn/spec/trunk/Core-Gadget.xml#ga > dgets.Prefs.set > > http://opensocial-resources.googlecode.com/svn/spec/trunk/Core-Gadget.xml#ga > dgets.Prefs.setArray > > And a client side subscribes and catches them registering its own > function-handler by gadgets.rpc.register('set_pref', setPrefs). > > > > Thanks. > > > > Kind regards, > > > > Darren >
