Difference between revisions of "E4/Resources"

From Eclipsepedia

< E4
Jump to: navigation, search
Line 11: Line 11:
  
 
'''The Goals''' are listed in detail on the [[E4/Resources/Requirements|Requirements]] page, in short:
 
'''The Goals''' are listed in detail on the [[E4/Resources/Requirements|Requirements]] page, in short:
* Enable Eclipse-based products to better adapt to the way how their users are working -
+
* Make the Workspace, Project and Resource structure flexible enough to embrace any existing (legacy) structures.
** support very '''large workspaces''' and aliasing (symbolic links) well,
+
* Build an architecture that's easy to understand, reliable, simple and safe to code against.
** allow '''importing''' any legacy project and file system structures,
+
* Support future environments (client/server, distributed, web, collaborative) - building a solid base of Eclipse for the 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 environments (client/server, distributed, web, collaborative),
+
* provide simpler and safer programming models enabling more concurrency,
+
* '''building a solid base of Eclipse for the next 10 years.'''
+
  
 
'''Interested Parties:''' (alphabetically) - See also the [[E4/Resources/Meeting/19-Sep-2008 Kick-off#Interested_Parties_and_Background|Kick-off meeting]]:
 
'''Interested Parties:''' (alphabetically) - See also the [[E4/Resources/Meeting/19-Sep-2008 Kick-off#Interested_Parties_and_Background|Kick-off meeting]]:

Revision as of 12:33, 24 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 listed in detail on the Requirements page, in short:

  • Make the Workspace, Project and Resource structure flexible enough to embrace any existing (legacy) structures.
  • Build an architecture that's easy to understand, reliable, simple and safe to code against.
  • Support future environments (client/server, distributed, web, collaborative) - building a solid base of Eclipse for the next 10 years.

Interested Parties: (alphabetically) - See also the Kick-off meeting:

  • Broadcom, Embarcadero, Freescale, Google, IBM, Nokia, NVidia, Wind River
  • Component Lead: Doug Schaefer (Wind River)

Documents:

Communication Channels

This calendar is available in the following formats:
Ical.gifiCal,Xml.gifATOM News Feed,Html.gifHTML