Well the last post here is quite old but that doesn't mean nothing happened over the last few months. It's actually quite the contrary!
Since the last udpate, orx's source repository was migrated to Mercurial on bitbucket. If you have any feature request/bug report, you can use bitbucket's issue tracker.
2. New features
A few new features have been added too!
- There's a timeline module that allows to create timelines of events from config.
- There's a command module that allows people to evaluate text commands. Custom commands can easily be added by users at runtime. You can find more info on the forum or with the notes Acksys has been taking down on the wiki.
By combining timelines and commands, one can have a mini scripting language as his disposition. For example, making a standard simple UI system based on menus and buttons can now be done with less than 10 lines of C++ code and driven entirely from config with commands and timelines.
- A console has been added. That means one can execute commands on the fly during runtime from the console. Whether it is for tweaking config values or creating and modifying objects on the fly, the console is here to help.
- 2D textured polygons (meshes) can now be easily drawn using the orxDisplay API.
3. Releases and future developments
As you've noticed, the latest package release (1.3rc0) is now seriously outdated and considered deprecated. However making a release by hand the way it has been done in the past requires too much effort (over 6 hours for a release if everything goes fine).
That's why we're currently trying to automatize our build process. To do so, we've chosen Premake to replace all our hand-edited project files and Buildbot to handle the continuous integration part.
And that's where you can come in and help us.
- We've had to modify the current version of Premake in order to generate all the configurations we need and there's still some work to be done in order to support OS X and iOS projects.
- When this is done, we'll need to setup a whole Buildbot-based compile farm. We'll need help writing the configuration scripts for all the platforms.
- We'll also need to have Buildbot slave machines that will be used to compile and package the builds. Those machines don't have to be connected all the time, only the server does. When a slave gets available, the master will dispatch work to it, only if needed.
Having a variety of slaves that can compile for different platforms (hopefully covering all those supported by orx: win32 mingw/visual studio, linux 32/64, OS X 32/64/PPC, iOS, Android, ...) would be great.
4. Community (forum, wiki, games, tools and editors)
And to finish, the community has been pretty active lately too. A few tools and editors have been created, ranging from SVG -> physics shape exporter to a full-fledged IDE project.
A couple of games made with orx by community users have also been announced!
Most of those projects have been announced on the Projects section of the forum and some of them are being hosted on Bitbucket under the same account as orx.
Lastly, any contribution to the wiki (tutorials, tricks, translations, ...), the forum itself (to help answering new users questions and make the community grow) or even the website (finding someone willing to improve the website design would be awesome!) is more than welcome.
Thanks for reading,