Summary: | User Specified Comparison Tool | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | JCH <houstonj> |
Component: | Compare | Assignee: | Platform-Compare-Inbox <platform-compare-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P4 | CC: | Michael.Valenta, pwebster |
Version: | 3.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
JCH
2004-05-18 09:20:18 EDT
After 3.0 Reopening That's a great idea! Michael have you made any research in this area? I would be happy to give it a try (as soon as I can), but that would be a start from scratch. Do you or anyone else have any experience in integrating external comparison tools the way reporter asks? Could your work on Word Document comparison be a good starting point? Would this require to write a generic contentMergeViewer for embedding external tools? Writing a generic contentMergeViewer for external tools would be complicated. I did give it some thought but I didn't get very far. The first step for this may be to add the ability to register multiple compare viewers for a content type where the user would pick which one to use if there were conflicts). You could then imagine that a third party could create a compare merge viewer that launches a separate window like the window merge does. If such a viewer could be associated with the Text content type and the user had the ability to specify that they wanted this viewer used for all TEXT types (i.e. UI that says use the merger for the target type and all sub-types) then I think that would do it. |