> 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")? We are going to replace all MVCHandlers (dialogs, tree, admin pages) by Vaadin. The AdminCentral is then the Vaadin application. The admin pages you are mentioning here will be Vaadin components (most likely panels, form layouts, ..).
To answer your question: you can embed/inject apps into a div in a HTML page (Vaadin's client side framework is based on GWT and hence works very similar). If you have a big application (and not just a mini app on a website) you will use their servlet which creates a minimal hosting page. see: http://vaadin.com/book/-/page/application.embedding.html > Oh, and is life without Eclipse in the Vaadin world a pain in the a...? Not at all. We have team members who work with IntelliJ and they have no complains so far. The visual UI builder plugin is a goody but less relevant in the Magnolia context. As a third party developer you will mainly write plain server side Java code. So it is not different to writing/debugging servlets. After the current sprint we plan to assemble a short video showing how the new AdminCentral will work. Cheers - Philipp ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
