Help offered

[Lior Mualem]

Hi everyone,
I've recently got some time freed and I would like to help improve / bring
kdevelop4 to maturity.
but I got a little bit lost - I couldn't find much information about
requirements / modules / tasks to be performed. Is there such a place?

Regardless, I have a few things that bothered me that I'd like to fix / code
first:
1. I couldn't find a "Class Browser" tool, is anyone doing something like
that? or can I start sketching something? I would hate doing duplicate work.
2. I saw some posts on the mailing lists and on some blogs about the current
debugger implementation not working and that someone started to port the old
debugger to kdevelop4. Can I help fix up the new debugger? Who's responsible
for it (or should I just start doing it all over again?)
3. This one is actually a minor improvement that bothered me, not really a
missing feature - There's no report for the current file being parsed in the
background.
When the cpp parser works in the background, I've noticed that it emit a
progress signal with a text such as "parsing included files" and on the UI,
this text is ignored.
It would be alot nicer to have the progress report the currently parsed file
and the UI display it on the status bar.
I've already created a proof of concept patch for myself as an introduction
to kdevelop programming but before I'll clean it up and do it properly - Is
there a reason why the text field is ignored and only a "start parsing" /
"Finished parsing" text is reported instead of a more descriptive text (such
as current file being parsed)?


Any help here would greatly be appreciated.
I already think that kdevelop rocks, especially it's cpp parser - one of the
best ones I've seen (although it still can't parse
boost::multi_index_container properly, no one can, but I'm sure it's just
temporary ;) ).
I can't wait to help improve it further and make it the best IDE around!

Thanks,
       Lior
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090225/bce63a62/attachment.html>