Difference between revisions of "E4/Resources"

From Eclipsepedia

< E4
Jump to: navigation, search
 
(23 intermediate revisions by 7 users not shown)
Line 1: Line 1:
<h1>Flexible Resource Model</h1>
+
__NOTOC__
  
* From [[Architecture Council/Minutes May 15 2008#Workspace, Resources, Content_Types]]:
+
<table border="0"  width="100%" cellspacing="6">
** Project Nesting
+
<tr>
*** Physically: Allow .project file below another .project file be separate full-blown projects -- break iterating over outer's children when finding a project
+
<td valign="top" width="66%">
*** Logically: Have nested project inherit Preferences from outer project
+
 
** Namespace Resolution (multiple projects with same name in a workspace)
+
The E4 Resources work is about improving Eclipse Platform [[Resources]],
** Inclusion of Files from Anywhere on the file system
+
both in terms of '''APIs and end-user usability'''.<br/>
** Full Native Support for Symbolic Links (avoiding problems with cyclic symlinks)
+
The '''Flexible Resource Model''' is especially about making the
** Add/remove project type/nature
+
concept of a '''Project''' more flexible.
** Listeners and plug-in Loading
+
 
** Getting rid of Project for RCP (see also [[e4/RCP Future]]) -- is the notion of "Project" a plumbing or User Artifact? Where should builders etc be hung off?
+
'''The Goals''' are listed in detail on the [[E4/Resources/Requirements|Requirements]] page, in short:
** Content Types:
+
* Make the Workspace, Project and Resource structure flexible enough to embrace any existing (legacy) structures.
*** Pattern Matching for content types rather than just file extensions + stream evaluation
+
* Build an architecture that's easy to understand, reliable, simple and safe to code against.
*** Case sensitive patterns for content types
+
* Support future environments (client/server, distributed, web, collaborative) - building a solid base of Eclipse for the next 10 years.
*** UI for Project-specific content types
+
 
 +
'''Interested Parties:''' (alphabetically) - See also the [[E4/Resources/Meeting/19-Sep-2008 Kick-off#Interested_Parties_and_Background|Kick-off meeting]]:
 +
* Broadcom, Cloudsmith, Embarcadero, Freescale, Google, IBM, Nokia, NVidia, Wind River
 +
* Component Lead: '''Doug Schaefer (Wind River)'''
 +
 
 +
'''Documents:'''
 +
* [[E4/Resources/Strawman]] - Strawman proposal
 +
* [[E4/Resources/Brainstorming]] - Notes and Ideas from early meetings
 +
* [[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
 +
** {{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.
 +
 
 +
</td>
 +
<td valign="top" width="33%">
 +
 
 +
<h3>Communication Channels</h3>
 +
* [https://dev.eclipse.org/mailman/listinfo/platform-core-dev platform-core-dev mailing list]
 +
* [[E4/Resources/Meeting Notes]]
 +
* 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>
 +
This calendar is available in the following formats:<br>
 +
[[Image:Ical.gif]][http://www.google.com/calendar/ical/ctri5teoag0n87t2qu9bla8u3g%40group.calendar.google.com/public/basic.ics iCal],[[Image:Xml.gif]][http://www.google.com/calendar/feeds/ctri5teoag0n87t2qu9bla8u3g%40group.calendar.google.com/public/basic ATOM News Feed],[[Image:Html.gif]][http://www.google.com/calendar/embed?src=ctri5teoag0n87t2qu9bla8u3g%40group.calendar.google.com&ctz=Canada/Toronto HTML]
 +
</td>
 +
</tr>
 +
</table>
 +
 
 +
[[Category:E4|Resources]]

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