The end of the nice GTK button

Post by marcosdumay » Fri, Mar 25, 2022, 2:01 AM UTC

flukus wrote: post #110

azinman2 wrote: post #42

So basically the new GTK is iOS but without the professional designers behind it. What I cannot understand is how Canonical, Red Hat, or some rich SV person hasn’t thrown money at the problem and hired a big wig design firm or person to overhaul it all. Johnny Ive is now even available (if he’d take the project). But even going thru a site like dribbble there are so many amazing designers out there. To me it would be…

> So basically the new GTK is iOS but without the professional designers behind it. Professional designers seem to be the ones creating these problems. Back when it was just programmers you could tell a button was a button, a tab was a tab and we didn't hide basic functionality behind a swipe gesture or long press that users were supposed to just know. Now everything is pretty but harder to use.

Post by jh721 » Fri, Mar 25, 2022, 2:01 AM UTC

Post by hedora » Fri, Mar 25, 2022, 2:02 AM UTC

jchw wrote: post #106

layer8 wrote: post #95

Earlier quoted context omitted.

“Scale-independent layout” (layout that ignores pixel aliasing) really requires PPI over ~200, that is, more than most desktop monitors provide. We’re still just not there.

It’s going to be a bloody mess for a long time, because the choices for how to handle resolution independence are all inherently filled with compromise. With font rendering, I think there is hope. Horizontal subpixel positioning with vertical hinting seems like a good tradeoff to me. Grid fitting vertically is not too jarring, and grid fitting horizontally to subpixels instead of pixels looks pretty good too, on low…

Post by linguae » Fri, Mar 25, 2022, 2:09 AM UTC

xedrac wrote: post #90

hoistbypetard wrote: post #52

The old button was good in the desktop context, but I can't get behind this point: > The design even works very well on Linux phone formfactors. The author must mean something very different when they say "works very well" than I do when I say that. As much as I want it to, nothing about GTK works well in a phone form factor, IME. I look forward to continued improvement that will make that statement incorrect.

I for one don't want the phone form factor to influence my desktop experience. They are two completely different workflows that have conflicting needs IMO.

Post by eyelidlessness » Fri, Mar 25, 2022, 2:12 AM UTC

cwillu wrote: post #192

eyelidlessness wrote: post #169

Earlier quoted context omitted.

1. Accommodating disabled people is in no way an insult. 2. Being disabled is a normal fact of life, also not an insult. 3. Accessibility affordances are not only for disabled people. Lots of people who wouldn’t identify as disabled routinely and gladly use a wide variety of accessibility features. 4. Having difficulty identifying actionable elements like buttons isn’t about reading anyone’s mind, and it isn’t a univ…

I read the parent as implying that it's the designer who is thinking of “disability” as a begrudged requirement that is afforded an out-of-the-way configuration option so as to not inflict the ugly affordances on the rest of the population.