41–50 of 308 posts
Honestly... this made things confusing without improving my reading ability. a lot of people actually like scrolling. So many people in fact, that they successfully pressured Apple to add scrolling as an alternative to pagination in iBooks. I'm one of the people who uses that. I'm trying to be polite, but my honest reaction to this interface was, "oh god, this is awful," when I tried to use the mouse to scroll the pa…
Honestly... this made things confusing without improving my reading ability. a lot of people actually like scrolling. So many people in fact, that they successfully pressured Apple to add scrolling as an alternative to pagination in iBooks. I'm one of the people who uses that. I'm trying to be polite, but my honest reaction to this interface was, "oh god, this is awful," when I tried to use the mouse to scroll the pa…
On the other hand, I imagine that if you were someone that liked pagination, this might be pretty nice.
This is great! I'm glad you're experimenting. I don't like this particular experiment, however. I far prefer using space / page down to handle a page of text at a time. I don't see much benefit to your method instead, and among other things, I miss having consistent visual anchors when I read.
One thing I find tough to deal with is the default amount of characters "scrolled" for a given mouse wheel move: the default takes way too long for my tastes. I find around 50 characters a lot nicer. Also, what about co-opting the scrollbar? It's a much more natural and smooth scroll as compared to the mousewheel, giving users more precise control over how much to scroll.
Honestly... this made things confusing without improving my reading ability. a lot of people actually like scrolling. So many people in fact, that they successfully pressured Apple to add scrolling as an alternative to pagination in iBooks. I'm one of the people who uses that. I'm trying to be polite, but my honest reaction to this interface was, "oh god, this is awful," when I tried to use the mouse to scroll the pa…
I accidentally clicked my mouse on page load and all content disappeared. There was absolutely no indication of how to get it back. I do not want the world to scroll this way.
Your conclusion may be valid, but I don't think the bug you found has anything to do with it.
Honestly... this made things confusing without improving my reading ability. a lot of people actually like scrolling. So many people in fact, that they successfully pressured Apple to add scrolling as an alternative to pagination in iBooks. I'm one of the people who uses that. I'm trying to be polite, but my honest reaction to this interface was, "oh god, this is awful," when I tried to use the mouse to scroll the pa…
What benefit does this have over scrolling = next page? Your eyes have to refocus on the top of the page anyway, you might as well have refreshed the whole text, not just the top line of the second line. Interesting idea though - what does this do on a touch device?
This is already standard on ereaders, nearly all (even if it's a tablet or PC app) do this. I don't like it, more than 1/3rd of the time a page turn is accompanied by a "back to last page, back to current page" as it annihilates my flow (yes, that includes dead trees). VT100 may have something to do with this though. Straight scroll isn't optimal either. When reading long texts, I prefer to have it presented in chunk…
Honestly... this made things confusing without improving my reading ability. a lot of people actually like scrolling. So many people in fact, that they successfully pressured Apple to add scrolling as an alternative to pagination in iBooks. I'm one of the people who uses that. I'm trying to be polite, but my honest reaction to this interface was, "oh god, this is awful," when I tried to use the mouse to scroll the pa…
The line is the interesting feature.
I accidentally clicked my mouse on page load and all content disappeared. There was absolutely no indication of how to get it back. I do not want the world to scroll this way.
I hate to be picky (well actually...), but you appear to be complaining about a bug on the site causing all content to disappear and then concluding that the scrolling effect is rubbish. Your conclusion may be valid, but I don't think the bug you found has anything to do with it.
Maybe it's just a bug, but it seems intentional and it ruins the experience for me.
The interface teaches me how to use it very badly. The most obvious interface clues are the arrows to either side of the page, but these work in the usual manner (hopping from page to page), so they distract me from the heart of your interface.
When I do happen to mousewheel, I can't immediately understand what that does. Am I moving myself or a divider? Why is the divider coming from the top? What's above the divider? Why is it snapping like that, instead of scrolling smoothly? The snapping erects a level of indirection between my (smooth) wheel movement and the movement of the divider, which obscures my ability to understand what's happening. I can't decide whether to scroll upwards or downwards—which is "forwards?"
Why is there a white page "behind" the text if I scroll the divider upwards? Is that what's on the next page or the previous page? Why are you showing me a white page?
The sense that I'm reading downward yet new text comes from above feels very strange. I see how you've ended up here, but it's highly unintuitive. Alas, it's also fundamental to your concept, so whether the concept lives or dies (once all other problems are removed) is a question of whether people can adapt to this spatial "warp."
The "snappy" movement of the page divider line feels clunky. Move per pixel, in immediate response to mouse wheel (or touch drag?) movement—preferably with inertia—definitely not per line.
This is not the way I want the world to scroll. But I see where you're going: leaving the text in place makes sense, and if you're going to do that then using a divider from the top follows inevitably. So the idea is worthwhile, but this implementation is its own enemy.