Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transfer graph could be made prettier #16

Open
ghost opened this issue Aug 8, 2012 · 1 comment
Open

Transfer graph could be made prettier #16

ghost opened this issue Aug 8, 2012 · 1 comment

Comments

@ghost
Copy link

ghost commented Aug 8, 2012

Just a thought about the upload/download speed graph. It could be made prettier, with the following suggestions:-

  1. Rather than a line graph, it should probably be some form of bar chart, as this is more indicative of the data
  2. Lock graph to 'pretty' numbers, rather than scaling from the maximum speed.
  3. Some horizontal lines and perhaps some vertical time lines
  4. Perhaps the ability to scale the graph on some form of slider / button switching
  5. Perhaps some form of update control
@ghost ghost self-assigned this Aug 8, 2012
@conicalflask
Copy link
Owner

You asked for it :) Go nuts.

  1. Yeah probably.
  2. Scaling from the maximum is a pretty standard thing to do. Performance graphs do it all over the place, especially where we don't know which pretty number is best.
  3. Probably with care. These can look busy quickly.
  4. I'm really not keen on this. It seems like a widget for the sake of it, on a page that largely exists for the sake of it anyway.
  5. Maybe. This might be more complex than you realise as all the data is collected and processed by the ProgressTracker class which is itself imperfect for this task. The ProgressTracker smooths out the rates to enable decent ETAs to be generated but in this case would just mean changing the update frequency would have no effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant