IntroductionMany flash designers have experienced the nagging feeling of uncertainty that comes with delivering some or all of a site before payment. While in an ideal world everything is solidly locked in with contracts, often deals are made via word of mouth, or the work is for a "friend" or aquaintance who may deserve more trust or special treatment. There's times where a newer flash developer may come across a contract-shy small-time client offering flash work which is highly desirable for portfolio, money, or experience reasons. Whatever the reason, covering your back end isn't a bad thing to do; and despite your best attempts, may become necessary.
This tutorial assumed you know how to make movie clips and buttons, have a fairly decent grasp of actionscript, and are familiar with loading movies.
How does it work?There are many ways to protect your work. The method we'll be dealing with here involves loading an .swf movie into their site from your server.
Take a look at this:
Set up your site so that your primary (shell) swf loads in the content from other swf files, it will also load your remote message into a target movie clip. This way if the client demands to have the .fla files (it happens) you can give them all of the files they need to have to edit their content... but you'll still have the security of still being able to keep your remote message capabilities.
In the top half of the diagram you see that the remote message is not loading into your shell (yellow) because you've renamed, moved, or deleted it. When that happens, the user will never see a hint of it, with no errors at all. It just simply fails to load it into your target MC (movie clip).
In the bottom half we see that your remote message (orange) loads in over top of everything else. All you had to do was place the right file in the right place on your server.
|» Level Intermediate|
Rating: 8 Votes: 53
|No details available.|
|Download the files used in this tutorial.|
|Download (57 kb)|
|More help? Search our boards for quick answers!|