When you turn on debugging in an app, the compiler actually just forces an <include> of the lps/components/debugger/debugger.lzx library, which contains the debugger window and all the resources. So it is exactly equivalent to if you manually did <include > of the debugger
On Sat, Aug 14, 2010 at 9:23 AM, Raju Bitter < [email protected]> wrote: > That's what I guess as well. But I've read - as Henry has pointed out > - that the Flex debugger should strip any AS2 code out of resources > directly embed into an app. Maybe that's different for SWCs? Is the > debug console with the resources baked into the SWF10 debug LFC? > > On Sat, Aug 14, 2010 at 3:48 AM, Max Carlson <[email protected]> wrote: > > The only think I can think of is there's some AS2 code embedded in an > old, > > AVM1 style resource. > > > > Regards, > > Max Carlson > > OpenLaszlo.org > > > > On 8/12/10 5:58 AM, Raju Bitter wrote: > >> > >> Adobe AIR for Android and AS2: > >> http://labs.adobe.com/technologies/air2/android/#faq > >> Which versions of ActionScript are supported when developing for > Android? > >> ActionScript 3 based content is supported on AIR for Android. > >> ActionScript 1 and 2 is not supported and will not work. > >> > >> Can I re-use existing Flash code and content when targeting the Android? > >> Yes, assuming that that code and content is written in ActionScript 3, > >> and does not use any of the APIs or functionality not available on the > >> device. > >> > >> I still wonder how we could have AS2 code in the application? > >> > >> On Thu, Aug 12, 2010 at 1:17 PM, P T Withington<[email protected]> wrote: > >>> > >>> Max made this change recently as part of > >>> > >>> http://jira.openlaszlo.org/jira/browse/LPP-9106 > >>> > >>> which shows the files affected. > >>> > >>> I think we should back out the preloader changes, because they are not > >>> related to the bug, and because of the reasons I cite below. > >>> > >>> On 2010-08-12, at 07:07, Raju Bitter wrote: > >>> > >>>> How is that implemented, Tucker? Where is the source code for the > >>>> progress bar? > >>>> > >>>> And I agree with you, we don't need a progress bar any more. > >>>> > >>>> On Thu, Aug 12, 2010 at 1:03 PM, P T Withington<[email protected]> > wrote: > >>>>> > >>>>> That would be bad. > >>>>> > >>>>> I noticed recently that Max enabled a 'progress' feature by default. > >>>>> Personally, I don't like it. I actually feel like the progress > >>>>> notification slows down the loading of the app: both psychologically > >>>>> (because I associate progress notification with things that are slow) > and > >>>>> actually (because there are CPU cycles used in the progress > notification > >>>>> that could better be used by getting my app going). > >>>>> > >>>>> On 2010-08-12, at 06:40, Raju Bitter wrote: > >>>>> > >>>>>> Testing the AIR runtime today I ran into an error when running the > AIR > >>>>>> application, which as packaged using the debug switch on (-target > >>>>>> apk-debug). > >>>>>> "Your application is attempting to run ActionScript 2.0 code, which > is > >>>>>> not supported on smart phone profile". Here's a screenshot of the > >>>>>> error message: > >>>>>> http://www.flickr.com/photos/semanticmemories/4884408977/ > >>>>>> > >>>>>> Are we using AS2 code in the LFC - even for the SWF9/10 runtime? > Might > >>>>>> that be the preloader? That would be my guess. > >>>>>> _______________________________________________ > >>>>>> Mobile mailing list > >>>>>> [email protected] > >>>>>> http://www.openlaszlo.org/mailman/listinfo/mobile > >>>>> > >>>>> > >>> > >>> > > > > -- Henry Minsky Software Architect [email protected]
