So, this is where we’re at - I got the most basic OpenFL sample running by putting a Kha backend in lime and a Kha renderer in OpenFL and I think I have a good understanding of what to do to make everything else run. But should I really do this? People trying to talk me into making Kha more like Flash is one of the more unpleasant parts of the whole affair. I get my kicks from seeing people learn about modern GPU programming via Kha so intrinsic motivation for providing Flash-like functionality is severely lacking. But making OpenFL run on Kha is something that comes up again and again and solving all flashy Kha demands like that makes sense and is not crazy difficult. Nonetheless I failed again and again to motivate anybody to actually do it so by now I’m pretty sure it won’t happen unless I do it myself. I am a greedy bastard though so here are my demands: I want a black Super Nt delivered to my door step - because there’s no better way to boost motivation than building connotations to SNES games. When I work on OpenFL I want to think of Super Mario Kart. Make that happen and you will be able to run all your HaxeFlixel games and more on Kha by this year’s Haxe Summit. Shy away from it and I have a nicely absurd reason to point my finger at whenever I dismiss OpenFL requests in the future.

Read this article

It looks like the times of big restructurings in Kha are over and consequently the need for blog posts about big breaking changes. But smaller breaking changes still happen of course. Those are from now on documented in the Kha Wiki - please have a look at them whenever you update Kha.

Read this article

“why is haxelib not liked?” - this question comes up semi-regularly in regards to my software in lots of different variations. Full context: haxelib is the package manager of Haxe, which is a programming language I tend to use a lot. I put versions of my software on haxelib but I encourage users to only use that for experiments and migrate to the git version (which is structured a little differently) for real projects. And I indeed do not like haxelib. I also do not like npm or even apt. Because package managers are not robust. Do you remember the recent npm tragedy? That’s just one of many ways in which package managers can fail.

Read this article

The first public version of Kode Studio is out, Github hosts the downloads. Kode Studio is a fork of Visual Studio Code, optimized for Kha (Kore support will also be added). This is a very early version of Kode Studio but features debugging support which is in many ways superior to anything else currently around for Haxe based development, based on VSCode’s Chrome debugger, Haxe’s JavaScript target and a modified HTML5 target in Kha. It’s cross-platform, very fast (runtime and compile time) and very convenient (no additional software required).

Read this article

When writing graphical applications there are typically two ways to drive the display. Either one can tell some other piece of software to call back when a new image is required

Read this article