Within the generated AS3 code you have markers pointing to the file and line number of the original LZX code, e.g.

<library>

<class name="myclass" extends="view" width="100" height="100" bgcolor="#ffccaa">

  </class>

</library>

tranlates to

package {
dynamic class $lzc$class_myclass extends LzView {
/* -*- file: myclass.lzx#4.1 -*- */
static var tagname = "myclass";static var attributes = new LzInheritedHash(LzView.attributes);function $lzc$class_myclass ($1:LzNode? = null, $2:Object? = null, $3:Array? = null, $4:Boolean = false) {
/* -*- file: -*- */
/* -*- file: myclass.lzx#7.1 -*- */
super($1, $2, $3, $4)
}
/* -*- file:  -*- */
/* -*- file: myclass.lzx#10.1 -*- */
LzNode.mergeAttributes({bgcolor: LzColorUtils.convertColor("0xffccaa"), height: 100, width: 100}, $lzc $class_myclass.attributes);}
}

I had best success with debugging in Flex Builder, but you can use the Flex command line debugger fdb as well.

- Raju

On Jul 24, 2009, at 1:28 PM, Sebastian Wagner wrote:

hi,

actually you run into a lot of compilation issues when you run a previous application into SWF9. I followed the SWF9 Migration Guide of course, the code has zero problems to be compiled to SWF8. I guess in most cases its something very tiny tricky in the code that needs to be changed but actually you don't get anything except *org.openlaszlo.sc.CompilerError: Errors from compiler, output file not created*
The console does also only pring:
FAIL: compiler returned 1 ... or another number

So how do you get those Compile Errors?
I guess they are not really that handy as they will show you only errors in the resulting ActionScript that is going to be compiled by the Flex compiler.
So you will not see which LZX-Codeline has the error.
But without any notice at which code-block to look at its almost impossible to migrate more then a bunch of code lines with every compilation.

I've seen that there are some properties in the configuration:
compiler.swf9.warnings=false
compiler.swf9.execflex=true
# Tell compiler to catch errors in debug mode
compiler.catcherrors=true

changing them does seem to have an effect.

Is there a clue that is hidden somewhere or how do you judge what needs to be done when you run into this?

thanks,
sebastian

--
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
[email protected]

Reply via email to