Announcement

Collapse
No announcement yet.

In Road To Qt, Audacious Switches From GTK3 Back To GTK2

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

  • In Road To Qt, Audacious Switches From GTK3 Back To GTK2

    Phoronix: In Road To Qt, Audacious Switches From GTK3 Back To GTK2

    The popular Audacious open-source audio player was ported to GNOME's GTK+ 3.x tool-kit, but now developers have decided to move back to their GTK2 user-interface port while ultimately they are planning for a Qt version...

    http://www.phoronix.com/vr.php?view=MTcyODA

  • #2
    Maybe they can revert version number too , 3.x was bumped because of gtk3. .

    Comment


    • #3
      Hooray!!

      I've been using kinda old 3.2.4 so far 'cause I refuse to use anything based on GTK3.

      Comment


      • #4
        funny reading this. Until now, I wasn't aware that they wanted to port to Qt. Going back to gtk2 for stability makes some sense, as gtk2 is as stable as it's going to get!
        I've been a long time audacious user but recently switched away from it, preferring qt programs with my kde desktop.
        Until audacious makes 'the right' switch toolkit-wise, I guess it wouldn't be wrong to link to http://qmmp.ylsoftware.com/.
        Qmmp is like audacious, at least it support the classic winamp interface styles and does what it says on the box - play music!

        Comment


        • #5
          I guess it's not that surprising, not everyone wants part of what Gnome is building, but given they switched to Gtk3 in the first place it is slightly confusing.

          Comment


          • #6
            well also Lubuntu is moving from Gtk2 to QT by LxQt graphical environment.

            Comment


            • #7
              If you want your stuff to run on windows - Qt is the only reasonable solution.
              For Gtk window$ and mac are just an afterthought, for example, to this day only the ancient gtk2 version of gedit is available for windows.

              Comment


              • #8
                Writing non-gnome stuff with GTK3 is like eating a cactus.
                "GTK3 was made for GNOME DE, we don't care if it's used anywhere else." -- official position of GNOME devs.

                Comment


                • #9
                  I can only understand and welcome their choice (even if I donít use Audacious) after having seen the disaster caused by a recent Gtk3 update (no more window borders, broken displayÖ). Not to mention the early problems that still havenít been fixed like the broken scrollbars. It looks like the only sane GUI choice nowadays is QtÖ (which I donít like much, mainly because itís C++Ö but it could be worse).

                  Comment


                  • #10
                    Awesome! Audacious is one of the first apps I used when I switched to Linux 3 years ago, and to this day it is IMO one of the best designed GTK apps out there. When they released their last GTK2 supported version, I stopped upgrading (and am using 3.0.4 to this day) because GTK3 looks plain horrible. Looks like I will finally be able to compile an up to date version again =)

                    I'm a bit sad about the switch to Qt because GTK2 is a very good looking toolkit, although I can understand it all the way, as I highly prefer Qt to it when developing my own programs (good cross platform support being just advantage).

                    Comment


                    • #11
                      I'm really conflicted. On the one hand, I love the direction they're going but, on the other hand, they removed support for sending MIDI output to my Yamaha PSR-E413 not to long ago (FluidSynth-only now) and the whole reason I use Audacious is to play all my esoteric formats in the same playlist.

                      Comment


                      • #12
                        I remember when everyone though that GTK3 was teh awesome for the lone reason of it representing a version number bump. Immediately GTK2 was stricken as old and obsolete and unusable, blah blah.

                        It'd be good if everything just moved to Qt at this point.

                        Comment


                        • #13
                          What is the point of another qt based music player? At least Clementine and Amarok should cover all the bases (the former for traditional music playing with all the network features, the latter for music browsing). It is kind of like how I'm not a fan of OpenShot porting to Qt when Kdenlive exists. It is completely redundant.

                          Comment


                          • #14
                            A few examples of non-traditional design choices: monochrome icons (or none at all), client-side window decorations, and message windows mimicking Android.
                            /me not understanding...

                            What monochrome icons? Isn't that, what icon themes are for?

                            Client side window decorations are optional, AFAIK. Yet, they allow greater flexibility for the application designer.

                            Android message windows?

                            Furthermore, using some #ifdefs and a few build system tweaks, a gtk3 app should compile as gtk2 app.

                            Comment


                            • #15
                              Anybody knows any tablet with gnome 3 in it? I would like to know if at least all those decissions they've made are worth anything.

                              Comment

                              Working...
                              X