Prevent IE javascript error

[faser]

I'm doing some tests with Logger.as. Is it possible to prevent
Internet Explorer javascript errors when debugging the application
with IE?
In this case I think it should be useful to redirect all Logger calls
to the standard trace function.
The other feature is missing is the ability to supress all logs, so we
can go to production code without removing all Logger calls.

[Eric Priou]

> I'm doing some tests with Logger.as. Is it possible to prevent
> Internet Explorer javascript errors when debugging the application
> with IE?
> In this case I think it should be useful to redirect all Logger calls
> to the standard trace function.

hm, what is the standard trace function ?

> The other feature is missing is the ability to supress all logs, so we
> can go to production code without removing all Logger calls.

I go for a preprocessor or mtasc -notrace

Should stop the js from being executed.
----
Eric Priou
aka erixtekila
Articles : http://www.v-i-a.net/inprogress
Oregano : http://www.v-i-a.net/inprogress/doku.php/oregano
Oregano forum : http://www.v-i-a.net/forum/

[aemkei]

Okay, I see your problem:

> I'm doing some tests with Logger.as. Is it possible to prevent
> Internet Explorer javascript errors when debugging the application
> with IE?

When running Flash-projects using Thunderbolt, we run into some
Javascript error message on line 47. This is caused by the code
injection used in our logger.

This issue is fixed now: I made sure the "console.log" method will
be called only if firebug is enabled.

To enable debugging in IE we could use the Lite version:
http://www.getfirebug.com/lite.html

- Martin

[faser]

Thanks, but I can't find the new revison in the class:
http://flash-thunderbolt.googlecode.com/svn/trunk/as3/source/org/osflash/thunderbolt/Logger.as

With the standard trace function I mean that we could revert to Flex
trace if firebug is not available.

[sec...@gmail.com]

Did you mean the ThunderBolt AS3?

Sorry, but this is the difference between ThunderBolt AS2 (based on
MTASC - AS2) and ThunderBolt AS3 for Flex and AS3. Flex doesn't
support an tracing facilities as MTASC (http://www.mtasc.org/#trace)
does, only a possibility to create a custom target class extending the
Flex 2 AbstractTarget class (http://livedocs.adobe.com/flex/2/langref/
mx/logging/AbstractTarget.html). Anyway, ThunderBolt AS3 provides a
custom target class called "ThunderBoltTarget" (http://flash-
thunderbolt.googlecode.com/svn/trunk/as3/source/org/osflash/
thunderbolt/ThunderBoltTarget.as). You'll find on WS-Blog a tutorial
to go this way:
http://www.websector.de/blog/2007/06/17/update-part-1-logging-flex-2-applications-with-firebug-and-thunderbolt-using-the-flex-2-logging-framework/

-sectore

On Jul 24, 8:49 pm, faser <faser...@gmail.com> wrote:
> Thanks, but I can't find the new revison in the class:http://flash-thunderbolt.googlecode.com/svn/trunk/as3/source/org/osfl...

[aemkei]

I digged into the IE error massage and figured out the problem:

You can not add an ExternalInterface callback called "profile" or
"start". So I switched the internal method names to "pause" and
"profileStart" but let the JS endpoints what they always have been.

- Martin