He Will, true - we were talking about exactly that case at the conference. I apologize for not having taken the time to do a practical exercise in the meantime. The whole core development team is/was busy with the 4.4 release right now so we were not "vaading" the last few weeks. We'll get back to Magnolia 5 in a few days. Any contribution (code, documentation, ...) for such an integration would be very welcome.
Cheers -Dan Daniel Lipp Magnolia International Ltd. Phone +41 61 228 9000 Fax +41 61 228 9001 http://www.magnolia-cms.com ---------------------------------------------------------- You should join us on Facebook: http://facebook.com/Magnolia Begin forwarded message: > From: Will Scheidegger <[email protected]> > Date: November 12, 2010 3:06:34 PM GMT+01:00 > To: Magnolia User-List <[email protected]> > Subject: Re: AW: [magnolia-user] Vaadin support question > Reply-To: "Magnolia User-List" <[email protected]> > > > Oh! I even asked the Vaading speaker at the Magnolia conference about how to > do this. How about writing a wiki tutorial once you've got the stuff sorted > out? That would be just awesome... > > -will > > On 12.11.2010, at 13:31, Unger, Richard wrote: > >> >> Hi Gregory! >> >> Sure - use case is boring though: >> >> It's simply a GUI for the "admins" to create magnolia users by picking the >> employee's record from the organisation's LDAP servers. It's to do with the >> complicated SSO setup used in Austrian government. >> >> The Vaadin idea comes from the desire not to have to rewrite the GUI for >> magnolia 5, and also because creating GUIs is easier in Vaadin than working >> with the old adminCentral's building blocks. >> >> I'd be happy to send a screenshot once it's integrated in magnolia, if >> you're interested, but it's nothing really CMS related, just "integration >> functionality". >> >> Regards from Vienna, >> >> Richard >> >> PS: I'm aware of the LDAP module, but it doesn't suit our scenario to read >> the users directly from LDAP - for us, importing them into magnolia is the >> right way to go. >> >> >> >> >> >> -----Ursprüngliche Nachricht----- >> Von: [email protected] >> [mailto:[email protected]] Im Auftrag von Grégory Joseph >> Gesendet: Freitag, 12. November 2010 12:54 >> An: Magnolia User-List >> Betreff: Re: [magnolia-user] Vaadin support question >> >> >> You guys never cease to amaze me ! >> Any chance we could hear more details about this use case ? :=) >> >> >> On Nov 12, 2010, at 9:47, Ernst Bunders wrote: >> >>> Hello Richard >>> >>> I did something similar. I wanted a way to connect forms to a groovy >>> scripts, so I could create generic tasks that can be configured by >>> users at runtime. What I did: >>> >>> 1 Create a vaadin app. This is pretty much a standalone thing. >>> 2 Add the vaadin jar and the vaadin servlet at Configuration > server >>>> filters > servlets (see attachment) >>> 3 create a link in the adminInterface module > config > menu > tools >>> menu to the app (in an iframe to the right) (see attachment) >>> >>> hopes this helps >>> >>> regards, >>> >>> -- >>> Ernst Bunders >>> Ontwikkelaar VPRO >>> >>> modules/extensions for Magnolia - >>>> nothing really CMS related, more things to interface with our >>>> customer's existing IT. >>>> >>>> >>>> >>>> To avoid having to rewrite everything in a few months for magnolia 5, >>>> we would like to implement the GUIs in Vaadin from the start. >>>> >>>> >>>> >>>> The question is: how? >>>> >>>> >>>> >>>> I've looked at Vaadin, done some tutorials, and have my GUI working >>>> outside of Magnolia. >>>> >>>> I've looked at the new magnolia-module-admincentral-vaadin. >>>> >>>> >>>> >>>> So I have 2 Questions: >>>> >>>> >>>> >>>> 1) What's the right way to integrate new Vaadin-based GUI components? >>>> >>>> >>>> >>>> What I'm doing would have been implemented as a "page" in the old >>>> adminCentral. Am I correct in assuming that I would extend >>>> info.magnolia.module.admincentral.components.MagnoliaBaseComponent >>>> to create my gui-component, and then simply configure a menu-item >>>> with view=myviewclassname to provide access to my view from adminCentral's >>>> menu? >>>> >>>> Do I need to do any special magnolia-related init() or cleanup work >>>> in the Vaadin component? >>>> >>>> >>>> >>>> 2) I don't want to run the experimental Vaadin-AdminCentral in >>>> production yet. Can I use Vaadin from within the old adminCentral? >>>> >>>> >>>> >>>> My problem is that I don't want to run Vaadin-Admincentral in >>>> production at the moment, it's not ready. I'd still like to offer my >>>> vaadin-based GUI. >>>> >>>> >>>> >>>> I see the MagnoliaBaseComponent class depends upon prior >>>> initialization of the AdminCentralVaadinApplication class, and uses >>>> the application's layout ("mainComponent"). >>>> >>>> >>>> >>>> I think one approach might be to directly extend CustomComponent for >>>> the moment, and use my own Vaadin Application class for the moment. >>>> By initializing it similarily to AdminCentralVaadinApplication I >>>> should be able to use the existing magnolia-vaadin-theme. >>>> >>>> Changing the class to extend MagnoliaBaseComponent should then be >>>> fairly easy when Magnolia 5.0 comes. >>>> >>>> >>>> >>>> Now one question remains: how add the Vaadin Servlet to the old >>>> adminCentral - would it be sufficient to create a new servlet mapping >>>> under >>>> config->filters->servlets, say mapped to the URI >>>> "/.magnolia/vaadinpreview/*" ? >>>> >>>> >>>> >>>> Thanks for your thoughts and feedback! >>>> >>>> >>>> >>>> Regards from Vienna, >>>> >>>> Richard >>>> >>>> >>>> >>>> >>>> >>>> ________________________________ >>>> ---------------------------------------------------------------- >>>> For list details see >>>> http://www.magnolia-cms.com/home/community/mailing-lists.html >>>> To unsubscribe, E-mail to: <[email protected]> >>>> ---------------------------------------------------------------- >>>> >>> >>> >>> >>> -- >>> Ernst Bunders >>> Ontwikkelaar VPRO >>> >>> >>> ---------------------------------------------------------------- >>> For list details see >>> http://www.magnolia-cms.com/home/community/mailing-lists.html >>> To unsubscribe, E-mail to: <[email protected]> >>> ---------------------------------------------------------------- >>> <config.modules.adminInterface.config.menu.tools.gui-script.xml><confi >>> g.server.filters.servlets.Vaadin-gui-script.xml> >> >> >> >> ---------------------------------------------------------------- >> 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]> >> ---------------------------------------------------------------- >> > > > > ---------------------------------------------------------------- > 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]> ----------------------------------------------------------------
