Which extension point can I use in order to extend the bottom part of the eclipse interface?
I am referring to the part as seen above:
I am interested in the File Search... section.
Related
I'm writing a plugin for the Eclipse IDE that adds a custom marker annotation to highlight portions of the code. Currently, I use textStylePreferenceValue="BOX" in the org.eclipse.ui.editors.markerAnnotationSpecification and get a changed background color that ends at the line-break for each line. That introduces a lot of visual noise, and I would like to have the color to extend to the whole width of the editor. How can I achieve this?
If this is not possible at the moment, what would be the next steps to add this functionality to the platform?
This is what I have:
This is what I want:
After researching further, it seems that this is not possible at the moment, at least not easily. The relevant Eclipse sub-project seems to be "platform.text" (https://github.com/eclipse/eclipse.platform.text/). The possible textStylePreferenceValues are defined in the class "org.eclipse.ui.texteditor.AnnotationPreference", and how to paint them is defined in the class "org.eclipse.jface.text.source.AnnotationPainter".
A low level solution could be to use a LineBackgroundListener together with the StyledText object of the editor.
Sorry for my vague question, but I'm missing the words to be more to the point. That's part of my question.
I'm using Eclipse Mars. Several views display little images next to, e.g., project names. Furthermore, these images are enriched by additional graphical features, depending on the properties and states of the entities they are attached to. So,
How are these images called?
How are the additions called?
How do I find out, what a specific addition means?
For example, I have no clue about the meaning of the strange antlers on the bottommost image in the following screen.
They are called 'decorations' or 'decorators'. They are added by various plugins to provide additional information about the file / folder / projects. Decorations can also be added to the beginning or end of the label text.
For example the first three projects in your image are Java projects (small J at the top right), they are under source control (bottom right image) and they all have some warnings about problems (warning sign at the bottom left).
You can control the display of many of these images in the Preferences in the 'General > Appearance > Label Decorations' page. Other decorations are controlled in other preference pages specific to the plugin that provides them (for example 'Team > SVN > Label Decorations').
Because they are added by many plugins it is hard to give a list of what they all mean. This answer lists some of them.
Plugins use the org.eclipse.ui.decorators to declare decorations.
I'm not sure but my guess is the 'strange antlers' decoration are because you have an ANTLR project.
Here's the official icon reference for the basic icons and decorators.
Plugins (including standard plugins) will add additional decorations. For example, the ones used by Git are listed in Preferences>Team>Git>Label Decorations, along with a key. You can enable/disable plugin-specific decorations in Preferences>General>Appearance>Label Decorations.
The antlers in your selected icon are from the ANTLR plugin. So that project is an ANTLR project (as well as being a Git-tracked project that causes a warning, per the other icons).
I hope that helps!
I am trying to develop an eclipse plugin that does some documentation check on java code and highlights some lines of code in the editor.
To achieve my goal, I DON'T want to create a new editor in eclipse, I simply want to extend the default java editor to draw a line under (or highlight) the methods that do not satisfy some set of predetermined requirements.
Do I need to create a PresentationReconciler? If yes, how do I make the JDT or workbench use my reconciler.
I have never done plugin development and this is my first attempt.
Several starting points for you:
Annotations are an UI feature of JFace's text editor that allows you to visually mark some places in an open editor.
Markers are a Workbench feature, more high-level. They are generic "objects that may be associated with Workbench resources", and they can display in several places: in text editors (as annotations) or in the Problems view, for example.
Depending on what you want to do, you would plug in your plug-in into extension points related to either of those.
The Eclipse Java editor is located in the org.eclipse.jdt.internal.ui.javaeditor.JavaEditor package.
The "internal" in the package name means that the Eclipse development team can change how the Java editor works with new revisions.
Try this help page: Juno Help on syntax highlighting
At the end of the page, it describes how to dynamically add a PresentationReconciler, which is used for syntax highlighting. See if that fits the problem that you want to solve.
I assume you already have a plugin project.
In your plugin.xml, open the tab Extensions, click Add..., search for org.eclipse.ui.editors, then you should see a template named Editor, which will produce a simple xml editor to experiment and play with. Also, you will be able to see the needed structure to define a custom editor.
Hope this helps...
I don't know if you still have a need for this, but you are going to want to use Annotations to keep track of what parts of the editor you need to highlight.
For actually doing the graphical effect of highlighting, you could do syntax highlighting via a PresentationReconciler, but I have no experience with that.
We used a technique we borrowed from http://editbox.sourceforge.net/, replacing the background image of the editor Shell. Its open source, so check it out. (Our code might also help -- its at https://github.com/IDE4edu/EclipseEditorOverlay )
I am developing a plug-in for Eclipse. I have to develop a Java text editor which allows several users to write the code at the same time, the same way as in Google Docs. But I came across the following problem: the text editor has to show the cursor position of the other users who are coding in same Java document. In other words, I want to place a marker in the text editor content (see this image that shows what I'm trying to implement).
I've already looked IMarker, but IMarker is placed on the text editor's vertical ruler, which is not what I want. Can I use this class? If not, what other class should I use?
The other idea of mine was to insert a JTable in the text editor, but I couldn't find the way how to do that. Is this a right approach, or I'm wrong?
Stack Overflow Gods, please help me...
Eclipse has two different concepts for managing extra information related to files: markers and annotations. Annotations are related to a single editor instance, and their appearance can be customized with a corresponding extension point; markers are used to store extra information permanently (and additionally an annotation can be set up for that reason).
I think, you need to use annotations, as markers are too heavyweight for a real-time collaboration. For future reference, see the Annotations in the Eclipse Help; and some time ago I have written a blog post that describes an automatic translation (and customization) of markers to annotations.
I need to make custom text folding as described here: Can I merge Syntax coloring and Folding? OR Projection colored from master document info
I'm digging through code, but its very perplexed... and I cant get access to some classes.
I still haven't found what class decides what to show when ProjectionAnnotation collapsed
I need some info on how folding/projection is implemented, but haven't found any articles.
Please if somebody familiar with Eclipse projection, or knows any articles, help!
The basic goals:
1) make ProjectionAnnotations to show text enclosed in xml tags, instead of first line
2) make ProjectionAnnotations unexpandable(permanently collapsed)
3) remove collapse/expand button (I think I know how to do it, but this decorative and have less priority)
Have a look at the excellent Eclipse corner article, you could also try looking at how Spring IDE implemented it (check out their source code from here).