Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

98.css – design system for building faithful recreations of Windows 98 UIs

jdan.github.io

Post reply on HN
Print view View original

191–200 of 216 posts

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#191

Post by ZoomZoomZoom »

Scapeghost wrote: post #174
ZoomZoomZoom wrote: post #144

Earlier quoted context omitted.

Actually, they very much do: 1. As a relative marker of a current position. 2. As an absolute number when your ebook/reader screws up saving its state.

1. Is solved by "N Pages left in chapter" which is more useful than "Page N" 2. There is no "absolute number" of pages on a e-reader app or device because the window or font size can change, changing all the page numbers. You can have 100 pages or 200 pages.

1. It's also solved by X/Y where X: page number, Y: total pages.

2. Most users read from fullscreen readers on their phones or ebooks, so the window size doesn't really change. I also strongly advice setting on a font for a particular book and stick to it. From my POV (unbacked by science) it helps with recall. If you don't change the font or other layout settings, the "pages" retain their numeration.

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#192

Post by JansjoFromIkea »

gmmeyer wrote: post #189
JansjoFromIkea wrote: post #128

Hey man, if you're looking for the fonts I had them on a similar thing I done a while ago. Only normal size unfortunately https://github.com/padraigfl/packard-belle/tree/master/src/_... Cant remember where I sourced them from but it's probably in the code somewhere, the MSSansSerif ones are pixel perfect as far as I'm aware. It outputted CSS to be used independently but it was very much a secondary concern, pretty su…

This looks so good, especially the fake monitor effects

Thanks! Funnily that bit caused big issues for most my friends I showed it too, was definitely a case where rigidly straining to try and be _authentic_ clashed with the way most people remember things. There's an option to turn it off, I think (maybe not on mobile)

Stole that filter off codepen mind, nowhere near that clever... this one but toned down a bit https://codepen.io/lbebber/pen/XJRdrV

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#194

Post by Scapeghost »

roelschroeven wrote: post #188
Scapeghost wrote: post #184

Earlier quoted context omitted.

> To know how long the page is Why? How often the first thing you do is look at the scroll bar and close a document because it's too short or too long? If you're gonna read it you'll read it regardless of its length. If you want to do anything else, like printing, you'll see the document size. > to know what state we are BEFORE we interact with it Why? If you open a new document you'll be at the top. It's almost alwa…

>> To know how long the page is > Why? How often the first thing you do is look at the scroll bar and close a document because it's too short or too long? > If you're gonna read it you'll read it regardless of its length. Something short, looking remotely interesting, I'll probably read in full. Something long, I'll probably skim to see if there's anything interesting buried in there. If I'm reading it completely, gl…

> If I'm reading it completely, glancing at the scroll bar tells me where I am in the document so it tells me if the document is reaching its conclusion, or perhaps just going on a side note.

You'll see the hidden scrollbars when you're reading through something anyway.

> A bit later, when I have read a page or two, how far have I advanced?

You'll see the hidden scrollbars as you scroll through the pages to begin with.

> do you have an explicit implementation in mind where you can optionally enable scroll bars? I don't think I've ever seen such an option, and certainly not easily accessible.

It's right there in Mac general preferences, defaulting to visible if you use a non-Apple mouse.

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#195

Post by the_pwner224 »

brirec wrote: post #52
the_pwner224 wrote: post #30

Earlier quoted context omitted.

Not anymore for chrome & edge https://blog.chromium.org/2020/03/updates-to-form-controls-a... All part of Google's master plan to commoditize desktop OSs. Everyone outside the US already uses Android, soon your computer will be a Chrome box instead of a Windows/Mac/Linux box. First they did the browser title bar & tab bar integration/styling & removed the normal OS title bar, then they made Chrome OS, now they are re…

I think you’re a little mistaken — it’s been a while since I’ve used Chromium on GTK, but on Mac and Windows it has never really used native widgets/controls. This change is good because it goes from something that looks straight out of the late 90s no matter what your computer’s OS is, to something that _probably_ looks a _little_ more like whatever your OS looks like.

I was mistaken, Firefox is the one that uses OS controls for webpage elements. At least on Linux.

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#196

Post by zozbot234 »

tiborsaas wrote: post #180
noisem4ker wrote: post #140

Earlier quoted context omitted.

The system theme should reflect the user's opinion (or at least their learned expectation), thus browsers should honor the system theme.

I disagree, it's a question of authoring freedom. We have a fairly recent "prefers-color-scheme: dark" media query for this which further proves my point, that it's either black or white by default. If you, the author of the page decide to respect it then it's fine, but I'd be a bit mad if the browser decided to override my page design to an arbitrary grey shade if I don't declare a background color for the body.

The prefers-color-scheme media query can return any of 'light', 'dark' or 'no-preference' (the default). There's no real default for "light" design except as may be provided by the page author, or perhaps by the user herself via setting such a preference.

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#197

Post by zubairq »

canada_dry wrote: post #146
zubairq wrote: post #115

Really 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

> https://news.ycombinator.com/item?id=21734845 This (yazz/pilot [i]) needs more exposure... the webapp form designer is gorgeous and useful. [i] https://yazz.com/app/homepage.html

Thanks, glad you like it. We haven’t really pushed it out yet as we really want to get the debugger and App Store released before we can say it is useful

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#198

Post by efreak »

andai wrote: post #87
fermienrico wrote: post #69

Earlier quoted context omitted.

I think the Text input field doesn’t match the rest.

On iOS text and textarea are rounded. Not sure if you can override that with css.

You can get around that with contentEditable, but that creates an even bigger mess.

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#199

Post by stjohnswarts »

tomxor wrote: post #173

I can't believe how intensely functional the UI design of windows 95/98 was when looking back, and I say this as someone who intensely hates windows overall - but credit where it's due. Only when using it now is it clear how well they minimized ambiguity and cognitive load... everything is so frickin obvious. Contrast that with modern aesthetically obsessed UIs, ever ambiguous, lack of clear distinctions not in both…

I don't get it when people people use strong descriptors like "unease" and "jarring" when describing UIs. I don't think I've ever had a UI that made me feel fearful for my life/psychological well-being like that.
Post reply on HN