Earlier this week, NME 3.2 was released. NME 3.2 added built-in SWF asset support, brought new APIs, improved the NMML project format, support for extensions and continued our support for devices and platforms.
While 3.2 was a feature release, 3.2.1 will be a stability and toolchain update.
Android builds have been updated to use the recently released Android NDK r7b. You will be able to update your copy of the NDK easily by running “nme setup android” after upgrading.
iOS builds have been updated to compile for the ARMv7 processor architecture instead of ARMv6. For performance and simplicity, we are not supporting universal packages at this time. This change also moves the minimum OS version from iOS 3.0 to 4.3.
It has become increasingly difficult to avoid making ARMv7 builds because of Apple’s changes to XCode and submission policies for the App Store. While we are also considering a move to OpenGL ES 2.0 in the not-so-distant future, we would need to begin supporting only ARMv7 or newer devices (many ARMv6 devices do not support GLES 2.0). To keep build times low, to maintain our current build process and for these reasons, making a move to ARMv7 for iOS has seemed to make the most sense.
This also means that if you use iOS 4.x or 5.x features in your application, such as through an NME extension, you will not need to create ARMv7 libraries yourself.
Version 1.08 of the SWF library was recently released, adding initial support for buttons. This update for NME improves our generation of SWF classes to create both MovieClip and SimpleButton classes automatically, and addresses API changes which took place because of the upgrade.
The waxe library has been posted to haxelib, and this version of NME resolves some minor issues which prevented you from compiling certain kinds of projects using the NME command-line tools. Believe it or not, the NME command-line tools do not require that you build an NME application. If
<haxelib name="nme" /> is included in your waxe project, NME will create an NME window (like normal) but you will be able to access additional UI elements like dialogs, windows, panels and buttons. On the the other hand, if the NME haxelib is not included in your NMML, you will be able to configure your own native OS window yourself.
We will be talking about waxe more in the future, and exploring how NME and waxe can continue to work together to improve application development.