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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • A grayscale "minesweeper" bitmap of code sounds like a nifty visualization, and a lot more straightforward than trying to extract history from CVS to "age" code, painting lines in different colors depending on how recently they've been touched.
    • Oh no, i'm not trying to age code, just show the migration of clumps of characters. I am curious how different the clumps look from start to finish. I might even be able to identity distinct coding styles.
      • I'm trying to age code, but progress is slow. Extracting the right info from CVS and collating it is messy.
        • After I read this I had a thought that whilst it may be interesting to display the age of code visually, it may be more worthwhile to consider displaying the variability of the code in a visual form - That is, plotting the number of revisions and changes made to code against the code age. My rationale for this is that while working with code age would provide a incidencal overview of code stability, variability assessed by revisions and changes, potentially as a secondary measure to age, could provide a more interesting overview of development trends within larger codebases.