Blog

Via <a href=”http://www.actionscripthero.com/blog/archives/000282.php”>aSH</a>.

If you can’t say something positive, don’t say anything at all. :: grits teeth :: Damn, that’s a hard virtue to live up to when press releases like this come along. :: deep inhale… exhale… :: Ok.

*ahem*

Empowering marketers to better track their results utilizing Flash is a very cool concept; hopefully helping them garner more information from their customers on responses to ads.

However, I strongly disapprove of Macromedia endorsing the use of those annoying pop-up Flash ads. This contributes to the negative effects to Flash’s adoption, the furthering of initiatives to add Flash blocking to pop-up blocking software, and a general negative connotation towards Flash as a whole. We’re already trying to shake off the Skip-intro filth that has tarnished our foot in the door. This only makes it more diffucult and frustrating to know we’re not getting much help.

<a href=”http://www.macromedia.com/macromedia/proom/pr/2004/motif.html”>Flash Ad Kit</a>

No, I’m not talking about the “Package Cam” over at <a href=”http://www.gmunk.com/”>Gmunk</a>. I mean the class packages you can use in Flash MX 2004. I felt like I should be careful in using too many packages because if I let it get out of hand, I may have too much code everywhere. After <a href=”http://www.darronschall.com/”>Darron’s</a> response to Andreas and my question about them on Flashn00bz, he pretty much said it’s up to you. So, I started organizing stuff like I would with files in folders based on subject. At first, I thought it was kind of dumb… I was like, “I’m not gonna end up with frikin’ MM’s setup, like they have in their Classes folder where Flash is installed.”

Boy was I wrong. I’ve got so many code files… and they are all organized! I couldn’t imagine NOT having packages knowing what I know now.

Definately a must for the next version of Flash is some form of integration with Shared Libraries… not sure how, but if I don’t want to SWC everything up front to keep it still editable, I shouldn’t have too.

Packages rule.

Taking a break from contract & homework to lament on something I’ve been thinking about all day…

So, I can’t compile. Flash can’t find my class. I reply, “It’s right there you tard…” Flash repeats itself. I like techno, but I hate things that repeat themselves for the sake of repetition. Through grit teeth, a spark fires in my brain and I remember while reading about class paths not to delete the main one, and if so, how to fix it. Cool, while I go to find it, I’m like, “I didn’t delete nuffin’, Flash is smoking crack.” Anyway, I find $(LocalData)/Classes, and paste it back in. Great, internal classes work, but my shite still doesn’t.

Then, in desperation, I remember that there was one other classpath there originally… a “.”. Add that in, and poof, all works.

Please update the docs for supposed st00pid users like me that magically delete classpaths and because of shrooms they don’t remember how to correctly fix their classpaths.