Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "E4/Resources"

< E4
 
(9 intermediate revisions by 3 users not shown)
Line 10: Line 10:
 
concept of a '''Project''' more flexible.
 
concept of a '''Project''' more flexible.
  
'''The Goals''' are to
+
'''The Goals''' are listed in detail on the [[E4/Resources/Requirements|Requirements]] page, in short:
* enable Eclipse-based products (and especially IDE's) 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.
* provide simpler and safer programming models enabling more concurrency,
+
* Build an architecture that's easy to understand, reliable, simple and safe to code against.
* be competitive with (Visual Studio, Slickedit, Netbeans, IDEA) and other IDE's,
+
* Support future environments (client/server, distributed, web, collaborative) - building a solid base of Eclipse for the next 10 years.
* 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:''' (alphabetically) - See also the [[E4/Resources/Meeting/19-Sep-2008 Kick-off#Interested_Parties_and_Background|Kick-off meeting]]:
* Wind River - Doug Schaefer (Lead), [[Martin Oberhuber]]
+
* Broadcom, Cloudsmith, Embarcadero, Freescale, Google, IBM, Nokia, NVidia, Wind River
* Freescale Semiconductor - [[User:sergebeauchamp.mac.com|Serge Beauchamp]]
+
* Component Lead: '''Doug Schaefer (Wind River)'''
  
 
'''Documents:'''
 
'''Documents:'''
 +
* [[E4/Resources/Strawman]] - Strawman proposal
 
* [[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/Comparison]] - Comparison of Eclipse with other systems
 +
* [[E4/Resources/Requirements]], Use-Cases and Goals
 +
* [[E4/Resources/Definitions of Terms]]
 
* [[E4/Resources/Work Areas]] - Planning
 
* [[E4/Resources/Work Areas]] - Planning
 +
** {{bug|252647}} is the master plan item. Look for bugs blocking on that one.
 
* [[E4/Resources/Meeting Notes]] - Our meetings are on the E4 Calendar.
 
* [[E4/Resources/Meeting Notes]] - Our meetings are on the E4 Calendar.
  
Line 33: Line 34:
 
<h3>Communication Channels</h3>
 
<h3>Communication Channels</h3>
 
* [https://dev.eclipse.org/mailman/listinfo/platform-core-dev platform-core-dev mailing list]
 
* [https://dev.eclipse.org/mailman/listinfo/platform-core-dev platform-core-dev mailing list]
* [https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev e4 mailing list]
 
* [irc://irc.freenode.net/#eclipse-e4 #eclipse-e4 on irc.freenode.net] - [http://echelog.matzon.dk/logs/browse/eclipse-e4/ logs] (also [[Eclipse_4.0/eclipse-e4-04-07-08 | here]]).
 
 
* [[E4/Resources/Meeting Notes]]
 
* [[E4/Resources/Meeting Notes]]
 
* Bugzilla as per the [[E4/Resources/Work Areas]]
 
* Bugzilla as per the [[E4/Resources/Work Areas]]
 +
* ...as well as the other [[E4]] communication channels
 
<googlecalendar width="100%" height="300" mode="AGENDA" title="e4 Calendar">ctri5teoag0n87t2qu9bla8u3g%40group.calendar.google.com</googlecalendar>
 
<googlecalendar width="100%" height="300" mode="AGENDA" title="e4 Calendar">ctri5teoag0n87t2qu9bla8u3g%40group.calendar.google.com</googlecalendar>
 
This calendar is available in the following formats:<br>
 
This calendar is available in the following formats:<br>

Latest revision as of 06:14, 26 November 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, Cloudsmith, 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

Back to the top