Announcement

Collapse
No announcement yet.

Did Hell Freeze Over? GIMP 2.8 Released

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

  • Did Hell Freeze Over? GIMP 2.8 Released

    Phoronix: Did Hell Freeze Over? GIMP 2.8 Released

    With word this morning of Electronic Arts making plans with Ubuntu and now the release of GIMP 2.8, some may think that hell has frozen over...

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

  • #2
    IMO this is a good example of why Gtk is not suited for complicated stuff. It's good for simple things, but once you're doing something *really* non-trivial, it becomes a liability.

    Comment


    • #3
      Chasing down the dependencies to install this from source is turning out to be a major pain in the ass. I wonder when this will hit the repos?

      Comment


      • #4
        Hoping to see this ship with Fedora 17.

        Comment


        • #5
          Originally posted by RealNC View Post
          IMO this is a good example of why Gtk is not suited for complicated stuff. It's good for simple things, but once you're doing something *really* non-trivial, it becomes a liability.
          Couldn't agree more. Having worked with higher-level UI toolkits like QT and Java/Swing it makes me wonder how so many developers can manage the burden of GTKs horrible API design.
          And the yet again completly screwed up their filechooser for GTK3 (and for fun, backported the changes to GTK2 - yeah!)

          Comment


          • #6
            Originally posted by Linuxhippy View Post
            QT and Java/Swing it makes me wonder how so many developers can manage the burden of GTKs horrible API design.
            I love qt, but please, please, don't talk about Java like this :'(.
            Last edited by Sverro2; 05-03-2012, 01:38 PM.

            Comment


            • #7
              Originally posted by Linuxhippy View Post
              Couldn't agree more. Having worked with higher-level UI toolkits like QT and Java/Swing it makes me wonder how so many developers can manage the burden of GTKs horrible API design.
              Well, they are GIMP, and not KIMP or QIMP

              Comment


              • #8
                Originally posted by Hamish Wilson View Post
                Hoping to see this ship with Fedora 17.
                F17 already has a RC version of Gimp, 2.8 will probably be available as a day 0 update .

                Comment


                • #9
                  It's already in a ppa for ubuntu

                  Comment


                  • #10
                    hopeless

                    It's hopeless. Not that GIMP isn't useful cause it is but look at the roadmap. We'll get the useful features in 3.2 which will probably when hell REALLY freezes over.
                    Yeah I know what people will say: "If you want those features then get involved and code". Maybe more people would get involved in these open source projects when coders become less sloppy/lazy and learn how to document what the hell they're doing.

                    GIMP 3.0
                    Port to GTK3
                    High bit depths

                    GIMP 3.2
                    Automatic layer boundary management
                    Filter layers and "Layer effects"
                    Non-destructive editing

                    GIMP 3.4
                    Auto-anchoring of floating selection - or better, get rid of floating selections!

                    GIMP 3.6
                    Script recording and playback
                    "Smart objects"

                    GIMP 3.8
                    Unified transform tool
                    Last edited by linux5850; 05-03-2012, 08:39 PM. Reason: typos

                    Comment


                    • #11
                      the only way that open source projects don't suck balls is for people to donate rougly the same as they would for commercial apps. that means forking over at least 150 when using gimp. otherwise it's going to be the same old crap

                      Comment


                      • #12
                        Originally posted by RealNC View Post
                        IMO this is a good example of why Gtk is not suited for complicated stuff. It's good for simple things, but once you're doing something *really* non-trivial, it becomes a liability.
                        Except the delays have nothing to do with GTK+.

                        Comment


                        • #13
                          Originally posted by prokoudine View Post
                          Except the delays have nothing to do with GTK+.
                          Ach, what do you know? You only keep up with the development so you can let people know the status of GIMP and try and get more people involved (I believe this is the meaning of "news and community outreach").
                          These guys ARE Qt! If any other toolkit is perceived to be anything other than suckage, where would they be?

                          Comment


                          • #14
                            Originally posted by Linuxhippy View Post
                            Couldn't agree more. Having worked with higher-level UI toolkits like QT and Java/Swing it makes me wonder how so many developers can manage the burden of GTKs horrible API design.
                            Implying Qt or Java are any better, they just suck at different parts. For example in Qt they have the most idiotic message system ever, one that doesn't let you know the sender. Wtf were they smoking? That's about the second most important part in messaging, after the message contents themselves.

                            That makes the usual hello world in many toolkits require absurd workarounds in Qt, mainly a window with some buttons and actions, "you pressed button 1", "pressed button 2". That doesn't exactly instill confidence in Qt as a toolkit in general.


                            Haven't done a Java GUI in a few years (thank $DEITY) so I can't remember what sucked hard there, I just have some undescribable nightmares from that era.

                            Comment


                            • #15
                              Originally posted by Linuxhippy View Post
                              Couldn't agree more. Having worked with higher-level UI toolkits like QT and Java/Swing it makes me wonder how so many developers can manage the burden of GTKs horrible API design.
                              And the yet again completly screwed up their filechooser for GTK3 (and for fun, backported the changes to GTK2 - yeah!)

                              I didn't read up on the filechooser changes (instead hoped they would have done a good job) so what changes were made that screw their filechooser?

                              Comment

                              Working...
                              X