Bugs item #1152642, was opened at 2005-02-27 00:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1152642&group_id=119783
Category: core Group: 1.0 Status: Open Resolution: None Priority: 5 Submitted By: Eelco Hillenius (eelco12) Assigned to: Nobody/Anonymous (nobody) Summary: remove Component.replace again Initial Comment: We need to get rid of Component.replace, as it encourages an anti-pattern. Though the replace method is convenient at times, it is also the reason why we can't support good back button behaviour right now. However, as some of the webapplications that are build with Wicket right now depend on this method heavily, we should not remove this method before we have a good alternative way of doing tabs, both tabs that work with Pages, and tabs that work with Panels. The latter would basically work the same as the current implementation of Maurice (and Johan?), but instead of replacing a panel, it could just use the 'visible' property of Component. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1152642&group_id=119783 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
