Question
AIR 3.7 Feedback
With the new IOS loading abilities introduced in 3.6 & 3.7, I find them pretty limited for a couple of reasons:
- The fact that the complier strips AS code from the external swf files and embeds it in the main swf file means that anytime my assets change, my master swf file must be recompiled and re-submitted to the App Store. Not desirable. The whole point of having remote swf assets is to keep the assets separate from the main application code, so that the application's content can be updated on an as needed basis without having to recompile the main app.
- Having the restriction to load an external swf file only once is a problem. Picture a view based mobile app that uses external swf assets, like pdfs that have been converted to swf files. Such an app would only allow the user to view the document only once when the view was loaded with this restriction. When the user goes back to the view again the app locks up.
My next task during the development of my application is to separate all of the images, xml, mp4, and swf assets from the main app and make them downloadable on an as needed basis, so that the initial download of the app is small. I think these new features don't really help do that in an ideal way. Is this just because of IOS restrictions?
AdChoices