• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
  • entries
  • comments
  • views

Auto-generating JSON serialization code in Objective C

Sign in to follow this  
Followers 0


I wrote this article for the Sidebolt company blog. Reposting it here for your reading pleasure!

Our latest game Skyward Slots makes extensive use of JSON. We send Gigabytes of it flying back and forth haphazardly between client and server over a WebSocket connection. At first, we wrote code by hand to pack and unpack each message. Later on we decided that life is too short for that.


In the beginning, we just dove into the JSON right where we needed it.

[/font][/color]-(void) updateUserInterface:(NSDictionary*)message{ topBar.coinsLabel.string = [[message objectForKey:@"coins"] stringValue];}[color=rgb(51,51,51)][font=Georgia]

This isn't so great because it's a) quite verbose and b) difficult to change. If we change the name of the "coins" parameter to "cash", we'll have to search-and-replace and hope that we get every instance. There's no way to tell if we missed one; it will fail silently.


Our solution was to write a layer of model objects which process JSON dictionaries and expose the data via properties.

[/font][/color]@interface Product : NSObject@property BOOL scalable;@property (strong) NSString* productType;@property int quantity;@property (strong) SKProduct* skProduct;-(id)initWithDictionary:(NSDictionary*)dic;@end@implementation Product-(id)initWithDictionary:(NSDictionary *)dic{ if (self = [super init]) { self.scalable = [[dic objectForKey:@"scalable"] boolValue]; self.productType = [dic objectForKey:@"productType"]; self.quantity = [[dic objectForKey:@"quantity"] intValue]; } return self;}[color=rgb(51,51,51)][font=Georgia]

Now if we change a property name, we'll get a bunch of compiler errors. This technique also gets us code completion, which is great.


The only downside is, writing these model classes gets old FAST. And they're so repetitive and simple, you'd think we could automate it somehow!


I sat down and wrote a gob of macros to do just that. Now we have one header file with all of our models, which now look like this:

[/font][/color]SBStruct(HSLoginResult) SBProperty(NSNumber, id) SBProperty(NSString, token) SBProperty(NSString, updateURL)SBEndStruct(HSLoginResult)[color=rgb(51,51,51)][font=Georgia]

This generates an Objective C class which can be used like so:

[/font][/color]HSLoginResult* result = [HSLoginResult decode:dictionary];NSLog(@"%d", result.id.intValue);[color=rgb(51,51,51)][font=Georgia]

Much better! The best part is, we still have code completion. We can also nest these structures.


So how does it work?


Here's the SBStruct and SBProxy macros:

[/font][/color]#define SBStruct(name) \@interface name : SBStructure#define SBProperty(type, name) \@property (strong, nonatomic) type* name;#define SBEndStruct(name) @end[color=rgb(51,51,51)][font=Georgia]

This generates a valid class definition with all the right properties. Then in the implementation file, we include our definitions again and set up the macros to generate the actual packing/unpacking code:

[/font][/color]#define SBStruct(name) \@implementation name (Decode) \+(id) decode:(id)dict \{ \ if (dict == [NSNull null]) \ return nil; \ name* instance = [name new];#define SBProperty(type, name) \ instance.name = [type decode:[dict objectForKey:@#name]];#define SBEndStruct(name) \ return instance; \} \@end[color=rgb(51,51,51)][font=Georgia]

The only thing left to do is to add categories to the basic data types to make them implement the decode: method, like so:

[/font][/color]@implementation NSNumber (Decode)+(NSNumber*) decode:(id)value{return value == [NSNull null] ? nil : (NSNumber*)value;}@end// and so on...[color=rgb(51,51,51)][font=Georgia]

If you're like me you may decide to go crazy with this. Our macros actually auto-generate methods that send messages and trigger block callbacks for received messages. They also generate a list class to go with each model class to make it easy to encode and decode NSArrays. Go forth and automate!


Sign in to follow this  
Followers 0


There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now