Projects tab UI (was: Re: [projects-dev] Workplace node and its API)

Vitezslav Stejskal <[email protected]>
Newsgroups gmane.comp.java.netbeans.modules.projects.devel
Message-ID <[email protected]>
Hi Svato,

here are my answers for your more UI oriented questions:

Svata Dedic wrote:

>
> Things, which are not obvious (to me) even after reading the UI spec 
> (please consider these as clarifications requests for both 
> functionality and the UI):
>
> * Could an already opened projects be added onto a Workplace ? 

Programaticaly, opening/closing the projects has nothing to do with 
showing/hiding it on the projects tab. However, the user shouldn't see 
any difference. So from users standpoint the answer would be: no.

>
> * Could one remove a project from the Workplace without closing it 
> first  ? (a counterpart operation for the first one). 

Not using the public API. And again the user should see only one version 
of 'Project Close' action, that one which closes the project and removes 
it from the Projects tab or do you have usecases questioning this approach?

>
> * When a project is closed, should it disappear from the Workplace ? 

I am not sure about this. The uispec says that it should dissapear, so I 
do follow this.

>
> * Seeing as "Close" operation si defined for a project group -- should 
> the Project Group remain in Workplace after it is closed ?

The answer should be the same as for above question.

>
> IMHO currently "Close" on a project does not seem very consistent -- 
> when the project is in a project group, its node remains on Workplace. 
> If it is not, it is removed from it.

That's true, but when user closes the project in the group she doesn't 
mean to modify this group by removing the project from it.

-vita
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.