[jira] Updated: (MPDASHBOARD-15) Alternative layout for report

[ji...@codehaus.org]

The following issue has been updated:

    Updater: Nascif A. Abousalh-Neto (mailto:nascif@acm.org)
       Date: Tue, 12 Oct 2004 9:57 PM
    Comment:
An example of the proposed new layout. Correlation between aggregator values and bar lengths may be wrong... :-)
    Changes:
             Attachment changed to dashboard-report-new.html
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MPDASHBOARD-15?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPDASHBOARD-15

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPDASHBOARD-15
    Summary: Alternative layout for report
       Type: Wish

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-dashboard-plugin
   Versions:
             1.5

   Assignee: 
   Reporter: Nascif A. Abousalh-Neto

    Created: Tue, 12 Oct 2004 9:36 PM
    Updated: Tue, 12 Oct 2004 9:57 PM

Description:
One of the problems (IMHO) of the current layout is that it makes it hard to compare values between projects - the brain would work better with graphs that visually put the values in a clear perspective.

For example, let's say that project A has 200 CheckStyle violations and project B has 400. Having a bar graph with its length proportional to the number of violations would clearly indicate the difference between the two values.

Going one step further, the graphs could be scaled in relation to a common measure of the project size - let's say the total number of lines of code, or the total number of lines covered by JCoverage/Clover.

So let's say that project A has 2000 lines, and project B has 8000. Just by looking at the bar graphs, we can easily tell that although B has twice as many violations then A, it is in better shape (theoretically) as it is half the rate of violations per line of code.

I manually changed a dashboard-report.html to illustrate the concept. I am still not clear about how hard it would be to implement it - one of the challenges is that it would introduce dependencies among the aggregators - or more precisely, among their results, during the rendering process.

 



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org