[Tweener] Strange thing happening after duplicating movie > solved

[Zeh Fernando]

It's not that it's messy, it's that it's safer.

I do have a global repository of my classes, but I never import directly 
from it. I merely copy from it to my project folder when I need some 
specific class.

The reasons are twofold: first, if a 'global' class goes through some 
interface change - say, removing some method, or changing the name of an 
existing function, or breaking some feature - I don't have to worry 
about whether my project will continue to work or not. Since it's using 
a snapshot of the class, it'll continue to work and I can update it 
later if I want to. That also allows me to create specific patches and 
features to the project copy of the 'global' class whenever I want/need, 
and I can move the class back to the global folder if I find the changes 
are good enough and the new version is reliable; so I really like 
branching out my 'global' classes - my personal framework, so to speak - 
in ways that may be experimental and that may not be fully compatible 
with previous versions. So, having the local copies allow me such freedom.

Secondly, if I need to backup a project source or send it to somebody, I 
just zip the entire project source folder and call it a day. I don't 
need to hunt down the classes I'm using from my global class folder, or 
pack my entire class folder. I really like my projects to be fully 
self-contained.

Maybe those two reasons are way too related to the way I work - I work 
at home, remotely, as a freelancer. So packing my sources and sending it 
to the studio I work for (Firstborn) should be specially fail-proof. In 
the old past I've had a number of problems concerning that kind of stuff 
- forgetting to add some classes or included .as files on my personal 
backups - so it's something that I automatically avoid with this approach.

I've used global class paths at first but dropped it a while ago. I 
really don't see absolutely any negatives in the way I do it, but maybe 
it's too tied to the way I work so other people's choices may vary.

TL;DR: I just find the local copy option to be safer and easier. I have 
the 'global' class folder, but just as a place to copy classes from.

Zeh

> Zeh, I don't agree with you on this one, why would you need to have many 
> copies of your classes?
> I think that's a bit messy, it's better to have a central repository of 
> all your classes divided by projects / packages so you can re-use them 
> in a more efficient and easier way. Maybe I didn't understand you though.
> I would definitely recommend having a global classpath.
> 
> salut!
> 
> 2008/7/29 Zeh Fernando <zeh at zehfernando.com <mailto:zeh at zehfernando.com>>
> 
>         On 7/29/08, Hans Verhoeven <hans at krachtstroom.net
>         <mailto:hans at krachtstroom.net>> wrote:
> 
>             I read something about global classes but
>             I'm not sure I understand the concept.
> 
> 
>         hit Ctrl+U, select Actionscript, then AS2, then class path. Add path
>         to tweener there, and it will be available in every project.
> 
> 
>     Exactly what Makc said; you can have a global class folder. But
>     personally, I wouldn't recommend it. It's usually better to have all
>     classes used on a subfolder of the current project (making copies of
>     the 'global' classes when needed). Makes later maintenance and
>     archival a lot less painful since all your code will be contained
>     within a single folder.
> 
> 
>     Zeh
> 
>     _______________________________________________
>     Tweener mailing list
>     Tweener at lists.caurinauebi.com <mailto:Tweener at lists.caurinauebi.com>
>     http://lists.caurinauebi.com/listinfo.cgi/tweener-caurinauebi.com
> 
> 
> 
> 
> -- 
> http://www.games-garden.com/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Tweener mailing list
> Tweener at lists.caurinauebi.com
> http://lists.caurinauebi.com/listinfo.cgi/tweener-caurinauebi.com