Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 96076 invoked by uid 500); 25 Apr 2003 07:22:04 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 96060 invoked from network); 25 Apr 2003 07:22:04 -0000 Received: from vern.chem.tu-berlin.de (130.149.66.116) by daedalus.apache.org with SMTP; 25 Apr 2003 07:22:04 -0000 Received: from vern.chem.tu-berlin.de (localhost [127.0.0.1]) by vern.chem.tu-berlin.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h3P7MEGD006755 for ; Fri, 25 Apr 2003 09:22:14 +0200 Received: from localhost (stephan@localhost) by vern.chem.tu-berlin.de (8.12.3/8.12.3/Submit) with ESMTP id h3P7MEfB006752 for ; Fri, 25 Apr 2003 09:22:14 +0200 X-Authentication-Warning: vern.chem.tu-berlin.de: stephan owned process doing -bs Date: Fri, 25 Apr 2003 09:22:13 +0200 (CEST) From: Stephan Michels X-X-Sender: stephan@vern.chem.tu-berlin.de To: cocoon-dev@xml.apache.org Subject: Re: Declarative XMLForm In-Reply-To: <15da01c30af1$80c77fe0$a52efea9@kpiroumian> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 25 Apr 2003, Konstantin Piroumian wrote: > Hi! > > I've been proposing this same idea a long time ago, before XMLForm was > started and flow was implemented. And I even had a similar implementation of > the WizardAction, but I never had time to finish it and make really useful. Link? > After long discussion on Flow/XMLForms the common opinion was that Flow is > much better for controlling the application's state than an action/set of > actions (don't remember details, but you'll find those discussions in > archive if you search by 'XForms', 'Flow', etc.). After all I'm not a fan of the current 'Flow'. I'm always happy to see alternatives. > As compared to XMLForm's action, your version seems to me much more flexible > and it'd be fine if you could tidy it up and post as a patch to Bugzilla. > > Just one comment: if you have a lot of places where you should use your > action then you'll have a very overloaded sitemap, which is not good and not > very maintainable. I'd suggest that the configuration of views/transitions > were external, so you could do something like this in the pipeline: > > Yes, I had the same suggestion. Perhaps time for a Struts look-a-like ;-) Anyway, great stuff. Stephan. > > From: "DURDINA Michal" > > > Hello, > > I just finished first iteration of developing the new action > > XMLFormController. It implements another solution to XMLForm and it is > > intended to be alternative to AbstractXMLFormAction. > > XMLFormController is similar to AbstractXMLFormAction but it does not > > require to code the flow between pages in perform() method. > > > > [...] > > > > > Tell me please your opinion on such a functionality of this controller, I > > have many other ideas and going to implement them. We will build the web > > layer for our new project on this approach so it is sure that I will spend > > much more time on it. I would like to share it in the cocoon comunity so > > tell me if you are interested and what suggestions you have. > > > > Regards, > > Michal > > > > PS: Attached source containes 'untidy' version of XMLFormController :) > > > > -- MisoD -- > > Michal Durdina - durdina@asset.sk > > ASSET Soft a.s., > > Kosicka 56, Bratislava, 821 08 > > Slovakia, Europe > > > > > >