Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 85751 - [rulers][api] Common way to globally add custom info into editor left bar
Summary: [rulers][api] Common way to globally add custom info into editor left bar
Status: RESOLVED DUPLICATE of bug 25793
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-17 15:05 EST by Eugene Kuleshov CLA
Modified: 2006-07-07 12:05 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 Eugene Kuleshov CLA 2005-02-17 15:05:20 EST
Currently the only way to add custom information to editor left bar (same place
where "Marker Bar" and line numbers) is to subclass the concrete editor. Please
add an API to allow to add such info globally to all editors. Use cases for this
feature may include CVS annotations, cross references, coverage information,
etc. In many cases marker icon is not enough.
Comment 1 Eugene Kuleshov CLA 2005-08-19 22:01:31 EDT
Any plans to address this issue in 3.2 stream?
Comment 2 Dani Megert CLA 2005-08-22 04:59:52 EDT
Not planned for 3.2.
Comment 3 Tom Hofmann CLA 2005-11-07 08:44:09 EST
From a discussion on platform-text-dev@eclipse.org:

If we added API for contributed columns, we would probably also provide an
abstract base implementation taking care of boilerplate code and offering some
event/notification mechanism for line-events (like "line selected", "line clicked").

One problem that would arise is that we have to stay compatible with the
existing API of CompositeRuler. CompositeRuler makes some assumptions about the
contained ruler columns (e.g. every column consists of a single Canvas and no
child controls) that we should get rid of before adding the API. Other questions
that need to be answered:

   * context menu - should the ruler continue to show the same context
     menu for all columns, or should a column (optionally) be able to
     have its own?
   * accessibility - with more and more information in the ruler, can
     we offer a way to make the ruler accessible (e.g. give focus to
     the ruler)?
   * painting: currently all ruler columns implement their own
     double-buffer painting, which may not scale well.
   * column ordering - this is currently done by the editor as the
     controlling instance - how would ordering work with arbitrary columns?
   * overview ruler - should there also be additional overview rulers?
     probably...
   * resizing - should rulers support (horizontal) resizing? this would
     be interesting to "expand" the condensed information upon user request 
Comment 4 Eugene Kuleshov CLA 2005-11-09 17:37:38 EST
Tom, what I've suggested here is to add a single column which content (text and
colors) would be rendered automatically, but the data (again, text, line ranges,
etc) could be dynamically changed by the custom data provider eliminating all
the work needed for custom canvas painting. User can choose which data provider
should be used at a moment in a way similar to quickdiff providers.

Speaking of the context meny, I think that the current one already has usability
issues, such as no keyboard shortcut for invoking it (which by the way should be
fixed too!) and adding new popup menus would only icrease this mess.

I probably agree with you about the resizing. It would be convenient to have it.
Comment 5 Dani Megert CLA 2005-11-09 17:49:27 EST
>Speaking of the context meny, I think that the current one already has usability
>issues, such as no keyboard shortcut for invoking it (which by the way should be
>fixed too!)
What's wrong with Ctrl+F10?
Comment 6 Eugene Kuleshov CLA 2005-11-09 19:48:11 EST
(In reply to comment #5)
> >Speaking of the context meny, I think that the current one already has usability
> >issues, such as no keyboard shortcut for invoking it (which by the way should be
> >fixed too!)
> What's wrong with Ctrl+F10?

Ops, my fault. Ctrl-F10 is just fine, please keep it there. :-)
Comment 7 Tom Hofmann CLA 2006-07-07 12:05:04 EDT
Marking as dup of bug 25793 which is even older; I will copy comment 3 over.

Note that this is on the 3.3 plan - please add any further thoughts and comments to bug 25793.

*** This bug has been marked as a duplicate of 25793 ***