Opera 10.50 Beta 2 released

[simonlang]

Navigate to

%appdata%\Roaming\Opera

Copy everything from inside the "Opera 10 beta" folder into the "Opera" folder, over write everything if necessary.

Remember to backup.

thanks! it worked. :D

now did opera change the navigation thing from beta2 to rc?

the beta2 was showing thumbnails like the win7 explorer does if you have several windows open. i liked that so much better! any way to get this back?

[tom01]

Meh, it's a lot more buggier than the last build. Facebook's being an ass with the wand. Divx plugin is still crashing and I want the transparent inactive tabs back. :crazy:

[Mike]

the beta2 was showing thumbnails like the win7 explorer does if you have several windows open. i liked that so much better! any way to get this back?

That's how windows does it when you have too many thumbnails to fit in. If the thumbnail size becomes too small it uses a list - standard windows thing.

Meh, it's a lot more buggier than the last build. Facebook's being an ass with the wand. Divx plugin is still crashing and I want the transparent inactive tabs back. :crazy:

The transparent inactive tabs didn't work if you had a black wallpaper :p

[JOHW]

The RC is out

Opera 10.50 RC for Windows

You might have noticed that the 10.50 snapshots contain a lot more changes and fixes than usual. This is the result of our increased focus and has sped up the development process significantly.

Thanks to the hard work of the Opera engineers Opera 10.50 for Windows has now reached RC status.

We hope you like the new speed of development because we plan to work as hard to finalize 10.50 for Unix and Mac.

Video seeking

This build build mainly includes stabilization fixes, but also a new feature in (html5) video: It's now possible to seek through videos that are not completely downloaded yet. If you skip forward in a video, Opera will adjust the download process so you don't have to download the part that you are not going see.

Downloads

Windows MSI / Windows Classic

Changelog

Desktop/UI

DSK-283685 Replying mail crashes Opera

DSK-283731 When replying to mail, I don't get the "X wrote:" header

DSK-283274 Appearance dialog does not have focus when opened

DSK-283890 History item deleted

DSK-279350 Page not unloaded when going back to speeddial (including favicon)

DSK-283507 About This widget has clipstring while hovering (PL)

DSK-282166 Fix for potential memory leak in context menus

DSK-284053 Tab bar background isn't fully repainted when window is activated/deactivated.

DSK-283958 Right click option "Inspect Element" crashes Opera

DSK-284052 Setting an image on a Web page as Speed Dial background using the context menu causes Opera to crash

Core

CORE-28188 crash on florawww.eeb.uconn.edu

CORE-27636 NOSCRIPT after FRAMESET not working as expected

CORE-28205 Crash fix when a color transform filter gets invalid values

CORE-28203 Fix for privacy mode crash

DSK-284020 Crash in vega

DSK-283965 Crash on save cookie

DSK-283966 Can't click any links on aftenposten.no

DSK-283959 Video has stopped working

Several other stability fixes

[simonlang]

That's how windows does it when you have too many thumbnails to fit in. If the thumbnail size becomes too small it uses a list - standard windows thing.

i closed a few and the thumbnails are back. :blush:

[.Neo]

Opera already has a cross-platform solution for spell checking in place. It would probably take longer to use the system's UI. Doesn't it use the system dictionary, though?

On Mac OS X most services like Dictionary, spelling and the Aqua interface are already extremely well done. Developers like Opera and Mozilla are reinventing the wheel with their own counterparts that most of the time aren't as good or polished. Opera's "Aqua" interface is still a slapped on skin that appears similar to the real deal (except for the tons of little quirks everywhere) but actually feels very different when using it.

[PreKe]

Developers like Opera and Mozilla are reinventing the wheel with their own counterparts that most of the time aren't as good or polished.

Sorry, but you are confused. They are not reinventing the wheel at all. They are reusing the existing cross-platform stuff they use on other platforms. Reusing something is exactly the opposite of reinventing the wheel. Whether you think this or that is better is irrelevant to your claim about reinventing the wheel.

Opera's "Aqua" interface is still a slapped on skin that appears similar to the real deal (except for the tons of little quirks everywhere) but actually feels very different when using it.

Opera for Mac is still on its first beta, right?

[Elliott]

Opera for Mac is still on its first beta, right?

From prior experience with both Firefox and Opera, it won't fully work like a real OS X application. They just don't care enough.

[PreKe]

From prior experience with both Firefox and Opera, it won't fully work like a real OS X application. They just don't care enough.

Yeah, they care so little they just rewrote everything to use Cocoa. That's how little they care.

[DavidM]

