> Well, I'm not really planing to use Vaadin to create websites, but rather to > extend the AdminCentral (which is the intention of PageMVCHandler).
Its one of the main goals to build an extendable/customizable AdminCentral in 5.0. We also need that for our own modules. So far I can say that it will be super easy and powerful, especially compared to what we have today. The concept in very short: - admin central will work similar to todays data module (register node types in workspaces, register possible actions, define what subtypes a node can have, define the assigned dialog or editor) - trees, dialog, menu, ... are configured using content2bean or are contributed alternatively in the module class by using a builder API -> this will make most of the update tasks obsolete - WCM is an independent module similar to the DMS and registers page types and the page editor - exchange module registers the activation action (assigned to pages, actions are also accessible directly in the page editor) - workflow module overwrites the activation action and plugs in the inbox view (like today just nicer) - dialogs can be used for everything (not only jcr content manipulation) and custom dialog fields can be any Vaadin component its promising ... Philipp > > -will > > On 18.08.2010, at 14:52, Nils Breunese wrote: > >> >> Will Scheidegger wrote: >> >>> From what is posted on the lists and in the blogs, Vaadin play a big part >>> in Magnolia's future. I had a quick look at it and it does look quite >>> impressive. >>> >>> One question though: The tutorials always start with the assumption that we >>> have a Vaadin application. Before I start reading "The Book of Vaadin" from >>> cover to cover can anyone show me how to have a Vaadin page (i.e. a >>> PageMVCHandler which produces "Vaadin output")? Oh, and is life without >>> Eclipse in the Vaadin world a pain in the a...? >> >> Magnolia plans on using Vaadin for the new AdminCentral in Magnolia 5. I >> don't believe there are any plans to expose Vaadin to the process of >> creating websites. (Which doesn't say that it's impossible, it's just not >> the goal of the choice for a new UI framework.) >> >> Nils. >> >> De informatie vervat in deze e-mail en meegezonden bijlagen is uitsluitend >> bedoeld voor gebruik door de geadresseerde en kan vertrouwelijke informatie >> bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking >> van deze informatie aan derden is voorbehouden aan geadresseerde. De VPRO >> staat niet in voor de juiste en volledige overbrenging van de inhoud van een >> verzonden e-mail, noch voor tijdige ontvangst daarvan. >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- >> > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- Cheers - Philipp ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
