Re: Re: [nbui] projects ui recommendations

Hi Svata,

thank you for your comments.

Svata Dedic wrote:
> Hi,
> 
> I would like to ask about the content in the left pane (tree view): the 
> tree is semi-dynamic - part of the tree is fixed (well, it probably may 
> change depending on what modules/natures are available), some subtrees 
> are dynamic as the user may add and remove entries in them.
> I did not see many such mixed designs and I suppose there could be a 
> cleaner model.
> 

You are right, the Running Profiles and Build Steps categories have 
dynamic children. We tried to keep individual build steps and running 
profiles customization in the same dialog, so that their customization 
is easily accessible. I hope that for most of users the list will not be 
dynamic as they won't need to create a new build steps or running 
profiles. We should provide default profiles and build steps that will 
cover most of use cases.

> Next comment is for usability of the project setup management; narrowing 
> the problem to Java only, in major part of use cases, individual build 
> steps have virtually identical settings; it should be possible to set up 
> project-wide defaults for them - but the tree at the left does not seem 
> to contain entries for such setup.
> 

Are you referring to "Compile" build step? Or you mean that each build 
step type should have project wide settings (probably stored in a build 
configuration)? We tried to avoid settings inheritance as much as 
possible. Most projects shouldn't have many build steps of same type. If 
a project has more such build steps then build configuration should be 
used for easily switching of settings in more build steps. Of course the 
user have to change the settings in each build step when creating a new 
configuration.

> Implementation-related comment: there are two levels of "transactions", 
> actually: first level when the user creates a new build step/running 
> profile/Resource, second step when the user OKs or Cancels the whole 
> dialog.

The ideal behavior is that everything (also build step and profiles) 
created/modified/deleted in the project customizer is canceled with 
Cancel button and confirmed with OK button.

> All the customizer's contents (btw, is it still a customizer if it has 
> OK / Cancel buttons ?) should definitely be consistent; Vita has 
> suggested a way how to propagate options throughout the dialog, while 
> keeping them "temporal".
> However creating a new build step, resource etc. requires a new object 
> created within the project model, which (currently) is one for the 
> project, there's no "temporal" model.
> Are some approaches how to solve this issue already known ?

Folks?

Thank you,
Jano

> 
> Thanks,
> -Svata
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>