Update for Neko 2
Flash compile fix
Disable experimental OpenAL sound for OS X for now, update Mac Neko binaries
Confirm that "nme_dev" is being defined properly

Haxe 3 supports values for defines. Now there will be an "nme_dev" value with the current version, similar to the new "haxe_dev" value

If you are maintaining Haxe 2 compatibility, you can adapt to NME 3.6 by either checking for "nme_dev" existing, or if using "haxe3", since no older version of NME supports Haxe 3.

With Haxe 3, you will be able to perform comparisons, like...

#if (nme_ver < "3.6.1")

#if (nme_ver > "3.6.0")

#if (nme_ver == "3.6.0")

In order for comparisons to work properly, you must surround it with parenthesis, and you must compare as a string, since "3.6.0" is not a valid number.
Change to core haxe.ds.Vector type and other clean-up
Begin to orient as a 4.0 release, because of Haxe 3 related changes
Fix 10.6.8 compatibility
Migrating platform setup to new tools, removing access to old tools, removing HXSSL dependency (will have to refactor to use URLLoader instead)
Switch back to nme.Vector

The haxe.ds.Vector type has strict size limits, which is not ideal as an enforced type for all places where the Flash API uses Vectors. Instead, we can have a new nme.Vector type, which is lenient (allowing push(), shift(), etc) and can have new conversions to add extra convenience, like automatically converting arrays to vectors, only on Flash
Have to switch back to basic typedefs for now on the Vector type, because properties must be "(get, never)"

Once abstract types can accept setters, we can switch it back, and could also use abstract types to help resolve some other areas of the API, such as extending flash.display.MovieClip
Update readme for working from the source
Now that abstract types in Haxe development builds support setters on properties, the new abstract Vector type is up and running, including automatic conversion for calls like this:

var vector:Vector<Int> = [ 1, 2, 3, 4 ];

I'll continue to try and pay attention to see if there are other ways that the NME vector can make the type less of a headache, and more like using standard arrays, which is the base type for most platforms, anyway.

The abstract implementation is commented out still, so NME remains compatible with the Haxe 3 RC for now
Remove the out-dated ApplicationMain.getAsset API