3 ms·

Positives: - Dig the concept overall, I need a way to track new additions to Git. - It's fast - Adds more items as I scroll down, however it would be great t

by bigohms 16y ago

Positives: - Dig the concept overall, I need a way to track new additions to Git. - It's fast - Adds more items as I scroll down, however it would be great to know when I've gotten to ones I've already read. Some suggestions: - RSS? - The dropdown readme functionality is awkward and not intuitive. Confusion as to where the hit area is and the expected interaction/net effort result. - Simplify and ease opportunities to engage, add the add a repo to the homepage, maybe sidebar it. - Repos should open up to new window? - Allow someone to create a cart of things to research or auto-watch items without clicking through to each repo. - Spend a little more time on the UI. Alternating row colors, maybe reduce the contrast of a white background against the creme background data set. - The most significant data point on the page is the descriptions of what each package is, not the package name. I'd consider making that the title line.

stagas 16y ago
First of all, thanks for taking the time to review. Your observations are really helpful. I should add a thicker border separating pages. Also to notice is that infinite scroll is entirely client-side, so no Javascript enabled browsers will just get the pagination as normally. RSS, yeah, it needs one. The dropdown moving into view is an experiment, and I'm just testing to see how it goes. My thinking was to scroll the readme into view, and scroll up a bit more to put the next element right under the mouse pointer. So if you try clicking somewhere below the middle of the screen (depending on the size of your screen), you can browse the entire list without using mousewheel or moving your mouse from position, and every readme will scroll to the position you are looking. This is especially helpful if you do a search for something and want to view all of this week's items. But if it turns out to be confusing I'll remove it. Links with target _new and _blank isn't something I like too much, so I leave it to user choice if they want to middle click or normal click, which is what they're used to already. The cart idea is interesting, and has some potential. I think it should be made to watch the repo on your account on github, so it'll probably require you to login with your github credentials. Also something for the future as I'm not ready to do logins yet. The UI needs work. You're probably right about the description as title I'll try that.
- stagas 16y ago
  Update: I tried description on top and didn't look as good. Maybe our mind isn't used of thinking so big paragraphs as titles and it was strange. If descriptions where short it would make sense, but now it's just random text which isn't easy on the eyes. Also tried removing the autoscroll, and it wasn't as good either. The reason is I catch mousewheel over readmes because it was annoying when scrolling through a readme, to have the page scrolling when it ended. So now, if there was no scrolling to the next element, you wouldn't be able to scroll down unless you moved your mouse away from the readme. I hope that makes sense.

by bigohms 16y ago

stagas 16y ago

First of all, thanks for taking the time to review. Your observations are really helpful. I should add a thicker border separating pages. Also to notice is that infinite scroll is entirely client-side, so no Javascript enabled browsers will just get the pagination as normally. RSS, yeah, it needs one. The dropdown moving into view is an experiment, and I'm just testing to see how it goes. My thinking was to scroll the readme into view, and scroll up a bit more to put the next element right under the mouse pointer. So if you try clicking somewhere below the middle of the screen (depending on the size of your screen), you can browse the entire list without using mousewheel or moving your mouse from position, and every readme will scroll to the position you are looking. This is especially helpful if you do a search for something and want to view all of this week's items. But if it turns out to be confusing I'll remove it. Links with target _new and _blank isn't something I like too much, so I leave it to user choice if they want to middle click or normal click, which is what they're used to already. The cart idea is interesting, and has some potential. I think it should be made to watch the repo on your account on github, so it'll probably require you to login with your github credentials. Also something for the future as I'm not ready to do logins yet. The UI needs work. You're probably right about the description as title I'll try that.

stagas 16y ago
Update: I tried description on top and didn't look as good. Maybe our mind isn't used of thinking so big paragraphs as titles and it was strange. If descriptions where short it would make sense, but now it's just random text which isn't easy on the eyes. Also tried removing the autoscroll, and it wasn't as good either. The reason is I catch mousewheel over readmes because it was annoying when scrolling through a readme, to have the page scrolling when it ended. So now, if there was no scrolling to the next element, you wouldn't be able to scroll down unless you moved your mouse away from the readme. I hope that makes sense.