[evla-sw-discuss] code organization

[Bryan Butler]

i agree with brian here.  for the webapps they also need the related assembly 
and config stuff, and it's nice to have it separated out.

sometimes it's nice to have everything all in one directory, but as things get 
more complicated, it becomes impossible to find the needle in the haystack, as 
it were.

	-bryan


On 10/25/06 15:31, Brian Truitt wrote:
> Kevin Ryan wrote:
>> A person searching the hierarchy for  
>> VlaAntenna should know that it is part of the AMCS of the EVLA of  
>> NRAO but should not have to know the name of the processor that it  
>> might run in or the language that it was written in in order to find  
>> it in our source repository.
>> 
>> Kevin
>> 
> 
> In this case, how do we organize projects utilizing multiple languages? 
> We have C, perl, java, and jsp at least strewn throughout our projects. 
> (There's a perl script used to compile the online help used in the PST 
> for example). I have no interest in mixing perl scripts in with my java 
> packages, or my jsp and html for that matter. Where do they go then? A 
> concrete alternate suggestion for this scenario would be useful.
> 
> I certainly find the directory structures verbose and lengthy as well, 
> so alternatives that handle all our use cases are welcome.
> 
> Brian
> _______________________________________________
> evla-sw-discuss mailing list
> evla-sw-discuss at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss