So, as people probably have realised by now the Gluon Alpha is a bit delayed. The work on renaming and all took a bit longer, thus causing everything else to be delayed as well. However, all changes have been pushed to master last sunday. With that done, there are only 3 "Blocker" Items left to do: A scriptable component, correct Asset handling (nearly done) and correct reorder and moving of things in the scene (which is also nearly done.)

So, it's been a while since the last update on Gluon. Quite a bit has been happening actually, of which more in this blog post. :)

Gluon Renaming

First off, we had a little IRC meeting in December in which we discussed some things related to the graphics library and other issues. One of the things we discussed was that considering the core Gluon libs will only depend on Qt, it does not make a whole lot of sense to name them "KSomething". Instead, it was decided that we will rename the libraries.

So, I originally planned to talk about this in my blog post about the Gluon sprint, but that post became really long so I decided to split it up into two parts. In this part I will talk about Gluon Creator, what it is, what we have planned and how far we are.

About the Creator

Modern game engines can be split up in basically two ways: those that compete for "Best Graphics" and those that compete for "Most easy to use". Many of the AAA-games run on an engine classified as the former, but a fairly large market is growing for the latter, the market of "Indie games".

Hello Planet. :)

First, let me introduce myself. My name is Arjen Hiemstra, I am almost 24 years old and I have recently finished my studies of Game Design. I have recently joined the Gluon team. I am very new to KDE development, having only started to use the KDE and Qt libraries two to three months ago. When the blog post about Gluon was posted on the Planet, I was intrigued and after some deliberation decided to join the development.