Difference between revisions of "E4/Resources/Requirements"
(→Overall Goals and Themes) |
|||
| Line 2: | Line 2: | ||
* Allow Eclipse projects to better model real-world setup of projects (Theme: [[RequirementsCouncilThemesAndPriorities#Ease Of Use|Ease Of Use]]). | * Allow Eclipse projects to better model real-world setup of projects (Theme: [[RequirementsCouncilThemesAndPriorities#Ease Of Use|Ease Of Use]]). | ||
| − | ** | + | ** Be competitive / integrate with with (Visual Studio, Slickedit, Netbeans, IDEA). Integrate with (Maven, Proprietary project systems...) |
| − | * Make it easier for end-users to get their stuff into Eclipse (Theme: [[RequirementsCouncilThemesAndPriorities#Facilitated On-Boarding|Facilitated On-Boarding]]) | + | ** Make it easier for end-users to get their stuff into Eclipse (Theme: [[RequirementsCouncilThemesAndPriorities#Facilitated On-Boarding|Facilitated On-Boarding]]) |
| + | ** Better support Aliases (symbolic links) | ||
| + | ** Scalability - Better support very large workspaces (by means of Filtering) | ||
* Support pervasive distributed workspaces | * Support pervasive distributed workspaces | ||
| − | * Improve concurrency and programming model | + | * Improve concurrency and programming model to fit in the overall [[E4]] world |
| − | + | ||
= Requirements = | = Requirements = | ||
Revision as of 12:32, 19 September 2008
Contents
Overall Goals and Themes
- Allow Eclipse projects to better model real-world setup of projects (Theme: Ease Of Use).
- Be competitive / integrate with with (Visual Studio, Slickedit, Netbeans, IDEA). Integrate with (Maven, Proprietary project systems...)
- Make it easier for end-users to get their stuff into Eclipse (Theme: Facilitated On-Boarding)
- Better support Aliases (symbolic links)
- Scalability - Better support very large workspaces (by means of Filtering)
- Support pervasive distributed workspaces
- Improve concurrency and programming model to fit in the overall E4 world
Requirements
- See the E4/Resources/Meeting/19-Sep-2008 Kick-off#Interested Parties and Background for the various interested parties, their background and Requirements.
- Do not break basic assumptions that clients of Eclipse Resources have today. What are these assumptions?
- Support the current form of resources today, and more.
- Support file-list based projects.
- Support natural organization of projects (physical nesting).
Use-Cases
Open an existing Eclipse 3.x project
Workspace compatibility is a must.
Import an existing DevStudio project
- Just toss the wsp / wpj files into Eclipse and use CDT's parsers immediately. Provide the same views as Devstudio.
Debug an Exectuable without a Project
- Assume that the Exe has debug info embedded. start debugging it immediately without having to set up a project. Support static analysis / parsing and symbol navigation seamlessly.
Support mixed Java/C++ projects easily
- On-boarding an existing team must be as easy as double clicking a file.