>this is true only for page#oninitialize() which is called at the time
>the first add(component) is called. it remains like this for backwards
>compatbility with the first introduction of #oninitialize().
Ahuh!
> In 1.5 this has been changed so that oninitialize() is called after
> the page is c
this is true only for page#oninitialize() which is called at the time
the first add(component) is called. it remains like this for backwards
compatbility with the first introduction of #oninitialize(). in 1.5
this has been changed so that oninitialize() is called after the page
is constructed.
-ig
I just realized that onInitialize() isn't the 'initialize' of
traditional frameworks that I thought it was: The style of
initialization that occurs in the lifecycle after instance construction
has completed and the call to the constructors has returned.
onInitialize appears to be called while sti
