Eclipse is known for its powerful plug-in mechanism, it can be said that the entire Eclipse is composed of plugins. With Eclipse 3.0, with the rise of the RCP concept, the entire Eclipse plugin also forms a clear hierarchy relationship. The bottom layer is RCP org.eclipse.core.Runtime, org.eclipse.ui; the middle is a large number of plugins constituting the Eclipse itself Workbench such as org.eclipse.jface, org.eclipse.Platform, to the top It is some dedicated function plug-ins, such as CDT, JDT, EMF, etc. This article is simple to make a simple introduction to the current popular plug-in.
The first is a plugin hierarchical figure
Eclipse SDK
Org.eclipse.sdk
Eclipse Platform
RCP
Org.eclipse.core.Runtime
Org.eclipse.ui
Org.eclipse.Update.configurator
Org.eclipse.swt
Org.ECLIPSE.JFACE
Org.eclipse.Platform
ORG.ECLIPSE.Debug
ORG.ECLIPSE.ANT
Org.eclipse.help
...
JDT
Org.eclipse.jdt.core
Org.eclipse.jdt.ui
Org.ECLIPSE.JDT.DOC
Org.eclipse.jdt.debug
Org.eclipse.jdt.junit
PDT
Org.eclipse.pde.pde
Org.eclipse.pde.build
Org.eclipse.pde.core
Org.eclipse.pde.runtime
Org.eclipse.pde.ui
Org.eclipse.pde.doc
Org.eclipse.pde.source
As can be seen from the above figure, Eclipse SDK is the sum of these plugins. In all of these plugins, the core is several plugins to which RCP belong, org.eclipse.ui (theoretical RCP should include these two components, but according to their understanding, no ORG . ECLIPSE.UPDATE.CONFIGURATION, ORG, Eclipse.swt, org.eclipse.jface, org.eclipse.workbenchde support,
Writing an RCP program with a UI is impossible). Org.eclipse.core.Runtime provides a cross-platform runtime support, as well as management mechanisms for other plugins; org.eclipse.ui provides cross-platform interface support, you need to note that org.eclipse.ui depends on 5 plugins, you may wish to open the Eclipse / Plugins / Org.eclipse.ui_3.0.1 / plugin.xml file, you can find the following lines, clearly illustrate this dependency:
requires>.
Above the RCP is the Platform layer of Eclipse, which is responsible for the interface, operations and functions of the Eclipse itself. For example, Eclipse menus, various views and editors, debugging capabilities, help support, etc. This layer is the largest and most complicated part of Eclipse.
Among them, org.eclipse.swt, org.eclipse.jface provides the underlying support of the UI cross-platform, and org.eclipse.ui.Workbench implements a part of the Eclipse part of the upper UI framework, and eventually by org.eclipse. Ui.IDE implements most menus, editing windows, task lists, etc. UI components and functions.
Platform is the Eclipse's SDK layer, in fact, Platform JDT PDT, above Platform, make Eclipse truly a complete development tool. At the same time, it is because of this design method of Eclipse, which makes Eclipse as a development environment, almost unlimited expansion, not only support Java development, plug-in development, C development, but also Python, XML, Perl, UML, etc. go with
Http://www.eclipse-plugins.info go to see, you will understand why I said this. Unfortunately, I have not found a Plugin related to .NET development.
It can be seen that the Eclipse is based on plug-in design, so that Eclipse itself has an unlimited development space and is unique in many development environments. And from version 3.0, Eclipse's development group is adjusting the Eclipse's plug-in structure so that the hierarchies of these plugins are clearer, and the RCP concepts that appear on this basis are possible to run separately from the plugin to Eclipse separately.