Announcement

Collapse
No announcement yet.

GNOME2-Forked MATE Desktop Is Being Ported To Wayland

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

  • GNOME2-Forked MATE Desktop Is Being Ported To Wayland

    Phoronix: GNOME2-Forked MATE Desktop Is Being Ported To Wayland

    MATE Desktop, the well known fork of the GNOME 2 desktop environment, is in the process of being ported to Wayland...

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

  • #2
    Does it mean that GTK2 is also being ported to wayland?

    I wonder how they will solve in Wayland the lack of am out of process nesting system equivalent to XEmbed, that a lot of older applications use.
    Last edited by newwen; 02-17-2014, 04:03 AM.

    Comment


    • #3
      Originally posted by newwen View Post
      Does it mean that GTK2 is also being ported to wayland?

      I wonder how they will solve in Wayland the lack of am out of process nesting system equivalent to XEmbed, that a lot of older applications use.
      It looks like MATE supports (or will support) GTK3:
      http://wiki.mate-desktop.org/status:gtk3

      As for XEmbed, that's the goal of the mailing post. The developer has proposed a solution, and is asking feedback about it to others devs.

      Comment


      • #4
        He should use the nested mini compositor approach, as suggested by Pekka:

        the conclusion was [referring to a previous discussion] to use a nested mini-compositor approach
        instead, which is demoed in weston clients as weston-nested.per weston


        We will see what will be the final solution.

        Comment


        • #5
          Originally posted by valeriodean View Post
          He should use the nested mini compositor approach, as suggested by Pekka:

          the conclusion was [referring to a previous discussion] to use a nested mini-compositor approach
          instead, which is demoed in weston clients as weston-nested.per weston


          We will see what will be the final solution.
          How does this differes from nested XWindows approach of Xorg where everything is nested window?
          Wasn't the simple planar surface per application one of the reason for Wayland development in the first place?

          Comment


          • #6
            Originally posted by brosis View Post
            How does this differes from nested XWindows approach of Xorg where everything is nested window?
            Wasn't the simple planar surface per application one of the reason for Wayland development in the first place?
            for once i have the same opinion as brosis

            Comment


            • #7
              Canonical's trying to break Wayland

              To bad Canonical is trying to Break Wayland support in Debian


              Which says right in that blog entry that:

              We’ll certainly complete work to make the new logind work without systemd
              as pid 1.

              Even supposing that GetUserByPID is critical for jessie, and even supposing
              that Canonical did not finish the work to make logind work with cgmanager,
              backporting this one interface to logind 204 will be trivial. There is no
              excuse at all for Debian getting the compatibility wrong in jessie. (But an
              awful lot of people who seem eager to make excuses for it.

              --
              Steve Langasek
              https://lists.debian.org/debian-ctte.../msg00500.html


              Nevertheless, the decision is for systemd, and given that Ubuntu is quite centrally a member of the Debian family, that’s a decision we support. I will ask members of the Ubuntu community to help to implement this decision efficiently, bringing systemd into both Debian and Ubuntu safely and expeditiously. It will no doubt take time to achieve the stability and coverage that we enjoy today and in 14.04 LTS with Upstart, but I will ask the Ubuntu tech board (many of whom do not work for Canonical) to review the position and map out appropriate transition plans. We’ll certainly complete work to make the new logind work without systemd as pid 1. I expect they will want to bring systemd into Ubuntu as an option for developers as soon as it is reliably available in Debian, and as our default as soon as it offers a credible quality of service to match the existing init.
              http://www.markshuttleworth.com/archives/1316

              Comment


              • #8
                Originally posted by Attentäter View Post
                To bad Canonical is trying to Break Wayland support in Debian
                Uhm... no? The quotes are from systemd (and logind without systemd as PID 1), not about Wayland nor Canonical trying anything...?

                Comment


                • #9
                  Originally posted by brosis View Post
                  How does this differes from nested XWindows approach of Xorg where everything is nested window?
                  Wasn't the simple planar surface per application one of the reason for Wayland development in the first place?
                  That is just one proposed approach.
                  About the second question: no, there are many reasons.
                  If you read the problem exposed in the mailing list, you will recognize why that case is not a "simple planar surface per application" problem.

                  Comment


                  • #10
                    Originally posted by valeriodean View Post
                    He should use the nested mini compositor approach, as suggested by Pekka:

                    the conclusion was [referring to a previous discussion] to use a nested mini-compositor approach
                    instead, which is demoed in weston clients as weston-nested.per weston


                    We will see what will be the final solution.
                    Reading through the list, I've seen the "wl_foreign_surface_manager" interface, but that protocol is missing an standarized IPC to communicate resizing requests for those exported/foreign subsurfaces, which is IMHO, essential.

                    Comment

                    Working...
                    X