98.css – design system for building faithful recreations of Windows 98 UIs
141–150 of 216 posts
Re: 98.css – design system for building faithful recreations of Windows 98 UIs
#142Earlier quoted context omitted.
Me asking myself "how long is this article" before I start reading it is a distraction? Too bad, I can't help but want to know. I could've learned that instantly by unconsciously glancing at the scroll indicator, but instead I have to move the whole content down for it to appear (possibly with a whizz-bang animation, no less), introducing friction and further distracting me from the content. Good job, I guess.
I don't know what you tell you - most people don't think about user interfaces like this. As we can clearly tell by people not designing them like this anymore.
Re: 98.css – design system for building faithful recreations of Windows 98 UIs
#143Earlier quoted context omitted.
Knowing how long a document is, and whereabouts your current view is, seems pretty fundamental. You may as well argue against page numbers in books.
You just scroll a tiny bit and you can see. Doesn't need to on the screen all the time, taking up space, distracting from the content which is what I care about, rather than whizz-bang user-interface elements.
Re: 98.css – design system for building faithful recreations of Windows 98 UIs
#144Earlier quoted context omitted.
Knowing how long a document is, and whereabouts your current view is, seems pretty fundamental. You may as well argue against page numbers in books.
> You may as well argue against page numbers in books. Actually, yes, when was the last time you looked at a page number in an e-book? They don't make sense anyway when you can resize the reader.
1. As a relative marker of a current position.
2. As an absolute number when your ebook/reader screws up saving its state.
Re: 98.css – design system for building faithful recreations of Windows 98 UIs
#145Earlier quoted context omitted.
An always visible scroll bar or indicator is conceptually simpler than one that disappears randomly. Knowing that a view is scrollable and there's more content to see is absolutely not an obscure edge case but a basic accessibility feature. Relevant past discussion: https://news.ycombinator.com/item?id=20951580 Also relevant, what happens when the user doesn't realize more content is available: https://news.ycombinat…
Well I just subjectively disagree - as apparently do the legions of professional experts at multiple distinct companies who research user interaction and design these interfaces.
Re: 98.css – design system for building faithful recreations of Windows 98 UIs
#146Really nice. I tried to get Windows look and feel in the headers for the Yazz code editor, but maybe I should have used this CSS lib instead. Great Job! https://yazz.com/app/homepage.html
This (yazz/pilot [i]) needs more exposure... the webapp form designer is gorgeous and useful.
Re: 98.css – design system for building faithful recreations of Windows 98 UIs
#147It may as well be called 2000.css, at least I won't be able to tell the difference.
Re: 98.css – design system for building faithful recreations of Windows 98 UIs
#148Really nice! One minor nitpick: the title bar buttons actually need to be a pixel or two larger in each direction (so 2 or 4 pixels more of height and width, while remaining centered).
Re: 98.css – design system for building faithful recreations of Windows 98 UIs
#149Earlier quoted context omitted.
You're in luck: https://codepen.io/matthijss/pen/wzYjJQ
Haha. I was just thinking of that. Been wondering if there's any operating system I can theme to look like Win3.1 any more - the aesthetic of Windows 95 is better but Windows 3.1 seems to fit our contemporary standards of flat and fewer colors better. I did like the more rounded buttons of Windows 3.1 better than the harsher edges of the Windows 95 buttons. The mistakes a driving me crazy. I assume the fonts are just…
Re: 98.css – design system for building faithful recreations of Windows 98 UIs
#150Earlier quoted context omitted.
Knowing how long a document is, and whereabouts your current view is, seems pretty fundamental. You may as well argue against page numbers in books.
> You may as well argue against page numbers in books. Actually, yes, when was the last time you looked at a page number in an e-book? They don't make sense anyway when you can resize the reader.