I changed the subject to ensure this gets seen. It has been suggested that, rather than link to a live wookie server we don't have control of we should bundle Wookie with the Rave release (as we do with Shindig).
This has a number of advantages, including: - we can control the widgets available in the demo - easier for third parties to integrate - can use the 0.9.0 release and thus we won't be held up by unexpected delays in the Wookie release vote - reduces the urgency to enhance the integration to use different servers (that is we can limit it to the local server for now). Not being a Maven user I'm not sure exactly how to do this, but Ate says it's "trivial" and I'm sure he can point me to a tutorial (or maybe I just look at the Shindig thing). Assuming there are no objections I will make this happen in time for the 0.5 release (unless it is so trivial it's easier for someone else to do it, just replace the dependency on the wookie-connector with a dependency on Wookie itself and deploy it as appropriate). Ross On 20 October 2011 10:44, Ate Douma <[email protected]> wrote: > Mighty cool Ross! > > I haven't had the time to try it but will do ASAP. > > And as a reply on a later message: I'm +1 on bundling Wookie with the demo. > I prefer keeping the demo self-contained and not rely or depend on an > external server. > Current OpenID integration being an exception, but its not required to login > any way and its kind of nature of the beast. > > Bundling Wookie of course should remain optional, as is/should be the case > for Shindig. Running Rave with only Wookie integration (bundled or not) > should be possible just as well. > > Ate > > On 10/20/2011 03:41 AM, Ross Gardler wrote: >> >> I've finally managed to find the time to complete the Wookie >> installation work. Well, the first stage of it at least. Thanks to >> Jasha at the hackathon for helping me get back up to speed with how >> Rave works these days. >> >> Currently the location of the Wookie is hard coded to a test server >> running in Oxford. Clearly this needs to be customisable. >> >> I've not added any W3C widgets to user screens by default as this >> should still be considered alpha. However, I have added a basic chat >> widget to the database. To test it out search for "chat" in the widget >> store and add the resulting widget to a page. >> >> If you log into a different browser or a different machiine with a >> different user and add the same widget you can chat across the >> browsers. >> >> Note, this uses a SNAPSHOT Wookie-Connector. Wookie is on target to >> release this becore Rave 0.5. However, if it does not manage to do so >> we can roll back to the 0.9 release which includes the necessary code. >> >> Finally, I have a request. Can someone who will be at ApacheCon please >> help me set up my dev environment properly. I am a complete Maven >> newbie. I can't believe that the development cycle should be as >> painful as I'm finding it. >> > > -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
