News for hackers. Stuff that matters.
Re:Wireshark is switching to Qt by leephillips on Thursday October 17, 2013 @10:35AM (#6565598)
I've never used this, but from the screenshots it looks like a perfect candidate for a curses-type interface. Is there a good reason for using the extra resources required by the GUI?
Re:Wireshark is switching to Qt by digitalsushi on Thursday October 17, 2013 @11:20AM (#6565923)
I walked around at sharkfest in 2011 and got to chat with a lot of wireshark users during the picnic lunches. What struck me as interesting is that so many people use wireshark that are not network professionals by trade. They are poking through it, trying to just find a clue or two to see what the issue of the day is. I think that's wonderful! That wireshark is accessible enough with the gui to let people who are not diehard packet geeks really take a stab at looking under the hood and having a go at it.
Re:Wireshark is switching to Qt by cbhl on Thursday October 17, 2013 @11:42AM (#6566099)
Using Wireshark was actually part of the assignments a mandatory course for my undergraduate program at the University of Waterloo.
Re:Wireshark is switching to Qt by avtar on Thursday October 17, 2013 @11:02AM (#6565785)
Is there a good reason for using the extra resources required by the GUI?

Do you mean extra resources required by the GUI while capturing data? I've never captured traffic on a server using Ethereal/Wireshark. It's easier to use tcpdump to do that, save the captured data to a file, and then view that in Wireshark.

http://www.wireshark.org/docs/wsug_html_chunked/AppToolstcpd...

Re:Wireshark is switching to Qt by pjmlp on Thursday October 17, 2013 @11:09AM (#6565838)
We are no longer in 197x?
Re:Wireshark is switching to Qt by astrobe_ on Thursday October 17, 2013 @12:40PM (#6566483)
Wrong. This is a common misconception that command-line tools are no longer relevant because they are "old".

In some cases text/keyboard interfaces are better. Like for instance when editing case. In some other cases, graphical/mouse interface is better. Like for instance web browsing.

Command-line tools generally offer a larger language than GUI applications. And if that language is not enough, you can still combine them; something that is impossible with a GUI app.

Re:Wireshark is switching to Qt by takluyver on Thursday October 17, 2013 @01:44PM (#6566905)
curses programs are not command line tools - they're effectively GUI applications, but using the terminal as their 'graphical' toolkit.
Re:Wireshark is switching to Qt by pjmlp on Thursday October 17, 2013 @01:51PM (#6566959)
Macros, scripting.
Re:Wireshark is switching to Qt by icebraining on Thursday October 17, 2013 @12:02PM (#6566226)
The mouse-driven GUI was invented in 1973. What do you use, a Kinect?
Re:Wireshark is switching to Qt by kristopolous on Thursday October 17, 2013 @12:35PM (#6566442)
Forgot Engelbart in mother of all demos (1968)??
Re:Wireshark is switching to Qt by icebraining on Thursday October 17, 2013 @12:44PM (#6566511)
Oh, right, I was thinking about the Alto, sorry.
Re:Wireshark is switching to Qt by pjmlp on Thursday October 17, 2013 @01:49PM (#6566950)
But it only become widespread to the what was the technical average Joe in the 80's.
Re:Wireshark is switching to Qt by Shish2k on Thursday October 17, 2013 @11:09AM (#6565834)
The screenshots there are fairly minimal; there are an insane number of knobs and twiddles when you start digging through the menus

(I know you can do modal dialogs, comboboxes, even graphics in a console, but most people seem to agree GUI is better for that)

Re:Wireshark is switching to Qt by iends on Thursday October 17, 2013 @10:50AM (#6565704)
Some find a gui more usable. You can use tshark of you disagree.
Re:Wireshark is switching to Qt by ajross on Thursday October 17, 2013 @11:13AM (#6565872)
Some (hi!) find that a UI of any kind gets in the way and prefer to do this kind of work with tcpdump logs and perl. It's as much a taste thing as anything else, and certainly wireshark is very well regarded. It's basically the gold standard in this world.

It also used to be very Linux/Gtk-centric too, and part of me is sad that the focus is now on enabling proprietary platforms at the same level of robustness. But that's obviously a philosophy thing and I'm not the developer.

And to get to the point of the blog post: it's absolutely true that cross-platform sanity has never been part of Gtk+'s design goals. It's always (well, since Gnome 1.0) been a playground for stuff in Gnome, and work on other environments a secondary thing done mostly by volunteers.

From the perspective of an app developer, Qt is much (much!) cleaner in this regard. Though it gets that at the cost of staggering code size and build complexity. Really Qt has to duplicate the superset of features provided by all the supported environments. It does it, but I can't say it's pretty.

Re:Wireshark is switching to Qt by routelastresort on Thursday October 17, 2013 @11:21AM (#6565934)
^^^ some
Re:Wireshark is switching to Qt by mikecarlton on Thursday October 17, 2013 @11:14AM (#6565876)
The wheel goes full circle as always. If you're worried about resources just use tcpdump. I've always viewed wireshark as a GUI alternative to tcpdump. And yes, I know wireshark does more packet dissecting, but I rarely need that.
Re:Wireshark is switching to Qt by sp332 on Thursday October 17, 2013 @11:13AM (#6565864)
Yeah, usually the packet data doesn't all fit on the screen. SO first I'll resize the top pane(that lists packets) so I can browse, then when I pick one I'll click the field I want to look at in the next pane, then probably resize again so I can see more data in the lowest pane. Using a keyboard to switch which packet and which field you're looking at sounds like a pain to me.