Native Extensions managed by Haxe Foundation?

[Aymeric Lamboley]

Hey,

There are a tons of awesome Haxe framework/library nowadays : OpenFL, NME, Luxe, Heaps, Kha... pick the one you want to make your mobile game! But each time I try a new "system" for mobile game I'm looking its ecosystem. Making a mobile game nowadays, is not only pushing pixels on screens, it's also having access to native services like In App Purchase, Push Notifications, Facebook Connect... and many of them shouldn't affect if you're using OpenFL or Luxe...

I see engine offering their own solutions https://github.com/luboslenco/iap_kha https://github.com/openfl/extension-iap But is there any reason why Kha created its own native extension?

Since native extension should be engine independant it could be something managed via the Haxe Foundation! I think to this post.

Making native extension is a complex task and require lots of works to be fully tested and updated (I made several for AIR), things like In App Purchase are critical in an application...

Is it something which could be managed by the Haxe Foundation? It would benefit to many developers.

[Nicolas Cannasse]

Le 03/09/2015 16:40, Aymeric Lamboley a écrit :
> Hey,
>
> There are a tons of awesome Haxe framework/library nowadays : OpenFL,
> NME, Luxe, Heaps, Kha... pick the one you want to make your mobile game!
> But each time I try a new "system" for mobile game I'm looking its
> ecosystem. Making a mobile game nowadays, is not only pushing pixels on
> screens, it's also having access to native services like In App
> Purchase, Push Notifications, Facebook Connect... and many of them
> shouldn't affect if you're using OpenFL or Luxe...
>
> I see engine offering their own solutions
> https://github.com/luboslenco/iap_kha
> https://github.com/openfl/extension-iap But is there any reason why Kha
> created its own native extension?
>
> Since native extension should be engine independant it could be
> something managed via the Haxe Foundation! I think to this post

> <https://groups.google.com/forum/#!searchin/haxelang/framework/haxelang/r5T-wNknAWI/Qf3JpD-tDAAJ>.

>
> Making native extension is a complex task and require lots of works to
> be fully tested and updated (I made several for AIR), things like In App
> Purchase are critical in an application...
>
> Is it something which could be managed by the Haxe Foundation? It would
> benefit to many developers.

That would be a good idea to have them in a single repository where
people can contribute, but we Haxe Foundation is lacking the manpower to
maintain them in the long term atm.

Best,
Nicolas

[Aymeric]

Indeed, I understand the amount of works required is problematic. But I'm pretty sure if everything was at one place, the amount of contributions on Native Extensions would increase.

[Aymeric]

Thoughts also shared in a blog post.