JavaNCSS?

Hi, all.

Has anyone worked on a plugin wrapping JavaNCSS? I am after the mccabe
metric primarily, but other info as needed. (ANT and command line work
fine, I just like better integration when I can get it.)

Scott

3 comments


It's not a neatly formatted report, but the InspectionGadgets plugin includes inspections for
NCSS and Cyclotomic complexity, flagging methods or classes with values above some (settable) threshold. There's a handful of other class and method metrics availale as well. I keep playing around with designing the Great IDEA Metrics Plugin, but polishing InspectionGadgets always seems to take priority.

--Dave

0

In article <29343711.1076535669959.JavaMail.itn@is.intellij.net>,
Dave Griffith <dave.griffith@cnn.com> wrote:

It's not a neatly formatted report, but the InspectionGadgets plugin includes
inspections for
NCSS and Cyclotomic complexity, flagging methods or classes with values above
some (settable) threshold. There's a handful of other class and method
metrics availale as well. I keep playing around with designing the Great
IDEA Metrics Plugin, but polishing InspectionGadgets always seems to take
priority.


Cool - thanks.

Metrics are an area where Together really shines - lists of routines in
metric sorted order and the like - but together is a pain in many other
ways.

I suspect that a Metric plugin could be created for IDEA a lot more
easily than many of the existing plugins. I am amazed at how much some
of the popular plugins do.

Scott

0

>I suspect that a Metric plugin could be created for IDEA >a lot more easily than many of the existing plugins.

Oh, absolutely. Given the PSI, calculating pretty much any metric is a trivial coding task. Just craft an appropriate PsiRecursiveElementVisitor and all of the parse tree creation, management, traversal, and reference resolution are done for you. The trick with a metrics plugin is the UI. You need to chose which classes to run metrics for, which metrics to run, and possibly configuration options for the metrics. The Inspect Code panel seems like a good template for the input side. Output is where it gets trickier. Like Together, you'd want output as either as tables (with all the bells and whistles) or several different sorts of graph (distribution, histogram, Kiviat), and you'd want to be able to show differences and overlays as the code evolves. Sadly, this all takes someone with more Swing and UI design experience than I, although if anyone wants to attempt it I'd be glad to add a hand.

--Dave Griffith

0

Please sign in to leave a comment.