In any software system there is going to be events, such as onComponentLoad, onMouseClick etc. Flax as an engine was based off another engine I had written in C++ using SDL as the graphics API, though it was never really finished and lacked a key element from the start: the ability to create custom events, which objects could listen for. What resulted was code which Continue reading ‘Flax engine: GWT event bus implementation’
During the design document stage of the Flax Game Engine we came up against a wall when trying to communicate information between the engine, the editor and networked clients, so we explored XML and JSON as data formats to communicate the information. Continue reading ‘Flax Engine: GWT client-side JSON serialization and deserialization’
First off, I have to apologise. This post is a few days late, and I’m sure that all none of you who hang on my every word were beginning to froth at the mouth. Anyway, in this dev diary is an explanation of our audio system, because I worked on that this week. First, I’m going to explain how we handle files, because that’s pretty cool too. Continue reading ‘Flax HTML5 Game Engine Development Diary Part 4′
After a weekend of Guinness, rebel songs, and Kildare football banter, I have finally got around to writing last weeks development diary. During the week the first draft of the design document for the Flax Engine was finished, a stage in the development Carl and myself are quite happy to have completed. Continue reading ‘Flax HTML5 Game Engine Development Diary Part 3′
Well, it’s been almost 3 weeks since we started full time work on our HTML5 game engine, Flax. Some of these days have been quite productive and other days the work just came to grinding halt because of technologies we were hoping to use or features that we where hoping to exploit deciding not to work. However, work is progressing quite well now and the design document is starting to come together nicely. Continue reading ‘Flax HTML5 Game Engine Development Diary Part 1′
