• Trigg@lemmy.world
    link
    fedilink
    English
    arrow-up
    94
    arrow-down
    5
    ·
    2 days ago

    Ah yes, API abuse. Which is when you use the API as intended and written.

    Gnome devs are completely out of touch.

    • neclimdul@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      3
      ·
      2 days ago

      if its internal, as they said, its not as intended? as the described it, its designed for compositors. which implies, an application using it could lead to conflicting behaviors with the compositor and WM.

      This is probably why they’re like “we cant support that” because it’d conflict with what mutter is doing.

      doesn’t make it any less a mess but the GNOME devs probably have a point.

      • Trigg@lemmy.world
        link
        fedilink
        English
        arrow-up
        36
        arrow-down
        1
        ·
        2 days ago

        https://wayland.app/protocols/wlr-layer-shell-unstable-v1

        This interface should be suitable for the implementation of many desktop shell components, and a broad number of other applications that interact with the desktop

        Suitable. Not strictly, and certainly not private. Everyone else, KDE included, have managed to make this work fine.

        I might add that I’m quite well aquianted with this protocol as it comes up in a lot of projects I’m involved with.

        • WhyJiffie@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          5
          ·
          18 hours ago

          Suitable. Not strictly, and certainly not private. Everyone else, KDE included, have managed to make this work fine.

          as others have mentioned, KDE implemented it but also opposes it, because any apps could abuse it without permission control

        • WhyJiffie@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          18 hours ago

          Suitable. Not strictly, and certainly not private. Everyone else, KDE included, have managed to make this work fine.

          as others have mentioned, KDE implemented it but also opposes it, because any apps could abuse it without permission control