OK, I've just committed the last of a series of changes to implement this new feature in basic form!
I'm sure its got a ton of bugs, but I've put in quite a few tests. Please do play with it* and report any issues. Basically you invoke it rather like the WidgetInstances API - the POST request has the same parameters (but is located at /export) - what you get back is just the URL to the .wgt you can download. See the test cases for an example. On 9 Feb 2011, at 17:14, Ross Gardler wrote: > >> One issue is that the W3C Widget Interface isn't exactly the same as >> the WAC widget object used by mobiles (e.g. different method >> signatures for preferences). Not sure what would be the best solution >> there; maybe a shim in our Widget interface to delegate to WAC where >> its present? > > Are there any moves at the specification level to resolve this? It seems like > it is something that needs to be addressed at that level and anything we do > here will be an intermediate step. Some good news on this one - see http://public.wholesaleappcommunity.com/redmine/embedded/wac2pubrev/core/web-standards.html Quote: > 2.7.2. Widget Interface > > The Widget Interface [Widgets-APIs] defines key APIs used by widgets, e.g. > for managing widget private storage. > > WS-1400 The WRT MUST implement the Widget interface in accordance with the > [Widgets-APIs] specification. So this means the WAC injection stuff I just committed this afternoon is already supporting legacy WRTs :-) [OK code sprint over for now, time to get a drink and to pay some attention to my girlfriend!] - S * AFTER you've tested the 0.9.0 release, obviously!
