Slashdot Mirror


Xfce, LXDE, GNOME3 Desktops Running On Ubuntu Mir Via XMir

An anonymous reader writes "Through the use of XMir, a translation layer for running legacy X11 applications atop Ubuntu's forthcoming Mir display server, the GNOME Shell, Xfce, and LXDE desktops now run on this X.Org Server alternative. With XMir, the traditional window managers are still running while Mir treats these desktops as a single window."

7 of 162 comments (clear)

  1. Re:Hello by Anonymous Coward · · Score: 5, Insightful

    Thousands of distros, tens of DE's and WM's, lots of different graphical toolkits, tons of libraries with significant overlapping functions, tons of system utils that do similar things, 6 or 7 common http servers, but TWO graphics servers? FRAGMENTATION! It's all gonna fly apart!

    You dumbass.

  2. Re:Multiple Displays? by Blaskowicz · · Score: 4, Insightful

    Each running separate X sessions and unable to move a window from one display to another? That is what I got the day I tried a second graphics card in my PC to connect a second monitor.
    The OS was an Ubuntu version released long after Windows 7 and it still expected me to write some xinerama xorg.conf bullshit, which would have probably ended with maximized windows covering both displays and modal windows appearing right in the middle, on both sides of the physical divide. But I think I would have had to give up running the nvidia driver. LOL!

    Sad thing is Windows 98 SE happily ran multiple monitors on different graphics cards (different card, different driver, different vendor).

  3. Re:FOSS overload by Anonymous Coward · · Score: 2, Insightful

    You understood it. Nowhere in the title or summary does it say anything about FOSS.

  4. Re:Hello by jedidiah · · Score: 4, Insightful

    ...except X.org is just another Xserver. It's not an entirely new protocol. This is why X servers and clients from a variety of Unixen and non-Unixen can all talk to each other.

    It's like HTTP.

    Mir is more like Microsoft trying to create it's own web browser protocol.

    You should really follow your own advice.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  5. Re:Hello by gmuslera · · Score: 3, Insightful

    The story is specifically about avoiding fragmentation, adding compatibility layers, so even if you don't develop for Mir it will run there. Maybe you meant goodbye fragmentation?

  6. Re:Hello by Bengie · · Score: 4, Insightful

    Except Wayland is being developed by 15 year X devs that understand windowing systems, and engineers. Mir is being developed by developers.

    what was that saying about developers and engineers. Windows was written by developers, Unix was designed by engineers?

  7. Re:Hello by raxx7 · · Score: 3, Insightful

    Err, no.
    DRI get X out of the way a lot, but there still areas for improvement.

    Besides using DRI for rendering (or doing it client side), once done rendering a frame, the X client needs to notify the X server so it can notify the X window manager so it can do it's job and notify the X server again so the frame can actually finally show up on screen on the correct place.
    And while in theory an X server could do this very quickly and efficienty, the real X.org server is quite slow.

    Clients also need to talk to the X server over other things like object property manipulation.
    Once more, in theory an X server could handle this quickly and efficiently, the real X.org server is quite slow.

    (And full screen does help, as there's less of this going on).

    All in all, Wayland won't get you higher frame rates in Portal. But it will make your desktop smoother, with less CPU/GPU usage.