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 >> >>
