[Non-Touchscreen Windows Mobile Other] Menneisyys:
A lot has happened in the last month on the Web browser scene. Let’s go over the news!

1.	Opera Mobile 8.65 Final released!

Since this March, there have been two beta versions of Opera Mobile, without doubt the BEST, fastest and most standards compliant Web browser for the Windows Mobile platform. Now, almost half a year after the release of the first Beta, the final version has, finally, been released, of which I was also a (closed) betatester, working closely together with the developers and decision makers of Opera.

Compared to the 8.65 betas, which I thoroughly elaborated on in the Web Browsing Bible (and, therefore, in here, I don’t elaborate on these new features – make sure you read my roundup above), there are only few changes. There, on the other hand, have been several bugfixes; for example, the really annoying DEFBROWSER bug I’ve, independent of some other people doing the same, discovered and reported HERE).

Design decisions

Single column layout removed. This is a design decision I don’t really agree with. Particularly if you have a VGA device, you MAY find the lack of the single column mode annoying, particularly with sites / pages that, otherwise, would work much better with a well-working One Column mode. An example: a Wikipedia article in PIE’s One Column mode on a VGA device in Landscape mode (Largest charsize, High Resolution enabled) (the same with Fit to screen – as can be seen, it’s pretty much useless) and the same in Opera Mobile (Minimum font size: 8; Zoom: 100%). As can clearly be seen, One Column modes will ALWAYS be able to present more information. You can, of course, use zoom facilities so that the horizontal screen estate is fully filled in but, then, the character size will also grow and, what is worse, the images will also become pixelizated. (Also see THIS thread for more info / discussion.)

Desktop view, which has been made the default (!) viewing mode, has been made much friendlier. Now, it’s using a bit smaller characters than before. Should you still find them too big, switch to the default (fit to screen) viewing mode because setting Menu / Tools / Settings / Minimum font size to even 8 doesn’t seem to do the trick. Thanks to the, most of the time, excellently working new wrapping functionality, makes it possible to live without having to scroll around. This is shown in the following (VGA Landscape) screenshot with the View menu shown:

Now, the cache is stored on the same drive as the executable program itself. While this is what many people have been asked for (particularly with devices only having 64 Mbytes of Flash ROM, meaning only 10-11 Mbytes of it available to the users – for example, the HTC Oxygen / s310 Smartphone is one of them –, you will definitely like this.

Note that, however, this approach might have negative consequences. As has been explained in my Web Browsing Bible, storing the browser cache on a slow-to-create-files-on storage card (most non-high-end cards are like this) may result in the slowdown of the page loading. If this is a concern to you (because you visit pages that contain a LOT of different images, which are all cached), make sure you manually (!) relocate the cache to somewhere else – or, for that matter, completely disable it in Menu / Tools / Settings / History / Cache Size as can be seen in HERE. To relocate it back to the main storage (or even a RAMdisk, if its being completely deleted each reset and the decrease of RAM memory isn’t a problem either because, for example, you use a 128M RAM model), just follow my previous Opera cache relocation tutorial.

Problems I’ve discovered and/or fixed in the meantime

On MS Smartphone (Windows Mobile Standard) phones, when you have really low RAM memory (you’re running out of it), problems may occur with keyboard shortcuts. Namely, no matter what hardware shortcut button you press, the same functionality (in general, Reload and / or Back) will be executed. This can lead to confusion – at first, it caused me a lot of headache too until I’ve understood how this all works.

All in all, if your hardware dialpad buttons don’t do what they’re supposed to do, you may want to shut down (some) other apps and / or Opera Mobile tabs. This will free up some RAM, which will result in the buttons working again.

There’s still no hardware application button support (you can only tie button shortcuts to dialpad / keyboard buttons), but now that I’ve published a FULL tutorial and explanation of all decent Windows Mobile button enhancers, including how you can configure your hardware buttons to simulate the pressing of numeric (dialpad) buttons, this isn’t that big an issue. Just make sure you read the Button Enhancer Bible and do what’s there.

There had been a problem with non-English operating systems because of the wired-in (English) directory names with the initial release. This, along with manually fixing it, has been fixed in the meantime; that is, current builds no longer have this problem.

Verdict

Opera Mobile is and, as it seems, definitely remaining the best browser for both Pocket PC’s and MS Smartphones. While there still are some glitches (the worst of them, the lack for hardware app buttons, having been fixed by me), these problems are nothing compared to the generic sluggishness and/or Web standards incompatibility with (most of) the other browsers. Make sure you get at least the trial version.

2.	New (1.0.5) Picsel version released!

There is (see THIS) also a new version of the Picsel Web browser.

As opposed to some XDA-Dev folks, I haven’t found much improvement. For example, the CSS compliance is still very bad (the result of the Acid2 test is HERE; that of the CSS1 test is HERE). The Ajax compliance isn’t a tad better either (tested with THIS and THIS test suite).

All in all, there isn’t much improvement. You may still want to give it a try if you are a big fan of the GUI. I, myself, would still stick to either Opera Mini or Mobile. Don’t necessarily believe the hype :)