In my 10 year anniversary blog post I mentioned how I wanted to fully redesign the icon chooser dialog which hasn’t changed since its inception and my childhood. Well, guess what I just did between sessions at this year’s Akademy.
I recently added a job creator test application to KJobWidgets so I could test the job tracker in Plasma’s notification center without having to write fake KJob classes all the time. The user interface for it was quickly bodged together in Qt Designer, so the other day I figured, I might as well try to recreate the new icon dialog layout and hook its existing C++ logic to a new UI.
Can you believe how time flies? Today, ten years ago my first ever KDE patch was merged. A little while later I was granted KDE developer rights with write access to all of KDE’s git repositories. This power was somewhat frightening, after having submitted not even a hand full of patches at that time, and it actually took many years for the thrill of hitting Return on a “git push” to abate. Let me take this decennial as an opportunity to tell you stories from back in the days™ and how I ended up where I did, where I surely would not be without KDE!
I actually started writing on this blog post last December, to have plenty of time for collecting trivia and ideas, never before seen prototype screenshots, and more. I surely wouldn’t have thought this to turn into half an autobiography. Mind that I’ll try my best to verify the statements that follow but they can still be inaccurate or skewed from being just memories. Now grab a cup of your favorite beverage, sit back, and join me on this trip down memory lane.
(or: “KDE Frameworks 6 Planning Sprint in Berlin”)
Only two weeks after my previous Berlin visit I came back for the KDE Frameworks 6 planning sprint, kindly hosted by MBition in their posh offices near Spree river and Landwehrkanal.
Already during this year’s Akademy we started discussing our strategies for a Qt 6 transition and created a giant work board of tasks for our next major release of Frameworks. Overall our goal is to keep API breakages to a minimum while still cleaning up some cruft that might have built up over the years. We kicked off the sprint Friday morning with discussions mostly around policies and guidelines.