Re: UI for setting up runtime classpath

so, i've been mistaken and it's clear that we need to have a project 
wide classpath customizer. what i'd like to do i a combination of old 
and new ideas so that we move all classpath customizing to the resources 
node (since that's the 'project wide' place to fuss with resources) and 
make the resources node customizer look something like:

   _________  _________  __________  _______________  _______
  /Resources\/Classpath\/Runtime CP\/Compile Time CP\/Boot CP\
|           \---------------------------------------------------+
|                                                               |
| Current resources:                                            |
| +--------------------------------------------+                |
| | Resource             |    Use In    | Show |  [ Add...    ] |
| |--------------------------------------------|                |
| | /path/to/Math Lib    | Everywhere |V| [x]  |  [ Remove    ] |
| |--------------------------------------------|                |
| | /path/to/Crypto      | Everywhere |V| [x]  |                |
| |--------------------------------------------|                |
| | /path/to/xmlParse.jar| Run Time   |V| [x]  |                |
| |--------------------------------------------|                |
| | /path/to/this.jar    | Compile T. |V| [x]  |                |
| +--------------------------------------------+                |
+---------------------------------------------------------------+

* Add... opens the add resource wizard
* Remove removes the resource from the project
* Use In column has contains a combo for specifying where a resource is 
used. the choices are Everywhere, Run Time, Compile Time, Unused, Other 
(the last two are new). if a resource is not used in any part of the 
classpath it is marked as unused. if the resource is used in a way not 
described by the other categories it is marked as Other (such as being 
used in one specific b.t. or profile but not project wide).
* Show column is a list of check boxes that indicate if the resource 
should be visible under the resources node.

if a resource does not belong as part of a classpath the Use In field 
for the resources is disabled.

   _________  _________  __________  _______________  _______
  /Resources\/Classpath\/Runtime CP\/Compile Time CP\/Boot CP\
|----------/           \-----------------------------------------+
|                                                                |
| Current resources:                                             |
| +--------------------------------------------+                 |
| | Resource                                   |  [ Assign New ] |
| |--------------------------------------------|                 |
| | /path/to/Math Lib                          |  [ Release    ] |
| |--------------------------------------------|                 |
| | /path/to/Crypto                            |                 |
| |--------------------------------------------|  [ Move Up    ] |
| |                                            |                 |
| |--------------------------------------------|  [ Move Down  ] |
| |                                            |                 |
| +--------------------------------------------+                 |
+----------------------------------------------------------------+

each of the classpath tabs will look like this.

* Assign New first opens a list of resources present in the project but 
not assigned to the current role. the user can select from the list.
* Release removes the resource from this classpath but not the project. 
if the resource is not used on any of the classpaths here it is marked 
as unused.
* Move Up/Down changes the order of the resources.

when this goes into the spec i'll nuke the general classpath text and 
make sure that every customizer that has classpath customization is 
appropriately documented. that should help the confusion factor in what 
was meant by a classpath customizer that clearly looked different from 
everywhere it was used.

so, the wheels sometimes turn slowly but they do turn. :-) now that 
everything is (once again) clear to me i remember why we had the 
classpath customizer as part of the projects customizer in the first 
place. :-) sorry to go back and revisit all of this. let me know how 
this looks.

cL
-- 

ui.netbeans.org
interaction designer
[email protected]