When I started using Opera 10.10 (the first Opera I ever installed), I was utmost thrilled by the GUI.
But (as with everything), as soon you start digging in stuff, you discover the bugs and the glitches.
I don't have a problem with a minor detail that can be fixed in a snap. I do the more when it considers core components like plug-ins not running properly. Mainly when you are a multimedia geek, you want your browser to play everything you feed it. Preferably, as soon as you installed it...
This blog will illustrate what my mission is and how tough it is to get to my target. Anything posted under PRO will reflect my desire to become an Opera evangelist. Anything posted under CON will reflect the downfalls encountered as I proceed towards my goal.
So here we go, enjoy the ride...
My Opera installed in a closed shell on a Windows running parallel on an Intel Mac seemed to be capable to pick up css, html and even exe files locally hosted on external volumes. This creates options for a whole new browser/multimedia experience. Now I can trigger .exe files with Opera to run inside an IE shell simultaneously, even on a Mac. Many of my shows were exported as .exe files in my formal XP life. Now I can enjoy these shows again to the maximum extent.
Opera side panels are ingeniously developed providing a new type of file management and system control options. The panels I created thus allow for quick reviewing where a file is stored, what it is about, what is related to, where it's css is residing etc.
When you run these locally hosted control panels, css residing on external volumes gets recognized by Opera 10.10. When you run the same url in Safari, it doesn't find that css. You don't need anything more to favor Opera.
The built-in rtf editor is very nice.
No plug-in add-on option is provided at download or installation. Presumably this results in an inability to run even the most common audio file like an mp3.
The last thing a novice Opera user wants to hear is he can file a bug report. A user enters a new scene hoping he/she will be able to enjoy a new browser experience equally, no, even better than the one he/she comes from.
Huge FAQ and/or help files are both a blessing as a curse. Seeing such elaborate knowledge base will freak out the people I would like to recommend Opera to. These people expect a problem free use of a new tool as soon they installed it. I can't assist a thousand people all running into the same problems over and over again.
If I contact a developer for whom a problem can be solved with the snap of one finger, I expect somebody to help a novice user thus encouraging him to dig deeper in the next best stuff. It's a small step to see a new user remove a just installed piece of software and never see him/her do it again.
You don't ask a novice user to help you if you haven't even offered help yourself yet.
Sharing code over the network seems to be impossible. As soon you hit the send button the mail interface translates that code to reflect an embedded file that is (obviously) not present. In other words: the receiver sees another message than the one you sent to be commented. I didn't find anything about aforementioned 'BB code' so far.
My first week @ Opera was a frustrating experience because of (presumably) a plug-in problem that could have been solved in just 5 minutes. Even though the size of my tags yelled for attention, I didn't get a hand at all. So I tried to sort it out myself but even after 72 hours of looking for an answer, I didn't manage to find one.
I am still an Opera believer but I wish the developers network itself would be more cooperative.