Integrated development Environment Eclipse

Eclipse is a well-known, cross-platform, free-integrated development environment (IDE). It was originally used primarily for Java language development, but it is now being made available as a development tool for other computer languages such as C + + and Python.

Eclipse itself is only a framework platform, but the support of many plugins makes it difficult for eclipse to have the flexibility of other functionally relatively fixed IDE software. Many software developers develop their own IDES in the framework of Eclipse.

Eclipse was originally developed by IBM as an alternative business software for the next Generation IDE development environment of Visual age for Java, which was contributed to the open source community in November 2001 and is now made up of the non-profit software vendor Alliance Eclipse Foundation (eclipse Foundation) management. In 2003, Eclipse 3.0 chose the OSGi Service platform specification as the runtime schema. June 2007, stable version 3.3 released. June 2008 released the 3.4 version codenamed Ganymede.

The foundation of Eclipse is the rich client platform (rich-client Platform, RCP). RCP consists of the following components:

Core platform (launch Eclipse, run plug-in)

OSGi (standard cluster framework)

SWT (Portable Artifact Toolkit)

JFace (file buffer, text processing, text editor)

Eclipse Workbench (Workbench, including views, editor (editors), Perspective (Perspectives), and wizards (Wizards))

The technology that Eclipse uses is developed by IBM (SWT), a Java-based window component that resembles the AWT and swing window components provided by Java itself, but the basic tutorial qkxue.net that SWT is more efficient than other Java window components. Eclipse's user interface also uses the GUI middle tier jface, which simplifies the building of SWT-based applications.

Eclipse's plug-in mechanism is a lightweight software component architecture. On the rich client platform, Eclipse uses plug-ins to provide all the additional functionality, such as support for languages other than Java. Existing decoupled plug-ins have been able to support C/D + + (CDT), Perl, Ruby,python, Telnet, and database development. The plug-in architecture enables the addition of arbitrary extensions to existing environments, such as configuration management, and is never limited to supporting a variety of programming languages.

Eclipse's design idea is that everything is plug-ins. The eclipse core is small and all other features are attached to the Eclipse core as plug-ins. The Eclipse basic kernel includes: Graphics API (SWT/JFACE), Java Development Environment Plug-in (JDT), plug-in development environment (PDE), etc.

Eclipse is made up of a variety of different plans. Some of the plans are listed below.

Eclipse Plan: itself includes the Eclipse platform, the Eclipse Rich client Platform (RCP), and the Java Development Tools (JDT).

Eclipse Test and Performance Tools platform (TPTP): Provides a platform that allows software developers to build test and performance tools such as test debugging, profile analysis, benchmarking, and more.

Eclipse Web Tools Platform Planning (WTP): Extend the Eclipse platform with Java Enterprise Web application development tools. It consists of the following sections: HTML, JavaScript, CSS, JSP, SQL, XML, DTD, XSD, and WSDL source editor, XSD and WSDL graphical interface Editor, Java Enterprise Edition project Nature, Builder and model, with a Java Enterprise Edition of Navigation (Navigator), a Web services (Web Service) wizard and Browser, and a WS-I test tool, and finally a tool and model for database access queries.

Eclipse Business Intelligence and Reporting tools program (BIRT): Provides report development tools for Web applications, especially Java-based Enterprise editions.

Eclipse Visual Interface Editor plan (VEP): A framework for creating a graphical user interface code generator under Eclipse.

Eclipse Modeling Framework (EMF): A tool that generates a structured data model and code for other applications, based on the modeling specifications described with XMI.

Graphical editor Framework (GEF): Enables developers to easily create rich graphical editors with a ready-made application model.

The implementation of a UML 2.0-meta model under the Uml2:eclipse platform to support the development of modeling tools.

AspectJ: A side-oriented language extension for Java.

Eclipse Communications Framework (ECF): Focus on the work of creating a communications application on the Eclipse platform.

Eclipse Data Tools Platform Planning (DTP)

Eclipse Device driver Software development Program (DSDP)

D/C + + development tool Plan (CDT): strives to provide a fully functional C and C + + integrated development Environment (IDE) for the Eclipse platform that uses GCC as a compiler.

Eclipse Platform COBOL Integrated development Environment Sub-plan (COBOL): A full-featured COBOL integrated development environment on an eclipse platform will be built.

Parallel tool Platform (PTP): A parallel tool platform that integrates with a set of tools in a parallel computer architecture, and this platform is portable, scalable, and standards-based.

Embedded rich client Platform (ERCP): Plan to extend the Eclipse rich client platform to embedded devices. This platform is primarily a collection of a subset of the rich client platform (RCP) components. It allows the application model in the desktop environment to be applied to embedded devices in roughly the same way.

Integrated development Environment Eclipse