After some time of working with Eclipse - Java Enterprise, STS etc. I found enormous quantity of icons, pictures, pictogram etc. Does is possible to find list of all to use in work?
Thanks.
In short, it is not possible to do. The longer explanation is, that every plug-in of Eclipse can contribute additional icons, and they are keyed using freeform string identifiers.
However, if you want to reuse some icons (and the EPL licence of Eclipse permits it), a non-complete list of icons is available at http://eclipse-icons.i24.cc/
Related
This is a relatively open ended question so I wouldn't just mind being pointed in the right direction.
I have a product that uses the Eclipse workbench to allow users to program in a custom language. For this product, I will also have some minor UI and internal changes for a lighter version to be exported. For example, a full version of the product contains some extra views and menus, and behaves slightly differently (like when creating a new file) where as the ligher version does not contain a lot of view and has a couple of different more simplified ones.
I do not want to make a copy of my workspace and then have 2 separate workspaces for a full version and a lighter version as that will be difficult to maintain in the long run especially when there are changes in code relevant to both. I want to be able to export both, full and light versions of a product from a common workspace.
How can I go about this? Or where can I start looking?
The product is a collection of features and uses the Eclipse workbench as its base application.
I would like to clarify that I am asking how I could hide a view for the full or light version, as an example. I know in C#, we have options like #if. I have seen a lot of questions which refer to having 2 different versions of the same code, but nothing about how they could have 2 different versions of the same code.
You want the Eclipse RCP book it really fully explains how to do this. And to do it you need a solid understanding of the concepts of Eclipse plugin, feature, product, fragment and a few other things.
Essentially you can segment your application in to multiple plugins (have a base plugin for example, and then another that provides additional functionality). Then you organize those plugins into features that are the collection of the functionality to be installed. The notion of a "product" in Eclipse has to do with the branding, so you would probably have two products, a lite and a full one. The products could have a branding plugin (where the product is actually declared).
This should get you started.
Many different Eclipse packages are listed on http://www.eclipse.org/downloads/ and the comparison chart on http://www.eclipse.org/downloads/compare.php helps with knowing some of the differences. What I don't know as a total Eclipse (and Java) noob is how important it is to download the "right one" and how easy it is to fix things afterward if I discover I need some feature/capability/addon/whatever later.
For example, I need to get up to speed on RCP (whatever that is) quickly, but suspect I might want to also know about "EMF" and "GEF" and other things which aren't in the RCP version of Eclipse, or not listed at all such as SWT. I'm further confused by the top line of the comparison table, "RCP/Platform" with checkmarks under all columns - does this mean any package will do for learning the basics of RCP? This is not noob-friendly!
As an Eclipse know-nothing, what should I do?
I'd say download Eclipse Classic, then you can add whatever you need as plugins when you discover you need them in the future.
Is it possible (via a plugin or other way) for Eclipse to build a full text index for a project, so that searching a String does not linearly search all the files in the project?
(or does it automatically build such an index to speed up future searches?)
http://code.inf.unibz.it/projects/instasearch/ (old)
Edit: https://github.com/ajermakovics/eclipse-instasearch
It's a plugin that does indexed search using Lucene. Exactly what you're looking for I think.
The index files used by the search component of Eclipse (like a SearchParticipant) are in your workspace:
.metadata\.plugins\org.eclipse.jdt.core
As mentioned in this thread,
These files are used by the search or some other tools in Eclipse.
If you remove them, they will created again when you restart Eclipse or when you will activate the indexes. Then you will see a progress bar saying the number of files that need to be indexed.
There's an absolutely amazing and free plugin made by Pivotal (the creators of spring) that does indexed search with realtime preview for eclipse and works really good. I use it every day and could not live without it:
Quick Search for Eclipse
https://marketplace.eclipse.org/content/quick-search-eclipse?mpc=true&mpc_state=
After install, it can be easily opened via ctrl+shift+L
Give it a try, in my opinion is better than eclipse instasearch, and periodically maintained
You can write a plugin that does that. Using the "Builder" example in Eclipse PDE in conjunction with Lucene, it should take a novice a couple of days to get something that works.
If you are interested, nWire (for Java or PHP) offers a full text search for all the elements in your code (not just types, but also methods, fields, constants, etc.). It does not index all the code, though.
I want to use Selection Service feature from the eclipse RCP in my swing project. Currently the o.e.ui.workbench bundle which contains the related interface is around 3.7 MB, that's way too huge for our requirement
Is there any way to split it the workbench to get only the selection service
Are there distros already for this
Is it leagal to do so. Are there any licencse issues?
It does not look like it would be that hard to do it yourself, and that's pretty much what you would have to do. I know of no distros that do this however.
It's certainly legal to do so; you can freely use or modify any part of Eclipse until the EPL. If you split it without modifications then you have no obligations under the license. However if you extend it (and redistribute your code), then you need to make available your code that extends it (which can be done using an Eclipse bug report for example).
I want to use the "Web Tools Editor" that is part of the Web Tools Plattform in my own RCP-Application. I think i have got some understanding on the RCP plattform by now, but I still have no clue how to access the functionality of the pagedesigner (org.eclipse.jst.pagedesigner) after adding it as a dependency to my project. Has anyone some experience in adding components of the web tools plattform into an RCP-Application and can give me a hint or something?
There's a difficulty with these sorts of requests (I am, myself, trying to include this or that feature that I saw in the Eclipse IDE, every so often).
The trick is to try and identify the component you want to bring in, and then try and pull it into your project, without bringing in too many dependencies.
The first step used to be quite hard, but since 3.4 it is a matter of using the Plug-In Spy - hold down Alt-Shift-F1 on whilst your desired component is in focus should give you a tooltip showing you the class, the bundle, etc etc.
The second step is altogether more tricky and is where I usuaully fail to get any results:
if you are lucky then you can just include the bundle in the launch configuration/.product of your app. Once you hit Add Required Bundles, you are not left with 3000 bundles (i.e. your RCP is now Eclipse).
usually, this is not the case, because the Eclipse team haven't refactored the bit of code you're interested in out into an RCP safe bundle. If so, then you're going to have to do that yourself.
Again, if you are lucky then that will mean moving some classes out of the eclipse bundle into your own, including internal classes, and that will be the end of it - i.e. the dependencies of your desired functionality are all within the bundle.
If you're unlucky, then you need to isolate/reimplement the bit of functionality that is required, and change your version of the copied code.
It is hard laborious, and pretty difficult to upgrade. I realise that none of this is what you want to hear.