E4/Resources

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: Enable Eclipse-based products to better adapt to the way how their users are working - support very large workspaces and aliasing (symbolic links) well, allow importing any legacy project and file system structures, 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 Kick-off meeting: Broadcom, Embarcadero, Freescale, Google, IBM, Nokia, NVidia, Wind River Component Lead: Doug Schaefer (Wind River) Documents: 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 E4/Resources/Meeting Notes - Our meetings are on the E4 Calendar.

Communication Channels 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 This calendar is available in the following formats: iCal,ATOM News Feed,HTML