Announcement

Collapse
No announcement yet.

Kodi's Wayland Support Was Successfully Revived With GSoC 2017

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

  • Kodi's Wayland Support Was Successfully Revived With GSoC 2017

    Phoronix: Kodi's Wayland Support Was Successfully Revived With GSoC 2017

    The Kodi HTPC/multimedia software has revamped support for Wayland as an alternative to the X.Org Server on Linux thanks to Google Summer of Code developer Philipp Kerling...

    http://www.phoronix.com/scan.php?pag...land-GSoC-2017

  • #2
    From the WindowDecorator.h:
    "To keep the impact on the overall architecture low, the Wayland platform implementation uses this very simple renderer to build ugly but fully functional decorations around the Kodi window."

    So I will do the same for Supertuxkart - simple subsurface that allows to move and close a window. And we will have ugly but functional decorations everywhere. MPV doesn't have decorations at all.

    Wayland is great in general to handle window creation, input events etc., but client-side decorations is just PITA...

    Comment


    • #3
      Very nice, I hoped somebody would revive Wayland support in Kodi... another important step.

      Comment


      • #4
        Originally posted by deve View Post
        client-side decorations is just PITA...
        every gtk app has working csd. because guess what? they are using shared library to draw them

        Comment


        • #5
          Originally posted by pal666 View Post
          every gtk app has working csd. because guess what? they are using shared library to draw them
          Depending on gtk just for window decorations on wayland doesn't sound like the best idea for stuff like mpv or supertuxkart.

          Comment


          • #6
            Originally posted by pal666 View Post
            every gtk app has working csd.
            But not everything is a gtk app...

            Wayland *needs* a SSD protocol, a uniform way implemented in all compositors that automatically provides decorations for all applications that don't draw decorations themselves.

            Comment


            • #7
              Originally posted by Masush5 View Post

              Depending on gtk just for window decorations on wayland doesn't sound like the best idea for stuff like mpv or supertuxkart.
              ...but maybe they can come together and do their own light-csd-library so they do not have to rely on gtk/qt/any other bigger project, and still do not have to reinvent the wheel themselves...
              Maybe, just maybe they will find others that want to support wayland, do not want to use more mature but larger toolkits, but a light just-csd-toolkit , that they can work together with?

              Comment


              • #8
                Originally posted by GhostOfFunkS View Post
                No. If you want something like that just stay on X.
                That's a great attitude to get people to adopt your technology, I must say...

                Comment


                • #9
                  Originally posted by Xake View Post
                  ...but maybe they can come together and do their own light-csd-library so they do not have to rely on gtk/qt/any other bigger project, and still do not have to reinvent the wheel themselves...
                  Maybe, just maybe they will find others that want to support wayland, do not want to use more mature but larger toolkits, but a light just-csd-toolkit , that they can work together with?
                  That's still far from ideal. One, it's still an external dependency that your app needs to handle. And two, the decorations provided by this little library would not integrate into the environment (unless the library had hooks for every compositor out there, but that would be a maintenance nightmare and possibly wouldn't fit into a library that intends to be light).

                  But if the environment provides SSD, it knows exactly how the decoration should look like and most importantly, how it should function - placement of elements such as minimize/maximize/close, context menu providing various functions and other such stuff.

                  Comment


                  • #10
                    You guys clearly don't know what you're talking about. There is only one way to do things and that's the way The Standard Linux Desktop's devs want it to be. Supporting the stack and working together with everyone else is obviously the wrong way to do things and not required since Gnome=Standard and everything else is just a toy/playground thing. If you want something different in Gnome just send a PR and we'll drop it cause it's not our thing, but hey, you did the right thing

                    Originally posted by GhostOfFunkS View Post

                    No. If you want something like that just stay on X.
                    I came here for this very reply. I was not let down.

                    In all honesty you're making this too easy. It's getting to the point where completely replacing you with a bot would require but a few well-documented steps:
                    1. Mention how CSD is fine while SSD is useless and a thing of the past
                    2. Praise ~~Gnome~~ The Standard Linux Desktop
                    3. *Insert Generic Illogical Copypasta here*
                    4. Possibly acuse people of being clueless about the situation indirectly
                    5. Praise "The Standard Desktop" again. (Optional as of 12.3.1b)
                    6. Refresh Phoronix
                    7. Locate all articles with a title containing any or all of the following keywords: Wayland, Gnome, Desktop, Qt, Gtk, XFCE (aka good gtk guys doing things the wrong way), Sway, KDE
                    8. Fork yourself and go to (1) for all targets







                    Comment

                    Working...
                    X