The following comment has been added to this issue:
Author: Nascif A. Abousalh-Neto
Created: Wed, 13 Oct 2004 9:10 AM
Body:
Hi Vincent,
Glad you like it. I was going to point out the scalability aspect as well - I got
myself picking among aggregators because of the lack of horizontal space in the table.
The patch will take a while. For now it is just an idea, I have to study the dashboard
"rendering" engine to have a better understanding of how to implement it. And I am in
a really tight schedule until December... If you have any pointers on how to do it or
where to look please send them my way.
Another possibility is to use JFreeChart, like StatCVS does, and have an even better
looking chart.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPDASHBOARD-15?page=comments#action_25303
---------------------------------------------------------------------
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: Wed, 13 Oct 2004 9:10 AM
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
