Well, to tell the truth I was thinking about sharing this module, as there might be some value in it. It basically is a small application that knows about runnable configurations. A runnable configuration consists of a script in the scripts workspace and a 'GuiScript component' which basically is an interface that abstracts the process of creating a form, validating it, and extracting a bean from it.
Those runnable configurations are created in the datamodule where i introduced Task en Taskgroup Data types. When you open the vaadin application you see all the tasks, grouped by taskgroup, and you can run them. There is a logging console as well. I'm actually quite willing to at least show the code, I guiss it would be a good idea if I create a small sample first. It's not all finished, but more like a work in progess, but we use it already. regards, -- Ernst Bunders Ontwikkelaar VPRO s 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><config.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]> > ---------------------------------------------------------------- > > -- 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]> ----------------------------------------------------------------
