Java-based Eclipse plugin development overview

But the RTC itself, or the Eclipse platform itself, does not have a convenient way for us to clearly identify the contents of these resource files, and a large amount of information can only be displayed in Unicode: for example: \u7675. So we need a tool or plugin (Eclipse plugin) to decode automatically to solve my problem. So what we see is no longer a confusing Unicode, but a decoded text display. (in the example above, it will be shown as "癵"). All in all, this tool has brought more convenience to the http://www.aliyun.com/zixun/aggregation/7155.html "> Developers and the review and tester of PII, greatly improving the efficiency of the work."

Requirement background: Decoding of language and text in TVT test

When TVT (translation verification testing translation validation) tests, we need to constantly translate PII into various languages (programmed integrated, information Program Integration information) file is updated to our resource file for our testing. For the management of resource files, we use the RTC most of the time. But the RTC itself, or the Eclipse platform itself, does not provide a way to show what the translated text will look like (which is in the form of native text), and a great deal of information is displayed in Unicode, which is bad for our reading and validation. So we must use a flexible and convenient tool to decode to achieve the display of various languages. We designed this on the Eclipse platform on the plug-in, we can easily achieve this need.

Technical background: Overview of Java-based Eclipse plugin development

The most fascinating part of Eclipse is its plug-in architecture. The most basic concept in this system is the extension point (extension points), which is the interface provided by the plug-in. Each plug-in is developed at an existing extension point and may have its own extension points to continue development on this plugin. With Plug-ins, the core part of the Eclipse system is simpler to do when it starts, and only needs to start the base part of the platform and find the system's plug-ins. Most of the functionality implemented in Eclipse is done by the appropriate plug-ins. Eclipse has made a number of basic functions into a plug-in form. The entire Eclipse architecture is like a jigsaw puzzle that can be constantly added to the plugin, and plug-ins can be added to existing plug-ins. Here is a process introduction to the common development model, as shown below:

Figure 1. Process development Model

Design idea and Code realization: Plug-in decoding design and code fragment

Plug-in engineering structure design idea and code realization:

1. Extend the Popumenu in Eclipse's texteditor to add menu options.

The menu option in this project is Decode Unicode (Code point-> Characters). This menu option is added as an editor TextEditor extension and is not visible to other editors, such as Xmleditor,javaeditor.

Open a text file in the project and right-click to see the added menu.

Figure 2. Added menu options