Re: Alternative UI of Project Explorer

Ann Sunhachawee wrote:

> John Jullion-Ceccarelli wrote:
> 
>> I think the main question is whether or not it is safe to assume that 
>> one project is open at a time is a reasonable constraint. I believe 
>> that the web apps team is splitting up a web apps project into lots of 
>> smaller sub-projects that are included in a project group. If this is 
>> the case, it may be unreasonable to force the user to switch between 
>> projects all the time. 
> 
> 
> True, if a user is working on say a J2EE app that contains a web module 
> and ejb module, they will have 3 projects to work with.
> 


Still, I don't think this is a big problem for us, given that we have 
the "Run J2EE Application" profile, which allows you to run a J2EE app 
project even if a subordinate web project is currently active. So the 
user would not be required to switch back and forth.


>>
>>
>> I do like the idea of making a cleaner separation between the Sources 
>> node and the Packages node. Regardless of what happens, we may want to 
>> shift Sources to a different tab. I believe that when we discussed 
>> this before though in a thread about how the Add Sources functionality 
>> worked, Chris said that web apps projects could not have a completely 
>> Physical view of their contents, but I never got the specifics.
> 


I did not know Chris had an opinion on this - I'd also like to know the 
details.


> 
> Not sure what is meant by a "completely physical view" here. This means 
> something like show all the files under each directory in a project to 
> me. It's also not clear to me what would appear in a Sources tab vs the 
> Packages tab. Definitely EJBs in S1S have a different approach to 
> developing apps since they have a notion of a logical node that might 
> correlate to multiple physical source files. The topic of what we show 
> in Web module projects is currently under discussion.
> 


Realistically, users will need to have a "completely physical view" for 
things like VCS, as Svata points out. Given the current overall design 
of projects (project node with three subnodes etc.), this requirement is 
not easy to accomodate. Currently Web projects design has the "Document 
Base" node under the Sources node, which partially takes on the role of 
the complete physical view.

Regarding the separation of Packages and Sources, I have a problem 
understanding the role of the Sources node as such, so I can't comment.

Petr


> -Ann
> 
>>
>>
>> -John
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>