Navigate to

%appdata%\Roaming\Opera

Copy everything from inside the "Opera 10 beta" folder into the "Opera" folder, over write everything if necessary.

Remember to backup.

Thanks, that worked like a charm.

Meh, it's a lot more buggier than the last build. Facebook's being an ass with the wand. Divx plugin is still crashing and I want the transparent inactive tabs back. :crazy:

Mine are transparent, but look blue with my black wallpaper. I don't use facebook, but my divx plugin seems to be working fine.

[Elliott]

Yeah, they care so little they just rewrote everything to use Cocoa. That's how little they care.

I should've worded that better. It's not really that they don't care. It's really that they just don't get it. Google, Opera, and Mozilla all make the same mistake: they want to do the same stuff they do on Windows and Linux on OS X. The problem is, OS X users have a certain feeling they expect from their apps, and just porting something from Windows or Linux doesn't work.

And trust me, rewriting something in Cocoa doesn't automatically make it better. I know the rewrite isn't complete, but Opera is still the same old clunky thing it's always been on OS X.

[ViperAFK]

Translation: OSX users are ridiculously picky.

Opera looks more native on OSX than it does on windows. It looks fine. Just because it doesn't conform to every little OSX specification doesn't make it horrible and clunky.

Now if you want to see ugly look mat the Linux version.

[PreKe]

Google, Opera, and Mozilla all make the same mistake: they want to do the same stuff they do on Windows and Linux on OS X. The problem is, OS X users have a certain feeling they expect from their apps, and just porting something from Windows or Linux doesn't work.

They aren't "just porting". They are rewriting huge parts of their code just for OS X.

And trust me, rewriting something in Cocoa doesn't automatically make it better.

It makes it faster, and it's easier to integrate.

I know the rewrite isn't complete, but Opera is still the same old clunky thing it's always been on OS X.

Hardly.

What's interesting is that Apple keeps violating its own GUI guidelines, but you never hear anyone complain about that.

[.Neo]

Sorry, but you are confused. They are not reinventing the wheel at all. They are reusing the existing cross-platform stuff they use on other platforms. Reusing something is exactly the opposite of reinventing the wheel. Whether you think this or that is better is irrelevant to your claim about reinventing the wheel.

I'm pretty sure that Mac OS X had system-wide spell check before Firefox, Opera and Chrome implemented it. In my book that's reinventing the wheel on that OS. You don't see most other applications, like Skype, on Mac OS X use their own custom spell-checking services. Nope, instead they use the system default.

They aren't "just porting". They are rewriting huge parts of their code just for OS X.

Yet they all fail in the interface department.

It makes it faster, and it's easier to integrate.

Opera nor Firefox integrate into Mac OS X very well and they're both largly "rewritten" in Cocoa.

What's interesting is that Apple keeps violating its own GUI guidelines, but you never hear anyone complain about that.

Are you kidding me? Mac forums are filled with complaints about the fact iTunes uses a custom interface compared to the rest of the OS... So if you really think that your either blind or just didn't bother looking before posting this reply.

[PreKe]

I'm pretty sure that Mac OS X had system-wide spell check before Firefox, Opera and Chrome implemented it.

That's irrelevant because they still needed it for other platforms. So they are merely reusing existing technology.

Yet they all fail in the interface department.

It's a beta. Do Mac fans not understand the concept?

Opera nor Firefox integrate into Mac OS X very well and they're both largly "rewritten" in Cocoa.

It's a beta. Do Mac fans not understand the concept?

[Elliott]

That's irrelevant because they still needed it for other platforms. So they are merely reusing existing technology.

But why not use standard controls on an OS that has them?

It's a beta. Do Mac fans not understand the concept?

Mac users are largely used to very high quality betas, but that's because Mac developers take time to make their products good. Opera has consistently pushed out awful products for OS X, so sue us for being a little skeptical (especially with the current proof that's been given to us).

[.Neo]

That's irrelevant because they still needed it for other platforms. So they are merely reusing existing technology.

They can (re)use the existing technology on Mac OS X provided by Mac OS X. Apple didn't put it in there just to sit and be pretty. And like I said, Skype is a perfect example of an application that's available on multiple platforms, it doesn't use custom stuff on the Mac.

It's a beta. Do Mac fans not understand the concept?

Firefox isn't in beta, nor is Chrome and I seriously doubt Opera 10.5 will suddenly spot a fully native interface when it hits final.

[PreKe]

But why not use standard controls on an OS that has them?

Maybe because there are other more important things to fix, and maybe it's fine to have something that just works in the meantime?

