This is generally what I have been doing for my projects as well. I
am guessing that SVN users are doing something similar but instead of
copying files manually, they are checking out a set of files and
using that as their local snapshot. During project A development,
they would update, check-in, etc... Then once it's time to move on
to Project B, they would create a new module in subversion for the
Project B files.
The problem I am trying to getting my head around is how to work with
common shared classes throughout multiple projects... BUT still keep
copies of these classes in the local snapshot for archiving. I am
wondering if the SVN "externals" functionality would be the right
solution? Has anyone successfully used it for this purpose?
-Danro
On Sep 26, 2006, at 10:18 AM, 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
_______________________________________________
Flashcoders@chattyfig.figleaf.com
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
_______________________________________________
Flashcoders@chattyfig.figleaf.com
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
_______________________________________________
Flashcoders@chattyfig.figleaf.com
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
