on 1152642, i think we should just remove replace() for RC1. it's a horrible antipattern that might cripple us in the future.
I think we need it somehow to support tabs.
Because setVisible also doesn't work because what does happen then if you press back? Then still the page is not in the same state
as it was when it was there the first time.
What the best way for tabs is (and how i do it now) is to clone the complete page. Then replace the tab with the wanted tab.
I really would like to have an interface in wicket that supports this like:
CloneablePage
And implemenations of that do a deep clone of all the components it has. And then uses the new tabpanel object i wanted to use (so i replace)
This i now do myself, but maybe wicket can give me a bit more?
This way the back button always works. You just have a new page for the tab. But the external things around the tab
are cloned.
johan
------------------------------------------------------- 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
