Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "E4/Project Proposal"
(→Background) |
(→Scope) |
||
| Line 10: | Line 10: | ||
== Scope == | == Scope == | ||
| + | The mission of the e4 project is to build a next generation platform for pervasive, component-based applications and tools. | ||
| + | |||
| + | Specifically, efforts will be directed towards but not limited to: | ||
| + | * Simplify the programming model, make it easier to write plugins | ||
| + | More uniform APIs | ||
| + | Rationalized and consistent application model exposed as services | ||
| + | Scripting (initially Javascript) | ||
| + | Plugins in other (non-Java) languages | ||
| + | More flexible, sophisticated UI styling | ||
| + | DOM based access to model of workbench | ||
| + | Improve separation of appearance and underlying function | ||
| + | Enable a broader array of applications to be built from Eclipse | ||
| + | Scale down to simpler RCP applications | ||
| + | Server-enabled Eclipse to permit Eclipse in a web browser | ||
| + | Client/server programming | ||
| + | Remote workspaces | ||
| + | RESTful services against workbench DOM | ||
| + | Multi-user enable the platform | ||
| + | SWT Browser Edition: SWT widgets in native web technologies (e.g. Dojo, Flex, Silverlight) | ||
| + | More flexible resource model. | ||
| + | |||
| + | As this is first and foremost a community effort, the actual set of items will expand and change to reflect the interests of those who join e4. | ||
| + | |||
| + | Also of importance are the necessary tools to be able to self-host, i.e. to develop e4 using tools based on e4. Wherever appropriate, we will use or adapt tools that already exist in other Eclipse pojects. | ||
| + | |||
| + | We expect the resulting platform to be backwards-compatible to Eclipse 3.x for API-clean plug-ins, possibly at the cost of 3.x plugins depending on compatibility plug-ins. | ||
== Organization == | == Organization == | ||
Revision as of 15:40, 21 July 2008
Contents
Introduction
The Eclipse e4 Project is a proposed open source project under the Eclipse Project.
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process document) and is written to declare its intent and scope. This proposal is written to solicit additional participation and input from the Eclipse community. You are invited to comment on and/or join the project. Please send all feedback to the https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev mail list.
Background
The Eclipse platform was first targetted to building an extensible IDE component framework. It has since grown to into Rich Client Platform, enabling whole new categories of scenarios and domains. As the software landscape changes, so must the Eclipse platform in order to remain relevant and vibrant. These trend lines point to web technologies, new user interface metaphors, and distributed infrastructure. Now is the time to rethink elements of the platform so that Eclipse may remain at the forefront of application development.
Description
Scope
The mission of the e4 project is to build a next generation platform for pervasive, component-based applications and tools.
Specifically, efforts will be directed towards but not limited to:
* Simplify the programming model, make it easier to write plugins
More uniform APIs Rationalized and consistent application model exposed as services Scripting (initially Javascript) Plugins in other (non-Java) languages More flexible, sophisticated UI styling DOM based access to model of workbench Improve separation of appearance and underlying function Enable a broader array of applications to be built from Eclipse Scale down to simpler RCP applications Server-enabled Eclipse to permit Eclipse in a web browser Client/server programming Remote workspaces RESTful services against workbench DOM Multi-user enable the platform SWT Browser Edition: SWT widgets in native web technologies (e.g. Dojo, Flex, Silverlight) More flexible resource model.
As this is first and foremost a community effort, the actual set of items will expand and change to reflect the interests of those who join e4.
Also of importance are the necessary tools to be able to self-host, i.e. to develop e4 using tools based on e4. Wherever appropriate, we will use or adapt tools that already exist in other Eclipse pojects.
We expect the resulting platform to be backwards-compatible to Eclipse 3.x for API-clean plug-ins, possibly at the cost of 3.x plugins depending on compatibility plug-ins.