Using new Simulator Support feature for iOS « AIR-o-Dynamics. With Adobe AIR 3.3, support for native iOS simulator would be available for application development. Prior to this feature, the only way to test AIR applications on iOS was to have an actual device along with a developer certificate from Apple. With simulator support now available however, there is no need to obtain a developer certificate (which is a time consuming process) or to create a provisioning profile before starting to develop an AIR application.
A p12 certificate, which can be created by the developer himself would be sufficient. Native simulator for iOS is very helpful in testing and debugging AIR applications. Simulator for iOS is based on x86 architecture and therefore two new targets have been added in ADT to support the same. Targets are: 1.) ipa-test-interpreter-simulator2.) ipa-debug-interpreter-simulator. To package application for simulator in any of the above targets, execute either of the following commands: Test Interpreter Target Debug Interpreter Target. Kick starting the garbage collector in Actionscript 3 with AIR « Craftymind.
During the final months of my work with eBay Desktop, my sights were set squarely on optimization, both memory and cpu. When it came time to start messing with the garbage collector, my sanity went from bad to worse. What I originally thought was going to be a straightforward way of releasing memory in AIR turned into a 2 month long testcase with some discouraging outcomes. Memory usage in eBay Desktop was something that always lingered in the back of my mind during the entire development cycle. Because of the shifting nature of our requirements, the issue was only explored near the end, even though we knew in the beginning that memory usage had to go through valleys and peaks in a managed way while users spent time in it throughout the day.
We had alerts that would open and close, we had an app that would run in the system tray, and we considered making a ‘lite’ mode that would sit on top of your desktop all day, each of which had different memory requirements. Flash.system.System.gc() Test Flight « « Native Extensions for Adobe AIRNative Extensions for Adobe AIR. Button on top of a StageWebView | LancelotMobile.com. WebStage AIR component is a really nice and powerful, but it has a drawback, at least on iOS.
If you make it full screen there is now easy way to close it and to return to your AIR application. Let’s discuss all possible way so solve this problem. One solution is to add a HTML(JS) button inside the web view, which will fire an event and you will handle it in your AIR app and then hide the web-view.
This sounds reasonable, but it is possible only if you are displaying local data. But what to do when we should display a public web site in full screen and we have no control on the HTML content which will be served? Here at Lancelot we were struggling with this problem so many times and finally we’ve decided to create a native ANE component which could be displayed on top a web stage view. This component is a simple button.
Here is a code which shows how this works. So far we support only iOS because there is real need. Here are the results: Hope you enjoy it and use it in your next app. Sign in. Garbage collector in Flash Player 9/Actionscript 3 (Comtaste Consulting | Enterprise RIA consulting and development) All Java developers that start developing software in Flex know what garbage collector is and how it works; the Flash developers, who can be not so well-informed about it, should begin to understand what it is, because the new functionalities introduced into Actionscript 3 can lead to memory leaks. The garbage collector of actionscript 3 works in 2 different ways to know which object should be deleted from memory: the reference counting method and the mark&sweep.
In the first case every object maintains the number of references to it during the application's execution; when an object is created its reference count starts from 1, every time this object is referenced by others its reference count grows, on the contrary the reference count decreasees when another object with a reference to it is deleted. When the number of references goes down to 0, then the garbage collector can remove the object from memory. At the end of the visit all the objects not marked could be deleted from memory. try.
Actionscript 3 - AS3 - iOS device UDID and IP access for Smaato integration. Tracking memory leaks in AS3 | Damian Connolly | divillysausages.com. If you're a super cool, handsome Flash dev like me, memory management is an important part of your daily coding routine. While Flash has a garbage collector available so you never have to go to the same lengths as in C++, there's a lot of things we can do to make its life a lot easier and make sure everything, including our game, runs like gravy. When things do go arse over tit and our program is leaking memory faster than my ability to forget names the minute they're told to me, how can we make life easier for ourselves? [Sod this, I only want the code] Refresher time! What is s? If you say s is a Sprite then hang your head in shame. s is actually a reference to a Sprite. In AS3, everything is passed as a reference (primitive objects like String, Number, int and their ilk have special operators in the background that make them act as if they were passed by value).
Pass by value example: Pass by reference example: What's this got to do with memory management? Magic. Reference counting. Contact Us – Mochi Media :: Fueling Creativity. @renaun posts: Developing for both retina and non-retina iOS screens using AIR 2.6. AIR 2.6 provides updates to the old Packager for iPhone (PFI). The packager binary is now part of the normal AIR packaged called adt. The new adt options are just like the old pfi packager options, see below: adt -package -target ( ipa-test | ipa-debug | ipa-app-store | ipa-ad-hoc ) CONNECT_OPTIONS?
SIGNING_OPTIONS <output-package> ( FILE_OPTIONS | <input-package> ) Screen Resolution and Pixels Per Inch (ppi) When developing you applications for retina and non-retina iOS screens, for example a iPhone 3GS and a iPhone 4G, you need to take in account the large differences in resolutions. The retina enabled devices have have a 960×640 resolution 3.5in physical screen which comes out to 324ppi . Abstractly lets just talk about what this means in terms of pixels. What about in the AIR based applications? In Flash we still play with pixels, so turning on the option for retina display will make your SWF either 960×640 or 480×320 in size depending on retina support. How to design for this? <? Air_deviphoneapps. AIR * iOS Settings. Adobe AIR 3.3 and higher supports multitasking on iOS by enabling certain background behaviors: AudioLocation updatesNetworkingOpting out of background app execution Note: With swf-version 21 and its earlier versions, AIR does not support background execution on iOS and Android when render mode direct is set.
Due to this restriction, Stage3D based apps cannot execute background tasks like audio playback, location updates, network upload or download, etc. iOS does not allow OpenGLES or rendering of calls in the background. Applications which attempt to make OpenGL calls in the background are terminated by iOS. Android does not restrict applications from either making OpenGLES calls in the background or performing other background tasks like audio playback. With swf-version 22 and later, AIR mobile applications can execute in the background when renderMode direct is set. Background audio <InfoAdditions><! Background location updates <InfoAdditions><! Background networking <InfoAdditions><!