I just created this somewhat nifty image using Wordle. It parses my blog posts and grabs the most used phrases. The larger the word, the more the phrase was used. Cool.
Pages
-
Categories
- Categories
-
Archives
Here’s a pretty great little tutorial on house to the use the new ”bone tool” in Flash CS4. Be sure to check it out!
I’ve really had a hard time about whether or not to purchase the new Adobe Master Suite. I’ve read some good/bad things about the newest incarnation of Flash, but I don’t think (at the moment) I can justify the steep price tag. The new features that I find quite useful are: the integration of a ’3D’ engine, and the use of inverse kinematics. Hopefully prices will start dropping around Xmas, as I’m sure that will help push me in the direction of making a purchase.
Last night I was working on a corporate project that has an upcoming deadline, when I hit a roadblock. I’d been working in the Flash IDE, strictly using class linkages from the library (ie. no assets on the stage/timeline whatsoever). When I’d finished the swf/final product, I decided to then make a preloader for the movie. This is where the epic headache began. I tried using the conventional method of adding a second frame to the timeline, and using a progress event handler on frame one/exported classes to frame 2. This was all fine and dandy except for the fact that all of my linked assets are being exported to frame one, in turn, caching all of the data to be preloaded on frame one. This basically makes for a blank screen while you’re waiting for the page to load, with the preloader making a brief appearance at around %98. Not good. I then stumbled upon a new tutorial over at www.gotoandlearn.com that explained the steps on how to make a bare bones external preloader using AS3. This method worked wonderfully using the stock content packaged in the .rar file, but when I tried applying it to my own SWF, it threw a #1009 error. Basically, it’s referencing a ‘null’ object, something that hasn’t been created or referenced yet. I rechecked my original project file, only to find that the error was being thrown in the first line of code being parsed, which also happened to be an import statement. The statement was importing a custom class for tweening in the timeline, and for some reason, the class was throwing an error. I’ve yet to figure this out, as I haven’t had much time to tinker around with it since yesterday. My plan is to create a document class, and retry the external preloader. Time will only tell if this is going to work…
