Wedge

I don't use it nor do my users AFAIK.

Plugin territory sounds about right (if there are requests for it). As stated before most if not all browsers have a spell checker anyway which I would think most people use over the forum's checker.

My only user who needs it actually uses Word to type his posts and leverage spellchecking. I guess to each their own.

If he's doing that, he doesn't need Wedge's spellchecking anyway because he's using Word's, right?

That's not so weird, actually. I know someone who always uses OpenOffice to write big emails out before copy/pasting them into their web-based email. It's just easier for them, apparently, though I have no idea *why* that's the case given that they're also a LiveJournal user and have no problem blogging directly into LJ.

I don't use it either. It's nice, but useless. I'd say ditch it. Discovered it somewhere in February 2011. Before: never missed it

He said its easier for him is all. I don't know of anyone who uses it-- even though it's pretty cool. But not very practical. Should be unlined really. Inlined.

I use my browser's spell checking if I use one.

Well, it's theoretically cool but it has issues. Firstly, it's not that well supported - and in future it's going to have to be reworked as PHP is dropping pspell support in favour of something else that I can't remember right now.

There is one thing it does do, though, that's cute: if it's enabled it'll spell check when searching and offer possible suggestions, but that can be integrated through the plugin (and should be, since it's still a pspell dependence, and mostly people don't even notice when it doesn't do it)

Hmm yeah, looks like direct support for pspell was dropped in 5.3 in favor of enchant... Which wasn't core before 5.3. Uh, so that pretty much rules out the possibility of using it in Wedge without hacks and such. Sucks... Unless we simply disable the spellcheck feature for PHP < 5.3.

Well, either we provide support for both in the core and do some magic to test it, or we move it all out of the core and let a plugin deal with it.

The greatest benefit about using plugins is that for stuff like this is that you get to isolate the functions and enhance them on their own without having to worry about everything else, which sounds ideal for this.

Yup, agreed...

Well, now is the moment where everyone says, "if AeMe doesn't handle avatars and attachments then it's better off as a plugin", I know I know :P (Except it'll do it... One day. Uh. Let's pray.)

Well, yes and no. There are quite a few limitations in the current attachment system, that can't be remedied without a significant amount of work - the quantity of which is probably not that far off what's needed to be able to use Aeva for attachments and avatars.

Which limitations? Apart from the one where you can't post attachments in PMs and they're 'stuck' to a post...

* No reasonable way to extend the system in any useful manner (e.g. the hurdles SD/WD have to do)
* Attachment folders are limited by size not number of files, and there's no automatic failover to a separate folder to prevent any given folder getting too big (in any case, the folder handling should not be based on linear progression, would be much better doing similar to what MediaWiki does, which encourages spreading files more equally by folder than simple progression does)
* Avatars are not in their own folder by default (frankly, I'm thinking about forcing them all to be in their own folder, and then ripping out the code that serves avatars through the system, there's really not a lot of reason to do so if avatars are tested against bad stuff up front)

spellchecker is enabled (not because it's needed, just because I was possible to activate the checker  :eheh:) for all of my forums but IMO it's not used widely.. I'm fine with it beeing a plugin.

IMHO the more "core functions" are made a plugin the better.. There are several other features which could be made a plugin instead of a build-in core feature, e.g. the calendar, the wysiwyg editor, personal messages, polls...