[evla-sw-discuss] code organization

[Kevin Ryan]

On Oct 26, 2006, at 9:09 AM, Rich Moeser wrote:

> Currently the structure of the higher layers is as follows:
>
> NRAO (root directory)
>             -> COMMONS (this contains reusable classes that can be  
> used
> by any project and by non-nrao developers, AngleFormat, AstroDate,
> MathLib, and Util)
>             -> EVLA
>                            -> OBSERVE
>                            -> TRANSITION
>                            -> ARCHIVE
>                            -> COMMONS (reusable components and static
> classes that only EVLA projects would use)
>                            ....etc, etc, etc
>             -> VLA
>                            ->JOBSERVE
>             -> VLBA
>                             -> OMS
>                            -> VLCj
>             -> E2E (this would be SSS)
>                             -> PST
>                             -> VOSERVER

Yes this is good, just drop the capital letters and the 'COMMONS'.

WIDAR has two (so far) packages that are shared: 'util' and  
'widget'.  widget contains shared Java Swing custom components.  The  
widget package is growing fairly large; util is quite small.  Why  
should something that is not a GUI, wanting just an XML parser, need  
to take along a bunch of Swing components as would be the case if  
they were combined into COMMONS?

Knowing that he is agrees with this, but stubbornly refusing to give  
in, Rich Moeser desperately wrote:  :)

>  I would probably change the COMMONS so that several types of
> commons projects can exist. For example the EVLA project could have
> COMMONS-UTIL (utility classes used exclusively by evla) and COMMONS- 
> NET
> (evla communications and network classes).

nrao.evla.util         = good,
nrao.evla.commons.util = bad,
nrao.evla.commons-util = bad.

> (And, yes, I think the term
> "commons" should be kept, indicating a collection of general purpose
> classes.)

Why?  'util', 'net', 'widgets' _are_ general purpose classes.

The gazillions of classes in the Java Language exist without a single  
'commons' package.

Kev