Announcement

Collapse
No announcement yet.

GTK+ Support Merged For Wayland CSD

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

  • GTK+ Support Merged For Wayland CSD

    Phoronix: GTK+ Support Merged For Wayland CSD

    For a fair amount of time now there's been work on client side decorations for Wayland so that the Weston compositor with GTK+ can do the window decorations on the client-side rather than server-side as done with the X.Org Server. That work has now been merged to master...

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

  • #2
    Why wayland needs CSD? I don't see point of CSD at all

    Comment


    • #3
      Originally posted by nslqqq View Post
      Why wayland needs CSD? I don't see point of CSD at all
      Wayland actually supports either, the compositor chooses Client or Server side decorations. (They can even do a hybrid approach where the user chooses--thats what Kwin is gonna do) so apparently the gnome guys wants to have the user decide as well, so they need to merge in both server and client side decorations.

      Comment


      • #4
        Just fyi Michael, this should allow GTK apps to use client-side decorations on any Wayland compositor, not just Weston.

        Comment


        • #5
          The good thing about Mir is that competition is stirring up wayland development and we could say goodbye to Xorg sooner than we think. Specially if Nvidia and Amd provide us with EGL platform drivers.

          Comment


          • #6
            Why not a common decoration library?

            Why not have a library called libdecoration that is used by GTK+, Qt, Clutter, EFL, FLTK, Tk, etc.

            Then all widget toolkits will re-use and share the same code for decorations.
            Then all applications will have the same decorations, instead of GTK+ and Qt and others have application windows with different looking decorators.

            We need a common unified well-integrated look-and-feel.

            Comment


            • #7
              Originally posted by uid313 View Post
              Why not have a library called libdecoration that is used by GTK+, Qt, Clutter, EFL, FLTK, Tk, etc.

              Then all widget toolkits will re-use and share the same code for decorations.
              Then all applications will have the same decorations, instead of GTK+ and Qt and others have application windows with different looking decorators.

              We need a common unified well-integrated look-and-feel.
              Well, Qt already has decoration support (so they can run on windows, for example) so it's probably not going to be easy to get them to throw that away and use some new libdecoration library that Gnome writes. And it's probably going to be even more difficult to get them to write it, since they already have support working for themselves.

              Comment


              • #8
                Originally posted by smitty3268 View Post
                Well, Qt already has decoration support (so they can run on windows, for example) so it's probably not going to be easy to get them to throw that away and use some new libdecoration library that Gnome writes. And it's probably going to be even more difficult to get them to write it, since they already have support working for themselves.
                On Windows they ought to re-use the native window decorators.

                Comment


                • #9
                  Originally posted by uid313 View Post
                  Why not have a library called libdecoration that is used by GTK+, Qt, Clutter, EFL, FLTK, Tk, etc.

                  Then all widget toolkits will re-use and share the same code for decorations.
                  Then all applications will have the same decorations, instead of GTK+ and Qt and others have application windows with different looking decorators.

                  We need a common unified well-integrated look-and-feel.
                  That's a great idea! Can we have a link to your repo with the initial code?
                  I'd be interested to see how you implemented this library.

                  Comment


                  • #10
                    Originally posted by newwen View Post
                    The good thing about Mir is that competition is stirring up wayland development and we could say goodbye to Xorg sooner than we think. Specially if Nvidia and Amd provide us with EGL platform drivers.
                    Say goodbye to Xorg and hello to driver wars as the blob vendors will now have to support two instead of one platform.

                    Mir is basically the same as Wayland, which Mir developers admitted themselves.
                    The only difference is the shell implementation, and the fact that Canonical has full control over the project.

                    Comment

                    Working...
                    X