Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

I Want This Code Visualizer 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I tried something similar in PerlySense, but I consider it a failed experiment.

    In the Overview, there is (well, was) a Signature Survey [cpan.org] of the file, i.e. a char for each type of "thing" in the file (pod blocks, subs, statements, string literals, etc). Like this:

    * Structure *
    ;;;';;;;;;;{;";}{;;;;{}"";{}"";";}{;;;';';";;;{;'";;';;;
    };';}S{;";"";;}S{;' {}{"};;;}S{;;;;";";;};
    I got the idea in an interesting article about Software Archeology [pragprog.com].

    I had hoped it would give me a kind of ambient feel of the structure of the file, but I found it didn't actually do that for me. Maybe it could have worked better with color highlighting, maybe it didn't actually represent anything useful. So I removed it in later versions.

    Looking at the image you linked to it's clear that may work better. It could also be an indicator next to each sub/method being displayed in the Overview (On a more visionary time scale (i.e. not right now) I'm also thinking of indicating complexity, edit volatility/vcs activity with sparklines, test coverage and stuff there).
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.