Announcement

Collapse
No announcement yet.

Wireshark Is Being Ported From GTK+ To Qt

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #51
    Originally posted by Delgarde View Post
    What'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"...
    I was responding to someone else who claimed that there were no tutorials on the Qt website, despite the fact that they were there and extremely easy to find. The person then went on to contrast that with the gtk tutorials, despite the fact that the gtk tutorials are on a different website, and on the gtk website are not labeled as tutorials at all. Yeah, sure, if you use google you can find tutorials for both gtk and Qt, but that wasn't what the person I was responding to did. If you think that google is the way to go, then tell that to the person I was responding to, not me.

    Comment


    • #52
      Originally posted by Alejandro Nova View Post
      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.
      Depends on your POV if that is a good thing (adding even more bloat to Qt).

      Comment


      • #53
        Originally posted by curaga View Post
        Depends on your POV if that is a good thing (adding even more bloat to Qt).
        KDE 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.

        Comment


        • #54
          Originally posted by curaga View Post
          Depends on your POV if that is a good thing (adding even more bloat to Qt).
          It is more complicated than that. First, one of the big changes in both Qt 5 and KDE Frameworks 5 is that the libraries have been modularized. Rather than pulling in "libqt" or "libkde", you pull in only the bits your program actually uses. A text editor won't need to pull in multimedia components, for example. So that will result in a significant drop in bloat for most applications.

          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


          • #55
            Originally posted by boudewijnrempt View Post
            KDE 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.
            Boudewijn, I was under the impression that KF5 would be a set of Qt plugins, a sort of an extension to Qt, rather than become integrated into Qt directly.

            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


            • #56
              First, as has already been discussed countless of times, QtCore alone is hugely bloated. And it's included in every Qt app.

              The "will become one" certainly didn't give confidence in that the KDE parts would stay a separate module. If they will, then I have nothing to complain about.

              Comment


              • #57
                Originally posted by curaga View Post
                First, as has already been discussed countless of times, QtCore alone is hugely bloated. And it's included in every Qt app.
                It doesn't matter if QtCore has 1 MB or 4 MB as it is shared among applications using mmap.

                Comment


                • #58
                  Originally posted by xeekei View Post
                  If only LibreOffice, Thunderbird, and Firefox would switch.
                  Plus GIMP.

                  Comment


                  • #59
                    Originally posted by Apopas View Post
                    Plus GIMP.
                    Wouldn't it be ironic for GIMP to move away from GIMP Toolkit?

                    Comment


                    • #60
                      Originally posted by Krejzi View Post
                      Wouldn't it be ironic for GIMP to move away from GIMP Toolkit?
                      Is there any problem with irony in general?

                      Comment

                      Working...
                      X