Sounds to me you are looking for something more special purpose :) Why don't you create a panel factory or something similar? You could make container components that would allow you to do a if/else like construction in your markup, but I wouldn't be a big fan of that. I think working with panels for conditional/ flexible markup is a great way to go. And as Wicket lets you manage your own components, you can implement any strategy you want to this.
Eelco On 11/15/05, Nick Heudecker <[EMAIL PROTECTED]> wrote: > Those are the two approaches I've used. I'm looking for a way to either > abstract one or both of those approaches to make them more general purpose. > > > On 11/15/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > there are two basic approaches: > > 1) add the component anyways and set its visibility tag accordingly > > 2) create panels that either contain or do not contain the component and > add the appropriate panel > > > > If either is unclear let me know and i can go further into detail. > > > > -Igor > > > > > > > > > > On 11/15/05, Nick Heudecker <[EMAIL PROTECTED] > wrote: > > > Hi, > > > > > > My app has multiple instances where, if a ListView is empty, I want to > display some message to the user, like "You haven't defined any widgets > yet." The problem is this requires what I feel to be a lot of code in the > Page implementation. Is there a pattern or component that I'm missing that > would make this easier? > > > > > > Thanks. > > > > > > > > > ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
