Arrow keys gone?

[icarito]

Hi, Docs say this exists, but it's commented out in the code: https://github.com/kittykatattack/hexi/blob/1de3223415b2150e0b5556195c10e3004990b3ad/src/core.js#L697

Would be nice to have, IMHO. Regards, Sebastian

[kittykatattack]

Yes! I actually don't remember why I removed that feature... but I remember it was for good reason 😄 It was kind of a cute shortcut, but in my own projects I've only ever used the long-form way because I preferred being more explicit about the exact ascii code name I was using. There's also an arrowControl super-shortcut you use, which auto-configures the arrow keys for you, as in here:

https://github.com/kittykatattack/hexi/blob/master/examples/src/keyboardMovement.js

[mattlima]

Love the package but silent deprecations like this really hurt usability. My team just wasted 30 min trying to figure out why the code wasn't working in the absence of a CHANGELOG.md.

[kittykatattack]

@mattlima Sorry about that - those features were gone for a very long time. And, really, I had no idea anyone besides me as using this library. 😄

Also, very importantly, I would not yet recommend anyone use Hexi for production code (code that your business depends on) until it reaches a stable v1.0 release. Please see this issue: https://github.com/kittykatattack/hexi/issues/5

[mattlima]

@kittykatattack Thanks, and I hear you. I'd be happy to help you maintain the package. It has been very useful for us and there's clearly been a lot of effort invested in it already; seems a shame to not take it the last mile to 1.0.

[kittykatattack]

@mattlima I would love the help - I'll add you as a collaborator!

I had been working almost full time on this project for about a year, but as you've noticed I'm super-busy on a ton of other projects at the moment and am not able to maintain Hexi as well as I should.

Here are just a couple of thoughts:

• The most important thing about this project is to maintain stability in the user-facing API. The reason for this is protect users (us!) from the often-changing Pixi API and to ensure the investment in code we write today will still work with 5 years from now. So before we make any changes to the top level API, we'll need to discuss this very thoroughly to make sure there's a significant benefit to the user. The worst thing about open-source projects with multiple collaborators is arbitrary breaking API changes and feature creep. This project is about, simplifying code, remove features and long term API stability.

• Any ideas you have for making this repo easier for collaborators to contribute to would be awesome!

• I'm busy updating Hexi to work with Pixi v4.3x, and all new work is happening in the pixi4 branch. Unfortunately there are lot of little API changes (and bugs!) in Pixi v4.3 and so debugging and upgrading the source code, modules, examples, tutorials and README is going to take much longer than I had hoped.

• The examples have 100% API coverage, and act as both Hexi's unit tests and documentation.

Thanks again for your interest in helping!