Announcement

Collapse
No announcement yet.

Wayland Live CD Updated Against Wayland/Weston 1.8

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

  • Wayland Live CD Updated Against Wayland/Weston 1.8

    Phoronix: Wayland Live CD Updated Against Wayland/Weston 1.8

    The reference Wayland Live CD with various Wayland software components enabled has been updated against Wayland/Weston 1.8 and other new code...

    http://www.phoronix.com/scan.php?pag...ck-Wayland-1.8

  • #2
    Originally posted by Master5000 View Post
    In about 20 years Wayland will replace X.org.... While Mir is already here. Mir won. They should focus their resouces on Mir not on Wayland.
    Come back to me with an actual Mir Live session with actual apps and demos without any Xorg dependency and we'll talk

    Comment


    • #3
      Originally posted by Master5000 View Post
      In about 20 years Wayland will replace X.org.... While Mir is already here. Mir won. They should focus their resouces on Mir not on Wayland.
      Windows is more popular than every other desktop OS combined. Windows won, so we should just focus on Windows and nothing else. Right?

      Comment


      • #4
        Originally posted by Master5000 View Post
        In about 20 years Wayland will replace X.org.... While Mir is already here. Mir won. They should focus their resouces on Mir not on Wayland.
        Mir is like windows 8/10, oriented at touch screen devices. Wayland is for desktop linux.

        Comment


        • #5
          Developers have to replace x11 by wayland quicker than possible. They have to force this replacement at cost to make incompatible many applications setting a timeline after it any incompatible applications will be declared DEPRECATED. Linux systems lost because developers are not structured as an enterprise criteria by internal organization. They think that opensource lies outside organization of activities.
          suggestions: PULSE AUDIO... it has to implement hardware acceleration so to free cpu from usage.

          Comment


          • #6
            Originally posted by Master5000 View Post
            In about 20 years Wayland will replace X.org.... While Mir is already here. Mir won. They should focus their resouces on Mir not on Wayland.
            Ha, good joke. It has taken quite a long time. But just in case you were serious:

            Mir is based on the graphics stack and (possibly) soon the input stack created for Wayland. This stack involved a few years of work in Mesa, the graphics drivers, and the kernel. Before, everything was tied into X.org without a way to have an alternative display server. The people who maintain the X.org code created this base of Wayland and Mir. The difference between Wayland and Mir is Wayland is a protocol to maintain compatibility between desktop projects. Even though Gnome and KDE will be creating their own display servers, apps will work under any Wayland-comptaible display server (KWin, Mutter, etc.) Whereas, Canonical is stuck maintaining a backend for every toolkit for their display server, even though both Mir and Wayland-based projects use the same drivers. Plus, in less than three months you can run a KDE Plasma session and Gnome Shell session under Wayland (unless you are running the Nvidia closed-source driver).

            Comment


            • #7
              Originally posted by CTown View Post
              Mir is based on the graphics stack and (possibly) soon the input stack created for Wayland.
              the graphics stack the way it is now was developed by embedded ppl for embedded things
              wayland wasnt even started then

              Comment


              • #8
                Originally posted by Master5000 View Post
                In about 20 years Wayland will replace X.org.... While Mir is already here. Mir won. They should focus their resouces on Mir not on Wayland.
                Die, Boss troll! Die!

                Comment


                • #9
                  Someone tried the new Rebecca Os ?

                  Comment


                  • #10
                    I'm all for Wayland, and the core protocol may be complete, but xdg_shell's and pointer lock protocol's development speed is somewhat disappointing. Pointer lock is mainly needed for games, a Wayland client currently can't grab the cursor, so first person games are unplayable under Wayland. The protocol is almost ready, but they're sitting on it for several months now, come on...
                    I understand that they don't want to publish a poorly designed interface, but they already did it with wl_shell, which is part of the core protocol, but incomplete and frozen. Instead we have xdg_shell, which isn't part of core Wayland (if you want to use it, you have to generate the bindings for it, eh) and also incomplete. The biggest flaw of it is that there's no way for a client to request server-side decoration. It's not a problem for Gtk/Qt applications, but for SDL/GLUT/GLFW/SFML/etc. games it is, because you'll have no titlebar, no window edges. And trust me, SDL/GLFW/etc. devs won't include thousands of lines for drawing window decorations just for Wayland. There were a lengthy discussion about this on the mailing list, but the 4-5 participating people had 4-5 different opinion on it, and they were overcomplicating the whole story. The saddest thing is, the main reason for requiring client-side decoration was that Gnome people doesn't want to maintain the server-side decoration code in Mutter, the compositor. Btw. I'm using Gnome 3 and love it, but this attitude is disappointing.

                    Comment

                    Working...
                    X