Book Image

Hands-On Game Development with WebAssembly

By : Rick Battagline
Book Image

Hands-On Game Development with WebAssembly

By: Rick Battagline

Overview of this book

Within the next few years, WebAssembly will change the web as we know it. It promises a world where you can write an application for the web in any language, and compile it for native platforms as well as the web. This book is designed to introduce web developers and game developers to the world of WebAssembly by walking through the development of a retro arcade game. You will learn how to build a WebAssembly application using C++, Emscripten, JavaScript, WebGL, SDL, and HTML5. This book covers a lot of ground in both game development and web application development. When creating a game or application that targets WebAssembly, developers need to learn a plethora of skills and tools. This book is a sample platter of those tools and skills. It covers topics including Emscripten, C/C++, WebGL, OpenGL, JavaScript, HTML5, and CSS. The reader will also learn basic techniques for game development, including 2D sprite animation, particle systems, 2D camera design, sound effects, 2D game physics, user interface design, shaders, debugging, and optimization. By the end of the book, you will be able to create simple web games and web applications targeting WebAssembly.
Table of Contents (18 chapters)

Browser debugging

Debugging WebAssembly in a web browser is still pretty crude. For example, at the time of writing, it is still not possible to directly watch a variable using the debugger. In both Firefox and Chrome, you must occasionally refresh your browser to see the CPP source file. Unlike debugging JavaScript, the WebAssembly debuggers feel (ironically) buggy. In Chrome, you frequently have to click the step over button several times to advance the line of code. In both browsers, breakpoints sometimes fail to work.

I frequently have to remove and then re-add a break point to get them to work again. It is still early days for WebAssembly source maps and in-browser debugging, so the hope is that the situation will improve soon. Until it does, try combining debugging in the browser with the addition debug statements, as I advised earlier.

...