phzr
phzr copied to clipboard
dparis
Update phzr to track phaser v2.4.3
http://phaser.io/news/2015/08/phaser-243-released
This should hopefully involve just re-generating code using gen-phaser and making sure the diff squares with the phaser v2.4.3 changelog.
How active is phzr? If I want to use the most recent version of phaser, should I just use standard interop?
@Engelberg Sorry I'm late to replying here! phzr is not very active at the moment, and likely won't be for at least a few more months given my work schedule. However, I will try to be more responsive to PRs and issues, so if you'd like to contribute updates or have questions feel free to post them here. I'll do my best to review and merge any reasonable contributions.
Once my work schedule dies down, I'd love to dig back into phzr. Hopefully that'll be soon. :tired_face:
Thanks. For the moment, I'll work with phaser via interop, so I'll be better poised to understand phzr when it is more active. Can you tell me what process you used to generate the externs for phaser?
The cljsjs package for phaser is here: https://github.com/cljsjs/packages/tree/master/phaser
The externs file was initially generated using @jmmk 's extern generator tool: https://github.com/jmmk/javascript-externs-generator
I can't recall if I had to do any manual tweaking of the generated externs. When it comes time to update phzr and the cljsjs package (or if anyone would like to take a crack at it), I would likely run the phaser source through the generator again and sanity check the diff. Hopefully the changeset would be minimal and reflect only the actual changes in the underlying phaser source.
Once the cljsjs package is updated, the source of the app I use to generate the phzr wrapper can be found here: https://github.com/dparis/gen-phzr
