Community
Participate
Working Groups
Build ID: N20090419-2000 It would be useful because I often want to debug changes that I'm inspecting in the compare editor.
Could be useful. Moving to compare: they first have to decide in general whether we want to start showing the vertical ruler. What about the overview ruler then?
I agree that showing the vertical ruler is the way to go. I guess this would allow us to show more than just breakpoints. We could display annotations, tasks etc. One thing I'm not so sure about is the "folding" ruler, don't know if this should be available while comparing. Regarding the overview ruler, I think we could use it as well but it should filter out any non-compare annotations by default. btw, with both rulers added we would be pretty close to use more of an embedded editor UI than we do so far. See bug 271787, comment 9 and 10, about calling createPartControl(Composite) method of an embedded editor, not just extracting a source viewer from it.
I think we need to keep in mind that screen real-estate can be tight when using the compare editor. It would be good if the user can hide the ruler if they prefer to use that real-estate for comparing.
Before we start adding rules and other useful things, I would ask UI whether they plan further work during 3.6 on embedded editors/parts. I think that it would be great if we could just use editors inside of "compare container" instead of creating similar flow for creating, configuring and removing editors in the compare framework.
> I would ask UI whether >they plan further work during 3.6 on embedded editors/parts. AFAIK this is deferred to e4.
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.
