• Content Count

  • Joined

  • Last visited

Everything posted by aaccurso

  1. Hi, I guess so, you are welcome to try it and post an issue in the github repo if you find anything unusual.
  2. Hi everyone, I just fixed the issues @efusien mentioned! @xnamex I have a proposal. I'm actively maintaining a fork of your plugin: https://github.com/aaccurso/phaser-state-transition-plugin I've fixed most issues people have found. Me and a coworker have added some refactors and features for our own apps. This updated version is published in bower and npm for better dependency management of our projects. We have a Gruntfile.js for usual tasks such as build, minify and bump. Also I've created a gh-pages branch based on your demo project so people can get the idea of what the plugin does in realtime. So what I propose is to deprecate the old repo and continue maintainance of the new repo. I'm happy to add you as the author or something else you think appropiate. What do you say? Cheers!
  3. Thanks @efusien, I'll fix and improve those things you mentioned.
  4. Good point, I'll try to add a demo on these days.
  5. Hi there, I've been working with a friend on a refactored state transition plugin. It's registered on bower and npm so you can add it as a dependency (much better than copy-pasting the file ). The original repo wasn't being maintained and we needed to add a new feature, so we thought the most healthy way would be to create a new project and share our work with the community. I hope you find it useful. Contributions are most welcome. Thanks Rich for this great framework! A.
  6. Hi there, I've created a new repository with a refactored state transition plugin => https://github.com/aaccurso/phaser-state-transition-plugin It's registered on bower and npm. Thanks for your contributions!
  7. Hi there, we've added to our games this nifty library to support named arguments https://github.com/dtao/named-args Currently we're only using it when calling #Tween.to, #Input.enableDrag and #Emitter.start. In the beggining I was a little afraid of these long argument methods and the legibility of our code (that's why we added named-args), but I realised in later releases of Phaser that we have more configuration methods so we can configure objects even after creation time (for example, #Tween.delay, #Tween.loop and so on). So if you follow the Tween API for the rest of the classes I wouldn't consider this as a priority, because Phaser can offer other ways to be more declarative.
  8. Transitions between states would be great.