Hi Mark,
I tend to use the following structure:
docs (documentation, api, ...)
docs/api
docs/step-by-step (tutorial)
test (unit tests etc.)
com.simonwacker... (same as in src, same package, class names, but class
names end with 'Test')
src
com.simonwacker... (your domain reversed as package naming, prevents
conflicts between classes with the same name)
samples (examples etc.)
lib (external libraries, third party stuff)
Greetings,
Simon
--
Simon Wacker
www.simonwacker.com
www.as2lib.org
www.hq-heilbronn.de
www.flik-flak.de
----- Original Message -----
From: "M Daggett" <[EMAIL PROTECTED]>
To: "Open Source Flash Mailing List" <[email protected]>
Sent: Saturday, September 03, 2005 9:55 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
