[daisy] [GSoc] daisydiff progress update 3

[André Ulrich]

Guy Van den Broeck schrieb:
>> As an example, think of long document where only the href of a link
>> changed, it can take quite some time to find where the curly-blue
>> underlined link is.
>>     
>
> Press "right arrow" or click "first"
>   

Yes, that´s what I mentioned in my mail by "there is already a 
navigation element to get from one change to another".
>     
>   
>> Another solution would be different modes for diffs. When you look at 
>> TWiki.org for example, they provide different modes to compare revisions:
>>
>> sequential
>> - Demo: http://twiki.org/cgi-bin/rdiff/Codev/TWikiStandAlone?rev1=3;rev2=1
>> - displays, also for severeal versions, only the changed part of the 
>> document.
>> - This view is very useful for large documents and many contributors, as 
>> you don´t have to scoll over the whole document in order to discover the 
>> change. And you get an overview when something gets changed in a 
>> timeline order.
>> - The view has a parameter called context, which defines the number of 
>> displayed lines above and below the changed line
>>
>> side-by-side
>> - Demos:
>>   - 
>> http://twiki.org/cgi-bin/rdiff/Codev/TWikiStandAlone?rev2=2&rev1=4&render=sidebyside 
>>
>>   - 
>> http://svn.apache.org/viewvc/apr/apr/trunk/misc/unix/rand.c?r1=382552&r2=384930&pathrev=553146&diff_format=h 
>>
>> - This is similar to the former suggested columns and will display the 
>> changes, also for several versions in a timely manner
>>     
>
> It's not very easy to remove unchanged html above and below the change.
> A lot of documents are just big tables or lists; then you will have to
> remove children of the list instead of the body; then what about
> numbered lists; ...
> I'm not saying it can't be done. It's just a lot of work for solving a
> problem twice.
>   

You´re right, cut down html is not that easy and it has to be done in 
consideration of the DOM. Forget the context-parameter for a moment. 
What I have in mind is, to focus on the first child-elements of 
daisy-xhtml. For example it would be possible to orientate on paragraphs 
which are changed and cut/hide other paragraphs which are not changed. 
Same could be applied to other tags. Even list items could be cut down 
as long the <ul> gets preserved. The question is, if your algorithm can 
identify where the change happen inside the DOM?
> Your suggestion would work for the classic mode. I'm not sure how often
> the classic mode will be used now that we have the Html mode. It might
> not be worth the trouble?

No, the CLASSIC option would be not an option. As I sad, I have 
collaboration enhancements and thereby the normal user in mind.

André