Re: UI for setting up runtime classpath

cL wrote:
> 
> the user can review classpaths on profiles and build targets -which is 
> the place they'll be most interested in since that's where the action 
> takes place.
> 
Negative - the "New > Resource" action is present at project level 
(precisely on Project's Resource node) and establishes a project-wide 
default path (which the individual targets/profiles default to). UI on 
individual build targets, or profiles, is just a local override of the 
project default established through the "New > Resource" action.
UI to inspect or alter the project-wide default does not exist at all.

> 
> when adding a resource via a specific b.t. or profile the user will get 
> a similar but more tuned choice -<bt or profile name>, compile/run time 
> (depends on whether added from b.t. or profile respectively), 
> everywhere. the default choice is the specific object (b.t. or profile).

So the spec now basically says that the user may, by customizing 
properties of a single execution profile in a modal window, alter 
properties of all other execution profiles when she chooses "run time" ?
The same explanation could be applied to build target's case.

I would find that quite counter-intuitive, since customizers are meant 
to change only the object which they are invoked on, not other objects, 
aren't they ?

The same issue as at the top of the e-mail: there's a way how to set up 
defaults for "Compile Time" for all build targets (by selecting 
"compile-time" from the list), but there is no way how to see that setup.
The user can only see individual build target's data, which are possibly 
mutated from the default and is not getting any clue about what 
resources are "project-wide" and which are for that target only.

BTW I am also missing spec for "Add" button in Fig 50 - the step that 
allows to select resource already in the project or browse for a new 
one. Maybe scheduled for the next update.

-Svata