Earlier quoted context omitted.
Perhaps partly, but the UI was also useful compared to WMP. WMP was slow, bulky, and took up lots of screen real estate. WinAmp, while it was themed, was slim , but also packed far more control into a tinier space than WMP. (The blue/grey theme that came later was far less performant; I mean the original dark green/black theme.) And WinAmp would open & play literally any format under the sun. WMP was limited to somet…
WMP plays anything the system has a codec for.
Remembering Windows 3.1 themes and user empowerment
231–240 of 333 posts
Re: Remembering Windows 3.1 themes and user empowerment
#232Unpopular 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.
This MSDN article (which starts by recounting a day in 1995) backs your theory up: https://docs.microsoft.com/en-us/previous-versions/ms364048(...
Re: Remembering Windows 3.1 themes and user empowerment
#233> But then I realized how much I struggled to get my Android UI the way I wanted, until I installed Nova Launcher that gave me Linux-levels of tweaking. The average user does not do this. No. Stop, please stop with the paternalism. I cringe every time someone talks about "the user" in third person, like they were laboratory specimens. We all are mostly average users. There is not really any difference between your fa…
I don't understand the point you're trying to make here. > We all are mostly average users. If by "we" you mean the population of HN - that is blatantly false. The average HN user is far more technically sophisticated than the average computer/phone user. >> The average user does not do this. This is completely true, and not "paternalistic" in the least - it's a statement of fact. > There is not really any difference…
Elitism, again.
> This is completely true, and not "paternalistic" in the least - it's a statement of fact.
Backed by nothing.
> Absolutely false. My father, as do most of the fathers I know, are profoundly disinterested in customization and learning more about their devices - even after I show them some of the stuff that they could do, and offer to teach them. It's simply not interesting to them - they want to do workworking, or something.
They want to do workworking or something... Honestly, that sounds quite dismissive. Hopefully your teaching offer was slightly more humble than that...
Re: Remembering Windows 3.1 themes and user empowerment
#234Good 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 is the use case for scroll bars, now that we have mouse wheels? Progress indication? My view is that content is king and any UI element that needlessly takes away space from the content needs to be destroyed.
Content is king, but kings have all sorts of people supporting them. In fact you can immediately tell who's the king not by how solitary and unencumbered he is but by how much clutter and commotion and how many attendants are around him. I realize I'm pushing the analogy too far.
Re: Remembering Windows 3.1 themes and user empowerment
#235Earlier quoted context omitted.
As a Technical PM, I fought against a former boss when they wanted to forego native controls because they wanted their app to be branded, because without a custom look they felt that their app would not be unique and memorable. If an app can't survive on its usefulness alone, it probably shouldn't exist. As a user, if an app doesn't have a native UI, I disregard it unless I need it for a specific and mandatory use.
> As a user, if an app doesn't have a native UI, I disregard it I disagree rather strongly with this. You should use the UI elements that make sense. It doesn't make sense for Maya or Blender or Photoshop to constrain themselves to whatever Microsoft picked out for them to use. The palette of native widgets and native UX methods is woeful across all systems. It's constrained to the set of generic elements which are a…
Re: Remembering Windows 3.1 themes and user empowerment
#236Earlier quoted context omitted.
Reading this discussion got me thinking. I've been using KDE now for years specifically because every part of it can be customized, but for the most part, i've used the same theme and configurations now for pretty much the entire time i've been using kde. I still think it comes down to branding though, even with those totally customizable environments. The difference is, it's not someone else's brand. I get to turn m…
the ability to remove someone else's brand from my computer and replace it with my own. In Windows 2000 and earlier, before system file protection, it was possible to use a resource editor and/or a specially crafted BMP file to change system icons, boot animations, start menu imagery, login screen, etc. With a hex editor you could change any UI text, too. I had a heavily customized W2K alongside my heavily customized…
Re: Remembering Windows 3.1 themes and user empowerment
#237Re: Remembering Windows 3.1 themes and user empowerment
#238Earlier quoted context omitted.
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…
I agree that theming was much more consistent a decade ago in linux-land. GTK2 + QT with GTK2-style would get you an almost seamless experience. The "dark or light" theme we have today is an absolute joke by comparison. Many Gtk-engines were also much faster in terms of pure rendering speed. Another issue as mentioned is that per-control CSS skinning breaks easily with custom themes. Instead of using system colors de…
Re: Remembering Windows 3.1 themes and user empowerment
#239Re: Remembering Windows 3.1 themes and user empowerment
#240Earlier 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. 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.
I think it's dependent on your mouse too. Personally I only use mice that have a click wheel, I absolutely hate free-spinning scroll wheels.
Some of their newer gaming mice have a half-ass version of this as well with a manual mechanical toggle.