Bug 704779 - RFE: Diff view for topic revisions
Summary: RFE: Diff view for topic revisions
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.x
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: 1.1
Assignee: Matthew Casperson
QA Contact:
URL:
Whiteboard:
: 787546 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-14 21:02 UTC by Joshua Wulf
Modified: 2014-10-19 22:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-03 21:56:15 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Joshua Wulf 2011-05-14 21:02:21 UTC 
Figure out a way to highlight text in a topic based on an svn diff.

This is so that when we ask an SME to review changes to a topic, we can visually display what has been changed in the html output.

One possibility is to use a role attribute on elements whose contents have changed. The development brand css can then be modified to provide a visual cue based on the resultant html div class.
Comment 1 Matthew Casperson 2011-09-16 01:50:11 UTC 
Daisy Diff might provide a solution once the topics have a HTML view stored in the database: http://code.google.com/p/daisydiff/
Comment 2 Matthew Casperson 2011-09-16 01:57:14 UTC 
http://xmlunit.sourceforge.net/ could be used to see diffs at the xml level
Comment 3 Joshua Wulf 2012-02-06 09:07:47 UTC 
*** Bug 787546 has been marked as a duplicate of this bug. ***
Comment 4 Joshua Wulf 2012-02-06 09:08:18 UTC 
Choose two revisions of a topic and view a graphical diff of them, side-by-side
with colour highlighting.

By default it should diff the latest revision of the topic against a
user-selected earlier revision, but the user should also be able to diff two
earlier revisions against each other.
Comment 6 Matthew Casperson 2012-12-03 21:56:15 UTC 
This has been implemented in the new UI.
Note You need to log in before you can comment on or make changes to this bug.