Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Eclipse Plug-in Development Beginner's Guide - Second Edition

You're reading from  Eclipse Plug-in Development Beginner's Guide - Second Edition

Product type Book
Published in Aug 2016
Publisher
ISBN-13 9781783980697
Pages 458 pages
Edition 2nd Edition
Languages
Author (1):
Alex Blewitt Alex Blewitt
Profile icon Alex Blewitt

Table of Contents (24) Chapters

Eclipse Plug-in Development Beginner's Guide Second Edition
Credits
Foreword
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
1. Creating Your First Plug-in 2. Creating Views with SWT 3. Creating JFace Viewers 4. Interacting with the User 5. Working with Preferences 6. Working with Resources 7. Creating Eclipse 4 Applications 8. Migrating to Eclipse 4.x 9. Styling Eclipse 4 Applications 10. Creating Features, Update Sites, Applications, and Products 11. Automated Testing of Plug-ins 12. Automated Builds with Tycho 13. Contributing to Eclipse Using OSGi Services to Dynamically Wire Applications Pop Quiz Answers Index

Chapter 1 – Creating Your First Plug-in


Eclipse workspaces and plug-ins

1. An Eclipse workspace is the location where all the projects are stored.

2. The naming convention for Eclipse plug-in projects is to use a reverse domain name prefix, such as com.packtpub. Additionally UI projects typically have a .ui. in their name.

3. The three key files in an Eclipse plug-in are META-INF/MANIFEST.MF, plugin.xml, and build.properties.

Launching Eclipse

1a. Quit the application with File | Exit.

1b. Use the stop button from the Debug or Console views.

2. Launch configurations are similar to pre-canned scripts which can start up an application, set its working directory and environment, and run a class.

3. Launch configurations are modified with the Run | Run Configurations… or Debug | Debug Configurations… menus.

Debugging

1. Use the Debug | Debug configurations or Debug | Debug As… menus.

2. Set step filters via the preferences menu to avoid certain package names.

3. Breakpoints can be: conditional, method entry/exit, enabled/disabled, or number of iterations.

4. Set a breakpoint and set it after a hit count of 256.

5. Use a conditional breakpoint and set argument==null as the condition.

6. Inspecting an object means opening it up in the viewer so that the values of the object can be interrogated and expanded.

7. The expression watches window allows arbitrary expressions to be set.

8. Multiple statements can be set in the breakpoint conditions provided that there is a return statement at the end.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}