New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] xcursor-configuration: initial protocol implementation #1324

Open
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
4 participants
@emersion
Copy link
Member

emersion commented Oct 21, 2018

  • Consider adding fallback seat and device type configurations (but how to handle adding configuration after a resource has been added to the fallback?)
@ddevault

This comment has been minimized.

Copy link
Member

ddevault commented Oct 21, 2018

Did I miss this protocol going under discussion in wlr-protocols?

@emersion

This comment has been minimized.

Copy link
Member

emersion commented Oct 21, 2018

This is a candidate for wayland-protocols, so it's in review on the wayland-devel mailing list: https://patchwork.freedesktop.org/series/50948/

Related is the RFC for the libwayland-cursor API update: https://patchwork.freedesktop.org/series/51203/

@emersion

This comment has been minimized.

Copy link
Member

emersion commented Oct 21, 2018

Also relevant: initial discussion about this protocol: https://lists.freedesktop.org/archives/wayland-devel/2018-October/039515.html

@emersion emersion force-pushed the emersion:xcursor-configuration branch from 7e8d1b1 to 57e8d2b Oct 22, 2018

@emersion

This comment has been minimized.

Copy link
Member

emersion commented Oct 22, 2018

Posted a full libwayland-cursor patch here: https://patchwork.freedesktop.org/series/51322/

@ddevault

This comment has been minimized.

Copy link
Member

ddevault commented Oct 22, 2018

Nice, looking good.

@dvc94ch

This comment has been minimized.

Copy link

dvc94ch commented Dec 9, 2018

Is this going anywhere? There doesn't seem to be much activity on the protocol and libwayland-cursor side.

@ddevault

This comment has been minimized.

Copy link
Member

ddevault commented Dec 9, 2018

Could stand to bump it and Cc some interested parties

@emersion

This comment has been minimized.

Copy link
Member

emersion commented Dec 9, 2018

I bumped the protocol something like a week ago. It seems that Qt have a WIP implementation.

@dvc94ch

This comment has been minimized.

Copy link

dvc94ch commented Dec 10, 2018

Can we add this to wlr-protocols for now? It would be nice to have support in wl-roots/sway so that I have a testing ground for implementing it in smithay-client-toolkit.

@dvc94ch dvc94ch referenced this pull request Dec 10, 2018

Closed

Cursor scaling #52

@emersion

This comment has been minimized.

Copy link
Member

emersion commented Dec 10, 2018

@ddevault

This comment has been minimized.

Copy link
Member

ddevault commented Dec 10, 2018

The GNOME folks can shove dbus

@ddevault

This comment has been minimized.

Copy link
Member

ddevault commented Dec 10, 2018

I'll write a more cordial response on the list.

@dvc94ch

This comment has been minimized.

Copy link

dvc94ch commented Dec 10, 2018

Am I just imagining this or is it redhat's agenda to force everyone to use gnome and gtk? It feels a little like microsofts embrace/extend/extinguish strategy.

@johanhelsing

This comment has been minimized.

Copy link

johanhelsing commented Dec 11, 2018

Just tested this with my WIP patch for Qt, and it seems to work nicely :)

@dvc94ch

This comment was marked as off-topic.

Copy link

dvc94ch commented Dec 11, 2018

mmh with qt and sway developers here I'd like to ask about an idea for a wayland protocol extension I've been thinking about. Being a vim keybindings fan I'd like all my applications to keyboard navigateable and have support for vim like keybindings. I was thinking that having the menu be part of the compositor (like for example mac osx does) and having a wayland protocol for registering menu items and the compositor handle keybindings and menu rendering, would help a lot providing a unified custom experience. Any thoughts on if this idea is worth pursuing?

@emersion

This comment has been minimized.

Copy link
Member

emersion commented Dec 11, 2018

@johanhelsing Nice! I'll have a look.

@dvc94ch Sorry, here is not a good place to talk about this. If you want to talk about a Wayland protocol, send an email to the wayland-devel mailing list.

@emersion emersion closed this Jan 18, 2019

@emersion emersion deleted the emersion:xcursor-configuration branch Jan 18, 2019

@emersion emersion restored the emersion:xcursor-configuration branch Jan 18, 2019

@emersion emersion reopened this Jan 18, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment