Re: Events review part I: 4.2 Initialization events

Well, I don't see what you can do with these events.

*modelConstruct : form controls do not exist yet, the model might not exist
(see Note)
*modelInitialize : form controls do not exist yet, the model might not exist
(see Note of chapter 4.2.1)
*initializeDone : form controls do not exist yet, the model might not exist
(see Note of chapter 4.2.1)
*UIInitialize : form controls do not exist yet, the model might not exist
(see Note of chapter 4.2.1)
*formControlInitialize : some form controls exist (but according to my
understanding of DOM Events, you're notified too late, see another thread),
part of the model might not exist.

My 0.02$

Jérôme

----- Original Message -----
From: "Mikko Honkala" <Mikko.Honkala@hut.fi>
To: "Jérôme Nègre" <jerome.negre@e-xmlmedia.fr>; <www-forms@w3c.org>
Sent: Monday, February 04, 2002 4:46 PM
Subject: RE: Events review part I: 4.2 Initialization events


> Listening is orthagonal to <dispatch>ing the events. I think it is very
good that you can attach listeners to all these events, so
> that you know exactly when your handler is executed in the initialization
chain.
>
> -mikko
>
> > -----Original Message-----
> > From: www-forms-editor-request@w3.org
> > [mailto:www-forms-editor-request@w3.org]On Behalf Of Jérôme Nègre
> > Sent: 4. helmikuuta 2002 12:04
> > To: Mikko Honkala; www-forms-editor@w3c.org
> > Subject: Re: Events review part I: 4.2 Initialization events
> >
> >
> > > 4.2 Initialization Events
> > > MH: Substantive: Do we want the user to be able to <dispatch> the
> > following events:
> > > ·         ModelConstruct
> > > ·         ModelInitialize
> > > ·         InitializeDone
> > > ·         FormControlInitialize
> > > ·         InitializeDone
> > >  should we prevent that somehow?
> >
> > Also, should event-handlers be able to listen to these events, since
form
> > controls are not yet initialized ?
> >
> > Jérôme
> >
>
>

Received on Monday, 4 February 2002 11:21:40 UTC