On 20 October 2011 10:11, Jasha Joachimsthal <[email protected]> wrote: > On 20 October 2011 03:41, Ross Gardler <[email protected]> wrote: > > Currently the location of the Wookie is hard coded to a test server >> running in Oxford. Clearly this needs to be customisable. >> > > We bundle Shindig with Rave to let all the OpenSocial gadgets work. In > theory you can use an external OpenSocial compliant server. Can't we bundle > a Wookie instance with Rave? >
Yes. We certainly can. I've not evaluated how many additional dependencies this would bring with it. At Wookie we are moving towards losing the web front end and just providing an API for access to that would certainly make it much smaller. I imagine that many of the dependencies that Wookie needs are already used by Rave. It would affect startup times a fair bit, but we could always make execution of the Wookie server optional. What do people think, should we have an embedded Wookie server? >> 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. >> > > I can confirm it works and I will show it today in our sprint demo :) The > chat session seems to be public to anyone using this widget so watch the > language. That's correct - I'm not sure if it is currently possible to limit the widgets that see the messages or not (obviously it is important to do so). Scott will know. We saw a demo from the ROLE project at the weekend, they have implemented spaces in their system. That should solve this problem for us. I'm hoping to get them on board here, they are keen to figure out how to work with us (and I believe some are lurking on this list)... >> 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. >> > > What's the difference between 0.9 and 0.9.1-SNAPSHOT right now? No significant features, just bug fixes. The main difference that affects Rave is that 0.9.0 does not provide the connector as a separate artifact. In order to use 0.9.0 we would have to pull the whole thing down. I was just being conservative. To my knowledge there are no changes to the connector that affect us. (note I have *not* tested against 0.9.0 code but the live instance of Wookie we are running against is 0.9.0 so I don't expect any surprises). Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
