Reply
Thread Tools
Traecer's Avatar
Posts: 165 | Thanked: 9 times | Joined on Jul 2007
#11
Originally Posted by Capt'n Corrupt View Post
I think the simplest solution is creating a fat scrollbar on the right. It would cut down on screen real-estate, but would be easy enough to target with a fat finger.
YES. Especially for apps that don't allow finger scrolling, there needs to be a scroll bar that can be fingered (if not thumbed) up and down. Though I think ultimately it would be better if all content areas simply supported finger scrolling.

Though I love finger scrolling, I believe in most cases kinetic scrolling SUX. In all the implementations I've seen so far (including the much-praised iPhone), the list scrolls unpredictably and too fast to easily read what is scrolling by.
 
hhedberg's Avatar
Posts: 84 | Thanked: 212 times | Joined on Nov 2007 @ Oulu, Finland
#12
Mauku¹ is using it's own Miaouw Library² to provide kinetic/inertial scrolling. The difference between Mauku/Miaouw and Kagu/UKMP is that the first is implemented in pure C/GTK+ while the latters uses Python.

The Miaouw Library is available under LGPL license. It would be nice to see also other developers using and improving it.

¹ http://mauku.henrikhedberg.com/
² http://miaouw.henrikhedberg.com/
 
zerojay's Avatar
Posts: 2,669 | Thanked: 2,555 times | Joined on Apr 2007
#13
Originally Posted by Capt'n Corrupt View Post
I think the simplest solution is creating a fat scrollbar on the right. It would cut down on screen real-estate, but would be easy enough to target with a fat finger.
While talking with ThoughtFix during his Tech Support chat thing, I asked him to show off the Media Player a bit and it was very very clear that the scroll bar in Media Player is absolutely huge.

Which sucks because I had no problems scrolling with the little scroll bar... but oh well.
 
Posts: 130 | Thanked: 5 times | Joined on Jul 2007 @ Maine & Florida - USA
#14
I like both capt'n 's ideas to improve scrolling.

Tapping near the corners would be something I like to test. Like how you can scroll maps on the web & software. Certainly in full screen that could work - no menu bar in the top right corner. Would have to be just below it in regular view.

Otherwise I always use the stylus. Doesn't seem I can rely on finger scrolling or the dpad - every time. And with the stylus it is never a problem. That said, if one could do it reliably without the stylus. That'd be great.
 
Capt'n Corrupt's Avatar
Posts: 3,524 | Thanked: 2,958 times | Joined on Oct 2007 @ Delta Quadrant
#15
Thanks guys!

I love the keypad for the N810 and the stylus, but don't think that they should necessarily be required for casual use. This is can be controlled through some clever adjustments to the interfaces of programs, most importantly, the web browser. The ability to use the finger to surf or look up information without fumbling around for a stylus is very important, and can make/break the decision to buy a tablet for some consumers.


}:^)~
YARR!

Capt'n Corrupt

Last edited by Capt'n Corrupt; 2007-11-11 at 10:31.
 
Posts: 529 | Thanked: 46 times | Joined on Sep 2007
#16
Originally Posted by Alvin View Post
using the MicroB browser on N800 I find that some web pages don't work with finger/stylus scrolling, whereas they always do with the Opera browser.

I hope this is better in OS2008...
Frankly speaking I don't see any finger scrolling in Opera.
I don't scroll but select web links in html document.
Scroll bars are too thin for finger operating.

Darius
 
Posts: 28 | Thanked: 4 times | Joined on Dec 2007 @ Spokane WA
#17
Anyone found a good solution to scrolling? Some pages you can click and drag, others don't like it and it selects text instead. What are you guys doing for browsing on web pages?
Thanks,
Isaac.S
 
Posts: 465 | Thanked: 149 times | Joined on Oct 2007
#18
On my N800 I usually page up and down with the hardware buttons, and occasionally tap the scrollbar if i don't feel like making clicking noises

Finger scrolling seems to work ok, but it's not as sensitive as I'd like, maybe that's because of the stock screen protector I'm using though.

It also uses more CPU than just a simple page up / down, since it's doing more screen updates.
 
Posts: 49 | Thanked: 6 times | Joined on Nov 2007
#19
Originally Posted by Capt'n Corrupt View Post
I think the simplest solution is creating a fat scrollbar on the right. It would cut down on screen real-estate, but would be easy enough to target with a fat finger.
That's definitely the simplest, but I think it's the worst. I'd hate to pay for and carry around a 4.1" screen only to get the use of a 3.8" screen. With multi-frame views (such as Modest) it's even worse.

Originally Posted by Capt'n Corrupt View Post
A twist on this idea, is a small box target in the top-right/bottom-right. Pressing the target with a finger then dragging initiates and completes the scroll. It could be translucent and would only obscure a minuscule portion of the interactive site.
That could work well.

Originally Posted by Capt'n Corrupt View Post
Another good solution is a button-touch combination to initiate scrolling using any dragging over the whole screen (or a portion). Perhaps one of the face keys, or the multi-purpose button can be leveraged for this.
I think this is a little less intuitive. But what about dedicated scroll buttons, or some other physical scrolling mechanism? I think a reasonable rule of thumb is that if an interaction is common enough, it should be removed from the screen so the screen can be used for more dynamic content.

Originally Posted by Capt'n Corrupt View Post
From here, fancy effects like inertial scrolling can be implemented.
How's this for fancy: Kinetic scrolling that creates a semi-transparent scroll bar where the finger stroked. This would allow someone to switch to manual scrolling from kinetic scrolling if they wanted to scroll faster or slower.

Originally Posted by Capt'n Corrupt View Post
The problem with scrolling using non-interactive space on the page is simply compatibility. While it is very convenient, many javascript and flash sites that capture the mouse event will not work properly with this type of interaction.
Do many sites capture the "stroke" event? It should be pretty easy to differentiate between a stroke and a tap. You don't have to capture the borderline cases, just the obvious ones, and the user will learn what to do. What is really needed is some sort of re-usable code base that can reliably differentiate between these events.
 
aflegg's Avatar
Posts: 1,463 | Thanked: 81 times | Joined on Oct 2005 @ UK
#20
Fat-scrolling is a really bad idea. The right answer for a finger/stylus-usable device with limited space is content-area drag to scroll.

I've raised a bug in Bugzilla about the 4 different ways I've counted in OS2008 that you've got, out-of-the-box, to scroll various different applications:

https://bugs.maemo.org/show_bug.cgi?id=2564
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
Now known as
Jaffa
 
Reply


 
Forum Jump


All times are GMT. The time now is 01:48.