<story><title>Improving cursor rendering on Wayland</title><url>https://blog.vaxry.net/articles/2024-cursors</url></story><parent_chain></parent_chain><comment><author>thayne</author><text>Some suggestions for improving adoption of this:&lt;p&gt;1. Don&amp;#x27;t have a dependency on hyprlang. Other projects will probably be averse to that. Use a more common configuration language, using a common library.&lt;p&gt;2. Have a shim layer so that hyprcursor cursors can be used by applications that use the XCursor API (maybe have a drop in replacement library for libxcursor that delegates to hyprcursor).&lt;p&gt;3. Have a specification so other implementations can use the cursor format as well, in case other compositors&amp;#x2F;clients don&amp;#x27;t like your implementation for some reason.</text></comment>
<story><title>Improving cursor rendering on Wayland</title><url>https://blog.vaxry.net/articles/2024-cursors</url></story><parent_chain></parent_chain><comment><author>saurik</author><text>The article essentially says--whether this is a good idea or not--that GTK is the one hold-out, which I wasn&amp;#x27;t really expecting as a punchline; why is GTK not implementing this?</text></comment>