On Thu, 2023-12-14 at 10:23 +0100, John Hendrikx wrote: > > Animated text is extremely rare in productivity applications, so I > think > this really should be an option on a Node by Node basis (there is > already the cache/cacheHint property which are animation related). A > big > wall of text (like in a rich text control, TextArea or some kind of > text > editor) shouldn't have to suffer in readability just in case we may > want > to rotate or scale it... If Browsers had the JavaFX mentality of font > rendering, everyone would switch to the one browser that renders font > properly -- and I can imagine poorly rendered text is one the first > things people notice and can be a big reason for worse JavaFX > adoption.
I agree strongly. Purely anecdotally, and obviously I'm only a single sample point (although there are two more lower down!): I started out as a classic Mac user back in the early days of Mac OS 7. I migrated to Windows 2000 and Linux, and have primarily been a Linux user and to a drastically lesser extent a Windows user for my entire career. I mention this because I want to make it clear that I'm not biased towards any particular style of text rendering. I've worked on GTK, QT, and FLTK applications. Some small-scale Cocoa applications when Mac OS X first appeared. I've written Windows applications in the Win32 days. I've written Swing applications. All of these have been used by others to varying degrees. What's the _one_ platform where users complained about the text? JavaFX. Worst is that there's really nothing I can tell them... "Sorry the text is awful, the UI library I used has made the decision for me and won't allow me to change it." It's essentially my only complaint with JavaFX. In all other respects, it's better than every other UI library I've ever used. -- Mark Raynsford | https://www.io7m.com
