3 ms·
> Applications (GUI toolkits) must implement their own fonts antialiasing - there's no API for setting system wide fonts rendering. What??! Most sane and advanc
by shmerl 11y ago
> Applications (GUI toolkits) must implement their own fonts antialiasing - there's no API for setting system wide fonts rendering. What??! Most sane and advanced windowing systems work exactly this way - Windows, Android, Mac OS X. In Wayland all clients (read applications) are totally independent.
That's interesting, I didn't know that. Is that going to be a huge mess after Wayland transition (which is likely to happen in 2016)? I'm used to fontconfig managing global fonts settings. What will happen in Wayland case?
- zobzu 11y agoits not really true. for ex i use Xorg dpi settings and xorg provided font rendering and driven antialiasing. gui toolkits can override this (and usually propose to), specially for older versions of Xorg that did not support native dpi scaling, antialising, etc.
- tadfisher 11y agoIn both Windows and OSX there are multiple choices for included font rendering libraries, so I'm not sure what the author is on about. There is no "system-level" font renderer on any of the three major OSes, and frankly such a thing doesn't make sense from an engineering standpoint.
- shmerl 11y agoIt might be not completely golbal, but fontconfig affects the vast majority of applications as far as I know. So it's something of that sort in a sense.
- the_why_of_y 11y agoWhat choices are there? On Windows, there is Uniscribe, DirectWrite (since Windows 7) and also the legacy GDI font rendering APIs. Probably Microsoft will never remove any of these options to ensure backward compatibility. On Mac OS X, you use CoreText - the legacy QuickDraw Text is deprecated and not even available for 64 bit applications. There are also applications that do not use the platform font rendering, e.g. Adobe has their own font rendering code and current versions of Chromium and Gecko use Harfbuzz on all platforms.
- xorblurb 11y agoIts very doubtful that Wayland will happen in 2016. I'm not sure it does anything to solve real GNU/Linux problems for consumer and/or workstation devices. At least not without breaking everything else far more. The idea to let all applications render all their pixels without any further system integration is just completely insane when you see the future of GUI computing and interactions. Work on higher/sideway layers should be absolute priority, and X should be considered good enough until then (at least when you are not maintaining it, but that is a completely different story).
- shmerl 11y agoIt can happen in 2016. KDE is almost ready, and even Nvidia is approaching releasing their KMS/DRM driver with EGL support. So pieces to at least being able to use Wayland will be in place. However as you say, stuff might be still broken for some use cases, so those will have to be fixed going forward. Wayland doesn't dictate how compositors approach desktop integration. For instance there can be client side or server side decorations and so on.
- xorblurb 11y agoYes, Wayland doesn't dictate anything, and that's the problem! It is the moral equivalent of a glorified framebuffer. Number of subjects relevant in today interfaces interactions? I'm not sure there are any. Meanwhile graphic/interaction stacks on other systems concentrate on what is really needed by advances in tech and usages like HighDPI / mixed DPI / responsive GUI while updating their existing tech (e.g. RemoteDesktop) instead of deprecating them. What does Wayland provides in term of modern usages with modern tech? Maybe I missed something but from what I read it is just backward-incompatible (for apps) low level tech, and for actual users this kind of stuff often have negative value...
- shmerl 11y ago> What does Wayland provides in term of modern usages with modern tech? More direct and simpler (and therefore efficient) way to deal with drawing. X is bloated with tons of overhead and obsolete legacy stuff. Here is a good talk about it: (The Real Story Behind Wayland and X) https://www.youtube.com/watch?v=RIctzAQOe44 https://www.youtube.com/watch?v=RIctzAQOe44
- EdiX 11y ago> What will happen in Wayland case? Nothing at all. Very few modern applications use server side font rendering anyway, the ones that don't either are obeying fontconfig rules independently already or will keep ignoring them. It's not even different for Windows and Mac OS X, some programs do their own font rendering that's different from the one provided by the system.