KDevPlaform Plugin development

Milian Wolff mail at milianw.de
Fri Oct 22 16:21:47 UTC 2010


On Friday 22 October 2010 16:48:17 Andreas Pakulat wrote:
> On 22.10.10 15:46:38, Milian Wolff wrote:
> > On Friday 22 October 2010 14:07:57 Sven Aßmann wrote:
> > > Hello,
> > > 
> > > i'm not sure if the question i have belongs to here? Maybe anyone can
> > > help me...
> > > 
> > > I try to develop a kdevplatform plugin for the famous TODO comment. To
> > > get an overview of the TODOs in a project. At the begining simple as
> > > hell. Like the Problems View.
> > > 
> > > The question:
> > > How can i test the plugin in action? Or how will kdevelop load my
> > > plugin?
> > > 
> > > Is there any documentation to get on with the first steps of plugin
> > > development or these problems?
> > 
> > As Syron said, you should contact Dmitry:
> > 
> > https://barney.cs.uni-potsdam.de/mailman/private/kdevelop-devel/2010-
> > October/038840.html
> > 
> > You two should try to work out how to improve the problems toolview to
> > make it useable with his patch for the TODO problems.
> > 
> > I can create you a git branch to work on.
> 
> Didn't we all agree that a separate 'Tasks' toolview would be better as
> TODO and FIXME are not really problems (not even warnings) in the sense
> that the problem toolview shows?

*sigh*, I don't care that much, I just disagree personally. Use the PHP 
language plugin for example, it reports quite a lot of *useful* errors there 
that it detects during its semantic analysis. Things like using deprecated 
functions comes to mind.

How is that different than a TODO? Maybe in "severity" but that would just make 
my point even more valid: Make the existing widget actually usable (filters, 
sorting, full project overview, ...).

Anyhow, who codes decides. This time it won't be me.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20101022/129eabc4/attachment.sig>


More information about the KDevelop-devel mailing list