servermap update chart doesn't fit #471

Open
opened 2008-06-20 18:14:10 +00:00 by zooko · 3 comments

This screen shot shows that the chart is too big for its britches. As we say here on the farm.

This screen shot shows that the chart is too big for its britches. As we say here on the farm.
zooko added the
code-frontend-web
major
defect
1.1.0
labels 2008-06-20 18:14:10 +00:00
zooko added this to the undecided milestone 2008-06-20 18:14:10 +00:00
Author

Attachment servermap_chart_doesnt_fit.png (162342 bytes) added

**Attachment** servermap_chart_doesnt_fit.png (162342 bytes) added

hm, looks like the mapupdate talks to a variable number of peers, and if that number is too large, the graph doesn't fit.

So the fix would be to either reduce the height of the individual bars (if that's possible) or increase the height of the overall graph, according to the number of peers being displayed.

It might be a good idea to switch to PIL and build the graph ourselves (instead of using the google chart API), but I didn't want to add another library dependency. Using PIL would get us more control, at the expense of needing to write more code.

hm, looks like the mapupdate talks to a variable number of peers, and if that number is too large, the graph doesn't fit. So the fix would be to either reduce the height of the individual bars (if that's possible) or increase the height of the overall graph, according to the number of peers being displayed. It might be a good idea to switch to PIL and build the graph ourselves (instead of using the google chart API), but I didn't want to add another library dependency. Using PIL would get us more control, at the expense of needing to write more code.
tahoe-lafs modified the milestone from undecided to eventually 2010-02-11 03:50:44 +00:00
Author

See also #1942 which would also fix this ticket. (I'd prefer to fix #1942, but if somebody fixes this ticket, I would accept it until #1942 obviates it.)

See also #1942 which would also fix this ticket. (I'd prefer to fix #1942, but if somebody fixes this ticket, I would accept it until #1942 obviates it.)
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#471
No description provided.