Phaser code needs to be in repo

[gamedevsam]

Since phaser code gets edited frequently, the binary that was used to generate the haxe code should be distributed in order to maintain stability and compatibility with the API.

[hexonaut]

By binary do you mean the source files for Phaser? If so then good point.

[gamedevsam]

This is not exactly what I meant. I meant that phaser.js and phaser-min.js should be included in the repo. Basically this repo should be all that you need (in addition to Haxe) in order to make games with haxe-phaser. I recommend we have a build.hxml that would quickly compile and launch an html5 game.

[gamedevsam]

I don't think there's a benefit having the Phaser source code in this repo. Actually I find it odd how there's a src folder that contains a phaser folder. Wouldn't it make more sense to have phaser be at the root of the repo?

Example folder structure:

export // location where games get exported to
lib // location of phaser.js and phaser-min.js
phaser // code to haxe-phaser

[hexonaut]

How's that? I want to keep Haxe externs in src.

[hexonaut]

More examples ported from the phaser-examples repo should help to see where we are missing functionality. Are you interested in doing that?

[gamedevsam]

If I get a project to compile at all, I wouldn't mind porting some of the examples.

[hexonaut]

What's the problem? Try the rendertext example. It should work.

[gamedevsam]

I just don't know how to compile HTML5 apps with vanilla Haxe (without openfl)...

[hexonaut]

Navigate to the examples/rendertext directory and run haxe build.hxml to build the javascript file then drag and drop the index.html file into your browser.

[gamedevsam]

Ahh gotcha!