From kde-devel Fri Jun 22 15:47:23 2007 From: Matthew Woehlke Date: Fri, 22 Jun 2007 15:47:23 +0000 To: kde-devel Subject: Re: How can I help? Message-Id: X-MARC-Message: https://marc.info/?l=kde-devel&m=118253301231694 Mirko Stocker wrote: > On Wednesday 20 June 2007 00:35:55 Matthew Woehlke wrote: >> Meh, forget what Urs said ;-), kate could really, really use some love >> :-). Christoph can probably give you his personal 'to-do' list, or >> there's my own personal 'to-do' list, both of which are more-or-less in >> TODO in kdelibs/kate. > > Ah, I was looking at the TODO file in kdesdk/kate and wondered why it was so > empty. :-) As you've discovered, there is Kate and there is KATE/kate/katepart. katepart is used by Kate of course (which I rarely if ever use :-) ), but also KWrite and KDevelop (which, with Konsole, are the most-used programs on my box). Not to say that Kate isn't worthy, but fixing katepart has a greater impact. > Now, with what should I start.. I suppose I'll just pick something off > the list that doesn't sound too hard or requires too much knowledge of the > code, right? Or can you guys suggest something? :) If you're looking at KATE, I would start with items that are regressions/bugs. Specifically: : highlighting issues * highlighting uses [wrong attributes] * dsNormal always using dark color : HL configuration issues - attributes appear backwards in list + current highlighter not selected - 'use default' never checked * wrong (can be illegible) color used for group headings * selected item uses system background color, not attribute color : general - reimplement bracket matching The last one is probably not a beginner task, actually not much is really a "beginner" task until you understand the code a bit but you have to start somewhere :-). The ones marked with '*' are usability/accessibility concerns, especially the second one IMO *really* needs to be addressed because right now KATE is unusable with a dark background color. For me those are higher priority, and the lone '+' is somewhere in the middle. Oh, and then there is the problem of the wrong attributes being used, which as a WAG might be related to them appearing backwards in the list. The last two '*'s are probably fairly easy but might be the fault of the control kate uses to configure colors (i.e. code in kdelibs/kdeui, not kdelibs/kate). Anyway, if you are indeed going to hack on KATE/Kate/KWrite, you should join kwrite-devel :-). (In fact, I would encourage you to direct any replies to that list.) -- Matthew What, no punchline? >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<