Not to say I don't do the same thing on occasion but this might fall
under the Copy-and-Paste Programming antipattern.
http://en.wikipedia.org/wiki/Copy_and_paste_programming
http://c2.com/cgi/wiki?CopyAndPasteProgramming
Copy-and-Paste Programming isn't necessarily wrong when used in the
correct context. Sometimes your copy will mutate into something so
different that it makes sense to have two separate versions. However,
if used poorly or abused it could lead to a headache.
One commenter on the second linked site put it nicely:
"If the original code has flaws, not only do you have to hunt down all
the clones, but what if you miss some? It's like a re-occurring rash -
Damn, I thought I got rid of that! - it keeps coming back when you think
its gone for good." -- ToddCoram
I have been specifically looking into software like subversion which
seems to be the standard.
James O'Reilly
http://www.jamesor.com
Mike Keesey wrote:
Lately I actually copy all packages to a folder within my project's
folder. Why? Suppose you have a package and you use it on project A.
Later, you use it on project B, and realize there are some issues, so
you change some of the code. Project B finishes. Then, later on, you
find you have to go back to project A with some tweaks and republish it.
Because of changes in the package, there may be problems--at best you
will still have to spend time regression testing.
Copying your packages to a project-local folder means that you have a
secure "snapshot" of the package.
―
Mike Keesey
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:flashcoders-
[EMAIL PROTECTED] On Behalf Of Dan Rogers
Sent: Monday, September 25, 2006 4:36 PM
To: Flashcoders mailing list
Subject: [Flashcoders] How do you manage your classes?
Flashcoders,
I've been wondering how other flash developers deal with AS2/AS3
class management on both a project-based and common library level,
while addressing the need to package up source code for a given
project to deliver to a team member or client.
I've used version control before, as well as doing the common
classpath thing for shared classes... but when it's time to deliver
the source code to someone, I would have to go in and hunt for all
the classes I used on a project and copy them to the FLA directory
(and recreate the com.package... structure as well). Sometimes it
seems faster to simply create the AS files along with the FLA (in a
single package), and copy over utility files as needed. But then you
get into duplicate classes scattered over multiple projects.
Can anyone provide any insight to a system that works well for them?
For example, does anyone run custom shell scripts (such as rsync)
that sync the current project with the main classpath directory?
Thanks,
-Danro
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
