More releases!

I just realized I forgot to announce the releases I made at the beginning of the month! Oops. This poor, neglected blog.

I updated all of my projects, and for the most part it was a very minor release that fixed an installation bug in Linux or updated the translations. Of course, FocusWriter had a few more fixes than the rest, but that is to be expected as it is a much more complicated program. And Tanglet actually had a feature release, thanks to Markus Enzenberger. If you have not yet updated, enjoy!

Advertisements

Releases galore!

Over the past week and a half, I have made releases for all of my projects. Most of them were pretty minor, and just amounted to updating the translations (and fixing an issue where the Qt-supplied translations were not being properly loaded). Packagers will now need to depend on lrelease, because I no longer include the precompiled binary .qm files.

The projects with actual feature releases were CuteMaze, Hexalate, Tanglet, and Tetzle. For the most part, the features added will not be obvious unless you have a 4K monitor, because the biggest thing I added was support for high-DPI displays. I did also finish moving my projects to be Qt 5 only, and to use C++11.

As usual, report any issues you have. Enjoy!

Some minor releases

Kapow

I have released a minor update to Kapow, version 1.4.4. This release is mostly to add an automatic backup system for the time data that I have been working on. A few users have experienced data loss, and this will hopefully prevent anybody else suffering that. Kapow now makes logarithmic backups (one backup a day for a week, then one backup a week for a month, then one backup a month for a year, and finally one backup a year after that) as well as a temporary backup that gets overwritten with each save. This release also adds support for building with Qt 5, although it is still released with Qt 4 as that is the primary development platform for now.

Longer term I am planning on making it easier for users to store the data file and backups in a location of their choosing, which will default to their documents folder. I have not settled on how I want to expose it in the interface (although you can already do this by using passing an XML file to the program).

Hexalate, Peg-E, and Simsu

I have also made a few other minor releases (Hexalate 1.0.2, Peg-E 1.1.2, and Simsu 1.2.3) over the past two weeks that I have not felt justify a blog post on their own. These releases mainly just add translations and support for building with Qt 5. I plan on making minor releases of the rest of my programs over the next few weeks to also update their translations, and to add support for building with Qt 5.

Development version numbers

Now that I am switching to release branches I am finally going to also tackle something that has always bothered me but I’ve never taken the time to solve: the development source code has the same version number as the most recent release. I have always wanted it to be some sort of automated number, but I wasn’t sure what I wanted it to be. And I didn’t want to have to update it myself with every single commit.

At first I had wondered about a number that gets incremented every time you compile the project, but I quickly realized that was a pointless thing to track. I may build a project 5,000 times and have a huge build number, but someone else might download the source and compile it only twice. Same source code, different version number. That’s frankly pretty silly.

Instead, I got inspired by the idea of using the git revision ID. It is obviously unique for each commit, and it identifies the specific source code for everyone. Of course, you can’t embed the revision ID because it is a hash that is created of the source code that you’re trying to embed it in. A hash that contains itself? Impossible! Of course, all you have to do instead is simply ask git for the revision ID, and pass that as a definition to the compiler:

VERSION = $$system(git rev-parse --short HEAD)
DEFINES += VERSIONSTR=\\\"git.$${VERSION}\\\"

The source code also needs to make use of the new compiler definition:

QCoreApplication::setApplicationVersion(VERSIONSTR);

This means that I finally have an automated version number for the development source code. I’ve only updated Kapow so far, but I am going to make this change to all of my projects.

The end of PowerPC support

I should have announced this sooner, but better late than never I suppose. I will no longer be creating new PowerPC builds of my programs. There are many reasons, but the biggest two are that my iBook G3 finally gave up the ghost, and that Qt has dropped support for PowerPC. I know that this is an inconvenience for some of my users, and I am sorry about that. Still, I hung in there as long as I could, but Apple has moved on.

Small Hexalate release

I was recently made aware of the fact that Hexalate wasn’t launching on the Mac. It turns out that it was linking to Qt’s SVG module, even though it did not need to. I have made a release that fixes that.

Another new project

A couple of weeks ago I got the idea to make a small game about matching colors. I wrote up the algorithm to create the puzzles for it, but I quickly got sidetracked finishing up Simsu. I have now completed the game, and I have released it as Hexalate 1.0. It is a very basic game, and not that easy to solve. I had fun writing it, though, and I hope somebody finds it fun to play!