On Thu, Sep 17, 2009 at 2:19 PM, Chris Colman <[email protected]>wrote:
> > > If they don't, what would be the best way to have the border go > > > invisible if the child is invisible? > > > > > > > How about using <wicket:enclosure child="wrappedPanel"> around the > border. > > > > refer > > http://cwiki.apache.org/WICKET/wickets-xhtml- > > tags.html#Wicket%27sXHTMLtags-Elementwicket:enclosure > > AWESOME! > > Everytime I need to do something special in wicket that I think will > need some home grown component I discover that there's already some > awesome wicket 'built in' component that's already made for the purpose! > > Yeah I know the feeling :) Just one thing, you can also search for previous discussions on this (I tried, nabble seems to be down) If the isVisible() logic on your wrappedPanel is "expensive" for e.g. querying the database or something, be warned, Wicket calls isVisible() on the tree of components under an enclosure a little more than you would expect, you can put in a logger statement to check. Of course, in most cases you won't have any issues. > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
