> On 18.Jul.2001 -- 04:45 PM, Torsten Curdt wrote:
> > Looking at all the approaches for xml based form handling
> > (including my own ones) I'm not really happy what there
> > is available up to now...
>
> There has been a discussion on the user list recently... I would
> prefer to stick as close to XForms as possible.
This not even a proposal but RT... I'm always pro standard! :)
> > Especially multipage forms, error messages and i18n
> > is not addressed in an extensive or sufficient manner.
>
> Well, I would like to tackle forms in a vew days, but frankly,
> I would reckon multipage forms to be too complex for an initial
> release...
I don't think it will make much sense to try a simple form
first when we don't have an idea which direction to go!
I really think we should find a way for that first...
> [...]
>
> > And the direct one:
> >
> > <?xml version="1.0"?>
> > <pages>
> > <page name="name">
> > <textbox name="firstname">
> > <caption><i18n:translate>Firstname</i18n:translate></caption>
> > <validation nullable="yes"/>
> > </textbox>
> > <textbox name="lastname">
> > <caption><i18n:translate>Lastname</i18n:translate></caption>
> > </textbox>
> > <textbox name="email">
> > <caption><i18n:translate>Email</i18n:translate></caption>
> > <validation type="string"
>regexp="^[\d\w][\d\w\-_\.]*@([\d\w\-_]+\.)\w\w\w?$"/>
> > </textbox>
> > <textbox name="age">
> > <caption><i18n:translate>Age</i18n:translate></caption>
> > <validation type="long" min="4" max="99"/>
> > </textbox>
> > </page>
> > </pages>
>
> This is really not very far from XForms.
I know... ;) But I'd really like to have MVC
mapping of the business objects aka form objects.
[..]
> > Now a FormPopulatorAction could populate the values (if it is
> > an object based form). A FormValidationAction could check the
> > values and propose a page to show. A FormTransformer could
> > filter out everything but the correct page and expand the
> > form elements the full introspective.
>
> I would prefer a "XForms logicsheet" or a "XForms stylesheet" to
> anything else. After all, you will probably want to use it on XSP.
As far as I was teached ;) XSP should be not a lot more than presentation
logic! A XForms Logicsheet would probably put a lot more logic into
the XSP pages than necessary.
> Of course this does not rule out a FormTransformer but I'm not sure
> about a FormPopulator -- a transformer might work as well. But I feel
> that's not within the scope of such a package.
What package should do it then?
So how would you address some of the common problems?
1. making a form stateful (keeping the input of e.g. textboxes and comboboxes)
2. prevent a combobox be filled from the database on each request
3. have a media independent definition of forms
4. i18n of the form label/captions
5. i18n of the comboboxes (they probably need to load their options on change of the
locale)
6. the most important thing: multipage form navigation
I'd really like to get rid of the PHP style of form coding...
I'm with you to get this on!
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
