LiveCycle® Data Services Developer's Guide

Administering Data Services Applications > Logging > Using the debugger version of Flash Player

Using the debugger version of Flash Player

The debugger version of Flash Player is a tool for development and testing. Like the standard version of Flash Player 9, it runs SWF files in a browser or on the desktop in a stand-alone player. Unlike Flash Player, the debugger version of Flash Player enables you to do the following:

• Output statements and application errors to the debugger version of the Flash Player local log file by using the trace() method.
• Write data services log messages to the local log file of the debugger version of Flash Player.
• View run-time errors (RTEs).
• Use the fdb command-line debugger.
• Use the Flex Builder debugging tool.

The debugger version of Flash Player lets you take advantage of the client-side logging utilities such as the trace() method and the Logging API. You are not required to run the debugger version of Flash Player to log compiler and web-tier messages because these logging mechanisms do not require a player.

In nearly all respects, the debugger version of Flash Player appears to be the same as the standard version of Flash Player. To determine whether or not you are running the debugger version of Flash Player, use the instructions in Determining Flash Player version in Flex.

The debugger version of Flash Player comes in ActiveX, Plug-in, and stand-alone versions for Microsoft Internet Explorer, Netscape-based browsers, and desktop applications, respectively. You can find the debugger version of Flash Player installers in the following locations:

• Flex Builder: install_dir/Player/debug
• Flex SDK: install_dir/player/debug
• LiveCycle Data Services: install_dir/resources/player/debug

Uninstall your current Flash Player before you install the debugger version of Flash Player. For information on installing the debugger version of Flash Player, see the Flex installation instructions.

You can enable or disable trace logging, change the location of the trace output, and perform other configuration tasks for the debugger version of Flash Player. For more information, see Configuring the debugger version of Flash Player.

Subtopics

Configuring the debugger version of Flash Player

You use the settings in the mm.cfg text file to configure the debugger version of Flash Player. You must create this file when you first configure the debugger version of Flash Player. The location of this file depends on your operating system. The following table shows where to create the mm.cfg file for several operating systems:

The following table lists the properties that you can set in the mm.cfg file:

The following sample mm.cfg file enables error reporting and trace logging:

ErrorReportingEnable=1
TraceOutputFileEnable=1

Log file location

The default log file location changed between the initial Flash Player 9 release and the Flash Player 9 Update. In the initial Flash Player 9 release, the default location is the same directory as the mm.cfg file and you can update the log file location and name through the TraceOutputFileName property. Beginning with the Flash Player 9 Update, you cannot modify the log file location or name and the log file location has changed, as follows:

Windows C:\Documents and Settings\user_name\Application Data\Macromedia\Flash Player\Logs

Macintosh Users/user_name/Library/Preferences/Macromedia/Flash Player/Logs/

Linux home/user_name/macromedia/Flash_Player/Logs/flashlog.txt

Determining Flash Player version in Flex

To determine which version of Flash Player you are currently using--the standard version or the debugger version--you can use the Capabilities class. This class contains information about Flash Player and the system that it is currently operating on. To determine if you are using the debugger version of Flash Player, you can use the isDebugger property of that class. This property returns a Boolean value: the value is true if the current player is the debugger version of Flash Player and false if it is not.

The following example uses the playerType, version, and isDebugger properties of the Capabilities class to display information about the Player:

<?xml version="1.0"?>
<!-- logging/CheckDebugger.mxml -->
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
    <mx:Script><![CDATA[
        import flash.system.Capabilities;

        private function reportVersion():String {
            if (Capabilities.isDebugger) {
                return "Debugger version of Flash Player";
            } else {
                return "Flash Player";
            }
        }
        private function reportType():String {
            return Capabilities.playerType + " (" + Capabilities.version + ")";
        }
    ]]></mx:Script>
    <mx:Label text="{reportVersion()}"/>
    <mx:Label text="{reportType()}"/>
</mx:Application>

Other properties of the Capabilities class include hasPrinting, os, and language.

LiveCycle Data Services ES 2.5

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/lcds/logging_3.html

Add Comment