Announcement

Collapse
No announcement yet.

Lubuntu Planning Switch To Wayland, Porting Openbox To Mir

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

  • Lubuntu Planning Switch To Wayland, Porting Openbox To Mir

    Phoronix: Lubuntu Planning Switch To Wayland, Porting Openbox To Mir

    Ubuntu derivative Lubuntu that is now using the LXQt desktop environment has laid out more of their plans to switch over to Wayland rather than the existing X.Org based session...

    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
    Aren't there several Qt tool chains for Wayland now?
    why mir?

    Comment


    • #3
      Amazing news. It is possible I switch to this distro again.

      Comment


      • #4
        Originally posted by phoronix View Post
        Ubuntu derivative Lubuntu that is now using the LXQt desktop environment
        It doesn't. Latest official Lubuntu release is using LXDE.

        Comment


        • #5
          Originally posted by pracedru View Post
          Aren't there several Qt tool chains for Wayland now?
          why mir?
          wayland regards with the protocol while MIR regards with the compositor so that wayland matches with mir.

          Comment


          • #6
            Originally posted by Azrael5 View Post

            wayland regards with the protocol while MIR regards with the compositor so that wayland matches with mir.
            I think he wanted to talk about Qt Wayland Compositor which is the Qt Wayland implementation for a Qt QML compositor.
            Mir seems to have its way to go, Qt Wayland Compositor allows more flexibility (I think... but someone experimenting with one or another can confirm ?)

            Comment


            • #7
              However 2 years before to implement it is too long time.

              Comment


              • #8
                Originally posted by Azrael5 View Post
                However 2 years before to implement it is too long time.
                Why? X.Org isn't running away and Wayland will have matured further by then. Then can take 4 years for all I care.

                Comment


                • #9
                  OpenBox is not a complex piece of software. Two years to implement / port suggests something else is at fault. I am assuming an immature API / Wayland is to blame.

                  Originally posted by WolfpackN64 View Post
                  Then can take 4 years for all I care.
                  That's too long. Wayland will have disappeared by then haha .

                  Comment


                  • #10
                    Originally posted by kpedersen View Post
                    OpenBox is not a complex piece of software. Two years to implement / port suggests something else is at fault. I am assuming an immature API / Wayland is to blame.
                    Lack of developer time perhaps?

                    Comment

                    Working...
                    X