Sylvain Wallez wrote:
Sylvain Wallez wrote:
Sorry to rain on the party, but the new widget state stuff in CForms
should make building multi-page forms a piece of cake.
Off writing an example
Done, I wrote my first wizard with CForms :-)
Please update branch 2.1.x and point your browser to
h
Reinhard Poetz wrote:
Sylvain Wallez wrote:
Sylvain Wallez wrote:
Sorry to rain on the party, but the new widget state stuff in CForms
should make building multi-page forms a piece of cake.
Off writing an example
Done, I wrote my first wizard with CForms :-)
Please update branch 2.1.x and po
Sylvain Wallez wrote:
That could be something like:
function validateWizard() {
currentPage.setState(WidgetState.INVISIBLE); // another one may be
chosen below
for (page in pageList) {
page.setState(WidgetState.ACTIVE);
if (page.validate()) {
page.setState(WidgetState.INVISIBLE);
}
--- Sylvain Wallez <[EMAIL PROTECTED]> schrieb:
> Reinhard Poetz wrote:
>
> > Sylvain Wallez wrote:
> >
> >> Sylvain Wallez wrote:
> >>
> >>> Sorry to rain on the party, but the new widget
> state stuff in CForms
> >>> should make building multi-page forms a piece of
> cake.
> >>>
> >>> Off wri
so that one can do the kind
of things you asked for in the section about multi page forms in
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106672364131946&w=2.
So now it is possible to write CForms wizards by writing javascript FSMs
in the form definition using widget states. Or if y
ced work of Jonas Ekstedt so that one can do the
kind of things you asked for in the section about multi page forms in
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106672364131946&w=2.
So now it is possible to write CForms wizards by writing javascript
FSMs in the form definition usin
-cocoon-dev&m=106672364131946&w=2.
So now it is possible to write CForms wizards by writing javascript
FSMs in the form definition using widget states. Or if you prefer, by
using flowscript back-button magic, and automatic selection of what is
validated based on what widgets you use in your
://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106672364131946&w=2.
So now it is possible to write CForms wizards by writing javascript
FSMs in the form definition using widget states. Or if you prefer,
by using flowscript back-button magic, and automatic selection of
what is validated based
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
Sure, IMO, you should always do a complete validation of _all_
widgets before binding your form model to business data. There is the
same problem with widget states, you can have faulty event logic so
