http://aphall.com/2014/10/future-of-flash-pro/

So you can use the Flash IDE to prepare and publish content for (not-the-flash-player) compile targets.

Among these new platforms is OpenFL:

http://www.openfl.org/blog/2014/10/10/future-of-flash/

When they demoed the custom project feature at Adobe MAX the other night, they brought out Joshua Granick (lead maintainer of OpenFL) to show off a custom OpenFL project format that lets you make Flash Art in Flash CC, then compile it to HTML5, Flash, and C++ (desktop+mobile) targets.

Some of you might remember that I pestered Adobe about this back in June:

http://www.fortressofdoors.com/dear-adobe-support-haxe-save-your-tools/.

Later, a tech evangelist from Adobe reached out to me (see comments section of linked article)... you'll notice it's the same guy (Andy Hall) who wrote the Adobe article linked above. Coincidence? :)

Granted, this is the tiniest baby step Adobe could have possibly made, but it's still pretty huge.

Reasons this matters:

1. Adobe admits the Flash ecosystem is no longer dominant

2. Adobe admits the Flash workflow has a lot of orphaned (and rightfully grumpy) users

3. Provides hope Flash CC might have a future beyond the Flash (SWF/AIR) platforms.

4. Perhaps Adobe will go further and actually provide monetary support to open source projects like Haxe and OpenFL?

Years ago I would have never believed we would one day see an entirely open source implementation of the Flash API with anything even remotely close to full API coverage, let alone the ability to export to HTML5, Flash, and C++. And if it had, I would never believe that Adobe would bring it on stage at MAX.

------

Anyways, interested in your thoughts on this.

(Full disclosure, I'm a known Haxe/OpenFL enthusiast, although nobody pays me for the privilege)