[flexcoders] Best practices for organizing base code library and project specific code

2006-07-25 Thread ben.clinkinbeard
Just wondering how people out there approach this. Obviously, I have
my project neautral, reusable code stored in a structure like
com.mydomain.utils, etc. This is off in a general location. Currently,
I have a structure like com.mydomain.projects.MyCurrentProject inside
the actual Flex project folder, and I link the reusable code's folder
into the project.

Using the com.mydomain.etc structure in my project folders means I
could later integrate all of the code into one location without
editing the packages, so I am wondering if I should just do that to
begin with. If I kept everything in a central place I could just link
my library to each project but I would not have any code held with the
actual Flex files. I think I prefer my current approach but would like
to get some feedback from others and see what other methods people are
using.

Thanks,
Ben
http://www.returnundefined.com/






 Yahoo! Groups Sponsor ~-- 
Check out the new improvements in Yahoo! Groups email.
http://us.click.yahoo.com/7EuRwD/fOaOAA/yQLSAA/nhFolB/TM
~- 

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 
Yahoo! Groups Links

* To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/

* To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]

* Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
 





Re: [flexcoders] Best practices for organizing base code library and project specific code

2006-07-25 Thread JesterXL
The only reason I don't keep com.jxl.utils.* as an SWC Library project in 
FlexBuilder to allow 50 billion projects to use it is because those classes 
get tweaked every single project... so, rather than tweak something, and 
break a ton of other projects that have dependencies on it, I just put a 
custom build for each project in the namespace like you said.

One of these days, maybe I'll stop tweaking.  Till then, there is SVN.

- Original Message - 
From: ben.clinkinbeard [EMAIL PROTECTED]
To: flexcoders@yahoogroups.com
Sent: Tuesday, July 25, 2006 10:25 AM
Subject: [flexcoders] Best practices for organizing base code library and 
project specific code


Just wondering how people out there approach this. Obviously, I have
my project neautral, reusable code stored in a structure like
com.mydomain.utils, etc. This is off in a general location. Currently,
I have a structure like com.mydomain.projects.MyCurrentProject inside
the actual Flex project folder, and I link the reusable code's folder
into the project.

Using the com.mydomain.etc structure in my project folders means I
could later integrate all of the code into one location without
editing the packages, so I am wondering if I should just do that to
begin with. If I kept everything in a central place I could just link
my library to each project but I would not have any code held with the
actual Flex files. I think I prefer my current approach but would like
to get some feedback from others and see what other methods people are
using.

Thanks,
Ben
http://www.returnundefined.com/







--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links








--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 
Yahoo! Groups Links

* To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/

* To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]

* Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/