MACROMEDIA FLASH 8-LEARNING ACTIONSCRIPT 2.0 IN FLASH, Руководство пользователя

Страница: 714 / 830

714 Debugging Applications
Debugging a SWF file from a remote location
You can debug a remote SWF file by using the stand-alone, ActiveX, or plug-in version of
Flash Player. To find these versions of Flash Player, look in the following directory in
Windows or Macintosh:
Flash install directory
\Players\Debug\.
When you export a SWF file, you can enable debugging in the file and create a debugging
password. If you don’t enable debugging, the Debugger is not activated.
To ensure that only trusted users can run your SWF files in the Flash Debug Player, you can
publish your file with a debugging password. As in JavaScript or HTML, users can view
client-side variables in ActionScript. To store variables securely, you must send them to a
server-side application instead of storing them in your file. However, as a Flash developer, you
may have other trade secrets, such as movie clip structures, that you do not want to reveal.
You can use a debugging password to protect your work.
To enable remote debugging of a SWF file:
1.
Select File > Publish Settings.
2.
On the Flash tab of the Publish Settings dialog box, select Debugging permitted.
3. To set a password, enter a password in the Password box.
After you set this password, no one can download information to the Debugger without
the password. However, if you leave the Password box blank, no password is required.
4.
Close the Publish Settings dialog box, and select one of the following commands:
■
Control > Debug Movie
■
File > Export > Export Movie
■
File > Publish
Flash creates a debugging file, with the extension .swd, and saves it in the same directory
as the SWF file. The SWD file is used to debug ActionScript, and contains information
that lets you use breakpoints and step through code.
5. Place the SWD file in the same directory as the SWF file on the server.
If the SWD file is not in the same directory as the SWF file, you can still debug remotely;
however, the Debugger has no breakpoint information, so you can’t step through code.