[–] ndiddy 2 days ago
[–] cowlevel 2 days ago
How do they know it's good design? Did they think long and hard about where people would click to shut down? Maybe, but the more direct reason is they had user testing labs, and at the end of the test they asked users to shut down the computer, and almost all of them clicked on Start.
[–] rafram 2 days ago
macOS’s Apple menu, which only ever contains system management commands and doesn’t try to be an app launcher too, is so much more logical.
[–] ndiddy 2 days ago
Because of how much of a radical departure Windows 95 was from previous UI designs, and because of how driven the design was by user testing, there's a lot of information available going over why the design is the way it is. For example, there's an article going over the iterative design process here: https://socket3.wordpress.com/2018/02/03/designing-windows-9... and there's a detailed document explaining the UI for reviewers here: https://web.archive.org/web/20260209083725/https://tech-insi...
[–] cowlevel 2 days ago
[–] senfiaj 2 days ago
[–] paulryanrogers 2 days ago
[–] kbolino 2 days ago
[–] M95D 2 days ago
TweakUI indeed doesn't add support for scrolling inactive windows. I used IntelliMouse driver for that feature.
[–] kbolino 2 days ago
I've been trying to piece together what was actually there based upon some historical sources [1], [2], [3] and it's quite murky to me. As far as I can tell, scroll-follows-mouse was not truly possible in Windows 95, because the custom MSH_MOUSEWHEEL event lacked a way to carry the keyboard state, and an unfocused window would not have received the keyboard events to infer it correctly, so it would have been broken in a lot of edge cases. Then, Windows 98 added the standard MS_MOUSEWHEEL event, which does carry the keyboard state, but only 32-bit applications are able to access it, so the O/S locked scrolling to the focused window. Finally, Windows 10 pulled the plug on 16-bit compatibility, and so could and did make true scroll-follows-mouse possible.
[1]: https://devblogs.microsoft.com/oldnewthing/20080806-00/?p=21...
[2]: https://web.archive.org/web/20070503040017/http://msdn2.micr...
[3]: https://devblogs.microsoft.com/oldnewthing/20160420-00/?p=93...
[–] paulryanrogers 2 days ago
[–] M95D 2 days ago
[–] ale42 2 days ago
[–] thomashabets2 2 days ago
And some others. IP? No, we are a NetWare IPX network!!
[–] adjejmxbdjdn 2 days ago
It’s hard to determine what was aesthetically good from a different time because tastes change.
But there’s nothing wrong with small buttons when your only input tool is a pixel accurate mouse. Arguably what’s worse is too large a button.
But what’s inarguably worse are things like window corners where the click zone extends far beyond the actual window, and parts of the window are not click zones.
[–] g-b-r 2 days ago
[–] cowlevel 2 days ago
Hence it was also extremely important to put the important stuff above the bottom of the first visible page.
[–] g-b-r 2 days ago
Someone really uses that??
I personally don't know any less convenient way to scroll (ok, except clicking on the scrollbar arrows).
And if mice with the scroll wheel weren't widely available at the Windows 95 launch, they became shortly after. You've also always been able to scroll with the keyboard, btw.
Scrollbars became disdained with the modern smartphones, because some ##### thought that touch scrolling was enough.
Except that without a scrollbar it's extremely hard to figure out how long the page you're considering to read is.
And, rather than scroll wheels, I love and always use chirals on laptops, but both with them and with touchscreens, to make big jumps in a document a scrollbar is often more convenient.
[–] jen20 2 days ago
As for inconsistent - what!? Every app looked approximately the same, and behaved in a predictable manner.
If you read through old HIGs, they generally have actual concrete reasoning behind the choices they made. They're pretty interesting to read because back then they did scientific user studies to try to make computers more usable.
For example, Microsoft didn't make the UI gray because of some aesthetic preference. They chose gray because black-on-gray text is easy to read, and because it makes it immediately obvious what's UI vs. what's content (vs. if they made the background white or something). They made all the buttons three-dimensional because it makes it immediately obvious that something is clickable. Getting rid of stuff like this makes the UI prettier, but it also gets rid of hints for how to use the software.