gkiagia's blog

Back to work! Moving to git

So, you thought that this project was dead? NOT YET! :D

I am back to work now and I want to work on this project for the next month as much as I can to do a usable 0.5 release. The good news is that I am moving the code to git. The new qtwine repository is now at github, right HERE. I have imported there all the svn history from commit 149. Commits < 149 refer to 0.4 and older code that is mostly unused now as I have moved from pure Qt4 to Qt4/KDE4 api.

Also, for quite a while now, I have an irc channel dedicated to qtwine. So, if you want to contact me, join #qtwine on irc.freenode.net

I am also going to do some housekeeping work on this site as it looks pretty old now :P

QtWine 0.4 status

It's been ages since I last entered this site, but in the meanwhile, I have done lots of work for the upcoming QtWine 0.4 release, which will be the first useful for the public release (I hope).

Currently, QtWine 0.4 is in a very good shape and I can actually use it as I could use version 0.3.1 until a few days ago. However it is still not ready for a public release as it misses some basic functionality that users would expect and it still has known bugs that lead to crashes and assertion failures.

About QtWine's logo

The current QtWine logo that you can see on the top left corner of this page is actually a KDE icon (wabi.png) from the default KDE 3.5 icon theme. Although it is suitable for an application such as QtWine, it still is not the best logo available.

So, I am in need of a new logo for QtWine. If anybody can help me find one, or even create one, I would be thankful.

QtWine's past, present and future

QtWine started one and a half year ago when I was learning and heavily testing wine. During this testing process, I discovered that wine inherits one major disadvantage of windows, the windows registry. I remember that in that period, my wine registry was all in a mess, in a state that in windows, the only remedy is FORMAT.

Syndicate content