Results 1 to 7 of 7

Thread: What It Takes To Write A Wayland Compositor

  1. #1
    Join Date
    Jan 2007
    Posts
    13,424

    Default What It Takes To Write A Wayland Compositor

    Phoronix: What It Takes To Write A Wayland Compositor

    For those curious about what it takes to write a standalone Wayland compositor and the challenges involved, two Enlightenment developers have shared their struggles and accomplishments in making Enlightenment a Wayland compositor...

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

  2. #2
    Join Date
    May 2012
    Posts
    348

    Default

    enlightenment crew
    doing things right since... a long time ago

  3. #3
    Join Date
    Jan 2009
    Posts
    1,518

    Default

    E will need WL 1.5 to be everyday usable right??

  4. #4
    Join Date
    Jan 2012
    Posts
    18

    Default

    Quote Originally Posted by 89c51 View Post
    E will need WL 1.5 to be everyday usable right??
    Currently it requires >= 1.3.0 But (more than likely) will (eventually) need 1.5 in order to support the xdg-shell protocol although the current EFL wayland stuff just needs 1.3.0

  5. #5
    Join Date
    Jan 2009
    Posts
    1,518

    Default

    Quote Originally Posted by devilhorns View Post
    Currently it requires >= 1.3.0 But (more than likely) will (eventually) need 1.5 in order to support the xdg-shell protocol although the current EFL wayland stuff just needs 1.3.0
    I should have worded it a bit differently and ask if the xdg_shell will make it everyday usable. Assuming this goes into WL1.5.

  6. #6
    Join Date
    Dec 2012
    Posts
    178

    Default

    The input library for wayland is an important component to be also be standardized, so that every wayland-based desktop compositor handles input the same way.

    BTW, does drag-and-drop currently work well in wayland, even among different toolkits or is this something well defined by the Wyaland protocol?

  7. #7
    Join Date
    Dec 2012
    Posts
    136

    Default

    xdg_shell is still beeing designed, but it should be very cool.

    You can see current proposition here: https://github.com/magcius/weston/bl.../xdg-shell.xml

    For example you can give an app id to the surface, and I was said the app id can be used to get the right icon, etc (something that was missing before).

    As for input, the protocol has been designed long ago now, and works well. The only bit missing I aware of, is pointer lock (used for example in fps games so that the mouse doesn't block when the pointer hits the borders of the screen).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •