[Laszlo-dev] Where do I find LzApplication.as

[Neil Mix]

Henry and PT,

Thanks for all the great pointers.  I'm sure this is going to be more  
than enough to keep me going for a bit, I'll poke around and let you  
know how things go.  To be clear we're scoping out possibilities right  
now, there's lots of hurdles to get through before we can even think  
of deploying Flash 9, so don't expect any changes soon.  Fingers  
crossed, though.  I guesstimated 2 weeks work, I'm about 2 days in,  
which puts me well ahead of schedule. :)

Thanks,
   -Neil

On Oct 28, 2009, at 5:41 PM, P T Withington wrote:

> Hey Neil, hi!
>
> Hopefully you have already seen:  http://wiki.openlaszlo.org/SWF9_Conversion
>
> You might want to read the latest copy of "OpenLaszlo <view>":  http://openlaszlo.org/misc/OpenLaszloView103109.pdf
>
> We've spiffed up our debugger in the latest trunk build so that it  
> _should_ be more helpful than what is available in 4.6.1.  So, you  
> might want to try a nightly build (from http://download.openlaszlo.org/nightly/trunk/) 
> .
>
> Alternatively, you can try using the flex debugger, fdb.  Henry (cc- 
> ed) can fill you in on the details of that.  If you lzc --debug  
> there should also be annotations in the intermediate files that  
> should point you back to your original source.
>
> Finally, you can set compiler.catcherrors=true in WEB-INF/lps/config/ 
> lps.properties (it's commented out in the distribution by default),  
> and this will make swf9 act a bit more like swf8 by catching and  
> ignoring any errors.  Not recommended, but sometimes needed as a  
> last resort.  (In the nightlies, essentially a debug compile catches  
> all errors and reports them in a way that you can relate back to  
> your LZX source).
>
> Let us know how it goes.  We need more 'big' swf9 projects, and  
> always glad to help out Pandora.  :)
>
> On 2009-10-28, at 18:14, Neil Mix wrote:
>
>> Hi folks,
>>
>> I'm attempting to port a very oooold Laszlo project to 4.6.1, swf9  
>> runtime.  The project is compiling successfully, but when I run the  
>> app it fails early on during startup.  No errors are showing up in  
>> the debug window, but the handy debug Flash is logging the  
>> following stack trace:
>>
>> TypeError: Error #1006: value is not a function.
>> 	at <anonymous>()[/private/var/folders/Af/AfhEQDevFwaKcP77YUvST+++ 
>> +TI/-Tmp-/lzswf9/Users/nmix/sbwork/neil-8.9-flash-upgrade/ 
>> SavageBeast/Engineering/projects/radio/src/flash/TMP_ANT/pandora/ 
>> build/tuner/LzApplication.as:16907]
>> 	at <anonymous>()[/private/var/folders/Af/AfhEQDevFwaKcP77YUvST+++ 
>> +TI/-Tmp-/lzswf9/Users/nmix/sbwork/neil-8.9-flash-upgrade/ 
>> SavageBeast/Engineering/projects/radio/src/flash/TMP_ANT/pandora/ 
>> build/tuner/LzApplication.as:17223]
>> 	at <anonymous>()[/private/var/folders/Af/AfhEQDevFwaKcP77YUvST+++ 
>> +TI/-Tmp-/lzswf9/Users/nmix/sbwork/neil-8.9-flash-upgrade/ 
>> SavageBeast/Engineering/projects/radio/src/flash/TMP_ANT/pandora/ 
>> build/tuner/LzApplication.as:17324]
>> 	at LzScript()[/tmp/lzswf9/lzgen24517/LzScript.as:8]
>> 	at LzNode/makeChild()[/tmp/lzswf9/lzgen24517/LzNode.as:866]
>> 	at LzInstantiatorService/makeSomeViews()[/tmp/lzswf9/lzgen24517/ 
>> LzInstantiatorService.as:221]
>> 	at LzInstantiatorService/checkQ()[/tmp/lzswf9/lzgen24517/ 
>> LzInstantiatorService.as:171]
>> 	at Function/http://adobe.com/AS3/2006/builtin::call()
>> 	at LzEvent/sendEvent()[/tmp/lzswf9/lzgen24517/LzEvent.as:89]
>> 	at LzIdleKernel$/__update()[/tmp/lzswf9/lzgen24517/LzIdleKernel.as: 
>> 19]
>>
>> Now I recognize that Flex is the compiler underneath and this is an  
>> intermediate auto-generated file.  Finding the file and the source  
>> of the bug is not very hard.  But this is almost certainly the  
>> first of many such errors I need to fix.  It would be great if I  
>> could automatically tie this back to the original source file/ 
>> line.  Is it normal for errors like this not to show up in the  
>> Debug window?  Is there anything I'm doing wrong that prevents me  
>> from seeing the original source file/line?
>>
>> A couple facts about my setup that could influence things:
>> - I'm compiling from the command-line
>> - As you can probably see, the app is pretty dang big
>>
>> Thanks for any advice,
>> -Neil
>