>-----Original Message----- >From: Andreas Deller [mailto:[email protected]] >Sent: Wednesday, February 22, 2012 10:24 AM >To: [email protected] >Subject: Re: Basics/documentation > >Hi Matthew > >Thanks for your fast reply! Please find my new input below. > > >On 02/22/2012 03:45 PM, Franklin, Matthew B. wrote: >>> -----Original Message----- >>> From: Andreas Deller [mailto:[email protected]] >>> Sent: Wednesday, February 22, 2012 6:42 AM >>> To: [email protected] >>> Cc: Andreas Deller >>> Subject: Basics/documentation >>> >>> Hi everybody >> >> Hi Andreas >> >>> >>> Sorry for the rookie question, but I've been trying in vain to get >>> documentation about: >>> - Rave architecture >> >> Good point. We haven't really documented the general architecture well. >While it is a little in flux, I think it is stable enough to support a >high-level >description. (I will create a ticket for this) >Thanks, this would be a huge help for newcomers. > >> >> Was there something specific you were looking for? >Yes: >- Web servers (Rave server, 3rd party server, google server hosting more > javascript, etc.) >- Maybe a port matrix what connections must be possible >- Module description (rave-components, rave-portal, rave-shindig, more?) >- Lifecycle description >- What is rendered where >- Security features (like Caja in Shindig) >- 'Extension points' where to add own widgets >- The role of Spring in the setup >The way I read the available documentation, Rave is a project >using/integrating >Shindig and Wookie. The relation between them would interest me.
Thanks. I created a ticket for this. > >> >>> - differences/improvements of rave-shindig vs. shindig >> >> The goal of Rave-shindig is to provide default SPI implementations and >abstractions of those SPIs that tie neatly back to core Rave functionality. >This >will allow implementers to more easily integrate custom implementations for >retrieval and storage of common data. >> >> That being said, we aren't there yet. >So extensions made in Shindig should be available in Rave, too? More the other way around. We have a Rave core set of functionality (repositories, etc) that will be used in Rave's Shindig. This way, you as an implementer could provide your own custom implementation and just include it in both places rather than having to write a custom Rave implementation and a custom Shindig implementation. > >> >>> - how to develop custom widgets >> >> Rave supports two widget specifications at the moment: OpenSocial [1] via >Shindig and W3C [2] via Wookie. Developing a widget that conforms to either >should be all you need to get it integrated in Rave. >> >> [1] : http://docs.opensocial.org/display/OSD/Building+OpenSocial+Apps >> [2] : http://www.w3.org/TR/widgets/ >[1] is a great link. >Since our application will not have much to do with OpenSocial contents, >developing custom widgets (news ticker, stock exchange rates incl. a >workflow >within the widgets etc.) is one of the core features the framework must allow. >If I understand you right, Rave doesn't limit these possibilities? Not at all. You could develop your own custom renderer to support your own widget type. For the record, each of those use cases you mentioned could be developed in either W3C or OpenSocial. OpenSocial has at its core a set of APIs and Gadget definition that lets you build any type of app. The social aspect is just an additional dimension. >> >>> - how to integrate custom widgets into a separate web app (that's what >>> we're ultimately interested in) >> >> We have a goal of embedding sets of Rave widgets in other apps, but don't >have anything substantial quite yet. If you have specific desires for how this >would work, we would love to hear them (or better yet, have you help work >on them) >We have an existing application, part of which should be extended >by widgets so the enabled pages look more 'fresh', more dynamic and >more user-centered. With Shindig, this seems to be possible, but with >much manual work. We wondered if Rave would make this easier (e.g. with >handling user preferences what/where widgets are located, DnD support >out of the box, add/remove possibility like in the portal demo, etc.). We absolutely intend on supporting this use case. There are others in this community that have even wider goals along the same lines and I'll let them tell you about them. >'Own' as well as 3rd party widgets should be integratable, and all placed >behind a reverse proxy (this raises problems with links created with >javascript, but is a must-have). >We're still not sure if the approach using Shindig or Rave is suitable for >this, so this is why I looked for documentation :-) > >> >>> >>> http://incubator.apache.org/rave/documentation/index.html didn't help >me, >>> neither did any other link on the Rave homepage nor Google, nor the >mailing >>> list. >>> >>> Thanks in advance >>> Andy Deller >>> >>> -- >>> [email protected] Tel +41 44 268 89 61 Fax +41 44 261 27 50 >>> Ergon Informatik AG, Kleinstrasse 15, CH-8008 Zürich >>> http://www.ergon.ch >>> >___________________________________________________________ >>> ___ >>> e r g o n smart people - smart software >>
