Q1 |
The application model is stored in the |
Q2 |
Parts are a more generic form of views and editors. Unlike Eclipse 3.x, not everything needs to fit into a View or Editor category; they are all just Parts which contain UI components underneath, and can be organized appropriately. |
Q3 |
Although extension points aren't used for things like commands, keybindings, or views, they are still used to define other extensions to Eclipse such as builders, marker types, and language parsers. The only thing that the Eclipse 4 model moves out of the extension points are the UI-related concepts. Even then, in the Eclipse 4 IDE the backward compatibility mode ensures that all the UI-related extension points are still rendered. For developing IDE plugins, the Eclipse 3.x APIs are likely to be around for the next couple of Eclipse releases. |
Q4 |
The Eclipse 4 parts can be styled with CSS, and the underlying renderer applies the styles on the fly, including if the CSS styles change. This allows theme managers to apply different color combinations in Eclipse 4 in ways which are not possible in Eclipse 3. |
Q5 |
The Eclipse 4 contexts are essentially a series of |
Q6 |
There are several annotations used by Eclipse 4, including:
|
Q7 |
Preferences are accessed with the |
Q8 |
Messages are sent via the |
Q9 |
Selection can be accessed using the value from the context with a method injection or value injection using |
Eclipse 4 Plug-in Development by Example : Beginner's Guide
By :
Eclipse 4 Plug-in Development by Example : Beginner's Guide
By:
Overview of this book
<p>As a highly extensible platform, Eclipse is used by everyone from independent software developers to NASA. Key to this is Eclipse’s plug-in ecosystem, which allows applications to be developed in a modular architecture and extended through its use of plug-ins and features.<br /><br />"Eclipse 4 Plug-in Development by Example Beginner's Guide" takes the reader through the full journey of plug-in development, starting with an introduction to Eclipse plug-ins, continued through packaging and culminating in automated testing and deployment. The example code provides simple snippets which can be developed and extended to get you going quickly.</p>
<p>This book covers basics of plug-in development, creating user interfaces with both SWT and JFace, and interacting with the user and execution of long-running tasks in the background.</p>
<p>Example-based tasks such as creating and working with preferences and advanced tasks such as well as working with Eclipse’s files and resources. A specific chapter on the differences between Eclipse 3.x and Eclipse 4.x presents a detailed view of the changes needed by applications and plug-ins upgrading to the new model. Finally, the book concludes on how to package plug-ins into update sites, and build and test them automatically.</p>
Table of Contents (19 chapters)
Eclipse 4 Plug-in Development by Example Beginner's Guide
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
Creating Your First Plug-in
Creating Views with SWT
Creating JFace Viewers
Interacting with the User
Storing Preferences and Settings
Working with Resources
Understanding the Eclipse 4 Model
Creating Features, Update Sites, Applications, and Products
Automated Testing of Plug-ins
Automated Builds with Tycho
Pop Quiz Answers
Index
Customer Reviews