Eclipse IDE插件开发指南

需积分: 10 63 浏览量更新于2024-07-26 1 收藏 20.18MB PDF 举报

"Eclipse 插件开发指南" 在Java开发领域，Eclipse作为一个免费、开源且功能强大的集成开发环境(IDE)，受到了广泛欢迎。本文主要针对那些希望在Eclipse中进行插件开发的用户，包括想要定制Eclipse、为企业员工开发工具、销售与自身产品配套工具或以其他品牌销售预装工具的开发者。要开始Eclipse插件开发，你需要具备基本的Eclipse使用经验和Java编程能力，同时熟悉标准Widget工具包(SWT)。首先，确保已安装Eclipse。如果你已经有了Eclipse 3，可以跳过安装步骤。若未安装，可以从Eclipse的官方网站下载最新稳定版，例如写作时的eclipse-SDK-3.0.1-win32.zip，将其解压缩到指定文件夹，如c:\dev。这将创建c:\dev\eclipse文件夹。 Eclipse插件开发涉及到以下几个关键知识点： 1. **Plug-in Development Environment (PDE)**：Eclipse提供了一个称为PDE的工具集，用于构建、调试和打包Eclipse插件。通过PDE，开发者可以在Eclipse内创建新的项目，编写代码，然后直接在IDE内进行测试。 2. **Plugin Manifest**：每个Eclipse插件都有一个名为MANIFEST.MF的文件，其中定义了插件的基本信息，包括插件ID、版本号、依赖项等。这是插件系统识别和管理插件的关键。 3. **Extension Points**：Eclipse的扩展点允许插件向Eclipse工作台（Workbench）添加新的功能。开发者可以通过定义扩展点来扩展Eclipse的现有功能或与其他插件交互。 4. **SWT and JFace**：标准Widget工具包（SWT）和Java Faces（JFace）是Eclipse界面构建的基础。SWT提供了操作系统级别的窗口和控件，而JFace则提供了一种抽象层，简化了UI开发。 5. **RCP (Rich Client Platform)**：Eclipse的RCP框架允许开发者创建基于Eclipse的桌面应用程序，利用Eclipse的插件架构和丰富的特性。 6. **Debugging and Testing**：Eclipse的内置调试器支持插件的调试，开发者可以直接在开发环境中对插件进行测试和调试。 7. **PDE Build**：PDE Build工具用于自动化插件的构建过程，包括编译、打包和签名，确保插件可以安全地分发和安装。 8. **插件部署**：开发完成后，插件可以作为Eclipse更新站点的一部分发布，或者以可执行的RCP应用形式分发。 9. **插件生命周期**：理解插件的启动、激活、运行以及关闭过程，对于编写响应用户操作和系统事件的插件至关重要。 10. **API 知识**：掌握Eclipse API，能够有效地调用和利用Eclipse提供的各种服务和功能。通过学习和实践这些知识点，开发者可以创建出满足特定需求的Eclipse插件，增强Eclipse的功能，提升开发效率，甚至构建出全新的桌面应用程序。

xxxvii

Preface

When 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 com-

pany was using a mix of technology composed of a hodgepodge of C/C++,

Java, and Smalltalk.

Many of IBM’s most important tools, including the award-winning Visual-

Age for Java IDE, were actually written in Smalltalk—a 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 out-

side 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 impor-

tant, 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 fam-

ily 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.

