Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 218896

Summary: [patch][editor] display changes of old -> new values
Product: z_Archived Reporter: Willian Mitsuda <wmitsuda>
Component: MylynAssignee: Jomar Santos <jomaroliversantos>
Status: CLOSED MOVED QA Contact:
Severity: enhancement    
Priority: P3 CC: dveyee, jaxsun.mccarthy, jomaroliversantos, qwang12, rd12hq, sam.davis, steffen.pingel
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: All   
OS: All   
See Also: https://git.eclipse.org/r/85029
Whiteboard:
Bug Depends on:    
Bug Blocks: 198501    
Attachments:
Description Flags
Description part that can open a compare dialog
none
patch to above file
none
small-magnifying-glass.png none

Description Willian Mitsuda CLA 2008-02-13 18:12:41 EST
When something is changed in depends, blocks, keywords and cc fields, there is no way in task editor to know what changed inside those fields.

This is particularly annoying in large depends/blocks lists, when someone adds/removes 1 new element. Mylyn should offer a finer grained visualization for these fields.

I was thinking about generalizing this idea, and showing old -> new values for all changed fields in task editor. This is something you lost if you stop relying in notification emails.

This "diff" is actually displayed in the notification popup, but notifications are not persistent and disappear to quickly; we need a nice way to blend this information inside task editor.

What about using tooltips? For example, if the depends on field changed, there would be a tooltip with:

+ 1234, 5678
- 456

1 tooltip for each changed field.

These tooltips can be implemented like JDT hovers; in this example, the user could press F2 and those bug numbers could get hyperlinked.
Comment 1 Willian Mitsuda CLA 2008-02-13 18:18:06 EST
Also, display who made the change, so you don't have to open the history just for this.
Comment 2 Steffen Pingel CLA 2008-02-13 18:32:28 EST
That sounds like a great idea. I would wait designing this though until the notification framework gets an API for the task change deltas  (bug 205861) and the task editor is refactored (bug 179254).
Comment 3 Mik Kersten CLA 2008-02-18 19:59:45 EST
I really like this idea too and our custom tooltips seem like a great way of implementing it.   Then all we need is an affordance to indicate to people that they can hover to see changes.  How about we use the little "*" icon that's used by CVS overlays if enabled?
Comment 4 Eugene Kuleshov CLA 2008-02-18 21:01:02 EST
BTW, this is a duplicate of enhancement request submitted over a year ago. See bug 171175
Comment 5 Steffen Pingel CLA 2008-02-18 21:48:38 EST
*** Bug 171175 has been marked as a duplicate of this bug. ***
Comment 6 Eugene Kuleshov CLA 2008-02-18 22:01:02 EST
Out of curiosity, why earlier bug is marked as a duplicate?
Comment 7 Mik Kersten CLA 2008-02-28 16:34:41 EST
In general older bugs should be left open and new bugs marked duplicate.  However, for the cases where a bug contains considerably more useful information or comments (e.g. the description of this one) we have tended to mark the others a duplicate of that one.
Comment 8 Sam Davis CLA 2011-09-20 12:30:29 EDT
Created attachment 203699 [details]
Description part that can open a compare dialog

This changes its background based on outgoing or conflicting state and adds a button to open a compare dialog or editor. It would be good to generalize this to all attribute editors, but this could be used for long text descriptions, which is probably the main use case.
Comment 9 Sam Davis CLA 2011-09-23 19:02:26 EDT
Created attachment 203949 [details]
patch to above file

This fixes a small bug where editing after getting an incoming would incorrectly cause the editor to be marked conflicted.
Comment 10 Miles Parker CLA 2012-11-22 16:29:36 EST
Sam, could you put these changes into a Gerrit review? I really like the idea of making the changes more prominent a lot as the current affordance for changed attributes is -- to my eyes anyway --hard to pick out.
Comment 11 Sam Davis CLA 2012-11-22 20:55:03 EST
Here you go: https://git.eclipse.org/r/#/c/8828/. Note that you won't see any difference unless you have a repository with editable descriptions (e.g. Accept360).
Comment 12 Jaxsun McCarthy Huggan CLA 2016-09-23 01:02:39 EDT
* Attribute editors have a tooltip showing the previous value of the attribute
* This could potentially leverage TaskHistory
* Rich text editors provide a way to see a diff of the changes, Sam's review may prove a useful starting point
Comment 13 Eclipse Genie CLA 2016-11-15 00:36:54 EST
New Gerrit change created: https://git.eclipse.org/r/85029
Comment 14 Eclipse Genie CLA 2016-11-15 00:36:56 EST
New Gerrit change created: https://git.eclipse.org/r/85029
Comment 15 Eclipse Genie CLA 2016-11-15 00:36:56 EST
New Gerrit change created: https://git.eclipse.org/r/85029
Comment 16 Sam Davis CLA 2016-11-25 15:00:11 EST
Created attachment 265587 [details]
small-magnifying-glass.png
Comment 17 Eclipse Webmaster CLA 2022-11-15 11:45:08 EST
Mylyn has been restructured, and our issue tracking has moved to GitHub [1].

We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub.

[1] https://github.com/orgs/eclipse-mylyn