Bug 213693

Summary: [EditorMgmt] Generic annotation support for non-text based editors
Product: [Eclipse Project] Platform Reporter: Ilya Shinkarenko <shinych>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3 CC: daniel_megert, pwebster, shinkarenko
Version: 3.4Keywords: helpwanted
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Ilya Shinkarenko CLA 2007-12-21 07:34:55 EST
Steps To Reproduce:
If you want to reuse the annotation support for a table based editor, then you have a problem. The current API does not support non-text based models/editors. 

As we did in our project, we just copied the pieces of org.eclipse.text / org.eclipse.jface.text / org.eclipse.ui.workbench.texteditor / org.eclipse.ui.editors and "adjusted" the implementation, which is of course will not work in a long run. It would be great if the platform would have some generic annotation support.

More information:
There is a necessity in having an annotation support for non-text based data viewers/editors, for example, table based. The solution should have same functionalities as the current text annotation support has. Some of th additional features may be:
 * horizontal annotation/overview ruler for tables 
 * standard annotation navigation actions ('Next Annotation' and 'Previous Annotation' buttons) must be reused
 * the additional property page "Table annotations" with table-specific contents
 * etc.
Comment 1 Boris Bokowski CLA 2008-01-02 11:17:09 EST
The enhancement request makes sense, but we won't have time to work on this in 3.4. Feel free to submit a patch.
Comment 2 Boris Bokowski CLA 2009-11-17 13:04:48 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:35:04 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.