I have been chosen by you to complete this interesting project that is
QtShark. I'm 21 years old and currently studying Computer Science in
I already have created a wiki page that I will maintain to keep a track
of the progression of the project.
My task for the next days will be to make a check-up of the current
QtShark: what is working, not working and what is demanding (more) work.
The "challenge" to apply was to implement the Summary dialog in the
Statistics menu. I have to check the bugs in it (compile in
Windows/Linux/Mac OS, and see if everything is working properly).
I have added a new button to refresh the dialog with new infos and maybe
implement an option to auto-refresh the dialog x times per
secondes/minutes. What do you think about this ?
Hmmm, I never would have thought of needing a "refresh" for this window. I
suppose the statistics might be interesting to watch during a live capture
but I'm not sure...
I think in general the things in the window which change will do so on
new packets being received. In this case the window should be able to
get events the same way (I assume) the status bar already does.
I think the summary was designed with loaded captures in mind I'm not
sure making it into something else
is a good idea. Statistical info from live capture (if interesting)
should perhaps be done differently.