Reply
Thread Tools
Posts: 5,335 | Thanked: 8,187 times | Joined on Mar 2007 @ Pennsylvania, USA
#81
Originally Posted by GeraldKo View Post
I'd "vote" for it if there is such a thing, but I haven't figured out how to.
Voting isn't as easy to spot as in maemo.org Bugzilla, but it is there, toward the top, in the section between the grey bar containing the bug number & title and the grey bar for attachments.

Look for the "Importance" line. As I write this, it shows "enhancement with 20 votes (vote)". You'll need to follow that "vote" link, and create an account there if you haven't already.
__________________
maemo.org profile
 

The Following User Says Thank You to sjgadsby For This Useful Post:
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#82
Originally Posted by GeraldKo View Post
I just signed up and posted a Comment in favor. I'd "vote" for it if there is such a thing, but I haven't figured out how to.
Vote
 

The Following 3 Users Say Thank You to GeneralAntilles For This Useful Post:
Posts: 1,097 | Thanked: 650 times | Joined on Nov 2007
#83
I agree with lm2 - it should be an option.

When there are discussion about possibility of Nokia removing the option of the stylus (or any choice for that matter), then I hear everone clamouring of the choice of having both. So how come the OPTION to have FWTV is not wanted or welcome and instead iss recommended to be removed ?

Its simple - don't enable it if YOU don't want it, but let users have an option at least.

And seriously UserContent.css editing is not a friendly solution. Its only for developers who know what they are doing. and even then its not a toggling way to change FWTV.

I for one use FWTV often and welcome this option.
In hope changing fonts is a easily selectable option (unlike on the desktop where you require multiple clicks and menu navigation).
IMO, this should be a quick-select-deselect kind of operation .
 

The Following User Says Thank You to nilchak For This Useful Post:
noventa98's Avatar
Posts: 122 | Thanked: 51 times | Joined on Nov 2007 @ Paris, France
#84
So we have apparently a workable solution for this issue.

If I understand correctly the FWTV buttons on the N8X0 have disappeared (the zoom function is reserved for the camera (any hints from NW09 attendees about other applications using those buttons? Can it be re-programmed for other uses?).

For browsing and reading there is:

- zooming function (with the spiraling movement), which as someone reported elsewhere is better used to view images. From what I have seen on the videos the movement is a little awkward, however having the real thing in hands could change the perception.

- double tapping on a frame to automatically fits the frame to the screen. Someone asked about text wrapping: so far I haven't seen an answer (or I just missed it): is this supported? How is the reading improved with this feature? What happens to images included in an article when fitting the frame?

Given the size of the screen, the size of the characters will inevitably be smaller than on the other tablets. General comments by people who have seen and used the N900 point to an excellent screen: in that respect does it make up for smaller characters?

Are there other tricks to improve online reading, especially for the über 50s (like me...)?

Thanks
 

The Following User Says Thank You to noventa98 For This Useful Post:
pelago's Avatar
Posts: 2,121 | Thanked: 1,540 times | Joined on Mar 2008 @ Oxford, UK
#85
I'm sure I saw in at least one video that you can still use the top buttons to zoom in the web browser.

Personally I would like to see being able to increase/decrease the font size independently of image and div widths, with reflowing of text. And have the choice remembered per site (like Firefox).

Last edited by pelago; 2009-09-05 at 14:34.
 

The Following User Says Thank You to pelago For This Useful Post:
Posts: 341 | Thanked: 607 times | Joined on Dec 2008
#86
You can increase the font size (which will re-flow the text), but I don't believe it is remembered on a site by site basis.

Generally nobody should have trouble finding a setup at which they can easily read text, but wildly different font sizes and paragraph widths on websites may still be an issue. In my experience, that is not a problem in general use though. In a few worst cases, you might need to zoom in a bit further (via spiralling or +/- buttons) and pan horizontally to read the text. But at the largest font size, I doubt that this would ever be the case for anyone.

As for images, if they are properly floating in the text paragraph, then they will just show up as expected. If they are outside the paragraph, you will of course have to pan to see them, if you zoomed in on the text.
 

The Following 4 Users Say Thank You to kanishou For This Useful Post:
daperl's Avatar
Posts: 2,427 | Thanked: 2,986 times | Joined on Dec 2007
#87
Originally Posted by kanishou View Post
If they are outside the paragraph, you will of course have to pan to see them, if you zoomed in on the text.
Is double-tap zooming a toggle? If I double-tap a second time does the browser zoom-out to the full page?
__________________
N9: Go white or go home
 

The Following User Says Thank You to daperl For This Useful Post:
Posts: 341 | Thanked: 607 times | Joined on Dec 2008
#88
Originally Posted by daperl View Post
Is double-tap zooming a toggle? If I double-tap a second time does the browser zoom-out to the full page?
Yes, though it can be a bit fiddly (I presume that if you double-tap on a different area, it will zoom in to it first).
 
daperl's Avatar
Posts: 2,427 | Thanked: 2,986 times | Joined on Dec 2007
#89
Originally Posted by kanishou View Post
Yes, though it can be a bit fiddly (I presume that if you double-tap on a different area, it will zoom in to it first).
Thanks for the info. That would be good. Some of the pseudo code should be as simple as this:

Code:
def beginPageLoad:
    lastArea = fullPage
def onDoubleTap:
    thisArea = getTappedArea()
    if thisArea is lastArea:
        zoom to fullPage
        lastArea = fullPage
    else:
        zoom to thisArea
        lastArea = thisArea
That's generally how mobile Safari works.
__________________
N9: Go white or go home
 
Posts: 36 | Thanked: 10 times | Joined on Aug 2009
#90
I'd like to voice my strong preference for having text reflow on double-tap, just as it works in Opera Mobile.

As others have said it just makes for a better reading experience (and I'm not hard of vision in the least). No side-scrolling, just perfect ease - it would be amazing in the N900 - especially with the page down on space bar behaviour this browser has (just watched Peter Schnaider's demo video where he illustrates it). It makes a huge difference to longer browsing sessions, as anyone who has used Opera Mobile on a WinMo device will tell you. My Xperia had the same resolution as the N900, and it was brilliant for browsing between the screen resolution and text reflow. You could take in the site, almost always in its entire width, at the default zoom and read text at that level (although not with ease) - you'd see what you wanted to read and then BAM! You double-tap and there it is in font of you, text reflowed, easy to read.

Did it work in all sites? No. Did it work for the vast majority? Yes.

Should it be a default setting? I don't honestly care, just as long as its there somewhere. For me this is a key behaviour of a mobile browser, even when browsing desktop website versions at WVGA resolution, and if you look at the iPhone, Android, and Opera Mobile you'll see that they all have this behaviour - doesn't seem to be turning off end-users in any of those environments does it?
 

The Following 3 Users Say Thank You to NZtechfreak For This Useful Post:
Reply

Tags
fixed in harmattan, what is microb?


 
Forum Jump


All times are GMT. The time now is 11:21.