I agree with you in general, its not great on mobile, but it's not terrible. Far better than hamburger menu'ed UI that I see in the wild that seems to show 1 card at a time and hijacks the scroll mechanism.
A lot of "Not designed for mobile" fear stems from early days of smartphones in 2010-era which still lingers today. Things have changed. Screens have gotten much better in resolution, responsiveness has improved and touch experience on modern phones is exceptional.
Maybe it's because iOS don't have a one finger zoom gesture like Android? I wonder why Apple never added that one?
On iOS you can try the gesture in Maps, and then wonder why they never added it to Safari.
The time it took me to double-tap zoom was less than the time it would have taken for an SPA to load over my weak ass T-Mobile connection
Specifically: https://github.com/Vestride/fancy-index/raw/main/after_mobil...
[1] https://github.com/Vestride/fancy-index/blob/main/before.png
[2] https://github.com/Vestride/fancy-index/blob/main/after.png
It's also not the same directory they're comparing. IMO why add padding? Why change #000000 to some grey text?
Just add icons to [1] and you're good to go. May be use Sans-serif fonts if you wanna feel bit ~fancy~.
https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_m...
Browsing the /map directory directly isn't intended to be informative in the way people are looking for. It's more of a file store that just happens to be browsable for advanced users. Rather this information is intended to be from the wiki which has more detail and is searchable etc. See for example: https://siliconpr0n.org/archive/doku.php?id=mcmaster:raspber...
Similarly if you can find additional information the wiki such as image conventions (https://siliconpr0n.org/archive/doku.php?id=conventions) and additional copyright info (ex: https://siliconpr0n.org/archive/doku.php?id=tommi:start)
I'm looking over people's suggestions and trying to see if there is anything I can take in to improve the site. Thanks for the feedback and feel free to reach out to me directly if you want to contribute something directly!
PS: yes I know there is some crufty stuff on there like search is doing weird stuff right now with the side bar. I upgraded the wiki software recently and haven't yet been
Better folder descriptions maybe but other than that perfect!
AFAIK that would require just a text-align rule for the title and margin-left: auto; and margin-right: auto; for the table, which seems a bit more readable on wide screens.
Here's a screenshot: https://i.imgur.com/y447V3g.png
Also, I arrange my windows such that overlapping windows don't hide important stuff underneath them. So I can see essential elements of a site even with chat windows on top. But if the website position changes on browser window width change, this invalidates ALL my other windows. It's simply awful.
I want degrees of freedom to be independent, otherwise they are far less useful.
People want centered websites because they are using browser windows that are far too wide, usually full screen. Just use a narrow browser window and left-aligned websites will look just fine. You'd think that with everyone having a narrow smartphone, websites would work well with narrow browser windows, but no, usually they use a different (bad!) layout on desktop browsers. I really hate this.
NameWidth=[n | *]
The NameWidth keyword allows you to specify the width of the filename column in bytes.I doubt it's a custom framework, but view source just shows uninformative compressed javascript and no info.
I'd like to display my high resolution ML images in a similar way.
The viewer is really cool. I wonder if it'd be possible to modify it to display a folder of PNGs in a nice streamable way...
(It looks like it only supports slicing a single png, whereas we usually have tens of thousands of pngs. I've been thinking of ways of letting people view lots of ML images better than e.g. how tensorboard does it.)
In 2021, this would be a "card" based page, about 6 cards visible, rounded corners, and it would have fucking infinite scroll, ofcourse with spinners to let you know its processing. God, help us.
Edit: I should clarify, I like JS for form submission and a few things. If you're building Google Docs competitor, by all means, go for SPA and big JS frameworks. That's what they're designed for.