YellowAfterlife Posted May 15, 2013 Share Posted May 15, 2013 I've just added a new blog post on getting a toolset & browser independent "live reload" done easily. If you don't know what "live reload" is (and you should! It's useful), here's a GIF: Basically it's the process of having your game/app reload itself in browser automatically whenever you compile/save the source. It can be used to assist debugging, especially parts that require series of small changes or value tweaks. Setting this up is easy for any toolset that provides a single JS file on output (if you are working with multiple files, you'll need to expand the code a bit). In animation above a Haxe/JS project is used. Personally I prefer this method over normal IDE-driven one, since it does not open an extra browser tab on every launch, and does not require switching to browser window at all (which can be especially useful if you are debugging a non-interactive fragment of application to make it "look right"). Hopefully, this was useful. Quote Link to comment Share on other sites More sharing options...
benny! Posted May 16, 2013 Share Posted May 16, 2013 Thanks for your tutorial. An alternative I guess a lot of people (esp. javascripters) use here, might be grunt.js in combination with the watch and reload task. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.