Eclipse Plug-ins

by ;
  • ISBN13:


  • ISBN10:


  • Edition: 3rd
  • Format: Paperback
  • Copyright: 2008-12-11
  • Publisher: Addison-Wesley Professional
  • View Upgraded Edition
  • Purchase Benefits
  • Free Shipping On Orders Over $35!
    Your order must be $35 or more to qualify for free economy shipping. Bulk sales, PO's, Marketplace items, eBooks and apparel do not qualify for this offer.
  • Get Rewarded for Ordering Your Textbooks! Enroll Now
List Price: $59.99 Save up to $9.00
  • Buy New
    Add to Cart Free Shipping


Supplemental Materials

What is included with this book?

  • The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.
  • The eBook copy of this book is not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.


The definitive book for anyone developing Eclipse plug-ins.

Author Biography

Eric Clayberg is Senior VP for Product Development for Instantiations, Inc., an Advanced IBM Business Partner that serves on the Eclipse Foundation and contributes extensively to the Eclipse initiative. He has more than seventeen years of commercial software development experience, including twelve years with Java and nine with Eclipse. He is primary architect and product manager for many award-winning Java and Smalltalk products, including WindowBuilder Pro, CodePro, and VA Assist. He has a B.S. from MIT, an MBA from Harvard, and has cofounded two successful software companies—ObjectShare and Instantiations.

Dan Rubel,
CTO for Instantiations, Inc., is an entrepreneur and an expert in the design and application of object-oriented technologies with more than fifteen years of commercial software development experience, including thirteen years of experience with Java and nine years with Eclipse. He is the primary architect and product manager for several successful products, including RCP Developer, WindowTester, jFactor, and jKit.  He has a B.S. from Bucknell and is a cofounder of Instantiations.

Table of Contents

Foreword by Skip McGaugheyp. xxxiii
Foreword by Simon Archerp. xxxv
Prefacep. xxxvii
Using Eclipse Toolsp. 1
Getting Startedp. 1
The Eclipse Workbenchp. 3
Setting Up Your Environmentp. 14
Creating a Projectp. 19
Navigatingp. 26
Searchingp. 28
Writing Codep. 35
Team Development Using CVSp. 49
Running Applicationsp. 55
Introduction to Debuggingp. 59
Introduction to Testingp. 63
Introduction to Mylynp. 65
Summaryp. 69
A Simple Plug-in Examplep. 71
The Favorites Plug-inp. 71
Creating a Plug-in Projectp. 72
Reviewing the Generated Codep. 77
Building a Productp. 86
Installing and Running the Productp. 92
Debugging the Productp. 94
PDE Viewsp. 96
Writing Plug-in Testsp. 99
Book Samplesp. 105
Summaryp. 106
Eclipse Infrastructurep. 107
Structural Overviewp. 107
Plug-in Directory or JAR filep. 110
Plug-in Manifestp. 113
Activator or Plug-in Classp. 120
Plug-in Modelp. 126
Loggingp. 128
Eclipse Plug-insp. 132
Summaryp. 133
The Standard Widget Toolkitp. 135
SWT History and Goalsp. 135
SWT Widgetsp. 138
Layout Managementp. 178
Resource Managementp. 188
GUI Buildersp. 190
Summaryp. 191
JFace Viewersp. 193
List-Oriented Viewersp. 193
Text Viewersp. 211
Summaryp. 214
Commands and Actionsp. 215
Commandsp. 216
Menu and Toolbar Contributionsp. 220
Handlersp. 236
Key Bindingsp. 238
IAction versus IActionDelegatep. 240
Workbench Window Actionsp. 242
Object Actionsp. 257
View Actionsp. 270
Editor Actionsp. 277
Actions and Key Bindingsp. 284
RFRS Considerationsp. 286
Summaryp. 287
Viewsp. 289
View Declarationp. 291
View Commandsp. 313
Linking the Viewp. 336
Saving View Statep. 340
Testingp. 345
Image Cachingp. 346
Auto-sizing Table Columnsp. 348
RFRS Considerationsp. 348
Summaryp. 352
Editorsp. 353
Editor Declaration
Table of Contents provided by Publisher. All Rights Reserved.


Preface PrefaceWhen we were first exposed to Eclipse back in late 1999, we were struck by the magnitude of the problem IBM was trying to solve. IBM wanted to unify all its development environments on a single code base. At the time, the company was using a mix of technology composed of a hodgepodge of C/C++, Java, and Smalltalk.PrefaceMany of IBM's most important tools, including the award-winning Visual-Age for Java IDE, were actually written in Smalltalka wonderful language for building sophisticated tools, but one that was rapidly losing market share to languages like Java. While IBM had one of the world's largest collections of Smalltalk developers, there wasn't a great deal of industry support for it outside of IBM, and there were very few independent software vendors (ISVs) qualified to create Smalltalk-based add-ons.Meanwhile, Java was winning the hearts and minds of developers world-wide with its promise of easy portability across a wide range of platforms, while providing the rich application programming interface (API) needed to build the latest generation of Web-based business applications. More important, Java was an object-oriented (OO) language, which meant that IBM could leverage the large body of highly skilled object-oriented developers it had built up over the years of creating Smalltalk-based tools. In fact, IBM took its premiere Object Technology International (OTI) group, which had been responsible for creating IBM's VisualAge Smalltalk and VisualAge Java environments (VisualAge Smalltalk was the first of the VisualAge brand family and VisualAge Java was built using it), and tasked the group with creating a highly extensible integrated development environment (IDE) construction set based in Java. Eclipse was the happy result.OTI was able to apply its highly evolved OO skills to produce an IDE unmatched in power, flexibility, and extensibility. The group was able to replicate most of the features that had made Smalltalk-based IDEs so popular the decade before, while simultaneously pushing the state of the art in IDE development ahead by an order of magnitude.The Java world had never seen anything as powerful or as compelling as Eclipse, and it now stands, with Microsoft's .NET, as one of the world's premier development environments. That alone makes Eclipse a perfect platform for developers wishing to get their tools out to as wide an audience as possible. The fact that Eclipse is completely free and open source is icing on the cake. An open, extensible IDE base that is available for free to anyone with a computer is a powerful motivator to the prospective tool developer.It certainly was to us. At Instantiations and earlier at ObjectShare, we had spent the better part of a decade as entrepreneurs focused on building add-on tools for various IDEs. We had started with building add-ons for Digitalk's Smalltalk/V, migrated to developing tools for IBM's VisualAge Smalltalk, and eventually ended up creating tools for IBM's VisualAge Java (including our award-winning VA Assist product and our jFactor product, one of the world's first Java refactoring tools). Every one of these environments provided a means to extend the IDE, but they were generally not well-documented and certainly not standardized in any way. Small market shares (relative to tools such as VisualBasic)

Rewards Program

Write a Review