An easy trick to avoid this is to use a Panel/Fragment instantiating just a WebMarkupContainer when you don't want to display/create the full component.
That's all Paolo On Jan 2, 2008 7:06 PM, Timo Rantalaiho <[EMAIL PROTECTED]> wrote: > On Tue, 18 Dec 2007, wfaler wrote: > > Hmm, haven't tried that. That might work - sometimes you just don't > check all > > the methods thoroughly enough.. :) > > Yep, as far as I know the Wicket Way (TM) of making > components optional is controlling their visibility. This > need becomes more obvious when you consider that (except > repeaters) there is a 1:1 correspondence between HTML > elements with wicket:id and Wicket components, and it > wouldn't be nice to need to change the HTML files runtime :) > > One consequence is that all components of the page always > get constructed even if they are not visible, so on one hand > you don't want to do heavy work in the constructor of such > component but on other hand you get more fail-fast with > regard to component creation. > > Best wishes, > Timo > > -- > Timo Rantalaiho > Reaktor Innovations Oy <URL: http://www.ri.fi/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
