The Good Life... a weblog about life, technology, and the Opera Web browser

Tim's Opera Bits v4.0

Welcome to the fourth edition of Tim's Opera Bits! A lot has happened since the last update, so let's get right to the news:

  1. We released Opera Desktop 9.1 with fraud protection/anti-phishing. This release includes fixes for a couple security issues, so please update. There're a lot of other changes and fixes in there too.
  2. We released Opera Mini 3.0, 3.01, 3.02, and 3.03! That's a whole lotta Opera Mini. New in 3.0 is RSS/Atom support, photo uploads, and secure browsing. But don't take my word for it, try it out yourself! Or, check out the Opera Mini simulator and Daniel's video demos of Opera Mini.

    I tried out Opera Mini for the first time back in April when I had free data access with my new mobile phone plan, but since I work at home and don't get mobile service in the house, I decided to stop the data access. I ended up realizing how much I could have used it this Thanksgiving while travelling throughout New England, so I recently signed up for a new data plan for my moblie. Since, I've used Opera Mini while standing in line, while waiting for a movie to start, and to search Amazon.com while shopping for movies at Borders. It's been a great help.

    Here are some usage tips:

    • Don't browse and drive. It's very naughty. Not to mention dangerous and illegal. And distracting.
    • Turn off images. Pages load significantly faster and you usually don't need them. You'll also save a bundle if your data plan has usage restrictions (like mine).
    • Share your browser.

    Anyway....

  3. We released a trial version of Opera Wii. Of course, you'll need a Wii to use it. You should totally get one, too, since they rock! They're still pretty scarce, though.

    Fortunately, Opera Wii is free through the end of June. That should give you plenty of time to pick one up. Oh, and the final should be released toward the end of March.

    PS: Opera Wii passes the Acid2 test. Sweet!

  4. We released a preview of forthcoming developer tools. These tools will find their way into a future Opera release in some form, so we'd appreciate your feedback. Thank you and happy developing!
  5. We released... a whole lot recently. We're glad that's over. Opera 9 got a great review over at MacWorld and Opera's CEO, the venerable Jon von Tetzchner, was interviewed by the Tech blog at SciFi.com about the silliness that is .mobi. There should only be one Web, people. Opera Mini, Opera Mobile, and Opera Wii all work with the existing Web. There's no reason things shouldn't continue that way.

Take a deep breath. Good. Now, the fun stuff. In the last issue, I asked y'all if you had any questions about Opera Software. I got some great questions, so here come the responses. Keep in mind that opinions expressed are my own and don't necessarily represent my employer, Opera Software.

Pallab asks, "Why is Opera so reluctant to add an API to allow extensions? It seems the natural step forward, and is one thing which Opera is lacking (other notable browsers like IE7, Firefox, Maxthon already has it). Lets face it, its impossible for any browser to cater to the demands of millions of people. So why not do the next best thing, and allow them to add the desired funtionalities themselves."

I wouldn't say we're reluctant, but there are certainly some hurdles along the way. First, it's not clear that an API for extensions is really the right answer. A lot of people ask for extensions because Firefox has them. Does that necessarily mean they're the correct thing for Opera? No. If we add an API, does that mean we'll have high quality extensions that you'll actually want to use? No.

There are a number of technical challenges in introducing an API for extensions. Opera's core functionality is kept lean and mean, making porting to all kinds of exotic platforms (like, say the Nintendo DS and Wii) as simple as possible. Adding in an extension API that arguably benefits only one platform (Opera Desktop) isn't necessarily the best thing for Opera as a whole.

I hear a lot of Opera fans blame extensions for Firefox's speed, memory, and stability problems. I really have no idea if this is true or not, but it's another thing we have to consider. Furthermore, I often hear that very few Firefox users actually install extensions. Most of the talk is from the vocal minority and is largely propaganda. I'm interested in some actual numbers, if anyone has them. If this is the case, the work needed to implement an API for extensions may be better spent on other things.

All that said, I'd personally like to see an extension API. Opera fans are a great, creative bunch of people and I'd like to see the stuff y'all could come up with. I think Opera Software could benefit from removing some of the current functionality from the base install and releasing it as extensions. Not everyone needs the ability to validate Web pages or view Widgets built in to their browser. Then again, they might think they don't, but they use it and end up loving it. And they probably never would have used it if it weren't there by default. It's a conundrum, really.

