[platform-core-dev] Re: Flexible Project Structure

[Glenn Meter <meter@xxxxxxxxxxxxxx>]

Doug,

I'm coming in late to this discussion. But as an Eclipse Java user  
and as a former lead of the CodeWarrior IDE team, here's my two cents.

My suggested basic requirements are:

(A) Allow linked resources to resolve to absolute paths or paths  
relative to one of:
	- The project
	- A workspace variable
	- The workspace

(B) Projects that only use paths relative to the project should be  
able to be checked out from CM into a new [CM] workspace and "just  
work" (whether on my machine, another machine with the same OS, or  
another machine with a different OS).  I should not have to create  
any symbolic links or do any other setup to be able to edit, compile,  
and debug the application.

(C) The resolution for a linked resource should be able to be viewed  
and changed via the Properties for the item. In 3.3, if a linked  
resource uses a workspace-variable-relative path and the variable is  
not defined then the Properties page for the resource does not show  
the resolution information. This makes it difficult to fix the  
problem by declaring the missing workspace path variable. It's not  
possible to fix the problem without viewing the .project file.

(D) Any referenced but undefined workspace path variables should show  
up in the workspace's Problems list.

(E) Projects should be able to refer to other projects, and include a  
preference for whether the referenced projects should be built before  
the referring project.  If I have a project hierarchy, I should not  
have to duplicate the hierarchy in each workspace that includes a  
root project.


I also agree with Serge (hey, Serge!) that it should be easier to  
create linked resources in general via drag & drop, etc.


I'm looking forward to see what you come up with at the E4 Summit.

Best regards,
Glenn Meter
meter@xxxxxxxxxxxxxx
gmeter@xxxxxxxxxxxx