On 7/12/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > Well, it's a matter of making choices really. For Wicket it is a design > decission to make everything a component, and nest those components > hierarchical.
How about dynamic changing of component structure in runtime or at least swapping components? Say, I have a large page, which in most times will be the only page. Think a portal. I have a small login component in it. No problem, I can define it in Page class. But now I want to remove this login component after user logs in, and to replace it with say, current promotions for registered users. Can I do that? Or you recommend to consider my scenario as having two pages? I would prefer to have one URL in the address bar ;) Michael. ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
