Blog

  • Packages Rock

    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.

  • The Challenges of a Flash Developer

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

  • Recreate classpath if Flash can’t find your class

    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.

  • DataProvider API already written for you

    After writing this for the 2nd time, I’m not writing it again. I’m saving this mofo to some easily retrievable AS file or a JSAPI command.

    At any rate, here it is for you to copy and paste into your own component that you wish to implement the DataProvider API, but don’t feel like typing it again and again and again……….

    <a href=”https://www.jessewarden.com/downloads/DataProvider_FillIn.as”>DataProvider_FillIn.as</a>