Eclipse SDK navigation

Opening a forum, I will post my translation:

EclipsePlatformSDKNavigation

Translated by xiaotaoliang 04.12.14

Core Runtime:

The core runtime of the platform implements the eclipse runtime engine, which starts the platform, dynamically discovers and runs the plug-in.Plug-insIs a structured component (Plugin. xml) To the system. The Platform maintains a registry to record installed plug-ins and their functions.

In general, the runtime goal is: if some plug-ins are installed on the platform and end users do not use these plug-ins, it will not cause memory or performance burden. The plug-in can be installed and added to the platform registry. However, the plug-in will not be activated unless some actions of the user request some features of the plug-in.

The Platform Runtime is implemented using the osgi service model. However, the Implementation Details during runtime are not important to most application developers. Developers familiar with osgi will see that an Eclipse plug-in is equivalent to an osgi bundle ).

Resource Management plug-in:

The Resource Management plug-in defines a general resource model for managing various resources of the "tool plug-in. Plug-ins can be created or modifiedProject,FolderAndFile. Resource extension points allow other plug-ins to define their own resource types.

Work Platform interface plug-in:

The work platform interface plug-in implements the work platform interface and defines some extensions to allow other plug-ins to provide menu and toolbar behavior, drag-and-drop operations, dialog boxes, wizard, and custom views and editors.

The additional interface plug-in defines some frameworks that are useful for user interface development. These frameworks were previously used to develop the work platform itself. Using these frameworks not only simplifies the development of the plug-in user interface, but also ensures the uniform appearance and view of the plug-in, and conforms to the consistent work platform integration standards.

The standard component Toolkit (SWT) is an underlying, operating system-independent toolkit that supports Platform Integration and lightweight Application Development interfaces. Description in another document.

The jface interface framework provides a high-level application layer structure to support dialog box, wizard, behavior, user parameter settings, and part management. The jface function is described in another document. (<Dialog box and Wizard >>,< jface: plug-in interface framework>)

Workgroup Plugin:

The workgroup plug-in allows other plug-ins to define and register functional modules that support workgroup programming, knowledge base access, and version management. The CVS plug-in included in the eclipse Platform SDK uses the Working Group plug-in to provide the CVS client function. The Working Group supports the description in another document.

Debugging plug-ins:

Debugging plug-ins allow other plug-ins to implement language-independent program starters and debuggers. Description in another document.

 

 

Help System Plugin:

The help system plug-in provides a platform-optimized help server and document integration tool. The extension points defined by this plug-in allow other plug-ins to provide help or plug-in documentation in the form of e-books. The document web server also includes some unique features, such as allowing plug-ins to reference documents through a logically hierarchical, plug-in-based URL, rather than through a file system URL.

Additional features include integrating Help topics into product-Level Document configuration. The help function is described in another document.

Java Development Tool plug-in (jdt ):

The Java Development Tool plug-in (jdt) extends the work platform by providing a series of functions to edit, view, compile, debug, and run Java code.

Jdt is installed and included in the SDK as a plug-in set. The Java Development User Guide describes how to use the Java tool. The jdt plug-in Development Guide describes the jdt Structure and Application Development interfaces.

Plug-in Development Environment (DTA ):

The plug-in development environment provides automated tools for creating, maintaining, debugging, and releasing plug-ins.

The module is installed as a plug-in set and included in the SDK. The module describes how to use this development environment.