THIS PART OF THE BOOK IS VERY MUCH UP FOR REVIEW AND DEBATE. Please let us know if you object to this approach, we will try to put our justifications below.
Make Code as Readable as Possible
There are different approaches to make this happen. We are at an advantage as we are using a relatively supported framework an a cleanish browser programming environment. As such, conflicts on a scope level are less likely to happen. Making code readable involves specifically naming the object which data is being added to at times. For example we think that it is more readable to have the following line of code
if (player.body.velocity.x < 0)
than this one
if (this.body.velocity.x < 0)
As such to start with code is structured to avoid the use of this and certain object oriented approaches. However, as learners progress, the value of using this as a keyword to allow code examples to be reused by learners increase, we introduce its use gradually.
Use Global Variables
Therefore to make it possible to use those object variables directly without using this, it is sometimes necessary to declare variables you will be using at the beginning of your code before your other game elements, and thus put them in the global (window) space. While this may go against some good coding practices, this is justified by the point above about making coding readable.
Do Repeat Yourself (at least at the beginning)
Elegant coding practices are to be admired and are sometimes expressed as DRY which stands for Don't Repeat Yourself. However sometimes the principle can be time consuming as you design to make your code elegant rather than getting up and running quickly. It can also make it harder to read for beginners.
One example of this is the use of platforms. Our tutorials create the platforms one after the other repeating similar lines of code. In the second half of the book this platform information is restructured into a json file and a for loop which cycles through that location data.
Start as hard as you going to get
This is referring to the coding structures that you use. If you are going to used simplfied structures and conventions, then make sure you can keep using these structures until the end of your project. This is because refactoring a project to bring in new knowledge can be hard to deal with as a new learner. You think you understand the process but then you have to adapt. Think carefully about when you need to upgrade.
In this guide we start with game states in place, for example the playState. Although this is more complicated than putting the preload, create and update functions directly in the game object, it means that we do not have to restructure the code when restarting our game or adding a welcome screen.
There is a bit of a jump up in the way our code is structured between the first half of this book and the second half. However, we aim to explain exactly why this is needed and use the process as a way of learning more about coding concepts.
There has been error in communication with Booktype server. Not sure right now where is the problem.
You should refresh this page.