On 29 Jun 2012, at 13:46, Olexiy Chudnovskyy wrote: > Hi Ross, > > thanks for your fast reply. > >> What I wanted to say is that your approach looks really good. I liked what > I >> saw in the video from a concept point of view. I really like the > simplicity of >> wiring widgets together. It looked potentially very powerful. I'd love to > see it >> applied in a more complex environment. >> Getting the code here would be a good way of encouraging that. > > I will put the source code online and publish the link here. > >> >> A couple of things I noticed. Most significantly it looked like your demo > is built >> on a pretty old version of Wookie (perhaps 0.8?). It probably wouldn't > take >> much to bring it all up to date, but we need to be aware of this. > > The current prototype was ported to Wookie 0.10 (the screencast is a little > older). It wasn't important for us at that moment as we just wanted to > demonstrate the idea. Also we don't utilize OpenAjax-Event Bus of Wookie > yet, but use our own quick & dirty implementation. However, it is planned to > switch to Wookie's IWC implementation. > >> >> This solution wouldn't work outside a browser instance would it? That is I >> couldn't have a map widget on Foo's page respond to the changes on Bar's. >> >> Would it work across browser tabs? > > If the Wookie-Event Bus implementation would allow it - than yes, as widgets > do nothing else then sending messages to the public event bus.
In Rave using the OpenAjax implementation of IWC it wouldn't as the scope of that is the browser window - OpenAjax relays the messages from child iFrames to the container and then to its registered children. However, if the ROLE implementation is ported to Rave, then that uses XMPP and server-side relaying, so that ought to work. As long as the messaging implementation works using the same API (i.e. hub.publish(topic,message); hub.subscribe(topic, callback)) it should also be portable between implementations. > >> >> In general, speaking purely as a potential user rather than a currently > active >> Wookie developer, I would like to see this integrated into Wookie and am >> happy to help in any way I can. > > Thanks, every feedback and report on experience with the system would be > helpful! Its a really nice solution for interactive widget development; maybe rather than extending the core Wookie server perhaps it could be an add-on application for use by widget developers? So something like: - user opens the "IWC Enchancer" application - user selects a widget src folder - "IWC Enchancer" application publishes widget to local Wookie server - user interacts with widget; "IWC Enchancer" application prompts user to annotate iwc events - "IWC Enchancer" application save changes to widget src folder, and re-deploys updated widget to Wookie What do you think? > > Best Regards, > Olexiy > > >> >> On 29 June 2012 12:58, Olexiy Chudnovskyy >> <[email protected]> wrote: >>> Hi all, >>> >>> >>> >>> my name is Olexiy Chudnovskyy, i’m a PhD student of Chemnitz >>> University of Technology. Together with other universities and >>> industrial partners we use/contribute to Wookie in course of the >>> European Research Project OMELETTE. Currently, our research focuses on >>> inter-widget communication facilities, which were introduced also in >> Wookie since 0.10 release. >>> >>> >>> >>> I wanted to share with you an idea of enriching existing stand-alone >>> widgets with inter-widget communication functionality. The goal is to >>> make already deployed widgets “talking” to each other without manual >>> intervention into widget internals. We have published a paper on the >>> approach and built a first simple prototype to demonstrate how it’s >> working: >>> >>> >>> >>> <http://vsr.informatik.tu-chemnitz.de/demo/iwc-extension> >>> http://vsr.informatik.tu-chemnitz.de/demo/iwc-extension >>> >>> >>> >>> It would be interesting to find out, what do you think about the idea. >>> Do you find it useful? Is this way of extending widgets is >>> understandable for end users? >>> >>> >>> >>> I would be happy to get some feedback from you! >>> >>> >>> >>> Best Regards, >>> >>> Olexiy >>> >>> >>> >>> E-Mail: <mailto:[email protected]> >>> [email protected] >>> >>> Phone: +49 371 531 39146 >>> >>> Chemnitz University of Technology >>> >>> Department of Computer Science >>> >>> Distributed and Self-organizing Systems Group >>> >>> Straße der Nationen 62 >>> >>> D-09107 Chemnitz >>> >>> Germany >>> >>> >>> >> >> >> >> -- >> Ross Gardler (@rgardler) >> Programme Leader (Open Development) >> OpenDirective http://opendirective.com > >
