Cross-Platform GUI Toolkit Trainwreck (2016)

Re:Cross-Platform GUI Toolkit Trainwreck (2016) by jcelerier on Thursday April 25, 2019 @04:03PM (#19751983)

I want the complete opposite. I use the three systems almost daily, and I freaking hate to have to context-switch to the platform's look-and-feel. Thankfully KDE apps work mostly everywhere nowadays.

Most of the users of the FOSS software I'm developing also switch platforms depending on the project they're in, but they want the software to be the same everywhere for instance.

[ Parent | on HN ]

Re:Cross-Platform GUI Toolkit Trainwreck (2016) by Wowfunhappy on Thursday April 25, 2019 @07:10PM (#19753384)

Are differently-styled UI elements really a mental burden? I'm not advocating for wholly different UI's on each platform—just that if your application uses checkboxes, and I'm on a Mac, I should see Mac checkboxes.

[ Parent | on HN ]

Re:Cross-Platform GUI Toolkit Trainwreck (2016) by Retra on Friday April 26, 2019 @11:42AM (#19758671)

It's probably more the behavior things. Keyboard shortcuts, focus behaviors, menu placement, file dialogs, etc. Settings panels in MacOs should take effect immediately, while in windows you have to click ok/apply... inconsistencies like this can lead to frustration.

[ Parent | on HN ]

Re:Cross-Platform GUI Toolkit Trainwreck (2016) by Wowfunhappy on Friday April 26, 2019 @02:40PM (#19760608)

But not doing this brings about an even worse kind of context switching—between apps on the same platform.

As annoying as it is to switch form cmd+C to ctrl+C when I go from Mac to Windows, it's even worse when a Mac app uses ctrl+C.

[ Parent | on HN ]

Re:Cross-Platform GUI Toolkit Trainwreck (2016) by jcelerier on Friday April 26, 2019 @01:18PM (#19759746)

this, and also the need to write three (or four if you want to do separate stuff for KDE & GNOME) times the amount of documentation to accomodate for the different "default" behaviours.

[ Parent | on HN ]