kdevelop development

Shawn McKenney shawn.mckenney at emmion.com
Mon Sep 12 01:32:34 UTC 2016

On Sun, Sep 11, 2016 at 12:46 PM, Milian Wolff <mail at milianw.de> wrote:

> On Sonntag, 11. September 2016 08:42:59 CEST Shawn McKenney wrote:
> > Hi All -
> >
> > I have just installed KDE neon and have built kdevelop from source using
> > the kdesrc-build tool. I would like to contribute to the project. I am
> > relatively new to KDE but have quite a bit of Qt and C++ background.
> Could
> > someone point me towards a good place to start?
> My answer to this question is always: Find something that bothers you
> personally and then fix it. This will keep your motivation much higher
> than us
> proposing something random to you that you may not even be using inside
> KDevelop.
> If you really would like to work on something that we'd like to see, then
> I'd
> propose a proper plugin for clang-format, i.e. with a nice configuration
> and so on.
> But really, just come up with something you think could be improved, and/or
> browse through our bug list, and then keep nagging us with questions or
> feedback and input on what you are trying to do.
> > Do you have a documented
> > development process and CI system? Do you usually build with kdesrc-build
> > or run cmake by hand?
> Laurent already answered that, I think.
> Cheers, and welcome to KDevelop - looking forward to your patches.
> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de

Thank you Laurent and Milian -

I think I'll tackle Bug 359136
<https://bugs.kde.org/show_bug.cgi?id=359136> first
and then maybe graduate to something like the clang formatter.

FYI - I found a link to the kdevplatform API
which is quite useful. It looks like the link to the Coding Guidelines
leads to the Welcome page (
https://www.kdevelop.org/mediawiki/Coding_Guidelines) of the wiki though.

I imagine that there are two ways to approach the .cpp/.h switching

1) First, determine which file is open and active. Then use an
IProjectManager (or something similar that contains a list of project
files) to determine which corresponding file to switch to. This works fine
if all cpp/h pairs are named the same.

2) Use the AST (DUChain?) to determine which File context the cursor is in.
>From there, try to determine the corresponding cpp/h file. This may be
ambiguous since a cpp file can include multiple h files and vice versa.

I could be missing something obvious here as well. I certainly don't know
the best approach for this project. Any input/ideas are appreciated.


Shawn McKenney
President, Emmion
858 254 5468
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160911/6ecd342e/attachment.html>

More information about the KDevelop-devel mailing list