Re:Cross-Platform GUI Toolkit Trainwreck (2016)
by edraferi on Thursday April 25, 2019 @08:06AM
(#19747165)
> But if you do some forms and basic UI controls, wxWindows does the job egregiously. Looks the way it should be on all platforms.
Word choice? "Egregiously" means "Conspicuously bad or offensive." [0] The context suggests you intended to say "adequate for the purpose," for which "competently" is the correct term.[1]
Re:Cross-Platform GUI Toolkit Trainwreck (2016)
by numeromancer on Friday April 26, 2019 @08:15AM
(#19756633)
I though he was being clever; "egregiously" means "in a manner consistent with being out of the herd". Bad or offensive for the goat-herd maybe, but perhaps not for the goat.
Re:Cross-Platform GUI Toolkit Trainwreck (2016)
by panemic on Thursday April 25, 2019 @10:54AM
(#19748789)
Thanks, I had a completely different meaning for this word in mind!
Re:Cross-Platform GUI Toolkit Trainwreck (2016)
by noisem4ker on Friday April 26, 2019 @01:35AM
(#19755093)
I also did. Given the Latin root (ēgregius, outstanding), I feel the pejorative connotation is out of place. The Italian term egregio definitely has a positive meaning, as it's also used to address people in letters.
Re:Cross-Platform GUI Toolkit Trainwreck (2016)
by ComputerGuru on Thursday April 25, 2019 @10:13AM
(#19748322)
I have filed numerous bug reports about Chrome's broken text rendering and hinting and had them closed as won't fix because they're too difficult to fix (note: not too difficult to reproduce, just too difficult to fix). I can't believe how low priority the correct displaying of the most important content in the window is to web browser developers.
Re:Cross-Platform GUI Toolkit Trainwreck (2016)
by weberc2 on Thursday April 25, 2019 @08:07AM
(#19747171)
Why does electron have broken text rendering? Surely the Chrome browser’s tendering does a good job? Or do you mean something like “it doesn’t match system defaults”?
Re:Cross-Platform GUI Toolkit Trainwreck (2016)
by tpush on Thursday April 25, 2019 @10:11AM
(#19748291)
Visual Studio Code on macOS right now has broken font rendering, since it uses Skia via Electron instead of macOS' native font rendering.
It's fixed in upstream Electron but until a fixed version is integrated into VSCode I have to live with (months of) broken font rendering.
It even makes me want to use Xcode somewhat. For all its flaws, its font rendering is just the system (working) one, and scrolling in Xcode is actually smooth 60fps instead of the laggy mess that is VSCode.
Re:Cross-Platform GUI Toolkit Trainwreck (2016)
by badsectoracula on Thursday April 25, 2019 @08:28AM
(#19747316)
Not matching system settings (not just defaults, but the setting, i set the settings for a reason) is broken!
Re:Cross-Platform GUI Toolkit Trainwreck (2016)
by blattimwind on Thursday April 25, 2019 @09:12AM
(#19747678)
This. It's a bug to use a different text renderer than the system, because it will never look the same and with text this is very noticeable and irritating even to some people. You do _not_ want your core visual to be irritating.
But if you do some forms and basic UI controls, wxWindows does the job egregiously. Looks the way it should be on all platforms.
It's funny an article from 2016 mentions issues about text rendering, because certainly we've been regressing in this area. I can spot QML and Electron apps by the broken text rendering alone. FF60+ with quantum has incorrect subpixel hinting and does not correctly hint at all sometimes.
Many of the mentioned apps int the article are "broken" in my eyes: I don't have perfect vision, and I do expect apps to follow the system text scaling (and they don't). For a "broken by design" example, see Darktable, which is awesome, and should do this by default, but the authors hard-coded a theme where literally every widget is styled for looks and not for function.
Nobody speaks about how the widgets should feel and interact, but that's exactly what feels off about "GTK" on windows or macos. QML, Electron and partly GTK3 brings that feeling to all platforms. My biggest letdown is QML, as many QT developers see it as the future so it has a larger adoption than it should have.
It breaks just about any rule in the book: poor behavior on any platform, noticeably slower, style not consistent with the platform, broken scrolling, broken text editing, broken text rendering...