Live data from Hacker News

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

jdan.github.io

201–210 of 216 posts

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

#201
post #72

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…

"Most of the kids I know think MS Word/Excel/PowerPoint are lame " Wait until they reach the age and get hired in a corporation. I am a die hard linux user ( been on linux desktop more than i can remember ), but the latest stuff (=365) from MS is really appealing compared with gSuite. It has a level of sophistication that Google cannot reach.

Everything works well for me other than excel. It's not even close to being as capable. Of course I've never been a pro at Microsoft Word or PP either, but I'm quite well versed in Excel and the online version is a huge let down.

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

#202
post #44

Earlier quoted context omitted.

To top it off the bundle size and memory usage would still be more than just running Win95 in a VM...

It would give you the authentic feeling of running Win95 on a machine that maybe only had 8 MiB ram.

My sister had a Win95 machine with 32mb of ram and 2mb of video memory. What a powerhouse! Played 3D games on that thing...

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

#203

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…

Beautiful work, thanks so much :) I'll keep poking at fonts and see what I can learn https://github.com/jdan/98.css/issues/10 I love that we arrived at the ~same solution using inset shadows for the buttons. Makes me feel validated.

Take a look at WiseJ. You can actually program fully-fledged WinForms.NET applications for the browser. They have a Vista theme, but not Win98.

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

#205

Earlier quoted context omitted.

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.

> 1. It's also solved

So you agree that there's an alternative solution to page numbers, but you want to go back to page numbers?

> 2. Most users read from fullscreen readers on their phones or ebooks, so the window size doesn't really change.

Font sizes can change, changing the number of pages.

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

#206

I’m impressed by how few people here have tested it in Firefox – Fieldset is broken, Button has ::-moz-focus-inner not properly disabled, Radio/Option isn’t rendering correctly (still shows the original input element as 2x2px black box), and quite a bit more. Hilariously, this is quite a good example on why the Chrome monoculture is just repeating the IE monoculture of years past

I’ve been getting a good amount of bug reports from FF users, and am grateful because - you are right - I did not test in it and should have. I’m tracking the fieldset and inner-focus ones (though unable to repro the latter on my machine). The third is new to me if you’d be so kind as to share some details about your system.

I’m running Firefox 75 on Ubuntu 18.04. Pretty standard usage.

Fieldset doesn’t allow inset box-shadows on Firefox, but you can fix that relatively easy:

    fieldset {
      position: relative;
    }

    fieldset::before  {
      content: "";
      display: block;
      position: absolute;
      top: 0;
      left: 0;
      right: 0;
      bottom: 0;
      box-shadow: inset -1px -1px #ffffff, inset 1px 1px #0a0a0a, inset -2px -2px #808080, inset 2px 2px #dfdfdf;
    }

Moz-Inner-Focus and the Radio/Options are also equally easily fixed:

    ::-moz-focus-inner {
      border: 0;
    }

    input[type="radio"], input[type="checkbox"] {
      visibility: hidden;
    }

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

#207

Earlier quoted context omitted.

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.

> 1. It's also solved So you agree that there's an alternative solution to page numbers, but you want to go back to page numbers? > 2. Most users read from fullscreen readers on their phones or ebooks, so the window size doesn't really change. Font sizes can change, changing the number of pages.

> So you agree that there's an alternative solution to page numbers, but you want to go back to page numbers? Yes, and I never had any reason to go away from them so I never did. > Font sizes can change, changing the number of pages. Fonts don't do it themselves, though.

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

#209

Earlier quoted context omitted.

There’s always obscure use cases like this. You could go on forever listing individual people’s wants and you’d end up with a Homer car. We design interfaces for the many first, and keep them as simple as possible but not simpler.

> We design interfaces for the many first, and keep them as simple as possible but not simpler. The many being able bodied, literate, touch-device-carrying people? I am not sure interfaces should be designed like that.

[deleted]

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

#210

Earlier quoted context omitted.

I've noticed there are a couple of these now so I threw a quick list up on Github: https://github.com/matt-auckland/retro-css

i found this too, (but i can’t find a demo page) https://github.com/npjg/new-dawn

That one was a bit disappointing - here's a screenshot: https://imgur.com/oFz7e0p

Funny enough, just yesterday (before seeing this post), I was searching for re-creations of the Macintosh interface.

Here's the best one I could find:

Apple Macintosh System 7 UI in CSS - https://github.com/pfcode/system7css (Screenshot: https://imgur.com/ZEKolbS)

Aah, that nostalgic comfort.. Makes me dream of building my next toy "OS in a browser" from this.

Post reply on HN