Re: Resource handling in Java UISpec
Svata Dedic <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.modules.projects.devel |
|---|---|
| Organization | CollabNet Hosting |
| Message-ID | <[email protected]> |
cL wrote:
> Svata Dedic wrote:
>> In rev. 1.23, there's no way how to add required libraries to a
>> library (only filechooser is opened):
>> http://java.netbeans.org/issues/show_bug.cgi?id=32661
>
> how is a library stored? assuming there is a file that collects the
> contents and roles of what makes up a library then the filechooser can
> grab those (we'd then need to add a location field for each library to
> say where it should be stored).
>
I assume it will be a folder with some metadata recognized specially by
the IDE. Petr has broadened the usage, so it can be now:
- in the project
- onto system filesystem (a.k.a Library Repository)
- anywhere on the local harddrive.
The filechooser is good only for the last option, I don't think that
user should be allowed to browse through $nb_install/system folders or
through project file structure -- to many confusing things/folders in
there. For both cases, we should be able to extract list of libraries
already defined in {library repo, project}, however.
>>
>> Next, the ClassPath Customizer on "Compiled Classes" - style targets
>> is implemented according to the UI spec, to the latest detail. Even
>> suffering the same bug as the UI spec: a resource from the very same
>> Project can not be added to the classpath:
>> http://java.netbeans.org/issues/show_bug.cgi?id=32662
>
> good point. we can add an intermediate step to Add in the classpath
> customizer that first lets the user choose from resources already
> present in the project with a 'New...' button to go off and add a
> completely new resource if they need to.
OK.
>> One could also discuss the commonality of adding something to the
>> bootstrap path. As it is relatively uncommon, the option should not
>> have its place in New Resource Wizard.
>
> i'm not convinced this is bug. see the bug description.
>
OK, we'll see after it is in action for some time.
>
> if the user opens the customizer on the resource and changes the Use
> Resource combo-box value they can assign the resource for use project
> wide. see figure 28.
>
Got me. Thanks.
-Svata