Jump to: navigation, search

Difference between revisions of "Eclipse 4.0/Wishlist"

(New page: This page lists things people would like to see addressed/fixed in Eclipse 4.0: * I'd like to have the modern container features like ioc in equinox for Eclipse 4. One example I can think...)
 
(Just another (non) committer)
Line 2: Line 2:
  
 
* I'd like to have the modern container features like ioc in equinox for Eclipse 4. One example I can think of is injecting configurations into plugin, configuration by annotation. For extension points, maybe we can borrow some things in Tapestry 5 (http://tapestry.apache.org/tapestry5/tapestry-ioc/). --John Willson
 
* I'd like to have the modern container features like ioc in equinox for Eclipse 4. One example I can think of is injecting configurations into plugin, configuration by annotation. For extension points, maybe we can borrow some things in Tapestry 5 (http://tapestry.apache.org/tapestry5/tapestry-ioc/). --John Willson
 +
 +
* Refactor and streamline the workbench so that the barrier for entry for new contributors is reduced.  -- Him Korne
  
 
* Fundamentally Eclipse is doing great but 2 big areas I think the community would love to see get attention in the next major version is the concept of  workspaces and the resources in them.  The WorkspaceRoot should be able to contain other workspaces and not just projects. Currently dealing with multiple projects with the same name (a project from the trunk and a branch) is cumbersome because multiple workspaces are needed.  In this case multiple workspaces are still needed but are contained, from a model standpoint not necessarily physically, within a single root.  And finally nested projects, the next major version simply needs to support them. As an example to hopefully make this clearer, if a user is working on 2 streams of development for Product Foo and another Product Bar then the Eclipse workspace model with look like: --Binyan
 
* Fundamentally Eclipse is doing great but 2 big areas I think the community would love to see get attention in the next major version is the concept of  workspaces and the resources in them.  The WorkspaceRoot should be able to contain other workspaces and not just projects. Currently dealing with multiple projects with the same name (a project from the trunk and a branch) is cumbersome because multiple workspaces are needed.  In this case multiple workspaces are still needed but are contained, from a model standpoint not necessarily physically, within a single root.  And finally nested projects, the next major version simply needs to support them. As an example to hopefully make this clearer, if a user is working on 2 streams of development for Product Foo and another Product Bar then the Eclipse workspace model with look like: --Binyan

Revision as of 19:29, 9 March 2008

This page lists things people would like to see addressed/fixed in Eclipse 4.0:

  • I'd like to have the modern container features like ioc in equinox for Eclipse 4. One example I can think of is injecting configurations into plugin, configuration by annotation. For extension points, maybe we can borrow some things in Tapestry 5 (http://tapestry.apache.org/tapestry5/tapestry-ioc/). --John Willson
  • Refactor and streamline the workbench so that the barrier for entry for new contributors is reduced. -- Him Korne
  • Fundamentally Eclipse is doing great but 2 big areas I think the community would love to see get attention in the next major version is the concept of workspaces and the resources in them. The WorkspaceRoot should be able to contain other workspaces and not just projects. Currently dealing with multiple projects with the same name (a project from the trunk and a branch) is cumbersome because multiple workspaces are needed. In this case multiple workspaces are still needed but are contained, from a model standpoint not necessarily physically, within a single root. And finally nested projects, the next major version simply needs to support them. As an example to hopefully make this clearer, if a user is working on 2 streams of development for Product Foo and another Product Bar then the Eclipse workspace model with look like: --Binyan
WorkspaceRoot/
  Product Foo [trunk]       <- is a workspace
    Project A
    Project B
    Project C
  Product Foo [3.x branch]  <- is a workspace
    Project A
    Project B
    Project C
  Product Bar [trunk]       <- is a workspace
    Project A
    Project B
    Project C