Hi Simon,
Sorry for not participating more activively in the discussion. Your summary
makes sense to me.
> Some people (from KDE, GLFW if I recall correctly) said
> there's some overhead in loading cursors on the client-side (a few megabytes,
> I/O when loading images) and that could be saved.
H
Hi Simon,
Thanks for working on this! :)
Is the intention to implement the client side inside libwayland-cursor? No
changes needed for toolkits except calling some new API when initializing
libwayland-cursor?
I guess it's also possible to implement it on the toolkit level using the old
libwaylan