Blog

  • Save as MX from MX 2004 Gotcha

    I converted my AS2 to AS1, and saved as MX so my manager in Florida could compile the app. However, he was getting rogue symbols in front of his #include scripts, causing errors and not allowing the FLA to be compiled.

    He thought that maybe it was the FLA since he had copied and pasted the text into a new file and saved around the affected area, deleted the actions layer, and recreated, and still no dice. I was worried since if you can’t save as MX, what then?

    Turns out, however, from a <a href=”http://www.macromedia.com/support/flash/ts/documents/howto_2004astomx.htm”>Macromedia technote</a>, that it is in fact that text files that are the problem. Flash MX 2004 saves your classes with UTF-8 Encoding. Flash MX does not support that encoding type for #include files. So, just saved them as ANSI, and good to go.

    So, if your saving as MX, don’t forget to also save your #include files as non-UTF-8 encoded.

  • Post AtlMMUG Flash App Meeting

    Meeting went good last night. Got to meet a few other peeps that I’ve talked to online, but didn’t get to talk long; guess they’re the responsible type who don’t go drinking after such meetings. This adult stuff blows.

    At any rate, I’ve had a few things I wish I could do better. The crowd had a lot of new faces in it, and while coding and writing some notes before the meeting, I listened intently to what the crowd talked about to gauge their expectations. It seemed a few really hadn’t had much experience with Flash, while a ton had jobs like me. I figured it was best to dummy down a lot of what I talked about, and instead focus on overall technologies, and spit out some of the tips I’ve run into. Didn’t really go as planned as I wasn’t getting the reactions I needed out of the crowd; usually, I can use body language from a person to determine how my communication is working with them; same thing with a crowd, but I’m guessing either I was talking way too fast + talking very technical, or it was just a deep subject. It was definately more interactive than my Flashcom talk a year ago, but I feel I need to be more proactive pre-meeting to ensure audience expectations. I didn’t get into the minutae on purpose, but there were a lot of people there I thought maybe could benefit from it.

    At any rate, one .NET’r brought up an interesting piont that I didn’t get to finish talking about. He was like, “What does Macromedia expect Central to have that appeals to a .NET’r that already has Smart Client?” My succinct answer to that is: .NET’rs can do what they do best; code their .NET web services, and code them well. Central can do what Flash does best and focus on the Rich GUI consuming those web services.

    As always, I learn more about public speaking the more I do this. If Leif get’s it captured (since Flashcom didn’t work out), then I’ll post later in the week.

    Thanks for those who came; need to make after hours time next time so we can geek out longer!

  • Central: Dungeons & Dragons Character Creator

    I’ll be discussing this application as well as 2 others tomorrow night at my presentation (Building Flash and Central Applications). If you cannot make it, I’ll be recording it for later viewing.

    This is a developer beta release, and is strictly meant for developers to tear apart the code and learn from it. However, I’d still love to hear ideas or any other comments.

    Special thanks to Geoffrey Williams for his Central AS2 classes, and to Arul for his ActionScript 2.0 code highlighter service.

    App | Help | How It’s Made

    …I wish I was presenting this in Australia, too… I miss you guyz and galz!!!

  • AS1 addProperty Weirdness: 2nd parameter is a must

    Spent the last 3 hours debugging an issue with a few of components that I’m hastily converting from AS2 to AS1. I have to manually use addProperty since AS1 does not support the AS2 way of implementing getters and setters.

    I found that if you only define a get method, for AS1 you have to type in null for the setter, even if you don’t want one. This explicitly tells Flash you dont’ want one. If you type in nothing, I think Flash assumes it’s an empty string or something… at any rate, read-only getter variables set this way must have null typed in the second parameter instead of omitted, or you’ll get the wrong value when you trace it out.