Those watching the Planet KDE aggregator may have noticed I just appeared again. I’ve taken Wednesdays off work until Christmas (I had some holiday left) in order to catch up with KDE development.
My .plan:
kpf: Write unit tests, fix anything I find broken. Implement two of the feature requests: An option to stop limiting bandwidth, and a super-server, which lets you see what kpf servers are available on the host. I’ll have a go at the ‘copy URL to clipboard’ thing which quite a few people want, but that could be tricky, as it’s hard to find your own IP (properly).
Other stuff. I’ve become a big fan of test-driven development, so I’d like to play with issues relating to KDE in that area. Perhaps I could make it easier to integrate unit tests into code. We’ll see. It’s not going to be easy to make life much easier, because C++ doesn’t make it easy.
I’ve been using C# and VB.NET, which despite being a little less hardcore than C++ are really very, very good when it comes to debugging (the VS.NET IDE is fantastic. Only wish it had vi keybindings...) and automated testing (NUnit and NCover are excellent).
The reason that the debugger VB.NET is so good is that it doesn’t have to work too hard. VB.NET is parsable, unlike C++. The reason that both languages have such great testing and test coverage utilities is that they support reflection, and it’s easy to use.
Anyway, I’ll rewrite Qt in C# when I get a weekend free.