While developing "about window" in eclipse RCP, we need to define:
aboutText=My text which will be shown in about window
in about.ini file.
I need to add version number, which is defined in the overview page
of the .product file.
Is there any way to parametrize this string?
I have tried to add {featureVersion} to aboutText, but it doesn't work - my about window is not displayed then.
Thanks!
Not so difficult... Use {0}, {1}, etc in the text itself and construct a file about.mappings with:
0=abc
1=def
...
Now the problem is reduced to making substitutions in the mappings file. Unfortunately there are no standardized way to do this in Eclipse. For Tycho, I typically use maven filters as described here.
Related
Hay, has anybody experiences with adding custom annotation types or appearance color options to the eclipse squish IDE? I'm trying to find a way to highlight previously verbalized words in the editor (i.e. **markme_**something(parameter). Sadly I can't find any plugins and as far as I noticed squish is doing a good job to hamper any kinds of external not former installed or in the manual mentioned plugins.
Another of my thoughts are to write an addition to the syntax checker but that would be probably kinda over the top and not that easy to realize. The source code is written in python.
Greetings and thanks!
Eduard
To mark a search string in the editor you can use Search > Search... (Ctrl+H). Then just enter the search string and press Enter. (While this will open and populate the "Search" view, the search string occurrences are being marked in the editor anyway.)
Perhaps you are trying to let the script editor color (a customizable set of) substrings in a customizable way? I have not found an Eclipse plug-in that would achieve that. The closest I could find (and available in source code form) is Highlight On Selection.
PS: Note that custom plug-ins are not supported in the Squish IDE, but that you can use the Eclipse IDE Integration, and then install the desired plug-ins into this Eclipse installation.
This may seem very small thing but it annoys me much since I'm used to code in Eclipse. When I double click a java source file in Eclipse it shows classes inside the file (expanding contents of java file) as marked by red circle in the image below. I wanna disable this behavior, I have used Eclipse for a long time and it has never been like this.
You can go to Prefences --> Content Assist and Enable/Disable the contents of Java file
[![enter image description here][1]][1]
Thanks,
Raghava
This is a bug in Eclipse, and several people have reported it, e.g., here.
One workaround is to change the "open mode" in the General preferences to single click", which does not have this annoying behaviour.
Is there a way to add more than one column for decorators in an Eclipse editor.
For example, a breakpoint and a search arrow on the same line dosen't play nice with each other.
You can add new columns there using the extension point, assuming you are an eclipse plugin developer.
You cannot change this as an eclipse user, however.
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 writing an eclipse plugin to analyze files for some defects, I get the list of java files, their classes and methods in a jface tree view, I need to open the file in the editor when I double click on the file node of the tree view.
please help me with this.
thanks,
Shasinda
You should either use a common navigator framework with corresponding filters that already has the link and open function built-in for Eclipse Resources, however, is much trickier to set up - see the blog post series starting with http://cvalcarcel.wordpress.com/2009/07/08/writing-an-eclipse-plug-in-part-1-what-im-going-to-do/
Alternatively, you could add a double click listener that opens an editor (or checks existing editors of the current workbenchpage) by looking the open editors. For the basic idea, see the corresponding Eclipse FAQ entry.
Use IDE.openEditor to open the editor.