[wp-trac] [WordPress Trac] #23497: Revisions Rewrite using JS/Backbone
WordPress Trac
noreply at wordpress.org
Mon Mar 11 15:02:13 UTC 2013
#23497: Revisions Rewrite using JS/Backbone
---------------------------------------+------------------------
Reporter: adamsilverstein | Owner: westi
Type: enhancement | Status: reviewing
Priority: normal | Milestone: 3.6
Component: Revisions | Version: 3.5.1
Severity: normal | Resolution:
Keywords: needs-patch needs-testing |
---------------------------------------+------------------------
Comment (by adamsilverstein):
changes
* set initial view to display passed revision id. now when you click to
view a revision in the list, that revision displays
* set maximum step width; now when there few revisions slider bar is
smaller size;
* remove cancel button, exctraneous
* new backbone view for tickmarks, ticks inside slider bar
* tickmarks indicate revision load state while loading (currently spinner
background on 1 line, but open to suggestions)
* tickmark width & color based on scope of changes, initial pass, five
weights (noted issue with wider ticks appearing left of centered)
* move compare two checkbox to upper right
* removed 'comparing x of y' language above slider
* reversed direction of revision view - oldest on left, newest on right
* html cleanup in revision.php
* move restore button next to compare from meta, change language to
'Resore this Revision'
* retain compare position when switching modes (bug fix)
* changed slider dragger to blue triangle from mock up; used base64
encoded image, think thats best but request suggestions
* turn viewing autosaves on by default
* started work on tooltips but didn't get that far, need help! trying to
have tooltips that work like these:
http://www.filamentgroup.com/examples/slider_v2/index3.php - slider is low
to accomidate tooltips; maybe add revision change lines added/deleted
info;not convinced we need them, clunky, same info as below
* misc bug fixes
* add check for latest revision matches post data (new methodology in
#16215)
* currently counting lines changed, is this useful or should it be words
changed
* currently hard coded thresholds determine scope_of_changes calculation,
should be scaled to range of values in all revisions
* up next, change compare method to compare to previous
--
Ticket URL: <http://core.trac.wordpress.org/ticket/23497#comment:73>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list