On Thu, Sep 09, 2004 at 05:50:08PM +0200, Sylvain Wallez wrote: > Tim Larson wrote: > >On Thu, Sep 09, 2004 at 03:46:52PM +0200, Sylvain Wallez wrote: > Exactly. In flat forms, custom initializations can be done in the > flowscript between "new Form()" and "form.showForm()", but I the case of > dynamically created widgets, this cannot be done that way. > > I have some complex use cases where the case field of an union, itself > in a class, has a selection-list that is defined by analyzing the values > defined somewhere else in the form. > > Still following me? If not, you need to attend my presentation at the GT ;-)
Following you fine. Wish I could come, but we are going to have a baby any day now, so I will be pretty busy at home this time. > So the idea is that in "on-create", the widget gathers in the form the > necessary data to build and set its own selection list. > > Even for flat forms, this create-event can allow custom initialization > code that currently is written in the flowscript back in the definition, > thus making the form definition self-contained in a single file. Turns out I am also going to need your on-create support so this works out quite nicely :) > +1. I'll add the "on-create" stuff on top of this. Committed. --Tim Larson
