Unpopular opinion: optimising for "branding" is what killed theming. Everyone wants to have their own custom colour theme, brand-associated font or button style, which clashes with uniformity of system controls. If everyone renders buttons in a custom way, they bypass the native, theming-capable, accessible-by-default system controls. As long as product managers are happy, it doesn't matter that users aren't.
Remembering Windows 3.1 themes and user empowerment
221–230 of 333 posts
Re: Remembering Windows 3.1 themes and user empowerment
#222Re: Remembering Windows 3.1 themes and user empowerment
#223Good Lord, just give me control over the appearance of scrollbars again. Was there some international UI/UX meeting where they declared a holy war on scrollbars? Seems like everyone is trying to make them disappear like they're an embarrassing and unwelcome distant relative they're passive aggressively trying to make go away.
What really irks me are the autohiding scrollbars, especially when working over a VNC connection and I have to wait for them to fade-in over a 3000km link Give me scrollbars and keep them visible please.
Mac: General Preferences has an option "Show scroll bars" which you can set to "Always".
Re: Remembering Windows 3.1 themes and user empowerment
#224Earlier quoted context omitted.
Except that Windows 10 themes are a severe security/malware hazard, not a customization of harmless graphical elements.
Eh? Windows 10 themes are just wallpaper packs and a defined accent color. I assume you’re referring to UxStyle etc as used since Windows XP? That doesn’t involve loading any executable code (unless there’s an RCE vulnerability in the theme resource loader, I suppose) - patching the signature checks in UxTheme.dll isn’t that big a deal, imo.
This might even be the main reason that the operating system as-is only allowed themes signed by Microsoft.
Re: Remembering Windows 3.1 themes and user empowerment
#225Unpopular opinion: optimising for "branding" is what killed theming. Everyone wants to have their own custom colour theme, brand-associated font or button style, which clashes with uniformity of system controls. If everyone renders buttons in a custom way, they bypass the native, theming-capable, accessible-by-default system controls. As long as product managers are happy, it doesn't matter that users aren't.
Theming was HUGE in Linux back in 2005-2010, consistency was paramount, adherence to toolkit was extremely important just like Apple claimed. For Apple it was about delivering a consistent branded experience, for the GNOME and KDE communities it was about being able to consistently customize the experience. In Windows? Always a free-for-all of such heavy customization on the side of the third-party applications that…
Re: Remembering Windows 3.1 themes and user empowerment
#226Earlier quoted context omitted.
> Another issue as mentioned is that per-control CSS skinning breaks easily with custom themes. Instead of using system colors devs often hard-code a custom look. After years of using MacOS, I made a commitment this year to use, support, and develop for Linux on a regular basis. Starting off with little knowledge of GTK, I progressed from "hello world" to working on my first app, but end user customization has always…
For whatever reason this is not well documented, but all the theme's colors are available with a special syntax in the CSS: https://gitlab.gnome.org/GNOME/gtk/-/blob/master/gtk/theme/A... So for example you should be using this to use the user's foreground and background color: color: @theme_fg_color; background-color: @theme_bg_color; You can use some modifier functions on those colors too to compute additional colo…
Re: Remembering Windows 3.1 themes and user empowerment
#227Earlier quoted context omitted.
Scroolbars are useful for making large coarse leaps within a page in an instant, while scroll wheels are good for accurate positioning over short distances. But please. just stop making everything flat ffs. On the GUIs of old, you knew straight away what you could interact with, while now, everything is so flat or hidden away that everything blends together, I have no idea what I can click on and what's static unless…
> Scroolbars are useful for making large coarse leaps within a page in an instant, while scroll wheels are good for accurate positioning over short distances. That's funny. I use them in the exact opposite way. When I want exact positioning then I will use the scrollbar. When I want to scroll past pages and pages, I will just fling the scrollwheel.
Re: Remembering Windows 3.1 themes and user empowerment
#228Earlier quoted context omitted.
What really irks me are the autohiding scrollbars, especially when working over a VNC connection and I have to wait for them to fade-in over a 3000km link Give me scrollbars and keep them visible please.
Windows: Disable "Automatically hide scrollbars in Windows". Mac: General Preferences has an option "Show scroll bars" which you can set to "Always".
Re: Remembering Windows 3.1 themes and user empowerment
#229Earlier quoted context omitted.
Your list is missing an entry: 0. The existence of a scrollbar tells you there's something to be scrolled. Flat UIs are pretty good at accidentally hiding the fact that not all of the content fits on screen on in whatever borderless frame.
It's always fun when the content layout naturally fits into the viewport in such a way to make it look like there's nothing down below. Also fun when websites that are waging their holy war against the bars don't anticipate that I'm zoomed in a bit. Having to delve into devtools to disable "overflow: hidden" is a delight.
Re: Remembering Windows 3.1 themes and user empowerment
#230Earlier quoted context omitted.
Windows: Disable "Automatically hide scrollbars in Windows". Mac: General Preferences has an option "Show scroll bars" which you can set to "Always".
The Mac setting does not seem to work for all applications.