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? Lukas Sommer <div class="gmail_quote">2011/6/17 Michal Suchanek <<a href="mailto:hramrach@centrum.cz">hramrach@centrum.cz</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div><div></div><div class="h5">On 17 June 2011 10:29, Lukas Sommer <<a href="mailto:sommerluk@gmail.com">sommerluk@gmail.com</a>> wrote: > Hello. > > About Wayland I have the following questions: > > When we run, in some future, a Wayland-only session, how will > Wayland-enabled applications behave in the following things: > > - Xft: How to retrieve the font DPI setting and how to determine which font > at which size will be used? > > - XCursor: Will the X11 cursor themes work on Wayland or will there be a > different standard? How can we configure it? > > Currently, I'm taking a look at KDE configuration and how to set the font > DPI and how to change the cursor size. Will this still work in Wayland or do > we need to reimplement it? </div></div>It will definitely have to be reimplemented, at the very least to read the settings from Wayland and not X. Cursors are likely trivial. However, DPI is a problem. I am not sure Wyaland even handles DPI in any way at this point. One problem is that DPI (and RGB order or even the available color components) may vary in different parts of the display (eg. in multiscreen configuration). X and current Xft uses don't account for this. Thanks Michal </blockquote></div>