Colorscheme to Agave

At long last, I’ve released a new version of GNOME Colorscheme. Only I’ve changed the name of the application with this release. The new name is Agave. I decided to change the name of the application after I found that people often assumed (due to the name) that it was an application that could be used to change the colorscheme of their desktop (i.e. window borders, etc). Plus I was just never happy with such a generic name.

Other than the name change / re-branding, there’s not a lot of major changes, but there are few minor improvements and an additional translation (Catalan). And now that I’ve got the name-change release out of the way, I can get back to working on some bigger changes to the application. I’ve been working on a branch to implement a custom TreeModel which can use standard C++ containers (e.g. std::vector) as its data store. This is of course completely uninteresting from a user perspective, but it makes the code much cleaner and maintainable as I don’t have to keep a standard container synchronized with the data in a ListModel and vice versa. I’ve just merged these changes back into master.

I have hopes that at some point a generic standard-container-based TreeModel can be shipped with gtkmm, but I think it needs a bit of testing here before I can propose adding anything to gtkmm. The implementation I’m using right now is still a bit rough around the edges since this is the first time I’ve ever implemented a custom TreeModel, but I think it’ll get there eventually.

In addition, I’ve got a few ideas regarding improving the UI for picking colors, and some other things. So that should start picking up soon as well.

In addition, with many thanks to Ross Burton, Agave is making its way into the Debian repository. You can keep an eye on its progress in the Debian NEW queue. Also, it looks like you can grab it from Ross’s personal repository if you want to try it out before it actually gets accepted into the official repository. Thanks Ross.

Leave a Reply

Your email address will not be published. Required fields are marked *