Maximus has just reached milestone 1.1.0. Maximus is a module manager for BlitzMax. Its purpose is to ease management and installation of BlitzMax modules, giving the developer more time to spend on developing, and not manually installing and downloading modules and their dependencies.
The most notable new addition to this release is a full fledged graphical user interface in the form of Maximus GUI. This makes Maximus a lot more user friendly for those who aren’t too keen on a command line interface (CLI). Maximus still comes as a CLI application, but for those who prefer a GUI there’s maximus-gui to use.
Users who want to upgrade to 1.1.0 and make use of the GUI version (as well as some other minor changes) should download the Maximus client.
Also, for this release I would like to thank Jens for providing me with version 5.4 of Logic GUI. Maximus GUI has been build with it and couldn’t have been developed this quickly without it. If you’re a BlitzMax programmer that uses MaxGUI you should, without question, buy Logic GUI.
For a while now I’ve been keeping a Git mirror of bah.mod updated on GitHub. I’ve now moved this repository from my account to the BlitzMaxModules organization. Aside from bah.mod I’m now also mirroring rigz.mod and maxgui.mod.
If there are any other Subversion hosted BlitzMax modules you want to see mirrored on GitHub let me know.
So already a week and a half ago I purchased ifsoGUI and only today I finally found (made) some time to experiment with it. I’ve read the examples and they were all very clear, but you don’t actually learn anything without experiencing it first hand. The API of ifsoGUI very much resembles that of MaxGUI so it’s very straightforward. With the only exception that besides using an event queue you can also use callbacks for every gadget. These callbacks get executed as soon as an event gets fired for the gadget. Powerful stuff.
Anyway, playing with ifsoGUI inspired me with new game ideas. My mind started to do some creative thinking again. Something I haven’t had for a long time. It’s nice to know that’s not gone yet and it’s very neat how an idea can evolve inside your head. Today I finally realized that I should change the genre of games I should try to create, or at least start with. I’ve been mainly focused on airplane/spaceship dogfighting games which is a genre I enjoy playing, but am currently bad at creating. It took me 3 prototypes to realize I’m not cut out yet for this genre. Of which the first two took more time than a prototype should take. For the third prototype I only invested a couple of hours. I realized I was doing the same thing over again and terminated it.
ifsoGUI inspired me to start thinking about a completely different genre. With the ease of creatingÂ panels, buttons, sliders, text boxes and all I started visualizing how easy it would be to create small little windows to manage lots of objects. So in other words, micro-management. I’ve always enjoyed playing Tycoon type games, like Roller Coaster Tycoon, Theme Park and Theme Hospital. I don’t play these game a lot anymore because they consume way too much time. But I’ve spend a lot of hours on it in the past already and it’s a fun genre.
So I suppose I’m changing my direction to set course to a new destination!
I had been looking for a nice library to create in-game graphical user interfaces but couldn’t find any BlitzMax module I liked. I’ve looked at FryGUI in the past but decided not to use it. The examples were impressive enough but I wasn’t under the impression that it’s being actively maintained. CEGUI, wrapped by Brucey, is an impressive module as well. My impression was that skinning is rather hard, as is its ease to use. I also heard it’s not fully wrapped yet, but I might be wrong. I don’t necessarily think this is a bad point as one rarely needs all features. But not being fully wrapped means the API can get some breaking changes as well. And I hate it when that happens (points to Zend Framework).
As both are free modules, which is of course always a good thing (my htbaapub.mod modules are free as well), you’re never certain of support when problems arise. Since it’s all open source I can make any changes I want myself if ever needed. But I’m lazy, I don’t want to do that. I want to focus on creating my game or application. Not being sidetracked because I library I use doesn’t do what it should do. I’m not saying that this is the case for FryGUI or CEGUI (which was recently updated), but it’s something to keep in mind.
Not too long ago a new commercial library was released, ifsoGUI. It had put me off at first because of the skin that was used looking fairly identical to the default Windows XP theme. It gave me the impression that it tried to be a in-game MaxGUI clone. Until I found out it had support for custom skins which are also easy to create.
All the demo’s were impressive enough, the module is well documented (there’s also a Wiki, the other named modules are documented as well by the way), a clear API, the source is available, it’s being actively developed and there’s active support for it. Another reason I chose this module was because of the short learning curve. I need to be able to quickly implement it, not spending hours and hours figuring out how the module is supposed to work. I think ifsoGUI gives me this, and that’s why I chose it.
PS: If I made any mis assumptions please let me know so I can correct my post.