Flash & Flex Technical Standards

Errors

It's easy to make your file work fine under normal conditions, but it's a lot tougher when it's strained. The reviewers will try to break your file. They'll click buttons quickly, click other buttons before the previous element is finished loading, and do whatever else it takes to put strain on your file. Files should be built in a way that they work flawlessly regardless of the strain put on them. Before submitting your file do your best to break it. Any error will result in a rejection.

Using the debug player

Files often react differently online than when tested locally. ActiveDen reviews use the debug player when testing your files in the browser. If the debug player reveals an error, your file will be rejected. Always test your files online using the Flash debug player. Follow these steps to download and use the Flash debug player:

• Determine which player you're currently using by going here. This will even tell you if you're using the debug player (which can be hard to test sometimes).
• If you're using Flash Player 10.0, you can download the debug player here. If you're on 10.1, download it here.
• Be sure to download and install both the activeX control and browser plugin. You need them both.
• If it doesn't work, try uninstalling and starting again. You can find the Flash Player uninstaller here.

Motion

Movements and transitions should be smooth. If your file's movements are choppy, there needs to be a good reason like on this file.

Try not to mix and match transitions. If most of your buttons fade in when rolled over and there's just one that jumps directly from one color to another, it may look out of place. That's not to say you should never mix and match. It just means that you should be aware of staying consistent with the style and feel of your file.

Rollover, rollout, release

If your rollover has an animation or transition, it needs to have a smooth rollout as well. If your button fades from white to black on rollover, it should fade back to white rather than instantly going back to white.

If the user rolls out before the transition is complete, it should transition from the point it got to. For example, let's say you have a contact us button that looks like an envelope. When the user rolls over, it opens. If the user rolls out when the envelope is only half open, it should close from the half open point. When the user rolls out it shouldn't jump from half open to fully open, then animate shut.

Make sure that if the user clicks a button, but releases outside, it continues to work properly.

CPU usage

Always be sure to optimize your file. Remember, not everyone has as fast of a computer as you do. Be sure to test your file on a slower computer to see how it reacts. Unoptomized files that slow down average computers will be rejected.

File size

The size of your file should reflect what it can do and looks like. As the file size goes up so should the visual and technical standards.

Code commenting

If your file uses any code, whether it be actionscript, PHP, or anything else, it needs to be commented. That allows buyers to be able to quickly and efficiently scan through your code and find what they need to change. Not every line needs to be commented. Just make sure that enough is commented so the buyer will be able to understand what you've created.

Name your layers and folder in the timeline in a way that will make sense to anyone trying to edit your file. Also, be sure not to put objects on the same layer as the actionscript.

Be sure not to put objects on the same layer as the actionscript.

Library

Name your library items and folder in a way that will make sense to the buyer. Don't use names like Symbol 1 or button copy. Make sure all your assets are organized into one main folder and logical sub folders.