forum > Haxe flash vs NME flash ??
Bart van der Schoor Apr 18 at 20:59
I'm new(ish) to Haxe and slightly confused on this api-split: what is the difference between Haxe's flash target and the flash target from NME?
They both have partial mirror API's, which is extra obvious now I checked-out gm2d, which so primarily opts for Haxe's flash package over NME. (But some mappings are identical. Why not use NME for all targets including flash? Why is this split?
jan Apr 19 at 03:36
Neko Media Engine. SDL like Bindings for haXe / Neko / cpp Create cross platform games and apps for the Neko & c++ platforms Now supports Mac(intel only), Linux, Windows, iPhone, WebOS and Android!As you can see, no mention of flash.
The above project is the same project you can also find in haxelib and which tells a bit more:
1)NME provides an API that is similar to Flash, but available for C++ or Neko. 2)Using the NME command-line tools, you can publish a single application for Windows, Mac, Linux, iOS, Android, webOS, Flash and HTML5.
'Command-line tools' are now included in NME and they are something like a 'Packager / Assets manager'.
Since you can already compile the same script to swf, why not use the same assets manager and also have a flash target?
Flash is a target of the 'Command-line tools' and not of the 'core' NME library.
The api is split because nme does not (yet) implement the complete flash api.
For the flash target 'nme-command-line-tools' use the haxe compiler and the flash api that comes with it.
Justin L Mills Apr 19 at 12:24
Justin L Mills Apr 19 at 12:46
See this years talk from a flashdevelop ide author on NME.