Book Image

Haxe Game Development Essentials

Book Image

Haxe Game Development Essentials

Overview of this book

Haxe is a powerful and high-level multi-platform language that's incredibly easy to learn. Used by thousands of developers and many high-profile companies, Haxe is quickly emerging as a forerunner in the area of cross-platform programming. OpenFL builds on top of Haxe to make developing for multiple platforms quick and painless. HaxeFlixel provides you with the tools you need to build amazing 2D games easier than ever before. Cross-platform development has been supercharged using the Haxe programming language, making it increasingly easy and hassle-free to develop multi-platform games. If you've programmed games before and want to learn out how to deliver games across multiple platforms, or develop games faster, then Haxe Game Development Essentials is the book for you. It starts by showing you how to set up your development environment, then running you through some Haxe language fundamentals, and finally taking you through the process of programming a game from start to finish. You will learn how to create a side scrolling shooter game using HaxeFlixel. Next you will learn to enhance the game with new gameplay features, user interfaces, animations, sound, and configuration files to make your game expandable. Once your game is built and ready, you will learn how to deploy it to web, Android, iOS, and desktop systems. By the end of this book, you will be confident about creating multi-platform games using Haxe, OpenFL, and HaxeFlixel in a faster and easier way.
Table of Contents (16 chapters)
Haxe Game Development Essentials
Credits
About the Author
Acknowledgements
About the Reviewers
www.PacktPub.com
Preface
Index

JSON versus XML


We'll go into detail on implementing both JSON and XML data in this chapter, but first, we should look at why you may choose one over the other. At their core, both JSON and XML are external text-based formats that you can use to store various types of data.

The key differences you should evaluate are:

  • Ease of implementation: How easy is the format to implement into a code base?

  • Readability: How easy is it to read? Can a nonprogrammer understand it quickly?

  • Efficiency: How much can the file be compressed?

On the first hand, JSON is slightly easier to implement. JSON data is parsed and turned into Haxe dynamic objects. XML uses the Fast class to pull out data as needed, which is still pretty easy, but does require a bit of extra effort.

On the other hand, XML is generally easier for nonprogrammers to read because you can add comments to describe the use of each property. JSON looks a bit closer to code, so programmers generally don't have problems with it. Since XML is generally...