Oh thanks for the mention in Retro Gamer then

We were not that close to Copenhagen, but on the other side of Denmark (west side) I’ve been to Copenhagen before though, lovely city. It was a nice trip, surely!

Too bad I only read about your trip to Denmark now. If I’d known you were here and if you’d come to Copenhagen I would’ve bought you a beer for having made the awesome Thrust Xtreme.

Are you aware that I chose Thrust Xtreme as one of my 5 favourite remakes a few months ago when I was interviewed by Retro Gamer Magazine? Good stuff.

I hope you had a nice trip though.

Interesting. If I can use the RR framework for the developement of my game and be free to do with my game as I choose, then I might reconsider using it for my development…

I’ll get back to you via email.

Glad you at least found some of the ideas in RRFW useful, even if you’re not using it yourself. It would be great to have a few more talented developers working on or with it though.

I’ve recently made some changes to the way framework works, as I found the existing TGameState mechanism was a bit limiting. You can still do things in a similar way if you want, but we now have the concept of a assigning renderable objects to render layers, which are then processed accordingly. Of course you can then add/move/remove these renderables at any time. There’s also now a high-level Game Manager class you can override which allows you to have something to manage actual game flow (I borrowed this idea from Angel Engine, which is a C++/OpenGL based 2D game framework developed by some guys at EA: http://code.google.com/p/angel-engine/). This is still a little WIP, but basically works (I need to fix all the examples now however).

One thing I’d like to point out is that the license for the framework (Artistic License 2.0) was specifically chosen so that people who want to use it for writing a commercial game are free to do so without having to apply the same license to their own code/game (as would be the case with GPL for instance). The only major thing specifically prohibited is taking the Framework itself and then sell/license it, either with or without changes.

Basically, Artistic License 2.0 protects the source code of the Framework a bit more than, say, MIT would, but doesn’t limit your use of it by forcing you to use the same license as the GPL does.

Oh, and I agree that BLIde is becoming a great editor (I’ve been using it for a couple of years now). It still has a few usability issues, but until Brucey finishes his Eclipse plugin it’s a much nicer option than the default IDE.