After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 346528 - Graphical display for ping
Graphical display for ping
Status: RESOLVED FIXED
Product: gnome-nettool
Classification: Applications
Component: Tools
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Germán Poo-Caamaño
Rodrigo Moya
Depends on:
Blocks:
 
 
Reported: 2006-07-04 09:52 UTC by Callum McKenzie
Modified: 2006-11-29 18:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Add a bar-graph to the ping tool. (11.42 KB, patch)
2006-07-04 09:54 UTC, Callum McKenzie
none Details | Review
Obligatory screen shot (37.41 KB, image/png)
2006-07-04 09:57 UTC, Callum McKenzie
  Details
New and improved version of the patch. (12.24 KB, patch)
2006-07-31 08:22 UTC, Callum McKenzie
none Details | Review
The real new patch (12.24 KB, patch)
2006-07-31 08:25 UTC, Callum McKenzie
committed Details | Review
Updated screen-shot (23.78 KB, image/png)
2006-07-31 08:28 UTC, Callum McKenzie
  Details

Description Callum McKenzie 2006-07-04 09:52:46 UTC
The following patch adds a bar-graph display for ping. The idea is that you can tell at a glance if there are packets missing or massive variations in RTT.

The list view gets hidden behind an expander and labelled "Details".

The patch is basically complete, but slightly less than perfect. However, I'm going to be travelling for the next two weeks and decided to put this out for consideration before I leave.

It needs some UI tweaking (especially the space around the graph and the font size). Also, the draw_ping_graph function should be broken up and I haven't updated the documentation.
Comment 1 Callum McKenzie 2006-07-04 09:54:18 UTC
Created attachment 68341 [details] [review]
Add a bar-graph to the ping tool.
Comment 2 Callum McKenzie 2006-07-04 09:57:40 UTC
Created attachment 68342 [details]
Obligatory screen shot
Comment 3 Callum McKenzie 2006-07-31 08:22:06 UTC
Created attachment 69947 [details] [review]
New and improved version of the patch.

This is the finished version of the patch. Rather than using cairo, the gtk_paint_* calls are used so there are no longer odd fonts. The code has also been reorganised slightly.
Comment 4 Callum McKenzie 2006-07-31 08:25:56 UTC
Created attachment 69948 [details] [review]
The real new patch

By "final" I obviously meant "final except for that one small bug". New version.
Comment 5 Callum McKenzie 2006-07-31 08:28:19 UTC
Created attachment 69949 [details]
Updated screen-shot
Comment 6 Germán Poo-Caamaño 2006-08-02 23:37:37 UTC
Now we are in UI/String Freeze, so I will wait until the next cycle to apply this patch.  I have some questions, even I haven't looked the patch yet.

What will happend if the user choose 100 pings?  What will look like the time in the lower bar?

On the other hand, I think that "Seq. No." could be replaced for some better word.  Yesterday I had one, but I forgot it :-(  May be, only Seq.

Thanks!
Comment 7 Callum McKenzie 2006-08-03 10:27:46 UTC
The graph only displays the five most recent pings; regardless of how many are performed in total. I didn't consider the small benefits of a scaling bar-graph to be worth the complications. For large data-sets the summary information is far more useful, which is why I moved it above the bar graph.

As for "seq. no." I couldn't think of anything good either, but I'm wide open to suggestions. Just "Number" might be a better option, it should be obvious by looking at them that they form a sequence.

Comment 8 Callum McKenzie 2006-10-02 08:43:20 UTC
Just a gentle reminder of this patch's existence now that the next cycle is starting. If you decide any work needs to be done to it, I'm more than happy to do it.




Comment 9 Germán Poo-Caamaño 2006-11-29 18:14:56 UTC
Instead of having the last 5 measures, it could be a kind of acumulative graph.  Every time with a line more thin, according it gets more pings.  In that case it could provide a good picture of the behaviour of the net.

Anyway, I committed the patch in HEAD.  


Please, accept my apologizes of being to slow in apply it.

Thanks a lot.