View Single Post
BrentDC's Avatar
Posts: 903 | Thanked: 632 times | Joined on Apr 2008
#64
Originally Posted by qgil View Post
Hi, wouldn't it be better to have separate threads to discuss different topics?

I'm only speaking as a Maemo & Fremantle user here.



Have you used such Help in Maemo applications? I know I haven't. Even in my full GNOME desktop I have used the Help system only in few occasions after several years. The apps I use in Maemo tend to be self-explanatory. If I have questions I find the answers online.

What are your experiences with Help systems in mobile devices?
What is wrong with the Help system now? Yes I realize that not many developers use it, but that is not because of the system, but because of the developers developing for the platform.

One-man Open Source developers were never known to write help documents

But isn't Fremantle supposed to be a mass-market device? And mass-market = commercial developers. And we all know commercial developers write very nice help systems. Look at Digia@scene or @Web, both utilize the help framework and provide very nice help documents. Digia is one of the few commercial developers developing for the platform now and they utilize the help system very well.

What are the thousands of commercial developers going to do with Fremantle? Are you saying Nokia doesn't want commercial developers and wants to keep Maemo a hobbyists toy? No? If not, why remove the help system right before it is going to be used as it was designed to be?

Also, my application uses the Help.

In terms of text selection, Modest is more an exception than a norm because it still uses gtkhtml. So please don't make conclusions for the whole platform based on it.

Let's see this from a user point of view:

- The Maemo selecting behavior up to Diablo could be improved specially in scrollable areas, according to many sources e.g. this old bug. This justifies the action to change things in Fremantle, where scrolling and panning has a more important role.

- The Maemo browser has a specific gesture to activate text selection. Any application using the browser engine to render its own content can benefit from its gestures at will, including text selection.

- Text selection is not an issue in non-scrolling/panning areas. Developers can offer an interface where the user just needs to move his finger from beginning to end of the text selected.

What cases fall out of these two categories? Developers can still offer the change from pannable to selectable areas in one click. The assumption is that this separation will make life of users easier than in Diablo and previous versions.
Where is the API document describing this property? I've looked everywhere, yet haven't found this documented in either hildon.PannableArea or hildon.TextView (my application, a text viewer, is an exception to the above rules I guess).

Thanks.

Let's discuss examples of real applications, please. In which ones do you expect selecting text is going to be a problem?
Quick Clip (the viewer part) for one.
__________________
-Brent

Author of TouchSearch -- web searching software for Maemo 5.

Mobile Device lineage: Palm Z22 -> Palm TX -> Nokia N800 -> Nokia N900

Last edited by BrentDC; 2009-06-10 at 17:24.
 

The Following 4 Users Say Thank You to BrentDC For This Useful Post: