The last few days I ploughed through the KDEPrint bugs.
This should serve the same purpose as outlined in my last blog entry: to make it more easy for the real coders to see the valid and important bugs (we're short of people who've enough time to work on KDEPrint code for KDE4).
Also, I wanted to get an overview about what were the main problems reported during the last year (I was unable to participate much in KDE, or even use it myself most of the time), so that these things stand a higher chance to get attention for KDE4.
Last, were there any wishlist items and suggestions for improvement that we had not yet noticed?
[image:2612 align="right" hspace=12 vspace=12 border=1 size=thumbnail] [image:2611 align="right" hspace=12 vspace=12 border=1 size=thumbnail] I found lots of useful tidbits (and closed quite some bug reports that were invalid because the problem was solved long ago without getting a bugzilla update).
I even created a new bug report of my own. It is annoying that the lower pane on the "Driver Settings" tab is fixed in height, and a very low height at that. Because it is not resize-able, it's difficult to get an overview about all supported media sizes, for example. See the two screenshots to understand what I mean (click thumbnails for bigger images).
- Here is a challenge for you:
- Fix that bug (#139882). I guess it can be done in less than 5 lines of code. The files to look at: kpdriverpage.cpp and driverview.cpp.
- Price for current KDE developers:
- (a) You'll feel good.
(b) Pizza and a coke or beer next time we meet.
- Price for anyone who's not (yet) a KDE developer:
- (a) You'll gain some appetite to fix more little things in KDE.
(b) You'll have completed the huge first step on your way to become a new KDE developer: your first patch.
(c) You may get one of these cool @kde.org email addresses for you soon.
Any takers?
Syndicate Blogs
I wouldn't mind trying to
I wouldn't mind trying to fix it, but no pizza/beer for non-kde developers? Cheapskate!
Just wondering though, could this be done without having to completely switch over to a compiled KDE? I would prefer to keep on using a packaged KDE for my main environment (at least for now).
Yes, I'm a cheapskate... :-)
...but I assume it is even more effort for me to make sure that @kde.org email address becomes a reality. And from then on, of course the pizza/beer thingie gets in reach too -- because I'm currently compiling a list of more "JJ:"-tagged jobs for KDEPrint development.
Anyway, I don't think you need to switch over to a completely compiled KDE.
It should be enough to have "kdelibs3-devel" (SUSE naming convention) or "kdelibs3-dev" (Debian naming convention) installed, which are mainly .h and .la files, and an assortment of scripts. Then the kdelibs source code (which includes kdelibs/kdeprint), plus kdebase/kdeprint.
I'm sure you can get good advice how to compile just the KDEPrint parts in IRC on #kde-devel. And you can also do all this in a different user account, with different paths, of course.
I assume you already have some experience with coding, in other areas?
Coding? Yeah, sort of,
Coding? Yeah, sort of, although I've mainly been a Java developer the last countless years so my C++ is a bit rusty.
Can I reach you somewhere by email? tako AT codejive DOT org
Hint
I felt like doing this myself but am too lazy to dl and compile kdelibs so I'll give a hint instead:
Just my $0.02 from the peanut gallery,
Ben
PS. can't remember if splitter should replace the layout or be a child.
Already done
Wow, Aaron sure did a fast patch.
I hope it gets integrated soon.
Cheers
Ben