Comments on: Debugging on your Web Browser [...] a HTTP server running inside your app or game. You can inspect your game entities at runtime (this #AltDevBlogaDay post talks about this approach), interact with your scripting engine for tweaking or even upload assets [...] [...] a HTTP server running inside your app or game. You can inspect your game entities at runtime (this #AltDevBlogaDay post talks about this approach), interact with your scripting engine for tweaking or even upload assets [...]

]]>
By: Web server - NecroSOFT/2011/03/15/debugging-on-your-web-browser/#comment-4844 Web server - NecroSOFT Wed, 25 May 2011 09:55:26 +0000 If you mean MKScope, that was not a little app. It was also not extendable gameside, so was of no use for adding project specific output. If you mean MKScope, that was not a little app. It was also not extendable gameside, so was of no use for adding project specific output.

]]>
By: Glenn-Watson/2011/03/15/debugging-on-your-web-browser/#comment-2356 Glenn-Watson Tue, 05 Apr 2011 10:58:15 +0000 We also started using Mongoose for that purpose at Fishing Cactus, with a little bit of XMLHttpRequest here and there. We are still trying various ideas and approaches but so far we have been amazed by how quickly we can expose useful stuff from directly within the game and interact with it. Promit: I would love to have a look at what you came up with :) We also started using Mongoose for that purpose at Fishing Cactus, with a little bit of XMLHttpRequest here and there. We are still trying various ideas and approaches but so far we have been amazed by how quickly we can expose useful stuff from directly within the game and interact with it.

Promit: I would love to have a look at what you came up with :)

]]>
By: Promit/2011/03/15/debugging-on-your-web-browser/#comment-1781 Promit Sun, 20 Mar 2011 00:45:50 +0000
Just grab the .h and .c files, and the interface is dead easy to work with. As I said before I don’t like your approach of generated HTML, so I actually send JSON over the wire.

]]>
By: alex/2011/03/15/debugging-on-your-web-browser/#comment-1735 alex Fri, 18 Mar 2011 23:29:29 +0000 I like the basic idea here, but I'm not thrilled about the fact that the target program exports an HTML page, instead of data. I think formatting/display should be the responsibility of the client, not the server. Maybe that can be done by setting up something that provides a REST API or AJAX capabilities? I like the basic idea here, but I’m not thrilled about the fact that the target program exports an HTML page, instead of data. I think formatting/display should be the responsibility of the client, not the server. Maybe that can be done by setting up something that provides a REST API or AJAX capabilities?

]]>
By: Julien Hamaide/2011/03/15/debugging-on-your-web-browser/#comment-1634 Julien Hamaide Wed, 16 Mar 2011 07:25:47 +0000 I think he means the clientside HTML will become more complex since you'll need to write the JavaScript and Ajax code as well. Once that's done though the actual data will be much easier to send. I think he means the clientside HTML will become more complex since you’ll need to write the JavaScript and Ajax code as well. Once that’s done though the actual data will be much easier to send.

]]>
By: Matthew Peers/2011/03/15/debugging-on-your-web-browser/#comment-1629 Matthew Peers Wed, 16 Mar 2011 03:51:56 +0000 I haven't looked into it deeply. That approach may work well, and would certainly be more powerful, though I don't know much ajax or javascript so its all learning curve to me. As it was a new tech for me, it seemed a simpler entry point to just give the game callbacks control of an entire html page to do with as they chose, rather than to try and co-ordinate how different (possibly unrelated) code fragments would elegantly share a page. I haven’t looked into it deeply. That approach may work well, and would certainly be more powerful, though I don’t know much ajax or javascript so its all learning curve to me. As it was a new tech for me, it seemed a simpler entry point to just give the game callbacks control of an entire html page to do with as they chose, rather than to try and co-ordinate how different (possibly unrelated) code fragments would elegantly share a page.

]]>
By: Colin Riley/2011/03/15/debugging-on-your-web-browser/#comment-1623 Colin Riley Tue, 15 Mar 2011 18:18:41 +0000 Very cool! Quite a bit easier than trying to build visual debugging stuff into the game itself, I would guess. Does it really get much more complex if you serve AJAX stuff instead of HTML? I would have expected it to be easier to write it such that the game just serves up simple hunks of data, and all the slicing and dicing, and HTML formatting, is done in Javascript instead of C++. Very cool! Quite a bit easier than trying to build visual debugging stuff into the game itself, I would guess.

Does it really get much more complex if you serve AJAX stuff instead of HTML? I would have expected it to be easier to write it such that the game just serves up simple hunks of data, and all the slicing and dicing, and HTML formatting, is done in Javascript instead of C++.

]]>
By: tuan kuranes/2011/03/15/debugging-on-your-web-browser/#comment-1620 tuan kuranes Tue, 15 Mar 2011 18:03:26 +0000 )

]]>