FataL asks, "Is there any reason [to not be] consistent in case of drag and drop? For example in Opera for Mac I can drag icon from address field and drop it in [another] browser -- it's an easy and handy way to open [the] current page in [another] browser to test. And it works both ways on Mac. On Windows (and I believe on *nix) there is no way..."

While much of Opera's functionality is cross-platform, there's some stuff that's still platform-specific, such as interaction with other programs and the operating system. Drag and drop is one of those cases. So, it basically means that the Mac team implemented this functionality but the Windows and *nix teams didn't.

Robust cross-platform functionality is important to us, but so is integrating with the operating system. Mac users are especially critical of software that doesn't integrate well with the OS. So, the Opera Mac team spends more time on such functionality, such as automatically importing contacts from Address Book and making the Apple Remote work in full screen mode. The Windows and *nix teams have their own sets of challenges and priorities. Hopefully better drag and drop is one of the latter.

xErath and Grey asked when developer tools will be available.
As I mentioned above, we've already released a preview of some of the upcoming developer tools. You can install them right now just by dragging them to a toolbar. A future release may include a dedicated developer toolbar with these tools plus many of Opera's other developer tools (e.g. page validation, sourcing editing). We're also updating the Info panel and we're looking for your suggestions. Please let Peter know what you want in there.
FataL asks, "why [does] Opera still use [the] 8.3 format when saving files?"
I asked about this internally a while back, as I'd prefer Opera save MHTML files with an .mhtml extension, rather than .mht. The Desktop Team prefers to continue to use the 8.3 format for filenames (maximum eight characters in filename and three characters in extension) because a) IE does and b) some programs still can't handle long filenames.
Pallab asks, "I remember about a year or so ago Daniel [wrote] that Opera would add skype like pc2phone service (voip). Can you provide/leak any more info about that?"

You're probably referring to these two articles from OperaWatch: Opera considering entering the IP telephony market and Opera to integrate VoIP into desktop and mobile browsers. The second article is based on a press release, which says, "Opera Software today announced a partnership with JAJAH, one of the world's fastest growing VoIP (Voice over Internet Protocol) companies.... JAJAH's services will be available through Opera Mobile and Opera Mini...and will also be included as a widget in the upcoming Opera 9 desktop browser."

So, where's the widget and Opera Mini release? Due to some unforeseen complications, these products are currently in limbo.

Pallab asks, "Why is Opera allowing sites like Google services ( gmail, google docs blah blah blah) to get away by blocking Opera.Have a look at this page. It seems that Google thinks that 6.03 is the latest version of Opera available. In the past you guys have sued MS with pleasent results. Why not try it again?"

First off, pursuant to the settlement, Opera Software has never stated who was on the other end of the lawsuit. To be honest, I don't even know. There was wide speculation that Microsoft was behind the payment, but it's just that: speculation.

Now, to answer your question: we aren't allowing sites to get away with blocking Opera. To my knowledge, we aren't pursuing legal action against them either, but we have other tricks. Instead of relying on web sites to update themselves, we push out work-arounds to Opera users via browser.js. We have great initiatives like Open the Web and great people working on these initiatives, such as David Storey and Hallvord Steen. Also, we've recently opened Dev.Opera, a site dedicated to educating web developers.

One of the best things we can do to prevent blocking is to increase our market share. That, of course, is another thing we're working on constantly. Personally, I prefer our current initiatives rather than lawsuits.

