Flare
Mon 23rd Jul '01, 8:40pm
Been mildly keeping up with the spell check issues in regards to spellcheck.net and various other methods of spell checking.
At this point, here are the options as I understand them from reading the posts:
1. Discontinue spell checking all together (Which is essentially what Jelsofts position is right now)
2. Keep spell checking via spellcheck.net while it lasts
3. Jelsoft hosts it's own spellcheck.net type service for registered users (good idea, IMHO)
4. Jelsoft includes support for common spellcheck modules (Best option)
Now, it seems to me, seeing as option number one is what Jelsoft is going with, is counterproductive to the extreme.
Putting in support for Aspell/Ispell would provide the users that have the ability to install those modules access to a local spell checker. This is a good thing. Yes, it does indeed leave those on a hosted solution/technically unable/etc... out in the cold, but currently EVERYONE is out in the cold. It would seem that you'd be better off making SOME of the people happy than NONE of the people happy.
This would also prevent Jelsoft from adding the extra expense to host a spellcheck.net like solution, perhaps even paving the way for an additional 'pay-for-play' spellcheck type system for vB's, given the proper stubs installed in the vB code for off-site spell checking.
Additionally, as time passes and new spell check options come out, you could have it configurable in the control panel which spell check system is used. Those that can do it locally can configure thier server to look locally for the module. If spellcheck.net doesn't fold, or another service takes its place, it would be trivial to use one or the other (or both?) via the control panel.
There's really not much of a reason, aside from time / effort to put in an option for the Aspell (or similar) module in vB, if nothing else, put it in as an undocumented 'feature' for those technically inclined and/or curious/desperate enough to get the appropriate modules working. I can't imagine it would be terribly hard to add this feature to vB as it stands currently. I am not a terribly good PHP coder, but I feel confident I could do this myself with a bit of trial and error (and perhaps I will), but I would first like to petition Jelsoft to add this as a real feature in vB, instead of relegating it to 'hack' status.
At this point, here are the options as I understand them from reading the posts:
1. Discontinue spell checking all together (Which is essentially what Jelsofts position is right now)
2. Keep spell checking via spellcheck.net while it lasts
3. Jelsoft hosts it's own spellcheck.net type service for registered users (good idea, IMHO)
4. Jelsoft includes support for common spellcheck modules (Best option)
Now, it seems to me, seeing as option number one is what Jelsoft is going with, is counterproductive to the extreme.
Putting in support for Aspell/Ispell would provide the users that have the ability to install those modules access to a local spell checker. This is a good thing. Yes, it does indeed leave those on a hosted solution/technically unable/etc... out in the cold, but currently EVERYONE is out in the cold. It would seem that you'd be better off making SOME of the people happy than NONE of the people happy.
This would also prevent Jelsoft from adding the extra expense to host a spellcheck.net like solution, perhaps even paving the way for an additional 'pay-for-play' spellcheck type system for vB's, given the proper stubs installed in the vB code for off-site spell checking.
Additionally, as time passes and new spell check options come out, you could have it configurable in the control panel which spell check system is used. Those that can do it locally can configure thier server to look locally for the module. If spellcheck.net doesn't fold, or another service takes its place, it would be trivial to use one or the other (or both?) via the control panel.
There's really not much of a reason, aside from time / effort to put in an option for the Aspell (or similar) module in vB, if nothing else, put it in as an undocumented 'feature' for those technically inclined and/or curious/desperate enough to get the appropriate modules working. I can't imagine it would be terribly hard to add this feature to vB as it stands currently. I am not a terribly good PHP coder, but I feel confident I could do this myself with a bit of trial and error (and perhaps I will), but I would first like to petition Jelsoft to add this as a real feature in vB, instead of relegating it to 'hack' status.