Guys, I think I've got a really simple and elegant solution to
the back button problem.
A while back I wrote my own UndoableEdit classes and posted
them here:
http://www.javadesktop.org/forums/thread.jspa?forumID=2&threadID=7669&me
ssageID=49420#49420
It occurs to me that when a user hits Back, he is really asking
for an undo operation and using the aforementioned undo framework, it
is *very* easy for web developers to configure undoable edits on every
step of the way.
What I propose is allowing webdevs to register UndoableEdits
that define how to step back one rendering step (to step back two
steps, you undo twice, etc). Our basic behavior would then be: if no
UndoableEdit is registered with the previous rendering, it must not be
undoable, hence hitting Back will result in a stale page.
Another huge benefit of this approach is that it is far easier
to implement than cloning pages and consumes far less resources.
What do you think?
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
