What Happened to ZDLSharp?

So if you’ve been looking for the promised 3.0.6.0 version of ZDLSharp, and feel disheartended by the talk of Triplet, don’t fear!

I promised a few weeks ago that there would be a bugfix 3.0.5.3 version out, however, due to family issues, I was unable to work on ZDLSharp. Now that I’m about to start Exams, I won’t have much time for either Triplet or ZDLSharp. Not to worry! I will be free after the 18th with loads of time until I start work on January 14th. I really want to roll out 3.0.5.3, and then roll out 3.0.6.0 by January 14th. No promises though! There are plenty of bugs to fix up, for both the windows and mono versions. It’s important that these be fixed up quickly, so that we can get to a stable point. There are a few critical blockers, that abolutely need to be released ASAP. Normally, 3.0.6.0 would have been released, skipping 3.0.5.3. One of the features of 3.0.6.0 is the reworked backend, ditching Bio’s old readini functionality. This has proved not to be useful, and very inflexible, introducing compatibility problems. Any new features I introduce in the ini file are erased as soon as an older client opens it. I would like to merge my changes with Risen’s version of ZDL 3.1. I believe it is very important that non-understood entries in the config file stay untouched.

Preliminary QT4 Client

My attempt to model Amarok has not been easy. I’ve had to learn a new library and new concepts. Here’s a sneak peak screenshot of what I have so far: