Re: Alternative method to initialise page

[John Patterson]

Mr Mean wrote:
> 
> But as Johan has already pointed out. onBeforeFirstRender (or whatever
> it is called) might not be called at all if the component is not
> (allowed to be) rendered. This is probably going to confuse people
> just as much as the current situation.
> And if we have an initialize method which should be called always
> after all sub component constructors have been called, then when do we
> trigger it and how will people abuse this?
> Such an initialize method can easily be done by users them self with a
> simple factory pattern. So why bloat our api with it?
> 

What is confusing about the component not being rendered if it is not
visible?  That is already the case with onBeforeRender().  How is this any
more confusing?
-- 
View this message in context: 
http://www.nabble.com/Alternative-method-to-initialise-page-tp16742636p16917466.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]