Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "E4/Resources"
< E4
Line 4: | Line 4: | ||
concept of a '''Project''' more flexible. | concept of a '''Project''' more flexible. | ||
− | '''The | + | '''The Goals''' are to |
− | to better adapt to the way how their users are working, provide simpler | + | * enable Eclipse-based products (and especially IDE's) to better adapt to the way how their users are working, |
− | and safer programming models, building a solid base of Eclipse for the | + | * provide simpler and safer programming models enabling more concurrency, |
− | next 10 years. | + | * be competitive with (Visual Studio, Slickedit, Netbeans, IDEA) and other IDE's, |
+ | * integrate with (Maven, Proprietary project systems...) and other project systems where appropriate, | ||
+ | * enable future programming models (client/server, distributed, web, collaborative), | ||
+ | * building a solid base of Eclipse for the next 10 years. | ||
− | Interested Parties: | + | '''Interested Parties:''' |
* Wind River - Doug Schaefer (Lead), [[User:martin.oberhuber.windriver.com|Martin Oberhuber]] | * Wind River - Doug Schaefer (Lead), [[User:martin.oberhuber.windriver.com|Martin Oberhuber]] | ||
− | Documents: | + | '''Documents:''' |
* [[E4/Resources/Brainstorming]] - Notes and Ideas from early meetings | * [[E4/Resources/Brainstorming]] - Notes and Ideas from early meetings | ||
+ | * [[E4/Resources/Comparison]] - Comparison of Eclipse with other systems | ||
* [[E4/Resources|Work Areas]] - Planning | * [[E4/Resources|Work Areas]] - Planning | ||
* [[E4/Resources/Meeting Notes]] | * [[E4/Resources/Meeting Notes]] |
Revision as of 10:41, 4 September 2008
The E4 Resources work is about improving Eclipse Platform Resources,
both in terms of APIs and end-user usability.
The Flexible Resource Model is especially about making the
concept of a Project more flexible.
The Goals are to
- enable Eclipse-based products (and especially IDE's) to better adapt to the way how their users are working,
- provide simpler and safer programming models enabling more concurrency,
- be competitive with (Visual Studio, Slickedit, Netbeans, IDEA) and other IDE's,
- integrate with (Maven, Proprietary project systems...) and other project systems where appropriate,
- enable future programming models (client/server, distributed, web, collaborative),
- building a solid base of Eclipse for the next 10 years.
Interested Parties:
- Wind River - Doug Schaefer (Lead), Martin Oberhuber
Documents:
- E4/Resources/Brainstorming - Notes and Ideas from early meetings
- E4/Resources/Comparison - Comparison of Eclipse with other systems
- Work Areas - Planning
- E4/Resources/Meeting Notes