Flash code planning — OZONE Asylum, home of the Mad Scientists

Multimedia/Animation

Flash code planning

This page's ID: 11462

Edit Post

Who can edit a post?	The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.

Your User Name:
Your Password:
Login Options:	Remember Me On This Computer

Your Text: Insert Slimies » Insert UBB Code » Close Last Tag \| All Tags UBB Help	You should be able to accomplish most things without needing to resort to numerous timeline scripts. Few of the tutorials I've found for flash are actually useful in a real application. Most of them are simply exploiting the ability to script within a timeline like environment to accomplish some cheap effect. That being said, Steve wrote a nice primer about where action script code goes and why over at the GN, I suggest you read it if you haven't done so already. Although, there will always be times when you'll need to do that. That?s just how flash is. However, there are many ways you can simplify things. For example, I usually make heavy use of the ability to attach movie clip instances from the library, which gives you the ability to code the application as a series of components (no, not the awkward flash "components" per say, I'm using the word in a more general sense, although I hear they're easier to develop in MX 2004). For example, say you have a custom alert box component, you could attach it then setup button events like so: depthN = 10 initObj = [type:"error", _x:100, _y:100] targetMC.attachMovie("linkageID","myAttachedMovie",depthN,initObj) // you'll want to check the syntax for this one... targetMC.myAttachedMC.controlsMC.closeButtonMC.onRelease = function() { Close alert box code.... _parent._parent.removeMovieClip() // not to sure that address is correct, might need another _parent but you get the idea... } And so forth. It can get a little long winded and it's still a bit of a pain trying to keep track of where everything resides as you dynamically attach things left right and centre, but it's no where near as confusing as having a mess of code throughout the movie. You can also make movie clip object instances children of custom code objects, which can also remove the need to have many scripts inside movie clips. Although, I've not played with this terribly much yet, but it does have it's uses here and there. Also note that with flash MX 2004, if you use classes then I believe you have to use external action script files, which should help you avoid this problem anyways. At the end of the day, it all depends on what you're trying to do. If you need to script timeline events and you don't want to go out of your way to create a scheduler to control all the animations you require, then you'll most likely need to use timeline/frame scripts here and there. However, if you do not need to script any time based actions, then you shouldn't be using frame scripts. Although, I've only been using flash for a few months, and only developed one not so usefull applicaiton with it, so I'm sure there are a lot of other ways to help keep it all togther, but their the ways I've found that seem to be working quite well. Loading...
Options:	Enable Slimies Enable Linkwords

« Backwards — Onwards »

Show Forum Drop Down Menu