Improve resource plots in JavaUI

[GoogleCodeExporter]

A number of improvements would help.  Here's an attempt at a rough priority 
order:

1. Show y-axis numbers.
2. Don't squash the chart if there isn't much variation (see attached 
screenshot, which causes the text on the right to be cutoff)
3. Included upper/lower bounds.
4. It would be really cool to be able to see all the tokens that contribute to 
a given resource level (I guess the master tokens for each use etc?) but I'm 
not sure how to do that :).

It may not make sense to try putting all of this in the gantt chart view?

Original issue reported on code.google.com by tristanb...@gmail.com on 4 Mar 2011 at 10:22

Attachments:

• SqaushedResources.png

[GoogleCodeExporter]

Just committed #2. The tooltip shows the lower/upper bounds, do you still want 
them printed on the chart itself? 

Original comment by kichkaylo@gmail.com on 28 May 2011 at 1:59

[GoogleCodeExporter]

Thanks for working on this.  I think it would be useful to see the bounds on 
the chart too.  A couple of comments:

 - Note that it's on the EUROPA todo list to add upper and lower bounds that can change over time, in case that affects your implementation

 - See the attached figure - the first level looks low (it's hard to see it drop at time 1), but is actually at the upper bound.  Is it possible to scale the y-axis so the upper bound is near the top?

Thanks!

Original comment by tristanb...@gmail.com on 1 Jun 2011 at 12:13

Attachments:

• Gantt.png

[GoogleCodeExporter]

1) It goes over all timepoints and pick the max of upper bounds and min of 
lower bounds.
2) Isn't this the case where it actually collapsed, so it was both the upper 
and the lower? Also, I am somewhat concerned that scaling might add confusion 
if neighboring lines have different Y-axis scale. I am collecting opinions. 

Original comment by kichkaylo@gmail.com on 1 Jun 2011 at 3:03

[GoogleCodeExporter]

My understanding is that it would scale the way I expect *except* in the case I 
have where it used to be squashing the text beside the resource curve (in that 
case I think you're just making the area higher without increasing the height 
of the levels?).

(the example attached has minLevel = 0, maxLevel = 10, and initLevel=10)

I agree that with multiple resources, different scaling could be confusing.  
I'd fix this by adding some sort of y-axis label.  A single number on the 
y-axis could be sufficient to indicate scale, perhaps....

Original comment by tristanb...@gmail.com on 1 Jun 2011 at 11:40