There are (at least) three use cases for setting widget attributes: * programmatically from within the widget by invoking the appropriate API - supported already within Shindig - requires a widget developer to utilise * programmatically from within the container framework - supported by the APIs already within Shindig - requires a container developer to utilise * data driven from the width and title settings within the gadget XML whilst the gadget is being rendered within the container - not implemented.
This last requires shindig to examine the (optional?) title and height settings and to use them when rendering the widget, e.g.: <ModulePrefs title="Zombies!" height="350" /> It would appear that the client-side Javascript has no direct access to the contents of the gadget XML? That the gadget XML is parsed by the server-side implementation (the proxy?). It would appear that the server-side implementation needs to provide the details of the ModulePres to the client-side implementation (possibly to the gadget.js)? I'd like to have a stab at solving this, but I'm not sure how this is supposed to be done. Is the proxy supposed to inject JavaScript code into the response to set the title, height? Is the proxy supposed to pass details of the ModulePrefs to the widget container, so that the container can (optionally) set the details? It can't be the responsibility of the gadget developer to do this - else all the existing gadgets in existence would requires changes. Regards Martin
