@see http://www.aosabook.org/en/eclipse.html
1.Eclipse was described as "an integrated development environment (IDE) for anything and nothing in particular.
2.The first committers who worked on this open source project were employees of an IBM subsidiary called Object Technology International (OTI).
3.Each of these projects is included in a top-level project (TLP) which is managed by a project management committee (PMC) consisting of senior members of the project nominated for the responsibility of setting technical direction and release goals.
4.Early versions of the Eclipse SDK architecture had three major elements, which corresponded to three major sub-projects: the Platform, the JDT (Java Development Tools) and the PDE (Plug-in Development Environment).
5.The Eclipse platform is written using Java and a Java VM is required to run it. It is built from small units of functionality called plugins.
6.One of the most important concepts about Eclipse is that everything is a plugin. Whether the plugin is included in the Eclipse platform, or you write it yourself, plugins are all first class components of the assembled application.
7.The workbench is the most familiar UI element to users of the Eclipse platform, as it provides the structures that organize how Eclipse appears to the user on the desktop. The workbench consists of perspectives, views, and editors.
8.The Eclipse workbench is built on the Standard Widget Toolkit (SWT) and JFace.
9.Unlike other computer languages such as C and C++, the first versions of Java came with a native widget toolkit library called the Abstract Window Toolkit (AWT).
10.JFace is a layer on top of SWT that provides tools for common UI programming tasks, such as frameworks for preferences and wizards. Like SWT, it was designed to work with many windowing systems. However, it is pure Java code and doesn't contain any native platform code.
11.Around 1999, OTI was using Java to implement a product called VisualAge Micro Edition.
12.JFace is a layer on top of SWT that provides tools for common UI programming tasks, such as frameworks for preferences and wizards. Like SWT, it was designed to work with many windowing systems. However, it is pure Java code and doesn't contain any native platform code.
13.The platform also provided an integrated help system based upon small units of information called topics.
14.One of the goals of the Eclipse project was to encourage open source and commercial consumers of this technology to extend the platform to meet their needs, and one way to encourage this adoption is to provide a stable API.
15.The JDT provides Java editors, wizards, refactoring support, debugger, compiler and an incremental builder.
16.The Equinox project was created as a new incubator project at Eclipse. The goal of the Equinox project was to replace the Eclipse component model with one that already existed, as well as provide support for dynamic plugins. The solutions under consideration included JMX, Jakarta Avalon and OSGi.
17.With the switch to OSGi, Eclipse plugins became known as bundles. A plugin and a bundle are the same thing: They both provide a modular subset of functionality that describes itself with metadata in a manifest.
18.With the OSGi version numbering scheme, each bundle has a unique identifier consisting of a name and a four part version number.
19.Equinox p2 is all about installation units (IU). An IU is a description of the name and id of the artifact you are installing.
20.Both the Eclipse extensions registry and OSGi services are examples of service programming models. By convention, a service programming model contains service producers and consumers. The broker is responsible for managing the relationship between producers and consumers.
21.The component-based architecture of Eclipse has evolved to incorporate new technology while maintaining backward compatibility. This has been costly, but the reward is the growth of the Eclipse community because of the trust established that consumers can continue to ship products based on a stable API.
1.Eclipse was described as "an integrated development environment (IDE) for anything and nothing in particular.
2.The first committers who worked on this open source project were employees of an IBM subsidiary called Object Technology International (OTI).
3.Each of these projects is included in a top-level project (TLP) which is managed by a project management committee (PMC) consisting of senior members of the project nominated for the responsibility of setting technical direction and release goals.
4.Early versions of the Eclipse SDK architecture had three major elements, which corresponded to three major sub-projects: the Platform, the JDT (Java Development Tools) and the PDE (Plug-in Development Environment).
5.The Eclipse platform is written using Java and a Java VM is required to run it. It is built from small units of functionality called plugins.
6.One of the most important concepts about Eclipse is that everything is a plugin. Whether the plugin is included in the Eclipse platform, or you write it yourself, plugins are all first class components of the assembled application.
7.The workbench is the most familiar UI element to users of the Eclipse platform, as it provides the structures that organize how Eclipse appears to the user on the desktop. The workbench consists of perspectives, views, and editors.
8.The Eclipse workbench is built on the Standard Widget Toolkit (SWT) and JFace.
9.Unlike other computer languages such as C and C++, the first versions of Java came with a native widget toolkit library called the Abstract Window Toolkit (AWT).
10.JFace is a layer on top of SWT that provides tools for common UI programming tasks, such as frameworks for preferences and wizards. Like SWT, it was designed to work with many windowing systems. However, it is pure Java code and doesn't contain any native platform code.
11.Around 1999, OTI was using Java to implement a product called VisualAge Micro Edition.
12.JFace is a layer on top of SWT that provides tools for common UI programming tasks, such as frameworks for preferences and wizards. Like SWT, it was designed to work with many windowing systems. However, it is pure Java code and doesn't contain any native platform code.
13.The platform also provided an integrated help system based upon small units of information called topics.
14.One of the goals of the Eclipse project was to encourage open source and commercial consumers of this technology to extend the platform to meet their needs, and one way to encourage this adoption is to provide a stable API.
15.The JDT provides Java editors, wizards, refactoring support, debugger, compiler and an incremental builder.
16.The Equinox project was created as a new incubator project at Eclipse. The goal of the Equinox project was to replace the Eclipse component model with one that already existed, as well as provide support for dynamic plugins. The solutions under consideration included JMX, Jakarta Avalon and OSGi.
17.With the switch to OSGi, Eclipse plugins became known as bundles. A plugin and a bundle are the same thing: They both provide a modular subset of functionality that describes itself with metadata in a manifest.
18.With the OSGi version numbering scheme, each bundle has a unique identifier consisting of a name and a four part version number.
19.Equinox p2 is all about installation units (IU). An IU is a description of the name and id of the artifact you are installing.
20.Both the Eclipse extensions registry and OSGi services are examples of service programming models. By convention, a service programming model contains service producers and consumers. The broker is responsible for managing the relationship between producers and consumers.
21.The component-based architecture of Eclipse has evolved to incorporate new technology while maintaining backward compatibility. This has been costly, but the reward is the growth of the Eclipse community because of the trust established that consumers can continue to ship products based on a stable API.
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
