Originally posted by mark45
View Post
Announcement
Collapse
No announcement yet.
Wireshark Is Being Ported From GTK+ To Qt
Collapse
X
-
-
Originally posted by Pawlerson View PostThanks, but no. springlobby client which uses WxWidgets is terribly slow and ugly.
wxWidgets uses native widgets, just don't use ugly themes in your OS and you'll be happy.Last edited by kosenko; 17 October 2013, 08:26 PM.
Comment
-
I saw something some time ago, reading through the history of Krita, about an incomplete KDE port for GIMP called "kimp". It caused nothing but a flamefest, but became the foundation for Krita.
This time is the turning point to do something like that. Less and less apps are going to use GTK 3 and more apps will use Qt 5. And remember: with Qt 5.2, there are no KDELibs anymore; Qt 5.2 marks the point where Qt and KDE Frameworks 5 become one.Last edited by Alejandro Nova; 17 October 2013, 09:35 PM.
Comment
-
Originally posted by TheBlackCat View PostI see. I never looked there because it never occurred to me that "Hello World" would be under "API Documentation", which on every other language or toolkit website I have been to has the documentation for the API, not "Hello World" examples. Usually such things are under "Examples" or "Tutorials".
Comment
-
Originally posted by Delgarde View PostWhat's your point? You claimed there were no official tutorials for Gtk3, now you're finding endless more complaints after people pointed out that it took half a second to find them on Google, the first hit under the most obvious of keywords "gtk3 tutorials"...
Comment
-
Originally posted by Alejandro Nova View PostThis time is the turning point to do something like that. Less and less apps are going to use GTK 3 and more apps will use Qt 5. And remember: with Qt 5.2, there are no KDELibs anymore; Qt 5.2 marks the point where Qt and KDE Frameworks 5 become one.
Comment
-
Originally posted by curaga View PostDepends on your POV if that is a good thing (adding even more bloat to Qt).
Comment
-
Originally posted by curaga View PostDepends on your POV if that is a good thing (adding even more bloat to Qt).
Further, for the most part KDE classes are still KDE classes, they have only added a few new classes directly to Qt (and that has been commonly-used, low-level stuff). Instead, they have been eliminating redundancy, looking for cases where KDE classes have the same or similar functionality as Qt classes and eliminating those, in some cases adding a few more capabilities to the Qt classes where needed. KDE classes are only being kept when they add significantly more features than their Qt counterparts or there are no Qt counterparts at all. So again, that results in a reduction in bloat, since there is less duplication and redundancy.
Comment
-
Originally posted by boudewijnrempt View PostKDE Frameworks 5 does not "add even more bloat to Qt" -- it provides developers with a set of libraries that they can use in their Qt-based applications, if they need the functionality. And that follows the lead of Qt itself, which is significantly more modularized than Qt4 was.
Is this right?
It would be a bit odd to complain about the bloat of that, and then insist that you must use glib, for example.
Comment
Comment