korpuskel

nice, glad you like it How did you get intellisense to work with the javadoc / yuidoc comment style in the first screenshot?

Totally valid question! I really don't like the fact that all project types have to output some kind of binary (*.dll, *.exe) in the bin/Debug or bin/Release folders. I went as far as calling at DOS batch script to remove those directories in the "post build event", but that's quite a hack... So currently I suggest not using any project at all. Just create a new solution with a dummy project of any type. Then in the solution explorer simply remove it (remember to also delete it from the file system). Then add new solution folders to hold the javascript files, like so: I just want to use VS as editor and use grunt to combine / minify the javascript files. Also I don't want to use the IIS which is why I don't use the Web- projects; I'd rather prefer a simple node-express. Take everything I say with a grain of salt since I have not yet done a real project with this setup... still lacking the time to do so

You need to include a special reference at the top of each javascript file you want to use intellisense in: /// <reference path="~/path/to/Phaser.js" />If that does not work for you I can also write a step by step guide and provide a sample solution file

The official runtime has the benefit of still being updated when new features come out, such as - keyable draw order - animated bounding boxes - free form deformation (not too soon) http://esotericsoftware.com/spine/bounding-boxes-and-a-special-announcement/ I don't know if these are important for your project, just wanted to mention it

Ah I see, it's issue https://github.com/GoodBoyDigital/pixi.js/issues/312. Okay, let's wait util UUIDs make it into Pixie, too I'm glad to hear you still plan to integrate Spine and I agree that you should implement it as 'extra' since most people won't need the code in spine.js. Keep up the good work!

Sorry for asking again for the Spine (http://esotericsoftware.com/) support in Phaser. I didn't have the time to try it out but since Pixi is used for rendering I really wonder if this is already possible. Despite being so great Spine does not seem to get used a lot so I understand if you don't plan to integrate it in the near future (at least you didn't put it under "Future Plans" in the Readme.md anymore). I guess I could wait for the documentation and then try to hack it in - maybe I can even get the code to look nice and make a PR though I doubt that Also thank you so much for your hard work on the 1.0 release! I followed the "march to 1.0" thread as well as the github commits so I can imagine how much effort you put into this

I can really recommend trying out VS2013 RC (http://www.microsoft.com/visualstudio/eng/2013-downloads). They improved the javascript parsing so Intellisense is much smarter now. I even get parameter information, which I did not get using Sublime Text 3 + Tern: I like the new Intellisense so much that I won't use Typescript when I Phaser 1.0 is released EDIT: the yuidoc is not understood by intellisense because it only parses the ugly XML style documentation used by the .NET languages :/

Sounds great! Since Pixi supports Spine skeletal animation we also get that in Phaser now for free, right? Reading through the recent posts really makes me wonder whether I should use TS or not. Too bad Ecmascript 6 is still so far away: http://kangax.github.io/es5-compat-table/es6/ Anyway, keep up the good work

After reading your posts on the Typescript forums I grabbed the Phaser 1.0 code and tried to compile a simple "Hello World". I only tried for some hours but I got so many random errors which even appeared and disappeared when editing whitespaces! As you said, the TSC must be seriously broken. I can't believe you still made it compile somehow Thank you very much for going through that hell which the current Typescript is.

Hey Rich, Happy Birthday! It is really appreciated (but a little crazy, too ) to work for and release v1.0 on your birthday. I really hate to nag again about the Spine support but from the README.md I concluded that it seems to be quite at the bottom of the todo list. Could you please move it up a little, so that the ETA is < 3-4 weeks orgive some hints on how you would implement it so I can do a quick-and-dirty impl until you do it properly? Keep up the good work, but seriously take break today

That is really appreciated because there even are no Typescript definitions for the Spine javascript runtime. Big thumbs up!

I am really exited about the 1.0 release, too Just one question: Spine (http://esotericsoftware.com) is getting really popular, do you plan to integrate support for it? I wish you best luck for your game release this week and as little last minute bugs as possible