Announcement

Collapse
No announcement yet.

Following Mir 1.0, Developers Encouraged To Target Wayland Instead Of Mir Client API

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

  • #11
    Originally posted by Aleksei View Post
    So Mir turned into just another Wayland compositor? Or is there more to it?
    Yeah, but it should be noted that desktop-grade wayland compositors aren't so common, so far there is only GNOME's Mutter and KDE's Kwin, plus maybe some other obscure DE using Qt's wayland compositor.



    Comment


    • #12
      Originally posted by SpyroRyder View Post

      "You keep using vaporware. I do not think it means what you think it means"
      We get it, he vapes.

      Comment


      • #13
        Originally posted by starshipeleven View Post
        Yeah, but it should be noted that desktop-grade wayland compositors aren't so common, so far there is only GNOME's Mutter and KDE's Kwin, plus maybe some other obscure DE using Qt's wayland compositor.
        Also Sway is in alpha. Not quite as drop-in of an i3 replacement as its description claims (I had to modify config file a lot when trying sway 0.15), but still.
        Last edited by Aleksei; 30 September 2018, 01:54 AM.

        Comment


        • #14
          Originally posted by GunpowaderGuy View Post
          dragon321 also , even if there was some edge case where utilizing the mir protocol would be truly beneficial . it would not mean a whole section of a forum should be dedicated to it
          Following news, writing shell for Mir require using Mir API.
          Last edited by dragon321; 30 September 2018, 01:42 PM.

          Comment

          Working...
          X