Mac users are largely used to very high quality betas

:laugh:

They can (re)use the existing technology on Mac OS X provided by Mac OS X.

They reused something else instead. And it isn't even a final version yet.

And like I said, Skype is a perfect example of an application that's available on multiple platforms, it doesn't use custom stuff on the Mac.

Skype is trivial compared to a full browser. Browsers are infinitely complex.

Firefox isn't in beta, nor is Chrome and I seriously doubt Opera 10.5 will suddenly spot a fully native interface when it hits final.

This is a thread about Opera. Opera for Mac is in beta.

[ViperAFK]

They can (re)use the existing technology on Mac OS X provided by Mac OS X. Apple didn't put it in there just to sit and be pretty. And like I said, Skype is a perfect example of an application that's available on multiple platforms, it doesn't use custom stuff on the Mac.

Firefox isn't in beta, nor is Chrome and I seriously doubt Opera 10.5 will suddenly spot a fully native interface when it hits final.

You completely ignored what he said. They still need spellcheck on windows and linux so they have to make their own anyway. Think as a programmer. Why should you have to do more work to use OSX's spellcheck when you can use what you ALREADY HAVE and works fine?

[Elliott]

Maybe because there are other more important things to fix, and maybe it's fine to have something that just works in the meantime?

The point is they'll never change it because they don't have to. Maybe they'll completely defy their history and prove me wrong, but I doubt it.

:laugh:

Not sure why you're laughing. I've used countless OS X apps that called themselves "betas" and yet were just as stable as their final products. A few quirks here and there, obviously (betas are betas), but nothing like completely stalling while trying to render a damn page or crashing because you just tried to access the preferences.

They reused something else instead. And it isn't even a final version yet.

It's just an example. They may be using Cocoa, but very few of the controls are native elements. Seems like they might've missed the point.

Skype is trivial compared to a full browser. Browsers are infinitely complex.

No, rendering engines are infinitely complex. Browsers are, but not to the level of the engine. WebKit manages to be a very cross-system-compatible rendering engine (using native widgets and the features of each OS). Presto doesn't make that effort (being closed source doesn't help).

You completely ignored what he said. They still need spellcheck on windows and linux so they have to make their own anyway. Think as a programmer. Why should you have to do more work to use OSX's spellcheck when you can use what you ALREADY HAVE and works fine?

Having a global dictionary and grammar and spell checker is only good if apps use it. "Oh, let me retrain this one app because some devs said this was good enough." Seriously?

It also extends to other features of OS X. For instance, if they don't use native widgets, they can't use the Services infrastructure that was revamped in 10.6 (hell, they can't even use the old one).

[ViperAFK]

The point is they'll never change it because they don't have to. Maybe they'll completely defy their history and prove me wrong, but I doubt it.

Not sure why you're laughing. I've used countless OS X apps that called themselves "betas" and yet were just as stable as their final products. A few quirks here and there, obviously (betas are betas), but nothing like completely stalling while trying to render a damn page or crashing because you just tried to access the preferences.

It's just an example. They may be using Cocoa, but very few of the controls are native elements. Seems like they might've missed the point.

No, rendering engines are infinitely complex. Browsers are, but not to the level of the engine. WebKit manages to be a very cross-system-compatible rendering engine (using native widgets and the features of each OS). Presto doesn't make that effort (being closed source doesn't help).

Having a global dictionary and grammar and spell checker is only good if apps use it. "Oh, let me retrain this one app because some devs said this was good enough." Seriously?

It also extends to other features of OS X. For instance, if they don't use native widgets, they can't use the Services infrastructure that was revamped in 10.6 (hell, they can't even use the old one).

But again Opera simply has no need to use it. Opera is cross platform, they already had to implement their own spell checking feature, it would be a rather pointless waste of time to implement OSX's spellchecking which does the exact same thing.

I do agree it is always nice if they use native widgets, in windows vista/7 I dislike the use of non native menus, but the spell checking thing seems like a weak and pointless argument.

[Elliott]

But again Opera simply has no need to use it. Opera is cross platform, they already had to implement their own spell checking feature, it would be a rather pointless waste of time to implement OSX's spellchecking which does the exact same thing.

I do agree it is always nice if they use native widgets, in windows vista/7 I dislike the use of non native menus, but the spell checking thing seems like a weak and pointless argument.

It's one of many things that compound on top of each other. I'm only trying to give my critique, and I've even sent Opera feedback and bug reports. I'm trying to make it better, but, like you said, it's a cross platform browser so they probably won't care that much, just like Apple doesn't care that much about Safari on Windows.