Xft and XCursor

Michal Suchanek hramrach at centrum.cz
Fri Jun 17 03:52:04 PDT 2011

On 17 June 2011 12:28, Lukas Sommer <sommerluk at gmail.com> wrote:
> Thanks for the fast reply :-)
> If I understand you correctly, XCursor and Xft will be dropped and replaced
> by something different?
> Xft is also important because it provides the custom font families and font
> sizes that the user has choosen. It's DPI value defaults to the native X
> server dpi value, which is normally 96 dpi, a simple convenience value,
> which in today's usage doesn't make much sense.
> The point is that you can force a custom font dpi value. This way you have
> an easy way to scale your user interface. Example: Set the font dpi value to
> 192 dpi and you see everything scaled with factor 2 (well, at least the
> fonts. If the use an application with a scalable widget style, than also the
> other UI elements.) Now: XCursor by default chooses the cursor size
> automatically depending on the font dpi. This is a very nice behavior (and
> IMHO important on the way to more resolution-independent desptops). Will
> this still be possible in Wayland?

Totally, that's just user preference unrelated to the environment in any way.

You will have to port the toolkit to use Wayland instead of X but how
the toolkit chooses to use it's rendering platform is up to the
toolkit. Neither the fonts nor the cursor are interpreted in any way
by either X or Wayland, it's up to the application to provide cursor
image or render some glyphs.



More information about the wayland-devel mailing list