Eclipse plug-in development process Review I learn the Eclipse plugin development process, summarize the following processes, I hope to learn from everyone. Want to learn the plugin development of Eclipse 1. First, Eclipse2.1.2 should be downloaded (not recommended using Eclipse 3.0.0) and its corresponding Chinese language package 2. It should be necessary to have a good understanding of the use and structure of Eclipse itself. It is best to look at the help file to see him to provide those features, and what they expected and the views are doing. The advantage of doing this is that the reference can be found while developing, and the basic plug-in provided by Eclipse itself generally has an extension interface. When you need to extend functionality, it is also known. For example, I am developing "Wizard, which is new," Wizard, "," I refer to the program when the Eclipse itself is new Java file. In my trial, I hope that the user appears in the "content" attribute, so I use the interface provided by the Property view to him. Key: The best way to understand Eclipse is to use and workbench user guide, because Eclipse Chinese document translation is particularly good, so it is the best way to learn.
3. It is now the development of learning plug-ins. This is the first to read the document. The documentation here is mainly Eclipse's help files are PDE Guide and Platform Plug-in Developer Guide, and there are some events that need to be combined. Eclipse provides a plug-in that supports plug-in development, which is a plug-in that supports plug-ins. This is PDE. The first purpose of learning PDE is to understand, PDE features and provide those support, if you can read PDE Guide configuration and build your first Plug-in (new and test running success), do not need more content, if you have time to read, after the problem, you know that in the plugin information is fine. Platform Plug-in Developer Guide (short below) is the most important information in the development of the entire plugin. You don't have to check it out without Google. This help provides almost all information. PPDG has made detailed introductions for the structure and basics of the entire Eclipse. Read PPDG, first understand the overall architecture of Eclipse and constitute the base element (such as view, editor, etc.), in combination with your Eclipse itself Using, first, there is a sense of sensibility in the heart, there is a general concept in your heart, at this time you can think about the plugin you want to do, the interface is aware of Eclipse's architecture and infrastructure, describing It looks like an element, such as, is there a view, there is an editor, etc. Then find the reference in Eclipse. Suggest: Read all the documents of PPDG from the head to the tail reading over again. I have read more than two times. Why is this important? Although his documents have been more detailed in Eclipse, it is not necessarily clear, so you have to find the reference, so you can find and read its source. Code, know how to do it. In fact, after the development of the Eclipse plugin has a detailed understanding and start writing a plugin, the reading source code replaces the document. The more PPDG, you must start writing your own plug-in, there is a case plugin in the PPDG, you can try it. In fact, when you create a new plug-in, you can provide a corresponding example in New Plug-in Wizard. You can build a preliminary understanding by creating these examples, and try to modify its source code, my first plugin is doing this from. 4. The development of advanced plug-in features, you must read the source code and other information.
Overall, Eclipse's plug-in is not developing, and it is necessary to learn about its overall architecture and elements by reading its helper documentation, and practice.
I hope to help everyone, there is an unclear place, please post, I will help everyone as much as possible.
Author: jlinux
