Announcement

Collapse
No announcement yet.

Casilda Is A New Project As A GTK4 Wayland Compositor Widget

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

  • Casilda Is A New Project As A GTK4 Wayland Compositor Widget

    Phoronix: Casilda Is A New Project As A GTK4 Wayland Compositor Widget

    Casilda is a new open-source project by GNOME developer Juan Pablo Ugarte to serve as a Wayland compositor widget. Casilda allows for embedding other processes windows within a GTK4 application...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    God, Wayland sucks. How sad that you need to run a whole extra compositor just to some of the functionality of XEmbed? Yes, only some, because who knows which of the dozen "optional" protocols they'll implement?

    16 years of this Wayland crap being pushed onto everyone and it's still not good enough.
    Last edited by mxan; 14 September 2024, 08:10 AM.

    Comment


    • #3
      It's not sad, it's designed in that way and always was. Things like gamescope did it before and its working alright. It just seems there was no big need earlier on for this particular usecase.

      Comment


      • #4
        Originally posted by Hibbelharry View Post
        It just seems there was no big need earlier on for this particular usecase.
        Indeed. Because the industry is happy using X11 for every usecase (in this particular case, XEmbed).

        Early adopters of Wayland, who are typically hobbyists tend to not need this to i.e play their Steam DRM platform games on their home PC.

        Originally posted by mxan View Post
        16 years of this Wayland crap being pushed onto everyone and it's still not good enough.
        ​I think it is quite funny when people try to claim that Wayland is already a suitable replacement for X11 when even this basic stuff is missing.

        (Plus, Wayland *still* won't have a standardized embed protocol. This is a GTK specific hack).
        Last edited by kpedersen; 14 September 2024, 08:45 AM.

        Comment


        • #5
          Nested compositors are a great approach!

          They allow application developers to separate things into processes while still keeping full control on how to display the processes' rendering, which events to forward or inject, etc.

          Essentially enabling every app developer to do things browser have been doing for quite a while now.

          I think Qt has had something similar via its QtWaylandCompositor module since Qt5.

          Comment


          • #6
            I think cosmic is doing something similar for their widgets?

            Comment


            • #7
              Not the first one of these. There's also this library associated with XFCE: https://gitlab.xfce.org/kelnos/libwlembed

              It's funny calling this a hack and while championing XEmbed. This is far cleaner and actually integrates properly into wherever you're embedding it. Just because you can do it in X11 doesn't mean that you should. w3m can draw images on your terminal, but it shouldn't even have the right to draw on the window of another process. Naturally, it is broken on several terminals.

              Comment


              • #8
                Originally posted by kpedersen View Post

                Indeed. Because the industry is happy using X11 for every usecase (in this particular case, XEmbed).

                Early adopters of Wayland, who are typically hobbyists tend to not need this to i.e play their Steam DRM platform games on their home PC.



                ​I think it is quite funny when people try to claim that Wayland is already a suitable replacement for X11 when even this basic stuff is missing.

                (Plus, Wayland *still* won't have a standardized embed protocol. This is a GTK specific hack).
                Yeh, that's why X11 has been popular in the embedded and mobile industry, and it's not as if those industries had to make alternatives because X11 certainly met their use cases.

                Comment


                • #9
                  Originally posted by kpedersen View Post
                  This is a GTK specific hack
                  The widget is GTK specific, i.e. the way the client contents are integrated into the host's content.

                  The communication between clients and host is the standard Wayland protocol stack.

                  Any Wayland client, using any toolkit, can have any number of windows embedded that way without any change to their code.

                  The widget, or the users of the widget, could of course support additional means of communication if that helps their use case

                  Comment


                  • #10
                    Originally posted by kpedersen View Post
                    Indeed. Because the industry is happy using X11 for every usecase (in this particular case, XEmbed).
                    Early adopters of Wayland, who are typically hobbyists tend to not need this to i.e play their Steam DRM platform games on their home PC.
                    Yip, except wrong. The 'industry' offers a lot of wayland usage and application. It's more the hobbyist cloud of old and grumpy 'experts' not able to accept any progress and sticking to X11.

                    Some usecases, just examples. I picked some embedded application references here just not to cite any desktop computing technology.


                    i.MX Graphics Wayland Compositor. Contribute to nxp-imx/weston-imx development by creating an account on GitHub.




                    Comment

                    Working...
                    X