Folks, can we have a css framework for TUIs please?
something like this? https://kristopolous.github.io/BOOTSTRA.386/v2.3.1/
98.css
31–40 of 141 posts
Re: 98.css
#32Author here! This was my burnout recovery project and holds a place near and dear to my heart. https://notes.jordanscales.com/98-css-reflections
Re: 98.css
#33Re: 98.css
#34Earlier quoted context omitted.
Hey I'm there. Thanks
I love your design! I used it in a prototype BBS game playable on the web :)
It's extremely grueling to do. We're talking hundreds of hours.
I question how much AI can really help here since it's a matter of careful pixel alignment, image capabilities probably beyond what models can do and taste
I'm down if I can figure out an attack plan for the newer versions. Right now ai just feels like wheel spinning here. I might have to do this manually still
Re: 98.css
#35Popular in 2024 (471 points, 93 comments) https://news.ycombinator.com/item?id=42056918 2022 (606 points, 182 comments) https://news.ycombinator.com/item?id=33310554 2020 (838 points, 211 comments) https://news.ycombinator.com/item?id=22940564
last time this came up people appreciated my collection https://alexbsoft.github.io/win95.css/ windows 95 https://bootstra386.com/ 1980's websites https://botoxparty.github.io/XP.css/ windows xp https://code.divshot.com/geo-bootstrap/ geocities https://cs16.samke.me/ counter strike 1.6 https://edwardtufte.github.io/tufte-css/ edward tufte https://jdan.github.io/98.css/ windows 98 https://khang-nd.github.io/7.css/ win…
Re: 98.css
#36unjokingly I think the fact that we removed grayed out buttons for "the button just doesn't appear" is one of the more confusing UI trends of our day and the sight of a grayed out button warms my heart
> Reconsider disabled controls. Disabled controls can be hard to use because users literally have to deduce why they are disabled. Disable a control when users expect it to apply and they can easily deduce why the control is disabled. Remove the control when there is no way for users to enable it or they don't expect it to apply, or leave it enabled, but provide an error message when it is used incorrectly.
> Tip: If you aren't sure whether you should disable a control or provide an error message, start by composing the error message that you might provide. If the error message contains helpful information that target users aren't likely to quickly deduce, leave the control enabled and provide the error. Otherwise, disable the control.
Unfortunately, that nuance has been lost in the modern version of the guidelines with no mention of disabled buttons at all [2]
[1]: https://learn.microsoft.com/en-us/windows/win32/uxguide/top-...
[2]: https://learn.microsoft.com/en-us/windows/apps/develop/ui/co...
Re: 98.css
#37Author here! This was my burnout recovery project and holds a place near and dear to my heart. https://notes.jordanscales.com/98-css-reflections
Re: 98.css
#38Author here! This was my burnout recovery project and holds a place near and dear to my heart. https://notes.jordanscales.com/98-css-reflections
Re: 98.css
#39Author here! This was my burnout recovery project and holds a place near and dear to my heart. https://notes.jordanscales.com/98-css-reflections
Re: 98.css
#40https://github.com/lolstring/window98-html-css-js https://github.com/anthmn/hackertosh.css https://github.com/AlexBSoft/win95.css https://github.com/1j01/os-gui https://github.com/themesberg/windows-95-ui-kit https://github.com/andersevenrud/retro-css-shell-demo https://github.com/arturbien/React95 https://github.com/botoxparty/XP.css https://github.com/Gioni06/terminal.css https://github.com/jdan/98.css https://gith…