I’ve been running a couple of tests with a new installation of Expression Engine 2.0 Public Beta. Everything has been running pretty smoothly, but I did run into an error when I tried to edit existing pages added during the installation (if you selected to have Agile Records added).
This morning I woke up to a downed site. I could log into the administration section of the site, but none of the public-facing pages worked. Turns out it ended up being a small change that was needed in the .htaccess file.
Now that I’m delving further in dynamic abstraction, I needed a way to convert my ActionScript-driven artwork into a workable vector file. After overcomplicating the issue the light bulb when off, and realized a very simple process was sitting right in front of me. It always seems to be the case right?
The biggest hang-up that I see developers get into is the tight coupling of different objects and classes in their Flash project. For example, one movie clip will contain two other child clips. These child clips will in turn directly call methods on the parent clip, that then call something else, and then call something else…. it just keeps going this way. Doing this ends up leaving you end up with a bunch of crossed wires, and eventually you’re dealing with something that’s very fragile to work with.
I try to follow one primary rule when it comes to this sort of thing: Parents can directly tell children what to do; children can only tell them that something with them occurred.