not sure where the extension point is. i just posted that IModel might be interesting...
models themselves could be either values or references.
Gili wrote:
I think you better clarify what you mean by "... provides some extension point where the user can specialize how the model of a given component is either referenced or cloned". You're saying components would know how to undo themselves but when a user subclasses a component (customizing it) he gets to override this behavior, chaining to the superclass using "super.undo()" and then adding his own behavior for dealing with the DB and other issues?
Gili
On Wed, 02 Mar 2005 14:34:50 -0800, Jonathan Locke wrote:
i don't think the user codes up any change records manually. the framework undoes the components and then provides some extension point where the user can specialize how the model of a given component is either referenced or cloned. it's essentially like cloning, but with more efficiency, less state and more flexibility over references to models. i love it so far!
and btw, in a multi-user environment, there will be cases where you could not revert the db change because someone else changed it in the meantime.
Gili wrote:
If that is the behavior you want (personally I consider it to be "incorrect") then you can still implement it. Simply code up an UndoableEdit that does not revert the DB change. You control the UndoableEdit, you can do whatever you want in it.
Gili
On Wed, 02 Mar 2005 14:06:03 -0800, Jonathan Locke wrote:
yes. you remove an item from a table, deleting it from the database. hitting back and editing the item should not /necessarily/ resurrect the item.
undo is really good for getting the page back into the state it was in when the rendering happened (in terms of components).
the trick is to deal with the model as well. i think this needs some pondering.
Gili wrote:
On Wed, 02 Mar 2005 22:43:27 +0100, Martijn Dashorst wrote:
I really hope we can come up with something good. Though Gili posted an interesting view on the subject, I don't think that the 'undo operation' is the correct view. When I hit the back button it is not *always* because I want to revert changes, but because I want to choose something else.
You're saying that if a user commits something to the database, then hits back, enter different data and "submit" again it should add the new data but not undo the original commit? I understand some websites let you do that, but I would argue that the behavior I suggested is the correct and intuitive one. Back means undo to me in all cases I can think of.
Can you come up with a clearer use-case where it does not?
Thanks, Gili
------------------------------------------------------- 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
------------------------------------------------------- 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
------------------------------------------------------- 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
