Announcement

Collapse
No announcement yet.

GTK+ 3.89.4 Released With More Vulkan Work, Wayland Fixes

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

  • GTK+ 3.89.4 Released With More Vulkan Work, Wayland Fixes

    Phoronix: GTK+ 3.89.4 Released With More Vulkan Work, Wayland Fixes

    Matthias Clasen has issued the newest GTK4 development release with more feature work...

    http://www.phoronix.com/scan.php?pag....89.4-Released

  • #2
    Meanwhile GIMP, Inkscape and Chrome aren't even on GTK3 yet.

    Heard Chrome is going to default to GTK3 sometime after version 57 though.

    Comment


    • #3
      Originally posted by uid313 View Post
      Meanwhile GIMP, Inkscape and Chrome aren't even on GTK3 yet.

      Heard Chrome is going to default to GTK3 sometime after version 57 though.
      As Micheal has posted about before, they may wait until 4.0 is closer to release and skip directly to GTK4 due to GSK.

      But yes, they really should jump on gtk3, as 4.0 may take a while.

      Comment


      • #4
        Im now aware of any decent gtk app using opengl, so what's the point in vulkan renderer ?

        Comment


        • #5
          Originally posted by mir3x View Post
          Im now aware of any decent gtk app using opengl, so what's the point in vulkan renderer ?
          It's for 2D rendering of windows. Currently, most everything is rendered on the CPU. With GTK4 and the GSK, it will be rendered on the GPU. It's one of big reasons why the GNOME experience isn't as smooth as it could be.

          Comment


          • #6
            Originally posted by Mystro256 View Post

            As Micheal has posted about before, they may wait until 4.0 is closer to release and skip directly to GTK4 due to GSK.

            But yes, they really should jump on gtk3, as 4.0 may take a while.
            Would GSK even matter to Chrome? I thought Gtk was just used for things like window creation and dialogs and nothing to do with rendering for which they use Skia.

            EDIT: Oh you meant GIMP. Yea that could make sense.
            Last edited by TingPing; 02-14-2017, 04:21 PM.

            Comment


            • #7
              Originally posted by mmstick View Post

              It's for 2D rendering of windows. Currently, most everything is rendered on the CPU. With GTK4 and the GSK, it will be rendered on the GPU. It's one of big reasons why the GNOME experience isn't as smooth as it could be.
              I've been curious about this for awhile, so i did a bit of reading in the GNOME gtk repo.

              Currently "Clutter" uses the gpu once the windows have been uploaded as textures.
              From what i can tell if gsk, cairo will still be responsible for creating and drawing window contents. Some operations, however, look to be handled by the gpu (clipping, blending, handling gradients, blits, etc).
              What remains to be done, afaict, is to create an efficient gpu targeted vector library (it would obviously need to do perform rasterization as well).

              Comment


              • #8
                Originally posted by uid313 View Post
                Meanwhile GIMP, Inkscape and Chrome aren't even on GTK3 yet.

                Heard Chrome is going to default to GTK3 sometime after version 57 though.
                GIMP has already confirmed that they're going to GTK4. Not sure why Chrome would go to GTK3 at this very last moment while GTK4 is making so much progress and Chrome is hardly using any GTK code even. They might as well stick it out with GTK2 and jump straight to 4 once it hits stable.

                Comment


                • #9
                  Originally posted by Vistaus View Post

                  GIMP has already confirmed that they're going to GTK4. Not sure why Chrome would go to GTK3 at this very last moment while GTK4 is making so much progress and Chrome is hardly using any GTK code even. They might as well stick it out with GTK2 and jump straight to 4 once it hits stable.
                  Chrome already has GTK3 code but it just isn't enabled by default.
                  I read that it will be enabled by default "sometime after version 57". Current version is 56.

                  Comment

                  Working...
                  X