We're experimenting with streamlining the way in which page revisions are presented, so that rather than clicking a link, going to a table, looking at a list of non-descript revisions, clicking through each one and then going to edit mode and saving from there, we animate the presentation using frames and ajax to make it easier to see every version, and easier to revert or use another page as a starting point.
Here's an online model:
http://home.us.archive.org/~larthur/history00.html
Here's what's supposed to happen:
1. Click "History" from upper right on any page.
2. New History version loads in frameset. The current version of the page is on bottom, a toolbar/navigation is on top.
3. Click the green "back" arrow to see the previous revision.
A. The bottom frame loads the previous revision.
B. The grey "fwd" arrow turns green to indicate there's a future version of the page.
I. Click this button to move forward through revision history.
C. The revision count iterates to the current version (i.e. 4 of 5)
D. The comment refreshes to the comments for this revision, if any.
E. The "Edited by" statement is refreshed to the data for the current revision, including relevant timestamp/author
F. The "Scroll through previous versions" statement is replaced with a "Revert to this version?" prompt.
I. If the user elects to revert, clicking the prompt unveils a small form allowing a comment and a submit.
II. Submitting will replace the current revision of the page with the one in the bottom frame.
III. Post-submit, bring user back to the non-Historical view and insert "Your changes have been committed" (or words to that effect) in the Flash message at page-top.
IV. Remove Flash message after appropriate amount of time.
4. Clicking "Edit" on any page in the bottom frame allows the user to Edit that page using the usual method.
5. Clicking "Cancel" in the upper frame will take the user back to the current revision of the page without History toolbar/nav
Several pieces of data will need to communicate between frames and/or the upper frame will need to refresh its content based on the currently loaded page. Ideally, the upper toolbar/nav should stay static as its data is updated, but the page in the lower frame will be replaced by subsequent page revisions.
Lance - I'm assigning this to you until we have the UI locked in. If you need bits and pieces of code from Anand (or Becky?) please use this bug to transmit information and work requests.