You should use isVisible when possible. The notion of component's visibility has to do with whether the component renderers or not. So yes, the list will be reconstructed from scratch. If you're doing something Ajaxy, this might not be what you want.
I personally wish that the Ajax implementation was a bit more automatic by default. Adding a behavior for Ajax to a component could easily set the right flags since this is the most common case. People who are doing custom ID management could turn off the automatic default. I usually look for places to handle this kind of thing centrally, whether it's some component base class or a base behavior class or a custom behavior. Once you've defined a component that's good for your application, you just repeat use of it. Kirk Israel-2 wrote: > > If I have a component with a nested ListView, and I make the parent > component go away for a bit with setVisible, the List will be > reconstructed from scratch? > > Is the understanding that for Wicket "Invisible" means "the component > objects (Labels, etc) have Gone Away"? > > What are the advantages of that? I know it means there's a lot of > boilerplate that has to be done for the opposite, > when something starts out as Visible false, the old > .setOutputMarkupId(true); and .setOutputMarkupPlaceholderTag(true); > I think it's part of the philosophy of Wicket I don't get yet... > > If you wanted to just a cosmetic, DHTM/CSS "display: none" type of > visibility, is there something you can do other than > making a new AttributeModifier (with a custom Visibility Model kind of > thing) or a SimplleAttributeModifier with a CSS > "display:none" String there? > > Thanks! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Wicket-Visibility-vs.-CSS-visibility-tp17285530p17286015.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]
