Help offered

[Andreas Pakulat]

On 25.02.09 15:10:46, Lior Mualem wrote:
> 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?

There's bugs.kde.org, look for bugs/wishes for kdevelop and kdevplatform.
There's also a feature-list on the wiki:
http://www.kdevelop.org/mediawiki/index.php/KDevelop_4/Feature_Plan 
 
> 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.

Its in trunk/playground/devtools/kdevelop4-extra-plugins/classbrowser, but
it needs some love before it can be moved back to kdevplatform.

> 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?)

Vladimir would be the one who knows the debugger best, the plugin is in
trunk/KDE/kdevelop/debuggers/gdb. Thats the completely rewritten new one.
There's another gdb plugin thats simply a Qt4 port of the KDE3 code in
playground/devtools/kdevelop4-extra-plugins/debugger

> 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.

We have a patch flying around the list which ported the kmail progress
widget to kdevelop which would enable us to show this information if the
user wants to see it, but hide it otherwise.

I'm not sure this is useful information and it would change quite often
causing annoying disturbances while you're editing code.

> 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)?

Well, the information is simply not very useful to a user, either the
parser does something or it doesn't do something. The user shouldn't be
concerned about what it does exactly.

> I can't wait to help improve it further and make it the best IDE around!

Welcome aboard :)
 
Andreas

-- 
The whole world is a tuxedo and you are a pair of brown shoes.
		-- George Gobel