programmatic access to dependency matrix information?

Hi,
The dependency matrix module first computes a lot of useful information, then it displays that information.

I would like to write a plugin that uses the information that the dependency matrix computes. I would like to display some or all of it in other ways.

Can I gain programmatic access to the information the dependency matrix computes?

Thank you.

2 comments
Comment actions Permalink

Hello softwarevisualization,

The dependency matrix module first computes a lot of useful
information, then it displays that information.
I would like to write a plugin that uses the information that the
dependency matrix computes. I would like to display some or all of it
in other ways.

Can I gain programmatic access to the information the dependency
matrix computes?


All of this information lives in the DSM plugin, for which we don't provide
source or OpenAPI. It should be possible to initiate the DSM calculation
and access the DSM model from a plugin that depends on the DSM plugin, but
unfortunately you'll have to figure this out by yourself - we're unable to
provide detailed support for this.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

OK so now I have to ask, and don't take this as criticism because it's not, and I appreciate your prompt and authoritative reply, but-

what good is a part of the IDE that isn't part of the OpenAPI? I mean, OK, people can use it, I sure do, but what place does non-OpenAPI code have in IntelliJ at all? If it's a licensing issue then Jetbrains needs to roll their own. Am I in the wrong place to argue that the future belongs to the Open-est API that still pays all the bills? How is JB going to tap that force of creative coders if the OpenAPI has huge holes in it or is too hard to understand or incomplete? I am not arguing for Open Sourcing IntelliJ, I am arguing for taking seriously the idea that having an OpenAPI that is at least as good as the modules and SPI etc that Netbeans has. Here's my free advice. If it's not possible to make a well documented, easy to understand OpenAPI around the existing code base, then assign a team to rewrite the product from scratch so it does have that property. It's not like your code base is freaking Windows and can't be extended OR improved OR rewritten because it's a big plate of spaghetti, can of worms choose your metaphor. ]]>

Am I alone in thinking that this issue is, well, everything?

0

Please sign in to leave a comment.