This add-on is only good for web paged based spell checking.

It would be nice if Opera overhauled the spell checker to use this, and made it work with email. It would be also nice if it did the way firefox does, and puts squiggles under misspelled words.

Opera’s User JavaScript is extremely powerful, but besides for not having an active distribution system, unfortunately installing a script with a simple click of a button is still lacking. Since Opera doesn’t support the Firefox-like extension model, extending the browser’s functionality using User JavaScript becomes vital to developers, which is why Opera needs to make it easier for developers to distribute their scripts.

Yes! Exactly!

Not being able to use User-JS when JS is globally deactivated is the killer for this feature. They should be handled separately.

Mathias, I think you can disable “regular” JS with a UserScript and still be able to use other UserJS. See http://userjs.org/scripts/browser/enhancements/disable-script

Daniel Goldman wrote:

1) The main script didn’t pickup the changes preferences script. I had to manually change the script to turn off Gmail checking.

Did you remove the old script before installing the new one?

I’ve also not heard of it having trouble with the preferences script. Do you have your UserJS folder set globally?

Daniel Goldman wrote:

2) Why is the Gmail spell checker the default, if it requires a log on? The script needs to be simple.

The version at my site is set to use the server provided by fearphage, and not GMail, but it defaults to GMail if the preferences file isn’t there. I’ll go ahead and change it in the version on my site, so that it always defaults to the fearphage server.

Daniel Goldman wrote:

3) I think the spell checker should be enabled by default only for text areas, not input boxes. First, the image below small text boxes look horrible, and second, text boxes are normally used just for short input (such as your name, etc.), I don’t think spell checking it important there.

There are a few people who agree with you, but there are also people who find it frustrating when it doesn’t check text fields (and I sympathise with them). I’ll leave it up to d.i.z. and Sombria to decide if that option needs changed in the next version.

If you have any further problems, questions, or suggestions, then you can leave a post in the OSpell forum topic at the My Opera Community. That way you’ll get more than just me trying to help you.

IceArdor wrote:

Aspell works fine for me. It sounds like OSpell is still undergoing some improvements, so I’ll wait until it is more refined before using it.

Yes, OSpell is having a few issues in it’s current state. Most people don’t seem to be having trouble with it, but there do seem to be more issues with OSpell than with previous scripts.

As for me, I have 3 computers, 4 different operating system, and OSpell works fine on all of them. Granted that doesn’t mean that it will work fine for everyone…

http://www.tinyspell.m6.net

Simpler, easier, and checks everything you spell or copy.

1) The main script didn’t pickup the changes preferences script. I had to manually change the script to turn off Gmail checking.
2) Why is the Gmail spell checker the default, if it requires a log on? The script needs to be simple.
3) I think the spell checker should be enabled by default only for text areas, not input boxes. First, the image below small text boxes look horrible, and second, text boxes are normally used just for short input (such as your name, etc.), I don’t think spell checking it important there.

My $0.02.

Orangoo v3 didn’t work in the latest weekly builds, and it required xErath’s cross-domain XMLHTTPRequest script (which came in the ZIP file). OSpell is a single script that works very similarly to Amix’s script, but is smaller in size.

I think it’s also important to mention that Sombria (the creator of the Orangoo v1 UserJS) made OSpell with a little help from d.i.z. (who made the Orangoo v2 UserJS, based on Sombria’s original).

Opera’s User JavaScript is extremely powerful, but besides for not having an active distribution system, unfortunately installing a script with a simple click of a button is still lacking.

Not being able to use User-JS when JS is globally deactivated is the killer for this feature. They should be handled separately.