incubator-wookie-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: [PROPOSAL] Wookie gadget "store" moved to Rave?
Date Wed, 11 May 2011 09:29:56 GMT
On 10/05/2011 19:44, Scott Wilson wrote:
> On 10 May 2011, at 16:17, Ross Gardler wrote:


> Making sure all Wookie's functionality is exposed by REST API  should
> be a priority - some things (API key management, registering
> OpenSocial gadgets) currently aren't and we should fix that.
> Second, providing XSLT to make the results of REST API calls more
> useful is a good idea.
> So, irrespective of the view of the proposal as a whole, I think the
> above should be added to Jira anyway (I'll do that soon...)


>> Thoughts?
> I like the idea of making Wookie more lightweight and modular;
> delegating the whole concept of an admin client to Rave is an
> attractive thought from that perspective. I already largely manage
> Wookie from the command line anyway - e.g. dragging and dropping in
> Widgets to /deploy rather than going through the web interface. I
> mostly use the web interface for some interactive debugging these
> days.
> I'd previously looked into providing Wookie admin functions as
> widgets (this is in the scratchapad area). These too could be
> submitted to Rave.


Implementing the admin UI as widgets in Rave means that other platforms 
(with suitable connectors) can then become the admin UI.

> (Note also I've worked on a prototype using an Apache Solr repository
> implementation to support searching and browsing across multiple
> widget/gadget providers - this might also be of interest to Rave:

I'll let you bring that idea to Rave in your own time. It sounds great.


>> Ross [1]

View raw message