Eclipse Plug-ins (3rd Edition)

All Stack Overflow 9
This Year Stack Overflow 2
This Month Stack Overflow 2


by anonymous   2017-08-20

How can I provide e.g. the SDCC compiler included inside my plugin?

You don't. You ask the user to provide you a link to the SDCC compiler.

Are there recommended libraries I should take a look at for plugin development?

agad already pointed you to the Vogella tutorials. I've used this book, Eclipse Plug-Ins, to learn Eclipse plug-in development.

Are there any tutorials that show how to configure a plugin such that there is a standard running configuration available (such that e.g. the project is built automatically and can be run by clicking the runner button)

You can take a look at the Eclipse class ImportOperation. It's found in the org.eclipse.ui.ide.source jar. Source jars are included with Eclipse RCP. This class does the actual work of copying objects from the local file system into the Eclipse workspace.

I tried to attach the source code, but an answer can only be 30,000 characters or less.

by anonymous   2017-08-20

Eclipse 3.x

The learning curve for Eclipse development in general is quite steep indeed, no matter if you are developing plug-ins or standalone RCP applications. The Eclipse Plug-ins (3rd Edition) book mentioned in zedoo's answer is a very good starting point for understanding the underlying concepts and APIs of the Eclipse 3.x stream. As far as online resources go, Lars Vogel has lots of very detailed and useful tutorials on his website for RCP deleopment and Eclipse plug-in development in general.


The Eclipse 4.0 SDK Early Adopter Release main page has links to a couple of tutorials and a very detailed release notes, and most importantly a new & noteworthy page with all the shiny new features compared to the 3.x stream.


Of course e4 is still not as mature as Eclipse 3.6, the latest release in the 3.x stream, which is clearly a downside. However, as far as I can see after playing around with it recently, the APIs and the whole development methodology have been streamlined, which makes it easier to get up and running. Documentation is still a bit sparse, but new tutorials and blog posts keep popping up frequently and there is more and more buzz around e4 in general.
Starting directly with e4 would save you the trouble of learning and eventually unlearning the 3.x API, so if you are in it for the long run, I would say go for e4 now. If this is just a relatively short one-off project and you want to reduce the risk, then go for 3.x and reap the benefits of the mature code base and lots of documentation.

by anonymous   2017-08-20

I have found the book Eclipse Plugins to be a good starting point

by anonymous   2017-08-20

You need to learn how to do Eclipse Plugin Development and then getting at the various property pages and manipulating them will require you to get familiar with the Eclipse RCP, and you will need to know how to query the workspace etc. Look at the book Eclipse Plug-ins