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"
m |
(updated abstract using JohnA's words) |
||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| + | |||
| + | '''e4''' is the community effort for building the next generation of the Eclipse Platform. The project has three principle aims: | ||
| + | * '''Simplify the Eclipse programming model:''' This will reduce development and maintenance costs and enable a larger developer community to leverage the platform in their own Eclipse-based applications. | ||
| + | * '''Enable the platform for use on emerging web-based runtime technologies:''' This will ensure the platform remains a compelling and viable application framework in a rapidly changing web technology landscape, and it will allow e4-based applications to leverage web technologies, while remaining insulated from specific technology choices that may quickly become obsolete. | ||
| + | * '''Broaden participation in development of the platform:''' This reduces the risks associated with building on a platform largely funded from a single source. Having a large and diverse group of commercial backers, will ensure the platform remains vibrant and viable over the long term. | ||
| + | Please refer to the [http://www.eclipse.org/proposals/e4 project proposal] for more information, including the initial list of committers. The e4 project summary page is [http://www.eclipse.org/projects/project_summary.php?projectid=eclipse.e4 here]. | ||
<table border="0" width="100%" cellspacing="6"> | <table border="0" width="100%" cellspacing="6"> | ||
<tr> | <tr> | ||
| − | <td valign="top" width=" | + | <td valign="top" width="45%"> |
| − | + | ||
| − | + | ||
| − | + | ||
<h3>Get it</h3> | <h3>Get it</h3> | ||
| − | We have an [[E4/Builds | automated build process ]] producing [http://download.eclipse.org/e4/downloads/ weekly builds] | + | We have an [[E4/Builds | automated build process ]] producing [http://download.eclipse.org/e4/downloads/ weekly builds]. You can get the projects directly from CVS via our [[E4/ProjectSetFiles | collection of project set files]] and load them into the latest [http://download.eclipse.org/eclipse/downloads/ integration build]. |
<h3>Milestones</h3> | <h3>Milestones</h3> | ||
| Line 23: | Line 26: | ||
<tr> | <tr> | ||
<td>0.9 M1</td> | <td>0.9 M1</td> | ||
| − | <td>02/06 | + | <td>2009/02/06</td> |
<td>based on 3.5 M5 and Galileo M4</td> | <td>based on 3.5 M5 and Galileo M4</td> | ||
</tr> | </tr> | ||
| Line 29: | Line 32: | ||
<tr> | <tr> | ||
<td>0.9 M2</td> | <td>0.9 M2</td> | ||
| − | <td>03/20 | + | <td>2009/03/20</td> |
<td>based on 3.5 M6 and Galileo M5</td> | <td>based on 3.5 M6 and Galileo M5</td> | ||
</tr> | </tr> | ||
| Line 56: | Line 59: | ||
</td> | </td> | ||
| − | <td valign="top" width=" | + | <td valign="top" width="45%"> |
<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> | ||
| Line 78: | Line 81: | ||
</td> | </td> | ||
| − | <td valign="top" width=" | + | <td valign="top" width="10%"> |
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
[[Category:e4]] | [[Category:e4]] | ||
Revision as of 11:01, 19 January 2009
e4 is the community effort for building the next generation of the Eclipse Platform. The project has three principle aims:
- Simplify the Eclipse programming model: This will reduce development and maintenance costs and enable a larger developer community to leverage the platform in their own Eclipse-based applications.
- Enable the platform for use on emerging web-based runtime technologies: This will ensure the platform remains a compelling and viable application framework in a rapidly changing web technology landscape, and it will allow e4-based applications to leverage web technologies, while remaining insulated from specific technology choices that may quickly become obsolete.
- Broaden participation in development of the platform: This reduces the risks associated with building on a platform largely funded from a single source. Having a large and diverse group of commercial backers, will ensure the platform remains vibrant and viable over the long term.
Please refer to the project proposal for more information, including the initial list of committers. The e4 project summary page is here.
