{"id":1041,"date":"2014-04-25T13:07:40","date_gmt":"2014-04-25T12:07:40","guid":{"rendered":"http:\/\/www.aymericlamboley.fr\/blog\/?p=1041"},"modified":"2014-11-01T14:32:56","modified_gmt":"2014-11-01T13:32:56","slug":"flambe-versus-the-world","status":"publish","type":"post","link":"http:\/\/www.aymericlamboley.fr\/blog\/flambe-versus-the-world\/","title":{"rendered":"Flambe versus the World!"},"content":{"rendered":"

The game<\/a>.<\/p>\n

The (HTML5) engines war<\/strong>
\nYou probably didn’t miss the engines war of the previous month: Unity announced Unity5<\/a> with WebGL support (which I already pre-ordered hurrah!) and Unreal Engine 4 did the same with an incredible price<\/a>. That was for the big guys.
\nFrom a more indie friendly point of view, PixiJS<\/a> continue to kick ass with awesome new features (cacheAsBitmap, blend mode for canvas, SpriteBatch…). Phaser<\/a> using PixiJS as its rendering engine, is becoming much more popular every day and obviously more stable. PixiJS has really the wind in its sails because OpenFL<\/a> switched to it for its HTML5 rendering engine!<\/p>\n

<\/p>\n

Witchcraft Works<\/strong>
\n\"ww\"<\/a>I had to make a new HTML5 game, Witchcraft Works<\/a>, available through (iOS, Android wasn’t required) devices browser. Since Unity5 isn’t available yet and even if they will support WebGL it can’t be used on a mobile game browser while WebGL isn’t available on mobile yet (iOS I’m looking at you!). So I needed an engine working with Canvas.
\nIn my latest HTML5 project<\/a>, I summarized my first experience with PixiJS and the issue with performances (certainly not the engine’s fault). Since StarlingJS<\/a> sounds like abandonned to me, and I wanted to test something new, CreateJS<\/a> just has WebGL support, I didn’t feel confident with that engine (and add JavaScript coding…). It was finally time to give a try to Flambe<\/a>, and I fell in love! I heard about it some years ago when I was most active in the Haxe community with a Citrus Engine<\/a>‘s port<\/a>.<\/p>\n

With the same code base, coded in Haxe<\/a>, Flambe enables to export Flash\/AIR (web, mobile applications), Canvas (old browser, device mobile browser) & WebGL (web) builds!<\/p>\n

Haxe<\/strong>
\nAs you probably know, I hate coding in JavaScript. With my previous project I found<\/a> TypeScript<\/a> not bad at all, but I’d to make a TypeScript definition file<\/a> for feeling comfortable with PixiJS. Using external libraries in the project, I didn’t have TypeScript support for them, that was a mess… Using Flambe I’m able to benefit from lots of Haxe’s libraries, and yeah coding in Haxe is lovely!<\/p>\n

When I played with NME, 2 years ago we were fighting with the lack of IDE support. There is an excellent plugin<\/a> for Sublime Text<\/a>, but I can’t feel enough comfortable, I needed an IDE. But now even if you’re not on Windows (and its awesome Flash Develop<\/a>), you have cross platform Haxe IDE support with FDT<\/a> which isn’t bad at all and IntelliJ<\/a> (I prefered FDT).
\nFlambe works with a command line interface, but you can also have easily a .hxml file<\/a> for your IDE \ud83d\ude09<\/p>\n

Flambe<\/strong>
\nGetting started with Flambe might be a bit complicated. Be sure to read its installation guide<\/a>, have a look on the examples<\/a> and on its official Cookbook<\/a>. Holy crap we’re seriously missing documentation here! Don’t panic have a look on Mark Knol<\/a>‘s one and you can already be grateful! Also be sure that Flambe will match with your project requirements<\/a> (add no video support).<\/p>\n

Entity component system<\/strong>
\nThe first thing you will notice with Flambe is its entity component system. Unlike many frameworks which cloned Flash display list, Flambe works with an entity component system even for rendering stuff! Basically that means if you create a Sprite object, you can’t addChild children directly. You have to create a new Entity, add it a display object, and addChild this entity to a parent entity! It’s really troubling at first, but once you get it it works like a charm.
\nIt’s sad that you can’t extend an Entity, it will be very useful for creating lots of custom objects, instead of that we are creating many Components for a project. I understand the design choice, but I find it too restrictive for making frameworks on top of Flambe. Also it would be cool to have getEntityAt method & I didn’t find an easy way to identify Entity\/Component like we do with their name in Flash.
\nAnyway it’s very pleasant to use its entity component model once you get it.<\/p>\n

Animations<\/strong>
\nWith Flambe you will have to use Flump<\/a> for your animations. Seems it sounds like a correct way for manipulating animations (you will write some JSFL for speeding your workflow), it’s crazy that Flambe can’t load SpriteSheet in any format provided by TexturePacker<\/a>! I may have missed something but that means even for making a SpriteSheet of images you will have to import them in Flash and export them with Flump. What the fuck?<\/p>\n

Performances<\/strong>
\nOk here we go. On my latest HTML5 games I fought a lot with bad performances on mobile… Here it just works… like a charm! I didn’t have to fight with anything. I have a strong 60 fps on my iPhone4S and iPad3. Nothing to add. So kudo Bruno!!<\/p>\n

I don’t need at all a Flash target, so why bother with Flambe?<\/strong>
\nMe neither, but having a Flash support will help you a lot with debugging your code!<\/p>\n

Still not convinced by Flambe? Have a look on its showcase<\/a> and see games made by big firms (Disney, Nickelodeon)! <\/p>\n

Finally I’m back in the Haxe world and that’s very pleasant! Using Flambe<\/a> at Da Viking Code<\/a> gives me without any doubt a strong weapon for future HTML5 project! Feeling even more like a Viking \ud83d\ude09
\n