Krazy2 plugin for KDevelop

[Aleix Pol]

On Mon, Oct 29, 2012 at 9:30 PM, Daniel Calviño Sánchez
<danxuliu at gmail.com> wrote:
> Hi all,
>
> I would like to inform you about a GPLv2+ licensed Krazy2 plugin for
> KDevelop that I have been working on.
>
> The plugin is just a GUI to select the files and directories to
> analyze, select the checkers to run, launch Krazy2 analysis from
> KDevelop, and then parse the results to view them in a table. The
> files where each Krazy2 issue appears can be opened by double clicking
> on the items of that table. Besides that, the issues shown in the
> table can be analyzed again (without running the rest of the checkers
> on all the files), which is useful to check if an issue was really
> fixed after modifying a file.
>
> That is pretty much what the plugin does. Not very impressive, I know
> :P Anyway, I have no plans to add more features, at least in the short
> term, as right now the plugin covers my own needs and I have a lot of
> others things to do. I will try to keep it up to date with the changes
> on KDevelop and Krazy2 (as soon as I realize that something is broken,
> which may take a while as I am not updating them regularly), but I am
> not adding new features.
>
> But, of course, there is a lot of room for improvement in the plugin.
> For example, make easier to analyze only the modified files based on
> the VCS of a project, ask the user to save a modified document if it
> is going to be analyzed again, show annotations in the side bar of the
> editor marking where the issues are, refactor to use QSharedPointer or
> alike with Checker and Issue objects...
>
> Besides those ideas, there is a problem that should also be tackled:
> if a directory with a lot of files (hundreds of thousands) happens to
> be selected to be analyzed, the KDevelop GUI will freeze while the
> plugin is getting the list of files. Probably no one would need to run
> a Krazy2 analysis from KDevelop on a directory with hundreds of
> thousands of files, but even if it is selected by mistake, a freezed
> GUI does not look good from a user perspective :)
>
> The Git repository of the plugin is currently here:
> http://quickgit.kde.org/index.php?p=scratch%2Fdanxuliu%2Fkdev-krazy2.git&a=summary
>
> Even if it is a simple plugin, I think that it is ready to be moved to
> Playground/Devtools/Plugins. So, if there are no objections by the end
> of this week (I think that is enough time to raise objections ;) ), I
> will ask the KDE Sysadmins to move the Git repository there.
>
> Thanks for reading :)
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel

Hi!
First of all, cool stuff! :)
It might be interesting to integrate it with the language Problems? I
don't really like the idea of having another toolview for finding
problems.
Maybe you can create an ILanguageChecksProvider plugin there? This
could start bringing the pieces together...

Aleix