I work with a large team at work and also on my own companies projects, I do this :
\projects\bluetube\clients\CartoonNetwork \projects\bluetube\clients\amvescap \projects\bluetube\clients\threeSquared etc.. for our own stuff \projects\bluetube\ourstuff\web2005 \projects\bluetube\outstuff\logo \projects\bluetube\ourstuff\tempHomePageProject Within a particular project I have : web2005\src (my code) web2005\lib (libraries web2005\dist (the stuff that will be uploaded to the webserver) web2005\conf (config files, xml files etc) web2005\fla (the starting .fla file if its a flash project) My source directory for my current project at Norfolk Southern would be : \projects\ns\EnterpriseArchitecture\AdministrationService\AdminstrationServiceEAR \projects\ns\EnterpriseArchitecture\AdministrationService\AdminstrationServiceEJB \projects\ns\EnterpriseArchitecture\AdministrationService\AdminstrationServiceWAR \projects\ns\EnterpriseArchitecture\AdministrationService\EnterpriseManagement console the first three are java projects, the last is flash and its structure is : \EnterpriseManagementConsole\src\com\ns\util \EnterpriseManagementConsole\src\com\ns\view \EnterpriseManagementConsole\src\com\ns\control \EnterpriseManagementConsole\src\com\ns\command \EnterpriseManagementConsole\src\com\ns\vo These would all be classes applicable to any project I build for NS, my project specific classes go : \EnterpriseManagementConsole\src\com\ns\app\EMC\util \EnterpriseManagementConsole\src\com\ns\app\EMC\view \EnterpriseManagementConsole\src\com\ns\app\EMC\command \EnterpriseManagementConsole\src\com\ns\app\EMC\control \EnterpriseManagementConsole\src\com\ns\app\EMC\vo I do something similar for my own company stuff bluetube but its : \web2005\src\com\bluetube\util \web2005\src\com\bluetube\control \web2005\src\com\bluetube\view etc.. If I build a lot of stuff into a library that does change much I'll eventually put the re-usable classes in the lib folder of the project that uses it rather than having it in the src tree so for example \web2005\src\com\bluetube\view\MyView.as \web2005\lib\com\bluetube\util\Logger.as the Logger could be used by multiple projects, the "master" copy of the Logger would be in its own project with other re-usable components : \btlibrary\src\com\bluetube\util\Logger.as \btlibrary\src\com\bluetube\util\ClassUtilities.as \btlibrary\src\com\bluetube\util\MovieClipLoader.as etc.. for tools : \developement\flashcomponents\alcon \developement\flashcomponents\remoting \developement\flashcomponents\openAMF \developement\flashcomponents\ariaware RIA Platform \developement\flashcomponents\xpath4AS \development\eclipse \development\bea\weblogic \development\apache\ant \development\mtasc-1.09 \development\Nhibernate-0.7.0.0 Let me know if you need more clarificaton . Grant ----- Original Message ----- From: M Daggett [EMAIL PROTECTED] To: Open Source Flash Mailing List [email protected] Sent: 9/3/05 3:58 AM Subject: [osflash] directory structure > OK this is not really an open source question (more best practices), > I just had to reinstall my computer's operating system (long story) > and so I am starting fresh. This time I promise not to let me > development directory structure turn out like a rat's nest! Can anyone > point me to any typical conventions used to organize files and folders > for development. Honestly I am still totally mystified by when to use > "com" or "org" or "net" though I think that I can infer a meaning. > > Ideally, I'd like to have a structure that specified something like: > > Tests go here: > Third party apps go here: > Classes go here: > Servers go here: > etc. etc. etc. > > Thanks! > Mark > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
