hi,
I use a fake Log class:
/**
* a fake log class
*/
class com.jaco.Log {
public static var NONE:Number = 0;
public static var INFO:Number = 4;
public static var WARNING:Number = 2;
public static var ERROR:Number = 1;
public static var VERBOSE:Number = 7;
}
and use a task similar to this:
<target name="compile" description="build swf file">
<mtasc
src="${src.dir}/${ant.project.name}.as"
classpath="${src.dir}:${std.dir}"
swf="${build.dir}/${ant.project.name}.swf"
main="true"
trace="null"
header="${width}:${height}:${framerate}"
version="8" />
</target>
so you can keep trace calls
For the latest and definitive productions I suggest to remove al trace calls
and remove -trace in mtasc and task
:)
Jaco - pixeldump
----- Original Message -----
From: "John Giotta" <[EMAIL PROTECTED]>
To: "Open Source Flash Mailing List" <[email protected]>
Sent: Monday, June 12, 2006 2:21 AM
Subject: [osflash] ASDT Logger Tips
>I ran into a problem just last week and it kind of interesting.
>
> I've used the Logger with ASDT projects in the past, but recently I've
> really had to integrate thorough debugging output. The logger code and
> tracing has been published to production a SWF still intact. Besides the
> unusual call to local host (which I understand), the Log class seems to
> cause a few unwanted effects/defects.
>
> The first one is that getURL seems to fail in some instances and other
> is the Settings Dialog goes completely bonkers.
>
> Does anyone have any tips on using the logger in production or should I
> just avoid all trace calls in the production build?
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
