On 4/7/11 1:34 PM, "Scott Wilson" <[email protected]> wrote:
>Hi everyone, > >I'm working on a project at the moment which concerns creating >"workspaces" containing mashups of multiple widgets and inter-widget >messaging that can be embedded in other applications (such as portals, >CMS, intranets etc) and also exported and shared. I've been wondering how >this could fit with Rave as in many ways its quite similar - and it would >be far better for us and our consortium partners to contribute to Rave >rather than to create another project. > >I'm currently thinking we could do this in two ways: > >1. Have "Rave Region providers" as well as "Rave Widget providers". > >So in this approach, a similar mechanism the one allowing Shindig to >provide OpenSocial gadgets for Rave Widgets also applies to a Rave Region >- so an external provider can hook in a complete Region which can itself >contain widgets. > >2. Have Rave act as a Plug-in for other platforms > >The alternative is to enable Rave to be plugged in to other applications, >to provide a Region or a Page that can be rendered for and embedded in >other platforms like Drupal, Jetspeed, LifeRay etc. So in this scenario >Rave is behaving like a kind of standalone mashup layout engine. I think >this would be really nice, the most complicated part being how you'd wire >up the SPI. I think this is the more supportable path of the two, though it would take some careful design. First and foremost, I think Rave's OOTB implementation should be a fully-featured, reference, social portal; however, we are already planning on creating a flexible, easy to define UI. One of the UI's could be a simple, iframe-includable engine that renders widgets, provides implementations of required container APIs for given widget renderers, etc. Obviously, it needs to be thought out more as we build the UI layer, but that was already in the cards. Everyone wanting something along the lines of SocialSite was how we got to this point in the first place :) > >Finally, we could always have it both ways which provides for the >intriguing possibility of publishing regions from one Rave instance >through another! > >S
