Re: ClassPath: Explanation requested

Svata Dedic wrote:

> Tomas Zezula wrote:
>
>> What I think is that for projects with Java nature, the ClassPath 
>> customizer
>> should go back to the Project customizer when it was before.
>> As far as I remember it was removed because of "big amunt" of tabs in 
>> the
>> project customizer, but this can be solved in different way (e.g. Single 
>
>
> Yes, I think I understand (and fully support) this reason -- the 
> number of tabs grows so that it may be not easily scannable.
>
> Very nice idea with the combo, BTW. Except the list contents and its 
> label, the customizers are just the same.
>
> To warm up old stuff, the page 
> "http://lit.fsid.cvut.cz/~svata/nb4dev/inextensible-ui.html" talks 
> exactly about that (and was created during January 2003, iirc). The 
> suggested solution may not be optimal though, but it aims to solve not 
> only for different flavours of classpath.
>
> -Svata 

The solution presented on the 
http://lit.fsid.cvut.cz/~svata/nb4dev/inextensible-ui.html is much more 
better than mine,
this solution is easy to extend by other modules (e.g. Pavel Buzek has 
some kind of special Class Path) and as shown
in the document is widely accepted across tool vendors. It is probably 
the right way to go. :-)

Tomas

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