Bug 43603 - [rulers] QuickDiff provider usability concerns
Summary: [rulers] QuickDiff provider usability concerns
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0   Edit
Hardware: PC All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 46170 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-09-24 15:09 EDT by Jean-Michel Lemieux CLA
Modified: 2019-09-06 16:08 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Michel Lemieux CLA 2003-09-24 15:09:06 EDT
From another PR:
Having used the quick diff with 'version on disk' and the new 'cvs provider' for
a little while now,  I have some questions and comments:

1. Currently, it is very hard to find out that your file has changes without
scrolling. I didn't find which hot keys to use to 'select next/previous change'.
I understand that you want to show line changes but there is no way to find
them. For example, in compare editors the overview ruler shows were the changes
are and the select next/previous are used to navigate. Maybe we need an editor
decoration to hint that it's changed based on the reference document? A hint
that you should look for changes?

2. The bar is so narrow that I can't hover my mouse over it. What is the hotkey
for showing the change? Also what are the hotkeys for replacing the changes?

3. Have you thought of providing 3-way diff support? With the CVS quick diff
provider it will be really useful to see the direction of the change to
understand if you made the change or if it was made remotely.

------- Additional Comment #6 From Tom Eicher 2003-08-10 17:57 -------

1. I agree - we would need a toggable indication on the overview ruler similar
to the one provided by the compare editor. Whether we will want shortcuts or
not, I am not sure - go to previous / next is usually assigned to something else
already (e.g. next problem in Java Editor), so we would have to introduce new
shortcuts. 

2. There are no hotkeys so far - as a workaround for the narrow ruler, if line
numbers are turned on, the ruler gets wider. Instead of using hotkeys for
undoing a change, the related actions can be acessed via the ruler's context
menu (Ctrl+W). 

3. The quick diff indication was really thought as a lightweight change
indication, and I am also considering a shortcutto open the full-fledged compare
editor from a change.

Note that the current diff information might not even be correct (i.e. the
shortest edit script from reference document to actual) because it is computed
incrementally. Try moving around lines for a demonstration of the current
algorithm's limitations.
Comment 1 Jean-Michel Lemieux CLA 2003-09-24 15:13:41 EDT
Don't get me wrong. I actually think that this feature could be really cool. But
it needs some tweaks. I would be happy if we could solve points 1 and 2 above. 

Comment 2 Tom Hofmann CLA 2003-09-25 03:58:19 EDT
I see that 2) is a valid point - you wan't to be able to use the normal editor
to merge and track changes.

1) will hopefully make it for M4.

3) - not sure yet how to visualize three-way compare... Well actually, we could
indicate on a change whether it is incoming / outgoing... Ok. I'll look into this.

Have you thought about revision tracking, i.e. now when I have integrated
incoming changes, I hit "mark as merged" so the revision number gets updated to
HEAD. Once merging is more of a continuous process than a update procedure with
a clearly defined start and end, this might be more complicated...?
Comment 3 Tom Hofmann CLA 2003-11-21 06:44:04 EST
1) has been fixed - quick diff can be shown in the overview ruler and selected
as "Go to Next / Previous" targets.

2) Still no way to see the reference using the keyboard. There are also other
concerns. Summarizing from other PRs:
- the reference hover covers up the current text, making it very hard to see
side by side
- use quick merging, a specific keyboard shortcut would be needed, instead of
going over the ruler context menu
- the full merge process would require several other issues:
   - set "mark as merged" 
   - select the compare version, instead of only using head, one would really
have all the options from the compare menu

If all these problems get solved, one would probably end up with today's compare
editor... I am still not convinced of whether one can get all the needed
functionality in one editor. I see, though, that the current compare editor
looks like a normal editor but really isn't one, which is suboptimal.

Of course, if someone implements a fine split-pane editor that would allow to
see the changes side by side...
Comment 4 Dani Megert CLA 2003-11-21 08:25:44 EST
*** Bug 46170 has been marked as a duplicate of this bug. ***
Comment 5 Tom Hofmann CLA 2005-10-20 12:11:27 EDT
Note that there are commands to replace the current line or block with the
reference contents. The commands are not bound by default, but I usually assign
"Revert Block/Selection" to to Alt+Ctrl+Left.

The remaining issues are:
- key shortcut to show the change hover (currently only available by hovering)
- allow to move from the quick diff ruler to two/three way compare in a smooth,
integrated way.
- 3-way diff  - probably won't happen; I am reluctant to add incremental (live)
3-way diffing, as this adds another document into memory and increases the
typing overhead even more.
Comment 6 Tom Hofmann CLA 2006-08-14 09:32:27 EDT
Moving back to inbox.
Comment 7 Dani Megert CLA 2006-08-14 09:51:53 EDT
Currently no plans to work on this.
Comment 8 Dani Megert CLA 2007-06-22 09:59:16 EDT
Get rid of deprecated state.
Comment 9 Eclipse Webmaster CLA 2019-09-06 16:08:57 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.