Just wanted to comment on the usability of directory listings (Apache server?). No javascript bs, no UI frameworks, no SPA garbage, just good ol folder listing in HTML. Glorious, fast and shall I say, impeccable?
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.
Totally perfect apart from the fact I don’t have a fuckin clue what most of this shorthand and naming means. Sort of detail someone might include on of those silly cards or newfangled js dohicky
Eh. It’s pretty terrible on mobile, though. I can’t read or click anything without zooming and a page load for each directory resets the zoom. I would say the content isn’t really relevant for mobile users but the images themselves actually work pretty well on my device. Far better than the site itself.
It's actually pretty decent on mobile IMO. Pinch and zoom is easy to do, atleast on the iPhone. Then you just scroll naturally. The entire page doesn't move on you.
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.
I don't know why people are terrified of zooming. Frankly, zooming to use a desktop site is better UX than 90% of mobile sites. All you have to do is ensure your text lines aren't too long, which is good practice anyway.
Maybe it's because iOS don't have a one finger zoom gesture like Android? I wonder why Apple never added that one?
AA sibling comment mentions double tap to zoom in on a paragraph, but there's also a single finger zoom (tap and hold, then move the held finger vertically) for Maps (and by default in MapBoxGL last I checked).
Yeah it was in the first iPhone but you can't control the amount of zoom and it often guesses wrong or just doesn't work. I pretty much gave up on using it. On Android in most apps you can double tap, hold the second tap, then swipe up and down to zoom. It's a lot more natural than it sounds and it gives you precise control over both the zoom location and zoom amount.
On iOS you can try the gesture in Maps, and then wonder why they never added it to Safari.
Glad you are enjoying! I've aggregated some question responses below to try to clarify a few things.
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...
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
I couldnt agree more, I use ublock in advanced mode (even on mobile) and I was expecting to have to enable multiple scripts, which nearly always consist or analitics and ads, to be able to use this thing. Nope, all first party scripts, brilliant.
Better folder descriptions maybe but other than that perfect!
Quick question: is there a particular reason why the table and the other elements aren't centered in the browser by default? Even this site seems to do that to some degree, which improves the usability at least somewhat.
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.
I really dislike centered websites. That means that if I change the width of the browser window, the position of the website elements changes. So when I make the window bigger for ONE annoying tab that requires more width, it changes ALL other tabs. This is horrible for my muscle memory.
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.
It's pretty good, but Apache tries to cut off long filenames and isn't Unicode-aware when it does this, so it looks untidy because names come out at apparently random lengths…
Fantastic! Thank you both. Such a high quality repo, and only 28 stars.
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.