On Sat, May 17, 2008 at 5:28 AM, Kirk Israel <[EMAIL PROTECTED]> wrote: > On Sat, May 17, 2008 at 2:46 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: >> Many people expect that is the component is not visible also the >> models and the data ias not called or touched. Because there state >> cant be resolved correctly. > > Still seems a little odd to me. "We're adding a component, but we're > counting on it not to do anything. Because it's not visible. So it's > not really there. But we put it there anyway!"
It is a great facility, really. Consider a search field and a panel that displays results. If there is no search given, you want to hide this panel (which probably also has a border and other visual elements that are only relevant when a search is provided) altogether, and since the panel isn't rendered if implement the hiding by overriding isVisible, you don't have to litter the code of that panel with a dozen null checks, because you know it will only be executed when there is a search term. The same thing /could/ be achieved using component replacement, but for cases like this, that would be way less elegant and more work. Whether 'visible' is the best name... I always found this completely natural, but sure there may be terms to would make more sense to others. Too late for that now, since it's been in Wicket like this from the start :-). Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
