On 9 Mar 2012, at 09:21, Ross Gardler wrote: > On 8 March 2012 23:15, Richard Kettelerij <[email protected]> wrote: >> Hi list, >> >> I'm working with Rave for a few months now and was thinking about the >> following new feature: ability to uploading widgets to the portal. Currently >> widgets can only be added by URL. This raises the question, where do you >> host your widgets? One can think of various solutions but having a simple >> upload function available might come in handy. >> >> Some thoughts: >> - W3C widget can be uploaded as .wgt file >> - OpenSocial widget can be uploaded as plain XML file, or as a zip file in >> case additional resources (CSS, JS) are required. >> - Rave contains a controller/servlet to serve the widget files, optionally >> allow placeholder replacements. >> - Rave treats uploaded widgets like any other widget, meaning a reference >> (e.g. http://localhost:8080/widget-repo/mywidget.xml) to the uploaded widget >> is stored in the widget database table. >> >> What do you think? > > Getting W3C widgets into Wookie (which provides the W3C widget engine > for Rave) is already supported API (see > http://incubator.apache.org/wookie/docs/api.html). However, this does > not automatically put the widget into the Rave widget store. Either > Rave needs to provide an API to allow this and pass it through to > Wookie or Rave can be configured to query the Wookie server and put > all widgets it finds into the the store (I'm assuming it doesn't do > this at present, it didn't do last time I looked - some time ago). > > Rave already hosts W3C Widgets via the embedded Wookie server. But I'm > not sure how complete the integration is at this point so there is > likely still some work to do.
Paul has submitted a patch for review that allows browsing Widgets already in Wookie from the Rave store to add them, however when we talked recently about it we weren't sure if this was the right workflow for Rave - I think uploading to Rave, and then Rave POSTing the Widget to Wookie is perhaps a more sensible flow from a Rave point of view. In any case in 0.10 we've just altered the Wookie REST API to return the metadata XML in the response to a widget upload POST so that Rave could do a one-step upload via Wookie without requiring users to enter any metadata manually. > > Ross
