Not more confusing, just confusing. i can already see the mails arriving on the mailing list. Documenting a behavior will only go so far, as the current problem so elegantly shows ;)
Don't get me wrong i am all in favor of finding a good solution for this, but imho so far i have not yet heard a solution that provides a significantly better approach. Maurice On Sat, Apr 26, 2008 at 11:02 PM, John Patterson <[EMAIL PROTECTED]> wrote: > > > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
