Hi Grégory, thank you for your feedback! Yes, we thought about migrating to 1.2. Right now we are in the estimation state of that task. As a first step i just changed my pom to the actual mgnl versions and saw many red crosses appearing in eclipse. Also some base classes changed, moved or vanished. That is the reason for my question. As for the different approaches: as far as i have investigated our two approaches to multi step i can say that the idea is quite similar: unique form state token, redirecting with token to next step, gathering submitted parameters etc. Yours has some more features though: iterating content for finding next step, executing form models before rendering. But most important: your architecture is better in terms of separation of concerns. 8-] As far as i see it now, it would not make much sense to contribute what we have done in the validation area. Because there again: it is not modular enough. But the plan is this: depending on which way we go (sticking to the old version or refactoring and adapting the new one), i will get back to you with potential ideas.
Thank you so far, Greetings, Anton 2011/3/21 Grégory Joseph <[email protected]>: > > > On 21 Mar 2011, at 16:33, Anton Matheis wrote: > >> >> Hello Magnolians, >> >> we have a Magnolia 4.3.8 project in which we needed multi step forms. >> Because at that time, 4.4 wasn't released, we built our own extensions >> to 4.3.8 to handle multi step. Apart from that, we have some >> non-trivial validation tasks that could not be dealt with by using the >> magnolia intern validation architecture. >> >> We now consider upgrading to 4.4. The problem is: the magnolia form >> module changed considerably and thus the architecture on which we >> built our module. >> Rewriting our form module would be quite time intense. To avoid that, >> we thought about integrating the actual Stk version (1.4.2) with the >> old form module version 1.1.2. >> >> Do you think that might be possible? > > The only possible way to know would be for you to try it. It all depends on > which features you use. For example, I know for a fact that the login/logout > templates, which have been changed with stk 1.4.x, will break with form > module 1.1. Others might still work. > > Have you considered using form 1.2 for multi-step ? Are your extensions that > different from what we've done ? If so - can you provide some details ? It > might be interesting to see how such things could be migrated. > > As for the validation - if anything, it should be simpler/more flexible now. > And if not, we'd love to improve this too. Can you provide some examples of > where it would be difficult for you to upgrade to 1.2 ? > > That's why open-source is great: I'm sure your extensions/improvements would > be extremely useful to others too, and could have been integrated in the > product by now. You should consider contributing them ;) > > > Cheers, > > -g > > > > ---------------------------------------------------------------- > 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]> ----------------------------------------------------------------