fsp asks, "Will there be ever [an] Opera/M2 Version [which] will support PGP/GPG? Or, is this a license issue?"
It's not a licensing issue. We do intend to support encryption in Opera Mail in a future release, but it's not clear when we'll have this functionality available. It'll probably have to wait beyond Peregrine.
Grey asks, "What's 'Peregrine'?"
Peregrine is the next major feature release, probably Opera 10. No version number has been set yet, though.
Grey asks, "What are the great plans for Opera 10? I'm not speaking of single features... more... overhauls (which standards to be implemented, what about the chat and mail clients?)."
Generally speaking, we don't disclose information about future releases. However, I have been given permision to tell you a thing or two about Opera Mail: a) one of the most-debated wish list items will finally appear, and b) the indexing back-end will be replaced, which will hopefully fix a long-standing and dreaded indexing corruption bug.
Grey asks, "will 'Quick' (the UI engine) be re-written? We severely need some features currently limited by Quick."
There are no plans to implement a new UI toolkit. As discussed in the comments on my previous post, Quick doesn't need to be rewritten, just updated a bit.
FataL and gossymer ask, "There was a really helpful and innovative feature in Opera 9 first TPs -- button-indicator that show you if current page already bookmarked/noted or not. Than it was removed, but not completly -- you still can add buttons manually (they are not even presented in customization dialog). So, the question is 'why is that?'"

For those of you unfamiliar with this particular feature, allow me to give you a bit of background information. Opera 9.0 Preview 1 included a star icon in the address bar. If you visited a bookmarked page, the star would turn yellow. As you can read in various forum threads, a lot of people liked it and a lot of people hated it. In Opera 9.0 Preview 2, we decided to remove the star based on the feedback we'd received and instead included the same functionality via a button that users could put on any toolbar.

In 9.1, the address bar has indicators for several things, such as notes, widgets, newsfeeds, fraud, and security. Frankly, it's getting cluttered. I hope we can make the inside of the address bar as configurable as regular toolbars in a future release so users can put the star back in the address bar, should they want to do so.

FataL asks via e-mail, "why [writing] BAK files was broken in Opera 9?"
My best guess is that it's a bug. Unfortunately, I can't find any bug reports about this issue. Please file a bug report about this issue and I'll see if we can find out what caused this change.

I hope y'all enjoyed this edition of Tim's Opera Bits. Do you have questions still have questions about Opera Software? Ask away in the comments!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Note: Comments with a light blue background were made by the site owner.

Mail indexing.

the indexing back-end will be replaced, which will hopefully fix a long-standing and dreaded indexing corruption bug.

*cracks whip*

Get a move on! :P

I'll have to refine my Roadmap - later

Thanks for mentioning the thing or two about Opera10's M2:

Opera Mail: a) one of the most-debated wish list items will finally appear, and b) the indexing back-end will be replaced, which will hopefully fix a long-standing and dreaded indexing corruption bug

So the first thing I already guessed (I remember Jon mentioned HTML-Mail it in some interview a year ago) and the second one is simply great - hopefully I'll be able to use my drafts-folder again and get more reliable search results. :cool:

And I think I know one reason, why you (Opera) don't disclose information about future releases: you don't know yourself for sure, because it's released WIR. But as I have even less information it might be possible I made some good points in my Opera roadmap prediction. Now you gave me some hints to refine my prediction, but I'll do it later, when some additional not disclosed information is available :wink:

Widgetized Post is broken

I just realized that this post in the Widget has a very very long text area linked to Bits v3.0. :jawdrop:
It seems there is some problem in the HTML-source.

I was missing a closing A

I was missing a closing A tag. It should be fixed now.

Thanks !

Thanks for taking the pain of answering the questions in such detail.

Cheers :)

You're welcome!

You're welcome!

Core/Rendering improvements?

Excellent answers, thanks, Tim. I didn't ask you a question here, so I just put one of my wishlists here.
With Peregrine, I'd like to view all of CSS decorations at David's my.opera blog.

Please use the wishlish

Please use the wishlish forum or newsgroup instead in the future.

8.3 filenames

The Desktop Team prefers to continue to use the 8.3 format for filenames (maximum eight characters in filename and three characters in extension) because a) IE does and b) some programs still can't handle long filenames.

At least "a" not true. Internet Explorer 6.0 and 7.0 write long filenames. As for "b" I don't think there should be any significantly important application (if any) these days to stay with 8.3 anachronism. Anyone still use apps for Windows 3.1?!
I hope that in a close future I will not need other browser just to save web page with some meaningful filenames for images.

As do I. Feel free to file

As do I. Feel free to file a bug report about it.

I hope we can make the

I hope we can make the inside of the address bar as configurable as regular toolbars in a future release so users can put the star back in the address bar, should they want to do so.

Really great!