(FOLSVH3OXJLQV7KLUG(GLWLRQ 3DJH 5HWXUQWR7DEOHRI&RQWHQWV

xxxviii

Preface

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 rep-

licate 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 devel-

opment 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 pre-

mier 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 com-

puter 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) and an eclectic user base also afflicted these environments

and, by extension, us.

As an Advanced IBM Business Partner, we were fortunate to have built a

long and trusted relationship with the folks at IBM responsible for the creation

of Eclipse. That relationship meant that we were in a unique position to be

briefed on the technology and to start using it on a daily basis nearly a year and

half before the rest of the world even heard about it. When IBM finally

announced Eclipse to the world in mid-2001, our team at Instantiations had

built some of the first demo applications IBM had to show. Later that year

when IBM released its first Eclipse-based commercial tool, WebSphere Studio

Application Developer v4.0 (v4.0 so that it synchronized with its then current

VisualAge for Java v4.0), our CodePro product became the very first commer-

cial add-on available for it (and for Eclipse in general) on the same day.

Currently, the CodePro product adds hundreds of enhancements to

Eclipse and any Eclipse-based IDE. Developing CodePro over the last several

years has provided us with an opportunity to learn the details of Eclipse devel-

opment at a level matched by very few others (with the obvious exception of

the IBM and OTI developers, who eat, sleep, and breathe this stuff on a daily

basis). CodePro has also served as a testbed for many of the ideas and tech-

(FOLSVH3OXJLQV7KLUG(GLWLRQ 3DJH 5HWXUQWR7DEOHRI&RQWHQWV

Preface

xxxix

niques presented in this book, providing us with a unique perspective from

which to write.

Goals of the Book

This book, originally titled Eclipse: Building Commercial-Quality Plug-ins,

provides an in-depth description of the process involved in building commer-

cial-quality extensions for the Eclipse and the IBM Software Development

Platform (SDP)—IBM’s commercial version of Eclipse—development envi-

ronments. To us, “commercial-quality” is synonymous with “commercial-

grade” or “high-quality.” Producing a commercial-quality plug-in means

going above and beyond the minimal requirements needed to integrate with

Eclipse. It means attending to all those details that contribute to the “fit and

polish” of a commercial offering.

In the world of Eclipse plug-ins, very few people take the time to really go

the extra mile, and most plug-ins fall into the open source, amateur category.

For folks interested in producing high-quality plug-ins (which would certainly

be the case for any software company wanting to develop Eclipse-based prod-

ucts), there are many details to consider. Our book is meant to encompass the

entire process of plug-in development, including all the extra things that need

to be done to achieve high-quality results. This book has several complemen-

tary goals:

• Provide a quick introduction to using Eclipse for new users

• Provide a reference for experienced Eclipse users wishing to expand their

knowledge and improve the quality of their Eclipse-based products

• Provide a detailed tutorial on creating sophisticated Eclipse plug-ins suit-

able for new and experienced users

The first three chapters introduce the Eclipse development environment

and outline the process of building a simple plug-in. The intention of these

chapters is to help developers new to Eclipse quickly pull together a plug-in

they can use to experiment with.

The first chapter, in particular, introduces the reader to the minimum set

of Eclipse tools that he or she will need to build plug-ins. It is a fairly quick

overview of the Eclipse IDE and relevant tools (one could write an entire book

on that topic alone), and we would expect expert Eclipse users to skip that

chapter entirely.

The second chapter introduces the example that we will use throughout

most of the book and provides a very quick introduction to building a working

plug-in from start to finish. The third chapter presents a high-level overview of

the Eclipse architecture and the structure of plug-ins and extension points.

(FOLSVH3OXJLQV7KLUG(GLWLRQ 3DJH 5HWXUQWR7DEOHRI&RQWHQWV

Preface

The fourth and fifth chapters cover the Standard Widget Toolkit (SWT)

and JFace, which are the building blocks for all Eclipse user interfaces (UIs).

These chapters can act as a stand-alone reference; they are intended to provide

just enough detail to get you going. Both of these topics are rich enough to

warrant entire books and several are currently available.

The subsequent chapters, comprising the bulk of this book, focus on

describing each of the various aspects of plug-in development and providing

the reader with in-depth knowledge of how to solve the various challenges

involved. Each chapter focuses on a different aspect of the problem, and

includes an overview, a detailed description, a discussion of challenges and

solutions, diagrams, screenshots, cookbook-style code examples, relevant API

listings, and a summary.

We have structured the book so that the most important material required

for every plug-in project appears in the first half of it. Some of the packaging-

and building-oriented material is placed at the end (for example, features and

product builds). This organizational scheme left several topics that, while not

critical to every plug-in, were important to the creation of commercial-quality

plug-ins. These topics have been placed in the second half of the book in an

order based on the importance of each and how it related to earlier material.

Internationalization, for example, is one of those topics. It isn’t critical, and it

isn’t even all that complicated when you get right down to it. It is, however,

important to the book’s premise, so we felt it was a topic we needed to include.

Since we aren’t assuming that the reader is an Eclipse expert (or even a plug-

in developer), we have tried to take the reader through each of the important

steps in as much detail as possible. While it is true that this is somewhat intro-

ductory, it is also an area that most plug-in developers totally ignore and have

little or no experience with.

Sometimes a developer needs a quick solution, while at other times that

same developer needs to gain in-depth knowledge about a particular aspect of

development. The intent is to provide several different ways for the reader to

absorb and use the information so that both needs can be addressed. Relevant

APIs are included in several of the chapters so that the book can be used as a

stand-alone reference during development without requiring the reader to

look up those APIs in the IDE. Most API descriptions are copied or para-

phrased from the Eclipse platform Javadoc.

As the originators of Eclipse and a major consumer of Eclipse-based tech-

nology, IBM is justifiably concerned that new plug-ins meet the same high-

quality standards that IBM adheres to. To that end, IBM has established a rig-

orous Ready for Rational Software (RFRS) certification program meant to

(FOLSVH3OXJLQV7KLUG(GLWLRQ 3DJH 5HWXUQWR7DEOHRI&RQWHQWV

剩余856页未读，继续阅读

tianlijian

粉丝: 0
资源: 8

Eclipse IDE插件开发指南

Eclipse插件开发学习笔记.pdf

eclipse插件开发指南.pdf

eclipse插件开发书源代码

eclipse插件开发第三版源码

eclipse插件开发笔记源码

eclipse插件开发 第三版 pdf

eclipse插件开发学习笔记 源码

eclipse 插件开发调试

eclipse插件开发中文教程

eclipse插件开发 gui画面

最新资源

eclipse插件开发第三版 pdf

eclipse插件开发学习笔记源码