Re: [projects-dev] Alternative UI of Project Explorer

Tomas Zezula wrote:
> cL wrote:
> 
>> i have seen the design and it has it's merits. i'm not convinced that 
>> pushing Resources and Outputs to other tabs will increase their 
>> discoverability but it's also something to consider. another thing to 
>> consider is that without the idea of an active project it is a bit 
>> more labor intensive to work with inter-dependent projects. e.g. if 
>> you have three projects that are all connected to each other (via b.t. 
>> outputs as resources) typically only one of those is the one you care 
>> to run. with an active project the runnable project is set active 
>> while work continues on other projects. without an active project the 
>> user will need to switch to the desired project before running.  it's 
>> an extra step that may, in the long run, not make that big of a 
>> difference all things considered but it is something we need to be 
>> aware of. 
> 
> Svata's Explorer can keep the notion of Active Project, (the project 
> will be marked as active in the Project Bookmark List), but I don't 
> think that this is good way,

Yes, in fact, the prototype equals "current project" to "active 
project", which - as Chris pointed out - does not work well for some 
scenarios: e.g. several projects making up a software system, one of 
them is the integration one - and that one should be (somehow) marked 
for running / building (since it will build/update its dependencies).

This scenario is problematic in both prj40_prototype branch and my UI 
prototype -- the UI prototype however minimizes usage of "active 
project" concept in other scenarios.

-Svata