On 29 March 2012 14:52, Paul Sharples <[email protected]> wrote: > On 29/03/2012 14:39, Ross Gardler wrote: >> >> On 29 March 2012 14:31, Scott Wilson<[email protected]> >> wrote: >>> >>> Hi everyone, >>> >>> We've now removed the UI client from trunk, the only UI now is a >>> HTML-only demo that lets you preview widgets (thanks Ross for the >>> improvements to this - I like the filter especially!) >> >> I'd like to turn the navigation part into a widget, that shouldn't be >> hard the way it is currently implemented. Just need to find a little >> time to do it. This is *not* a blocker though. It is one more step >> towards extracting all the UI functionality out of core. >> >>> Widgets >>> ====== >>> Drop into /deploy folder, or use REST API. The only function not >>> supported outside of the REST API is deleting widgets. >> >> So how do we delete a widget in a running instance of Wookie? Seems >> like a necessary feature (but not a blocker). > > > I presume you'd use the RESTAPI - see > org.apache.wookie.tests.functional.WidgetControllerTest for an example.
Yes, sorry I misread Scotts original mail. >>> The question I have is: is this sufficient to consider WOOKIE-262 >>> completed? ... > I guess this probably covers it. If we find anything else we've missed then > we can open a new issue for it (more specific) > The only other thing is that WOOKIE-262 also mentions a command line > management utility (is this a provided .bat and .sh script?) +1 > > Paul > >> >>> If so, I'll get on with sorting out the remaining documentation so I can >>> close WOOKIE-19& WOOKIE-15. >> >> This email is a good start for FAQ documentation. >> >> Ross >> > -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
