《计算机编程类外文翻译.doc》由会员分享，可在线阅读，更多相关《计算机编程类外文翻译.doc（27页珍藏版）》请在三一文库上搜索。
1、本科毕业设计外文文献及译文文献、资料题目：Eclipse Distilled文献、资料来源：Eclipse Distilled 文献、资料发表（出版）日期：2005.2.14院 （部）： 理学院专 业： 信息与计算科学班 级： 信计姓 名： 学 号： 指导教师： 翻译日期： 2012.5.12外文文献：Chapter 1. A Java IDE and So Much More!Looking at Eclipse is similar to looking at a well-cut diamond. What you see depends on the angle of your vie
2、w and on how deeply you gaze into the interior. To some viewers Eclipse is a Java IDE with the usual features one expects from such an environment: editor, debugger, and project builder with a wide array of preference customizations. To others Eclipse is a generic framework for tool integration prov
3、iding an extensive, flexible plug-in API. The www.eclipse.org home page declares that Eclipse is a kind of universal tool platforman open extensible IDE for anything and nothing in particular.Both perspectives are valid interpretations. As the Eclipse community continues its rapid expansion, other u
4、sers will see it as a modeling tool, a business rules management application, a business process designer, a development environment for embedded systems written in C+, or an HTML authoring and document management environment. Using the Rich Client Platform (RCP) configuration, Eclipse is the basis
5、for any end-user client application.Many books have been and will be written to describe each facet of the Eclipse diamond. This book focuses on Eclipse as an integrated development environment for building Java applications. Those applications may be other open source utilities, large enterprise sy
6、stems, or new plug-ins for Eclipse. This book is equally applicable to each of those project teams and individuals.Eclipse is developed by and for teams using a modern, agile development process. Eclipse is developed using Eclipse in a large, distributed team and with an iterative approach that rebu
7、ilds and tests the entire project every night. As a result, Eclipse is well suited to any project using these methods. This book describes several best practices common to agile development teams and explains in detail how Eclipse assists you in those tasks.In this chapter, well view these facets of
8、 Eclipse:Building blocks of the Eclipse platform architecture.Development components provided by other Eclipse projects.Alignment of Eclipse with the principles of agile development.1.1. Eclipse Platform ArchitectureGiven the wide-ranging interpretations of Eclipse, it is difficult to present a quic
9、k summary of its architecture. The most general description is an abstract view of the development and runtime environment for creating and deploying plug-in contributions. Alternatively, we can take a functional view that describes Eclipse as a flexible, extensible integrated development environmen
10、t (IDE). Well take the latter viewpoint and focus our attention on how Eclipse provides an unparalleled opportunity to improve productivity of software development work.The Eclipse IDE is as follows:Multi-platform. The target operating systems of Eclipse 3.0 are Windows, Linux (motif and GTK), Solar
11、is, AIX, HP-UX, and Mac OSX.Multi-language. Eclipse is developed using the Java language, but it supports writing applications in Java, C/C+, and Cobol; additional language support is being developed for Python, Perl, PHP, and others. Plug-in contributions to Eclipse must be written in Java.Multi-ro
12、le. In addition to programming activities, Eclipse supports modeling, testing, Web authoring, and many other roles.The functional building blocks of the Eclipse IDE are illustrated in Figure 1-1. Each block added to the structure builds on the foundation of those below it. Its this modular nature of
13、 the Eclipse platform that has led to its unprecedented growth. The entire platform is open source and royalty-free for other open source or commercial products that add new building blocks.Figure 1-1. Functional building blocks of the Eclipse development environment.The shaded blocks represent this
14、 books focus. However, along the way well review other contributed plug-ins that enhance the platforms capabilities for specialized tasks. Examples are unit-testing frameworks for Web-based applications, static code analysis tools, and a style checker that ensures consistent use of coding standards.
15、The next several sections introduce each of the building blocks shown in Figure 1-1.1.1.1. Eclipse Runtime PlatformThe core runtime platform provides the most basic level of services:Plug-in registry. Loading plug-ins and managing a registry of available plug-ins.Resources. Managing a platform-indep
16、endent view of operating system files and folders, including linked resource locations.UI components. The Eclipse user interface components are based on SWT and JFace libraries.Update facility. Eclipse applications have built-in support for installing and updating plug-ins from URL addressable locat
17、ions, including remote Internet sites.Help facility. A common help facility is shared by all plug-ins.The Eclipse model for platform-independent resources is an important foundation for representing projects, folders, and files in an IDE; we review this in Chapter 3, Managing Your Projects. The upda
18、te facility assists you in customizing your IDE with new plug-in contributions; we review it in Chapter 9, Updating the Eclipse IDE.All of these basic services are implemented as plug-ins on a very small kernel. The Eclipse design makes everything a plug-in. The intent was to treat all developers (a
19、nd all plug-ins) the same. This ensures that the facilities are both sufficient for the platform itself and for any clients.1.1.2. Integrated Development EnvironmentThe Eclipse IDE provides a common user experience across multi-language and multi-role development activities. Other contributed plug-i
20、ns that build on this IDE foundation dont need to reinvent the wheel.The most significant IDE features are as follows:Shared views. Many Eclipse features share the use of common views for displaying and editing properties, for listing syntax problems found in the code, and for listing work tasks.Per
21、spectives. A perspective collects a related group of views in a layout suited to particular tasks, such as Java development, debugging, and version control.Preferences. A centralized dialog gathers preference setting pages for all plug-ins installed in the workbench.Search engine. The platform searc
22、h engine provides general capabilities for searching resources and presenting results. This facility can be extended with resource-specific search criteria, e.g., for Java, C+, or UML model resources.Debugging. Defines a language-independent debug model and UI classes for building debuggers and laun
23、chers.Ant project build files. Ant provides general-purpose, flexible build services that can be extended with specialized tasks. The IDE includes an Ant editor and runtime configuration.Team-oriented. Eclipse provides a generic API for integration with version control repositories. Complete support
24、 for CVS is included, and plug-ins are available for other vendors repositories.In Chapter 4, Customizing Your Workbench, well study the use of Eclipse perspectives, views, and preferences. The debugger is covered in Chapter 7, Debugging Your Code, and Ant build files are used in Chapter 12, Continu
25、ous Integration with Ant. The team-oriented capabilities are covered in Chapter 13, Team Ownership with CVS.There are additional Eclipse IDE features that are not provided in a generic way by the platform, but users have learned to expect the following capabilities in editors:Synchronized editor and
26、 outline. An outline displays a hierarchical list of constructs in the file being edited. Select an outline item to position the editor at the corresponding location.Content Assist. The editor suggests appropriate content to be inserted at the cursor location when the Ctrl+Space key combination is p
27、ressed.Templates. Code or other text patterns (such as a Java for loop or an HTML table) are defined in templates that are inserted into a file as part of Content Assist.Formatter. Syntactic formatting rules are defined and customized in preference settings and are applied to editor selections or en
28、tire files.Problems identified on-the-fly. Errors or warnings are identified while typing in the editor and are highlighted by icons and messages in the ruler at the editor left margin.Well use these features while studying the Java editor in Chapter 5, Rapid Development, and then well see them agai
29、n while using the Ant build file editor in Chapter 12.1.1.2.1 Java Development ToolsJava Development Tools (JDT) are the only programming language plug-ins included with the Eclipse SDK. However, other language tools are available or under development by Eclipse subprojects and plug-in contributors.
30、 The Eclipse Java development perspective is shown in Figure 1-2.Figure 1-2. Eclipse Java development perspective.View full size imageFundamental capabilities provided by the Java tools include the following:Editor, outline, Content Assist, templates, and formatting. These general editor features ar
31、e provided for Java source files.Java views. Several views are provided for navigating and managing Java projects. The Package Explorer view is the cornerstone of the Java perspective, and a specialized Java Browsing perspective assists developers in understanding and navigating large, multi-project
32、 applications.Project Configuration. Extensive support is included for configuring Java project classpaths, dependencies, libraries, compiler options, and many other characteristics.Debugger. A rich debugging environment is provided by the Java tools. You can set breakpoints, step through execution,
33、 inspect and set variable values, and change method code during debugging.We cover Java project configuration in Chapter 6, Java Project Configuration, and debugging in Chapter 7. The Java tools devote special attention to supporting agile development techniques. Section 1.3, Agile Development with
34、Eclipse, introduces this topic with more detail, and Part 2 of this book, Getting Agile, is dedicated to studying agile development in Eclipse.1.1.2.2 C/C+ Development ToolsThe C/C+ Development Tools (CDT) project is creating a fully functional C and C+ IDE for the Eclipse platform. The current focu
35、s is on developing and deploying on Linux, but this projects leaders are interested in participation from contributors who would like to extend the work in other directions. For example, targeting Windows, Unix, or embedded platforms and providing wizards that assist development with particular libr
36、ary, database, or messaging APIs.The CDT 2.0 release includes the following:C/C+ editor. The generic platform text editor is specialized with C/C+ syntax coloring, Content Assist, and formatting.C/C+ debugger. A default debugger implementation is provided using GDB.C/C+ program launcher. Similar to
37、launching Java programs with optional debugging, CDT provides support for launching C/C+ programs.C/C+ parser and syntax API. The parser is an essential foundation for other plug-in contributions that extend CDT.Search engine. General platform search facilities are specialized with C/C+ syntax optio
38、ns that accurately locate code definitions and references.Makefile generator. Similar to the use of Ant in Java development, makefiles are ubiquitous in development of C/C+ projects.Details and downloads are available on the CDT Web site, www.eclipse.org/cdt/.1.1.2.3 Plug-in Development EnvironmentT
39、he Plug-in Development Environment (PDE) supplies tools that automate the creation, manipulation, debugging, and deploying of plug-ins. The PDE is part of the Eclipse SDK and is not a separately launched tool. In line with the general Eclipse platform philosophy, the PDE provides a wide variety of p
40、latform contributions (e.g., views, editors, wizards, launchers, etc.) that blend transparently with the rest of the Eclipse workbench and assist the developer in every stage of plug-in development while working inside the Eclipse workbench.PDE perspective. A specialized perspective includes views a
41、nd shortcuts to commands used most frequently during plug-in development.Host Versus Runtime workbench. The workbench that you are running as you develop your plug-in is the host workbench. After you are happy with your plug-in and want to test it, you can launch another workbenchthe runtime workben
42、ch. This will utilize the same plug-ins as the host workbench, but it will also run the plug-ins you were working on in the host workbench.Debugging plug-ins. The Java debugger enables complete control while testing plug-ins in the runtime workbench.Packaging plug-ins. Tools for packaging plug-ins a
43、nd features for distribution to users via an update site are provided.This book does not address plug-in development specifically, but all Eclipse capabilities described here are applicable to the PDE. Other books in this series describe patterns for plug-in development (Gamma and Beck, 2004) and co
44、ver the details of building commercial-quality plug-ins (Clayberg and Rubel, 2004).1.1.2.4 Web Tools PlatformThe Web Tools Platform (WTP) project was formally approved by the Eclipse Board in June 2004 and received initial open source code contributions from IBM and Object Web. At the time this book
45、 was written, those contributions were being reviewed and assimilated into the first milestone integration build. This project is of great importance to the Eclipse community and is likely of interest to most readers of this book. It is still in a formative stage; nonetheless, here we review the pro
46、jects charter and summarize its expected integration into the Eclipse IDE.The mission of the Web Tools Platform project is to provide a generic, extensible, and standards-based tool platform that builds on the Eclipse platform and other core Eclipse technologies. The project will deliver a common fo
47、undation of frameworks and services upon which software providers can create specialized, differentiated offerings for J2EE and Web-centric application development. Key objectives are to enable product innovation with adherence to vendor-neutral standards and technologies while delivering practical
48、solutions to real development concerns.The WTP project is composed of two parts. The Web Standard Tools subproject will provide a common infrastructure targeting Web-enabled applications. This includes tools for developing three-tier applications (presentation, business, and data logic) and publishi
49、ng the resulting system artifacts to servers.Tools provided by this subproject will include the following:Standard languages. Support will be provided for HTML/XHMTL, XML, XML Schema, Web Services, XQueries, SQL, and other languages used by Web-centric applications.Editors. Editors will be provided for supported languages, in