GIMP 3.2 Will Aim To Be Out Within One Year Of GIMP 3.0

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • fintux
    Junior Member
    • Nov 2019
    • 29

    #11
    Originally posted by uid313 View Post
    I hope they can soon get to GTK 4.
    It is kind of funny that GTK originally came from GIMP (the name stands for GIMP ToolKit), and now they are lagging behind it so far. Though on the naming in more general, the G in GIMP comes from GNU and in it in turn comes from GNU's Not Unix, which is a recursive acronym. So actually the G in GTK comes two hops from a recursive acronym.

    Comment

    • Quackdoc
      Senior Member
      • Oct 2020
      • 4980

      #12
      I just hope it has a fully colormanaged pipeline

      Comment

      • caligula
        Senior Member
        • Jan 2014
        • 3312

        #13
        Originally posted by fintux View Post

        It is kind of funny that GTK originally came from GIMP (the name stands for GIMP ToolKit), and now they are lagging behind it so far. Though on the naming in more general, the G in GIMP comes from GNU and in it in turn comes from GNU's Not Unix, which is a recursive acronym. So actually the G in GTK comes two hops from a recursive acronym.
        Unfortunately GNU usually means outdated technical standards. Lots of outdated programming conventions, stupid extensions, bloat (compare gnu coreutils with the musl based distros). Also doing object oriented GUI in C is just crazy.

        Comment

        • Old Grouch
          Senior Member
          • Apr 2020
          • 669

          #14
          Originally posted by caligula View Post

          Unfortunately GNU usually means outdated technical standards. Lots of outdated programming conventions, stupid extensions, bloat (compare gnu coreutils with the musl based distros). Also doing object oriented GUI in C is just crazy.
          Do you object to the object-orientedness of the GUI, the use of C for a GUI, or doing object-oriented programming (in C)?

          Comment

          • FireBurn
            Senior Member
            • Dec 2007
            • 2126

            #15
            Sure Jan

            Comment

            • loganj
              Senior Member
              • Nov 2017
              • 606

              #16
              before GTA 7????

              Comment

              • aviallon
                Senior Member
                • Dec 2022
                • 275

                #17
                Originally posted by ElectricPrism View Post
                Interface Toolkits aside, IDGAF as long as the image transformations and engine is separate. And it seems like that's exactly what's done as GEGL can be scripted. So you want a Qt Interface? Start making patches, have at it. I'm sure a lot of people would love a Raster Qt tool.
                It's called Krita

                Comment

                • fintux
                  Junior Member
                  • Nov 2019
                  • 29

                  #18
                  Originally posted by Old Grouch View Post

                  Do you object to the object-orientedness of the GUI, the use of C for a GUI, or doing object-oriented programming (in C)?
                  I can only speak for myself, but I think it is the last part that doesn't make sense. I guess it did back when GTK originated, as C++ was not yet standardized, many compilers had all sorts of bugs and quirks and maybe not even supported on some platforms. And also could have been more resource-heavy. Nowadays, however, I don't think C would make sense. C++ provides natively many of the things that are bolted onto GLib (like subclassing, reference counting). Or if one wants to use a simpler language, then there's Rust.

                  I'm sure there are reasons, like personal preference/skills etc. But I've used both, GTK and Qt, and for me, it is a night-and-day difference between how easy they are to use, and a lot of that boils down to the language they're based on.

                  Comment

                  • Old Grouch
                    Senior Member
                    • Apr 2020
                    • 669

                    #19
                    Originally posted by fintux View Post

                    I can only speak for myself, but I think it is the last part that doesn't make sense. I guess it did back when GTK originated, as C++ was not yet standardized, many compilers had all sorts of bugs and quirks and maybe not even supported on some platforms. And also could have been more resource-heavy. Nowadays, however, I don't think C would make sense. C++ provides natively many of the things that are bolted onto GLib (like subclassing, reference counting). Or if one wants to use a simpler language, then there's Rust.

                    I'm sure there are reasons, like personal preference/skills etc. But I've used both, GTK and Qt, and for me, it is a night-and-day difference between how easy they are to use, and a lot of that boils down to the language they're based on.
                    Thanks for that. I suspected that might be the case. In principle, if the binding exists, you can use a GUI toolkit from any language (Python is used (!)), so it is just down to ease-of-use/productivity, in which case, using an OO language with an toolkit written in an OO language probably has the least 'impedance'. There's also an academic debate that could be had over whether 'pure' OO is sufficient/ideal for programming a GUI, depending on what someone defines as 'pure' OO (I don't want to go there - I have no wish to participate in a religious war, but it is sometimes interesting to watch from afar).
                    No matter what, when someone describes something as 'crazy', there's usually something going on. People do apparently crazy things for reasons that appear good to them, so understanding why can sometimes lead to useful insights. Thanks for the reply.

                    Comment

                    • Jumbotron
                      Senior Member
                      • Jul 2015
                      • 1197

                      #20
                      Originally posted by uid313 View Post
                      I hope they can soon get to GTK 4.
                      Gimp 3.2 by 2026

                      Gimp 4.0 with full GTK 4 rewrite.....2050

                      Comment

                      Working...
                      X