Yes and that is the problem
I don't care about model changes at the moment, Models can change everywhere, anytime,anyplace.
The thing that is the big problem is that the componentstrucure is not the same anymore with the view on screen (because of a back button)
this happens in 2 places:
1> replace (tabpanels) 2> removeAll (listview)
That is the problem we are trying to fix. So please keep it purely focused on that.
So Undoable support for components (at this time not models if i have to say it, and absoluutly not data in the models)
For example:
i have a tabpanel where tab1 is selected.
then in the code i say: replace tab1 with tab2
then i make a Undoable Object. Where i hold a reference to tab1 (the replaced one)
then when we suddenly see in the page that we are in redering X (before when the replace happend)
We will call undo() on the undoable object
This will call replace again with but then replaces tab2 with tab1. So the old situation is back in the saddle again....
The model that tab1 also had is still there. And i think a developer should be resposeable how this one is handled...
johan
Eelco Hillenius wrote:
What misses is what actually causes the problems in the first place: the reachability of components. We want components to be reachable even though they were replaced or removed from the current rendering of the page, but that were there on a previous rendering. We don't allways want that. But we want to be able to.
Eelco
Martijn Dashorst wrote:
Reading Jonathans posts, I am getting convinced that the undo mechanism is _NOT_ the way to go. It does not solve the real problem. I think we *really* need to get back to what exactly is the problem, before we discuss solutions. Otherwise we will keep having the 'I say/you say' discussions for the next several months.
My throw at the problem at hand:
- we have models and components
- the components are generated using the data from the models
- after the components are rendered, the model changes in such a way that the components will not be representing the actual model anymore when the user returns to the page without resubmitting the data (i.e. press the back button)
- currently Wicket shows a 'stale data' error message when the data is submitted again.
- the 'stale data' error message is something we don't want.
Anything I left out? Any discrepancies?
Martijn
------------------------------------------------------- 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
------------------------------------------------------- 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
