Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Re:To Clarify (Score 1) 166

There's a few things here and there, not sure if there's an actual list. If you target flash, obviously you have all flash functionality available, but certain things (such as super-advanced international text field support) still need to be added on various targets. HTML5 is a brand new target so that's the least mature, whereas mobile and desktop targets have really good coverage. A "list of gaps we need to fill" would definitely a good feature to add to the OpenFL site, though.

Comment Re:To Clarify (Score 1) 166

OpenFL supports HTML5: http://www.openfl.org/blog/201... So any improvements to HTML5 will also benefit OpenFL. What OpenFL solves is the issue of "shit, my platform holder's investors got bored and yanked the rug out from under me, time to build my workflow back together from scratch!" By using Haxe, I can preserve my codebase and pivot to whatever the hot next technology is without having to bet on any one platform. I see that as a feature, not a bug.

Comment Re:Native Targets? (Score 2) 166

Okay, so that's a semantic difference then. If by "native" you mean "original source code written in the original language" than by that definition it's not native. I'm trying to clarify that it's not using a virtual machine, or relying on a plugin, whatever you want to call that.

Comment To Clarify (Score 5, Informative) 166

It seems a lot of people either didn't RTFA or are basically misunderstanding what OpenFL is. OpenFL is NOT an open source version of the flash Flash Plugin, like Gnash. OpenFL is a code library written in Haxe. You use OpenFL, and then you can output a truly native (C++) app, but can still use the flash API. It doesn't embed the flash player, or Adobe AIR, or anything like that, in your generated C++ app. You can use this to create truly native apps for mac/windows/linux/mobile, etc. Very recently they've added the ability to output to HTML5: http://www.openfl.org/blog/201... So you can take your old flash code, port it to Haxe, and then have a 100% Javascript based HTML5 game. And you can take that same Haxe code and make a native C++ app with it. And so on. Hope this helps demystify things.

Submission + - Flash is Dead, Long Live OpenFL! (gamasutra.com)

lars_doucet writes: I am a 15-year Flash veteran and nobody hates to say this more than me: Flash is dying, and the killer is Adobe. Where to now? HTML5 doesn't help me with native targets, and Unity is proprietary just like Flash was — "don't worry, we'll be around forever! And so sorry about that neglected bug report — we're busy."

I'm putting my bets on OpenFL, a Haxe-based, fully open-source implementation of the Flash API that might just please both Flash refugees and longtime Flash haters alike.

My article discusses my experiences with it and gives a brief overview for newcomers. In short — I can keep making flash games if I want, but with the same codebase I can also *natively* target Win/Mac/Linux desktops, mobile, and more, without having to mess with Adobe AIR or other virtual machines.

Slashdot Top Deals

The number of computer scientists in a room is inversely proportional to the number of bugs in their code.

Working...