Announcement

Collapse
No announcement yet.

Enlightenment Wires In Wayland's Pointer Constraints & Relative Pointer Support

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

  • Enlightenment Wires In Wayland's Pointer Constraints & Relative Pointer Support

    Phoronix: Enlightenment Wires In Wayland's Pointer Constraints & Relative Pointer Support

    It's been a while since we last had anything to report on Enlightenment's Wayland compositor work, but that changed as we begin February...

    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
    But still no multimonitor support.

    And many bugs wrt to window management. So many apps open emty window frames etc.
    Wayland is far frm being really useful on Exx at the moment.

    Comment


    • #3
      Originally posted by Brane215 View Post
      But still no multimonitor support.

      And many bugs wrt to window management. So many apps open emty window frames etc.
      Wayland is far frm being really useful on Exx at the moment.
      Which apps open empty win frames?

      Comment


      • #4
        Firefox, Codeblocks, Codelite, MPLABX etc.


        I can't test this ATM, since E crashes with Wayland on start. I updated an existing ebuild per README in git-efl and switched afew options as it was suggested there, but now it doesn't start with "enlightenment_start". I don't have time for this now, will look into it later. I have a feeling this might have something to do with --enable-elput that I did have to add to efl's configure phase...


        Last edited by Brane215; 04 February 2017, 10:08 AM.

        Comment


        • #5
          you mean this is X11 apps emulated via xwayland in e? not wayland apps? as wayland apps work just fine for me. and xwayland emulation i have seen work with crhomium, xterm and xev without "empty frames" just fine on intel. driver may vary your result fyi.

          Comment


          • #6
            I use latest drm+radeon+mesa. Chromium works for me, but mousewheel scroll is insanely slow and there are perhaps a few other annoyances I can't remember ATM.
            mpv also works I think. It's without a frame IIRC, but that's probably not an Exx fault.

            Comment


            • #7
              no idea how well radeon works. but intel works very well. yes - mouse wheel is slow but i am not sure whose fault this is? xwayland? try actual wayland using apps (gtk3 apps will manage to do wayland) as opposed to x11 emulation. under weston chromium doesn't even work for me, but it does under enlightenment (on my rpi3). so try a machine with intel gfx first...

              Comment


              • #8
                Originally posted by Brane215 View Post
                Firefox, Codeblocks, Codelite, MPLABX etc.


                I can't test this ATM, since E crashes with Wayland on start. I updated an existing ebuild per README in git-efl and switched afew options as it was suggested there, but now it doesn't start with "enlightenment_start". I don't have time for this now, will look into it later. I have a feeling this might have something to do with --enable-elput that I did have to add to efl's configure phase...

                Test the same apps on weston and if they work there then there is a problem with E. File bugs and the devs will look into it.

                Also multimonitor is in the plans AFAIK.

                Comment


                • #9
                  Originally posted by raster View Post
                  no idea how well radeon works. but intel works very well. yes - mouse wheel is slow but i am not sure whose fault this is? xwayland? try actual wayland using apps (gtk3 apps will manage to do wayland) as opposed to x11 emulation. under weston chromium doesn't even work for me, but it does under enlightenment (on my rpi3). so try a machine with intel gfx first...
                  I doubt that slow mouse wheel is E's or XWayland's fault as I had that happen under Trinity on X11(!) as well (while it doesn't happen for on every other DE that I've tried on X or Wayland).

                  Comment


                  • #10
                    Well, a statement "I have a problem on Wayland" doesn't mean there is a problem with Wayland. The same for E. For lack of time, I am not capable provide some comparative tests for different wayland configuration, compositors and DEs. Under pure Weston with xwayland on Arch, my LXQT desktop starts and functions well enough despite of wrong lxpanel positioning far above of screen bottom edge...

                    Comment

                    Working...
                    X