Best posts made by jmwking

I've upgraded and have been playing a bit. I'm a little confused between "Mini" mode and "Turbo" mode. As best I can figure it, Mini mode uses the proxy servers while Turbo mode renders directly in the device.

However, there are some differences beyond that:

When I select Mini, the font is much smaller than when I select "Turbo". No idea why.

In Mini mode, I have access to the (now sadly reduced) opera:config options. In Turbo, I don't. Are there any configuration options for Turbo?

In Mini mode I can't seem to save passwords anymore.

In Turbo mode, opening a link with a page anchor (mostly to jump to a new post on a forum) doesn't work - or at least it doesn't seem to work properly in vBulletin boards.

I've been using Mini for ages - first on my BB, and for the last few years on my iphone. I see a few big drawbacks to the new release:

-control text size; it's a little too small now

-save passwords on request (it seems to in Turbo, but not Mini)

-get single column view back; though I rarely use it, when I need it it's fantastic

-cache pages without refresh; the frequent reload is really annoying, especially in forums where it reloads and makes me lose my place

-jk

I have no idea if the mini simulator can be installed locally as a java aplet. But if you're having intermittent java issues, you should resolve those first. Try different computers on different ISPs and see if you can find a pattern.

Otherwise, I'm out of ideas.

-jk

Can't be worse, right?

This is just a comment engine...

-jk

Regardless of the computer, if the java test site fails, the mini simulator will almost surely also fail. If the test site fails, you'll have to install the Java runtime environment - and I still recommend you install it in Chrome as the safest handling of possible Java exploits.

Additionally, some firewalls block access to proxy servers, including Opera Mini servers, especially at schools and libraries where kids routinely browse the internet. Otherwise, they can use proxies to get around any age-appropriate content filtering.

For both reasons, I'm not sure the library will let you install Java on, or access the Mini Simulator from, their computers.

In case you missed it, here's a discussion of last year's java security warning:

http://www.informationweek.com/security/vulnerabilities/java-security-warnings-cut-through-the-c/240146598

-jk

Have you verified your Java installation? You can at the Java test site:

http://www.java.com/testjava

-jk

You install Java runtime from an executable as an application in Windows. On my machine, it installed in C:\Program Files (x86)\Java.

Download the installer here: http://www.java.com/en/download/index.jsp

Then disable Java in browsers that don't need it: http://nakedsecurity.sophos.com/?s=disable+java

-jk

Since Mini is a thin client, it just manages the connection between the device and the Opera servers. So long as Mini stays compatible with the device OS, there's not much need to update Mini itself.

Where the real upgrades have to happen is on the Opera servers. Those servers have to handle fetching data from the constantly evolving interwebs, and then creating the pageviews for Mini to display on the device. Much heavier lifting.

I presume Opera is fairly constantly working on the server side. I've seen static sites I use change over time how they look in the same Mini client, so I figure they're doing something on the other end.

-jk

Java has some serious security flaws. I only run it in Chrome, as Chrome always asks before letting any java apps run.

http://www.java.com/en/download/faq/chrome.xml

-jk