Bug 271120 - [Viewers][Preferences] Customize and persist the way *MergeViewers are picked and used in compare
Summary: [Viewers][Preferences] Customize and persist the way *MergeViewers are picked...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-03 08:02 EDT by Tomasz Zarna CLA
Modified: 2019-09-06 15:38 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Zarna CLA 2009-04-03 08:02:16 EDT
Recently an option to switch to non-default Content Merge Viewer has been added[1], similar fix for switching Structure Merge Viewer is on its way[2]... but this is not enough. Switching viewers each time we compare files and Compare picked wrong (in our opinion) MVs can be annoying.

This bug is an enhancement request for an option (a preference page preferably) that would allow users to prioritize available ContentMergeViewers and StructureMergeViewers. Setting a higher priority to CMV A then to CMV B would result in picking A if content types bounded to A and B are equal. However, if content type for B is more specific for entities being compare B will be picked, even though it has a lower priority.

The approach described above is a minimal solution. It would provide lists of available CMVs and SMVs and an option the change the default order. The initial solution would place all available MVs into one list, with no distinction to content types nor extensions they are bounded to. This could be changed in the future by providing a better grained customization.

The default order would be determined as it is so far, MVs bounded to a content type go before those for extension. However, this could be enhanced by detecting a conflicting situation when to MVs fit for the same content type. Then a dialog asking for a user selection could be shown. The selection would be remembered and displayed in the pref page mentioned above.

In order to be displayed in the list MVs would have to provide a human-readable label[1][3].

[1] bug 201116
[2] bug 220457, comment 8
[3] bug 266877
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:38:31 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.