Wireshark Switches To Qt 79
An anonymous reader writes "Beginning with version 1.11.0, open source packet analyzer Wireshark is switching its user interface library from GTK+ to Qt. 'Both libraries make it easy for developers [to] write applications that will run on different platforms without having to rewrite a lot of code. GTK+ has had a huge impact on the way Wireshark looks and feels and on its popularity but it doesn't cover our supported platforms as effectively as it should and the situation is getting worse as time goes on.'"
Meh (Score:3)
I can't say that I really mind. I like to try to use mostly GTK based apps but it still falls down to the quality of the app. I use qBittorrent as my Torrent client because it works better than Deluge or any other GTK client I've found. Particularly when set to the same theme QT is just fine.
Re: (Score:1, Funny)
GTK is not called the Gay ToolKit for nothing!
Re: (Score:1)
Re: (Score:2)
The quality of applications is all I've come to care about. I used to be the same about trying to use GTK, but I just can't bring myself to ditch a superior program for an inferior one just because of which toolkit they use. License for their code? Sure. GTK vs QT? Meh.
There goes another one (Score:4, Interesting)
Re: (Score:1)
I really want to see gimp ported to Qt. That would be hilarious. We could call it qtImp, pronounced "cute imp."
Re: (Score:2)
Re: (Score:2)
GIMP isn't named GIMP because it used GTK.
Re:There goes another one (Score:5, Informative)
It's just the opposite. GTK is named after GIMP.
GIMP is GNU Image Manipulation Program
GTK is GIMP ToolKit
Re: (Score:2)
Re: (Score:1)
Gnome ToolKit?
Re: (Score:3)
He'll switch when Microsoft does.
Re: (Score:2)
Not the guy who said it originally, but I think that would be the lion's share of the hilarity he mentioned.
Re: (Score:2)
Re: (Score:3)
Re: (Score:2)
What exactly are you concerned about them loosing [google.com]? Maybe some horrible monster they've been keeping in their basement? Or a bio-genetic plague?
Why can't you just tow the line and give him free reign? It passed the spell checker, isn't that all that counts?
Re: (Score:2)
It should have read: "Why can't ewe just tow the line and give him free rain?
The "reign" was already wrong - the correct word would have been "rein". Not quite as much fail as at first sight?
Re: (Score:2)
Not... a... typographical error!!!
Re: (Score:2)
Worse. Much worse.
More code.
Re: (Score:2)
A Beowulf cluster of grammar Nazis!
Re: (Score:1)
Re: (Score:2)
Loose, v.: pass. and intr. To finish working; (of a school, factory, etc.) to close, disperse, ‘break up’.
If you like historicisms, there's also: intr. To crumble away; to dissolve, melt. Or even transf. To relax or loosen (the bowels). Yeah, the last one could be accurate. I hope they have their brown pants at the ready. :-)
Props to all sticking it out and trying Qt out! (Score:5, Insightful)
This is a big win for the Qt ecosystem. Between KDE libraries reworked into portable Qt modules [slashdot.org] and official iOS and Android support [slashdot.org] even with support from Digia [slashdot.org]-- Qt is gaining momentum. They even managed to survive being gobbled by Nokia [slashdot.org], then being sold [slashdot.org] to Digia [slashdot.org]-- it has been a bumpy ride.
I recently tried out the latest Kubuntu and have been loving it installed on an old Dell D410 (12inch, 1.8Ghz SC Pentium, 1.5G RAM) laptop and it runs well and does everything I need (which in this case is Qt related application development :-)
Re: (Score:3)
You're running Kubuntu 13.10? How is it so far?
I've long enjoyed KDE and pyqt programming. It's nice to see the underlying library move forward so successfully. I've found that, at least with pyqt, the QT libraries are rather large to ship around. I hope this doesn't increase the size of wireshark too much. It's nice to be able to easily install and run it on platforms like raspbian.
Re: (Score:2)
Someone really needs to explain the appeal of Kubuntu and KDE to me. I just don't get it. It's so *busy*: everything is huge with glowing drop shadows and spinning cursors and animations everywhere. It's also the only desktop environment I've ever sat down at that I couldn't just use immediately - I tried "creating an activity" and was left with a completely blank desktop, not even any panels or anything. There may have been keyboard shortcuts to get out of that situation, but I didn't know them and shouldn
Re: (Score:2)
Activities are just workspaces. They might offer a little more customization than a workspace-- but that's all they are.
I used XFCE for many years on this same machine-- without compliant. What I liked about KDE is that it ran as well as XFCE and came with everything I needed for Qt development. Also I don't need to double-load application frameworks. Iv'e been able to use KDE or pure Qt apps for everything I need.
As for drop-shadows, bouncy cursors and business-- that's both accepted and came be done ta
Re: (Score:2)
Re: (Score:2)
Someone really needs to explain the appeal of Kubuntu and KDE to me. I just don't get it. It's so *busy*: everything is huge with glowing drop shadows and spinning cursors and animations everywhere.
hmm. i stare at the animations a couple of days after my first install, then disable them all :)
It's also the only desktop environment I've ever sat down at that I couldn't just use immediately - I tried "creating an activity" and was left with a completely blank desktop, not even any panels or anything. There may have been keyboard shortcuts to get out of that situation, but I didn't know them and shouldn't have had to.
i'll admit that as a kde user since kde 2 (and it being my primary platform since kde 3.0), i do not use activities. i kinda understand the concept, but don't fully embrace it. the great thing is that i don't have to use them ;)
Re: (Score:2)
It's probably due in part to the whole KDE Free Qt [kde.org] thing. It keeps Qt free in the event Qt isn't...um...kept free. It's pretty nice.
GTK+ is ugly. (Score:3, Insightful)
There you go, "Gnome" with all your bullshit misunderstanding of how a GUI is intended to look like. Go Qt!
Gnome tool kit (Score:5, Insightful)
Gtk used to stand for the gimp toolkit, but more and more it's the gnome toolkit. I wouldn't be surprised to see it merged into the gnome framework entirely at and future date. Even the mailing list is now renamed to gnome-list.
It's still a great toolkit, and still somewhat cross-platform. It's still being actively worked on on Windows and Mac osx. But with the focus mainly on gnome and Linux (gnome 3 has little support for other platforms now) they are not as advanced or stable ports.
I think wireshark's move to qt is a good one. Will definitely lead to better apps on Windows and Mac.
Re: (Score:2)
Gtk used to stand for the gimp toolkit, but more and more it's the gnome toolkit. I wouldn't be surprised to see it merged into the gnome framework entirely at and future date. Even the mailing list is now renamed to gnome-list.
They did? I still receive email to gtk-list.
Re: (Score:2)
That's true. gtk-list is still gtk-list@gnome.org, but my e-mail client shows "Gnome list" as the long name.
Re: (Score:3)
Well with GTK+ being cross platform, Wireshark on MacOS still required using the X Windows interface. So will the move to Qt finally make it a native app?
Re: (Score:2)
Well with GTK+ being cross platform, Wireshark on MacOS still required using the X Windows interface. So will the move to Qt finally make it a native app?
It will make it an app that doesn't use X11 on OS X.
It won't make it an all-Cocoa app (although it will, modulo issues with QtMacExtras, use the native toolbar widget, at least, and, time permitting, it'll use the native file dialog sheets rather than the definitely-doesn't-look-like-OS-X Qt file dialog).
It won't be sufficient to make it an app following the OS X "one process for all open windows" model; that would require, for example, replacing all the static variables holding dissection state with per-
Re: (Score:2)
Yes Qt will make it a non-X11, more native application on OS X (carbon, though if I recall correctly).
Re: (Score:2)
Yes Qt will make it a non-X11, more native application on OS X (carbon, though if I recall correctly).
Newer versions of Qt support 64-bit programs, so they don't run atop Carbon.
Re: Wireshark runs without X11 under MacOSX (Score:1)
Well with GTK+ being cross platform, Wireshark on MacOS still required using the X Windows interface. So will the move to Qt finally make it a native app?
Wireshark doesn't require X11, GTK2 does.
So when you've installed GTK2 via Macports like this
gtk2 @2.24.21_0+no_x11+quartz+universal
then wireshark isn't using X11 and feels like a native MacOS-Application:
- Wireshark-Dockicon
- No X11 is started
- The menubar is on top, like in any other mac-applcation
regards
WINGs (Score:2)
I'd like to see it ported to WINGs [wikipedia.org]. It's simple, fast, pretty and not married to C++.
Status of QT? (Score:1)
When last I heard, a few years ago, QT had been acquired by Nokia. More recently, it seems that Nokia is being acquired by the borg(Microsoft).
It would seem that QT is to be owned by Microsoft. Is this correct? If so, what does that hold for QT? I realize that QT is LGPL or some such, but that doesn't mean that Microsoft won't ruin it or snuff it out. See Oracle and MySQL for a road map. Hopefully I am wrong.
Re:Status of QT? (Score:4, Insightful)
When last I heard, a few years ago, QT had been acquired by Nokia. More recently, it seems that Nokia is being acquired by the borg(Microsoft).
It would seem that QT is to be owned by Microsoft. Is this correct? If so, what does that hold for QT? I realize that QT is LGPL or some such, but that doesn't mean that Microsoft won't ruin it or snuff it out. See Oracle and MySQL for a road map. Hopefully I am wrong.
Fortunately, yes, you are wrong. Digia bought the business side of Qt from Nokia in 2012 [digia.com]. The free-software side of Qt is the Qt Project [qt-project.org].
Re: (Score:3)
i met digia guys in tallinn last year at akademy (kde conference), they gave me a free t-shirt. seemed nice =)
Re: (Score:2)
I don't use software that chmods or chown mydirectories. Wireshark has done so. Citation? Look it up. Wireshark sucks.
Well, I looked it up, and there are no chmod or chown calls in the Wireshark source (trunk, 1.10, or 1.8), and there are no obvious pages found by Teh Google about this.
Citation (and, no, "look it up" isn't a citation, it's a trick used by people who don't actually have citations) or it didn't happen.
Re: (Score:2)
I don't use software that chmods or chown mydirectories. Wireshark has done so. Citation? Look it up. Wireshark sucks.
To fully access the data stack from eth0 or wlan0 you need to run wireshark as root otherwise your trace will not be complete. The result is that the files created by wireshark then are owned by # not $
All packet sniffers technically need to have root to be effective on any Unix like system. All you have to do is chown the output files and you can edit and delete them to your hearts content. Technically wireshark does not change the ownership of any directories but only inherits root because it is run as r
Re: (Score:2)
To fully access the data stack from eth0 or wlan0 you need to run wireshark as root otherwise your trace will not be complete.
Nope.
For one thing, Wireshark shouldn't be accessing the network interfaces, it should be asking the dumpcap program, which is one of the components of Wireshark, to do so. To quote Wireshark's README.packaging file [wireshark.org]:
For another thing, the README.packaging document (in the "Privileges" section, which contains that rather emphatic quote), and the CaptureSetup/CapturePrivileges page in the Wireshark Wiki [wireshark.org], discuss ways in which
Re: (Score:2)
To fully access the data stack from eth0 or wlan0 you need to run wireshark as root otherwise your trace will not be complete.
Nope.
For one thing, Wireshark shouldn't be accessing the network interfaces, it should be asking the dumpcap program, which is one of the components of Wireshark, to do so. To quote Wireshark's README.packaging file [wireshark.org]:
For another thing, the README.packaging document (in the "Privileges" section, which contains that rather emphatic quote), and the CaptureSetup/CapturePrivileges page in the Wireshark Wiki [wireshark.org], discuss ways in which you can avoid even running dumpcap as root - it may need additional privileges, but not full root privileges.
All packet sniffers technically need to have root to be effective on any Unix like system.
Nope. See the above documents and the main libpcap man page [tcpdump.org] (following "Reading packets from a network interface may require that you have special privileges:"). That's what the ChmodBPF script installed by Wireshark on OS X does; see the "Under BSD (this includes Mac OS X)" section - it does the "some other way to make that happen at boot time".
This message was not sent from an iPhone because Peter Sellers really was a deviated prevert without a dime for the call
Presumably he had to answer to the Coca-Cola company for that?
Ok Thanks I am running the older version LOL
$ wireshark --version wireshark 1.4.6 Copyright 1998-2011 Gerald Combs and contributors. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled (32-bit) with GTK+ 2.24.4, with GLib 2.28.6, with libpcap 1.1.1, with libz 1.2.3.4, with POSIX capabilities (Linux), without libpcre, with SMI 0.4.8, with c-ares 1.7.3, with Lua 5.1, without Python, with GnuTLS 2.8.6, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 18 2011 15:44:36), without AirPcap. Running on Linux 2.6.38-8-generic, with libpcap version 1.1.1, with libz 1.2.3.4, GnuTLS 2.8.6, Gcrypt 1.4.6. Built using gcc 4.5.2. ~ $
Guess I should upgrade and RTFM. I only use it when doing single traces though so the chances of leaving something open and being hacked while using it are almost zero, I do not run it as a process on the server only as a tracking mechanism if something gets hacked and then only on a the old laptop that I use for diagnostics. I should set it up as a service though if I can figure out an effective way to keep the log sizes down to specific info instead of a verbos
Re: (Score:2)
GTK+ community is declining (Score:3)
GTK+ was outrageously superior to anything out there about 5 years ago and today it's a declining community without clear goals and without strong support from developers that need this kind of library. I don't fully understand all the details that make this happened, but I clearly remember that about 2 or 3 years ago, something changed radically when Nokia changed the Qt license and when the Gnome leaders started to act against there own community with the suicidal Gnome 3 project.
There nothing to hope when a few peoples take the power to deny the criticisms from a large part of there community. The community simple change to get away from the toxic. That's the strong power of the open source, and it's a shame that leaders from leading open source project don't understand that simple rule.
In a ideal world GTK+ and QT should have merged there most valuable features in a new neutral project as soon as QT was fully open source. Real developers don't car about the name of the project as long as the quality and the community are driving the project up to the edge of there expectations.
Re: (Score:1)
The only thing Nokia changed was adding an LGPL option. It was already dual licensed under the GPL.
Re: (Score:2)
LGPL vs GPL was the key point for non-free projects that instead was forced to use the commercial license.
Re: (Score:2)
I should have used the Gnome libraries dependencies instead of GTK+ to compare to the Qt complete library.
The GPL license was a showstopper for non-open projects that don't wants to use a commercial license. The LGPL changed that important nuance.
The difference in the language is certainly a massive concern in case of a direct merge, but I don't think there is any features of one of the project that cannot be implemented in the language used by the other project. This is still a hug amount of work...
A other
Intrusion detection (Score:1)