Category: Software

Posted on
by

Since I’ve been using Opera a lot more than usual since Opera 9 Preview 2 came out, I’ve repeatedly run into the canonical reason that sharing one button for stop/refresh is a bad idea: Reaction time.

When a button changes in response to your own actions, it’s easy to adjust. When a button changes in response to something over which you have no control, there’s a possibility that it may change between the time your brain tells your finger to click on the mouse button and the time it presses down, registering the click with the computer.

Case in point: A web page is loading slowly. You’ve already seen the part you’re looking for, and you don’t need the rest of the images, or the rest of the 587 comments on the blog post. Maybe all you needed to do was confirm you had the right site, and you need to copy the URL. So you go to hit Stop. The web page finishes loading before your finger finishes clicking, the button changes to Reload… and the browser starts reloading the entire slow page from byte one.

I’ve done this at least four times in the past week.

The bad news: I can’t find separate stop/reload buttons anywhere in Opera’s button collection. The closest I could find seem to apply only to panels, not to browser views.

The good news: The Custom Buttons page at NonTroppo.org has them!

Once I get these on all the computers where I normally use Opera, accidental reloads should be a thing of the past!

*This post originally appeared on Confessions of a Web Developer, my blog at the My Opera community.

Posted on
by

The Opera web browser has introduced a Dashboard-like Widget feature in Opera 9 Preview 2. I believe this is the first 3+ platform widget framework out there.

Dashboard is, of course, Mac OS X only. Yahoo! Widgets (formerly Konfabulator) is Windows XP and Mac OS X only. The KDE Desktop (mostly used on Linux and *BSD) has plans to include floating applets in KDE4’s revamped desktop, Plasma. Opera runs on Windows, Mac, Linux, and a number of other platforms.

Opera’s taken a very similar approach to Apple’s. A widget is a bundle of HTML, CSS, and JavaScript. The most obvious difference is the structure of the bundle: Continue reading →

Posted on
by

Opera BrowserOpera Software celebrates its 10th anniversary today with an online party and free registration codes for a day.

I first discovered the Opera web browser in college, probably 1998 or back in 1999. A friend who worked with me at the Artslab showed it to me, and I was impressed by how fast it was and that the installer fit on a floppy. Opera was shareware only back then, with a 30-day trial period, and I had no objection to paying the $15 or $20 $18 it cost with a student discount. (I remember scanning my student ID and emailing them a JPEG to prove I was a student.)

By the time Y2K rolled around, Netscape 4 was showing its age, and Mozilla was still early in its development cycle. IE—well, IE had won the browser war, and was arguably better than Netscape at this point, but as far as I was concerned they had cheated to do so instead of winning solely on merits. Opera was a lean, mean browsing machine.

Things changed during 2000, though. Opera 4 and 5 started getting cluttered, and Mozilla was starting to stabilize. Side projects like Galeon started branching off of Mozilla. Pretty soon I was using Mozilla all the time on Windows and Galeon on Linux.

I kept up with new releases, though, and the latest version of Opera is excellent—on both Windows and Linux. I mostly use Firefox these days, but I’m using Opera a lot more than I used to—and not just for testing!

Check out Opera, grab a free reg code while they’re still available, or just drop in on the party.

Seen in rounds at WaSP Buzz, Slashdot, and Opera Watch.

Also interesting: the Opera 10th Anniversary T-Shirt reminded me of Joi Ito’s comments on wearing Firefox (via a*dot). I wonder how people would react if I wore a Firefox shirt and an Opera hat, or vice-versa?

(Other notable tens this August: Windows 95 and Internet Explorer)

Posted on
by

The new Opera 8.0.1 includes an experimental feature called Browser JavaScript. It’s a collection of client-side scripts that automatically corrects known errors on websites as they’re displayed. Opera downloads updated scripts once a week.

It’s an extension of the User JavaScript concept. Firefox’s Greasemonkey is basically the same thing, and it’s gotten a lot of attention as a method for correcting or enhancing sites. The key difference is that these scripts are centrally maintained, and automatically updated.

Browser JavaScript is disabled by default, and can be turned on by putting Browser JavaScript=1 in the [User Prefs] section of your opera6.ini file.

(via Opera Watch)

Posted on
by

FirefoxFollowing up on my comments on Opera, Firefox supporters have a major blind spot as well. It has to do largely with the heavy emphasis on web standards among the developers and the early adopters, and the ideals of the open source/free software community. There are a lot of websites out there that don’t look quite right on anything but Internet Explorer, and there are sites out there that just plain don’t work in anything but IE. This is largely due to three facts:

  • There is a lot of broken HTML out there that has only been tested on IE, and the designers relied on IE’s particular error-recovery behavior.
  • There are sites that rely on ActiveX or other IE-specific code without providing an alternative.
  • There are sites with bad browser-detection logic that deliberately exclude other browsers, regardless of whether they would otherwise handle the site.

In each case you can either change the browser to handle the websites, or you can change the web to handle the browser. Both approaches are difficult, and while the former often yields more immediate results, the latter is more ideal, because it benefits users of all web browsers. In most cases Opera has chosen to adapt the browser, while Mozilla has chosen to promote standards for web development. Continue reading →