Categories
Asides

AJAX Spell Checker

This AJAX spell checker seems pretty interesting and functions a lot like Gmail’s. Has anyone written a plugin using it yet?

27 replies on “AJAX Spell Checker”

okay I have it working, nicely written by broken-notebook – but it requires some editing of admin files atm :/ Is there a way to append an onsubmit to the edit and and onFocus to the textarea? (can’t find it on the codex..)

You’d need to start an output buffer and then edit the HTML. Check out how my WYSIWYG plugin does this for guidance.

Okay, and so I have “made” my first wp plugin. fxsp.tbz (its about 10k) – this is ALPHA and really messy. I have to go to work now and its pretty early, but hopefully someone will post some useful (and more intelligent) suggestions/code and I’ll finish it up all nicely later on.

Thanks for the help with the buffering Matt, nice trick.

There is a small readme, but basically just
cd wp-content/plugins && tar yxvf fxsp.tbz

then enable it in the plugins page. Plz note no feedback is going to be ignored, as this is a first :/ Also any users please don’t post about it yet, I’ll make a post here once I’ve released it

p.s. I hope you don’t mind me posting it here Matt, I’m pretty sure more intelligent people read your blog than mine atm though 😉

No problem at all! Why don’t you send a request from wp-plugins.org and I’ll set you up a repository so you can track the changes being made to the plugin. It would also give you an automatically generated ZIP download.

[…] When I woke up this morning I read Matt’s post about the AJAX spell checker and him asking if anyone was going to write a plugin – this sounded like a good opportunity to learn about WP plug-ins. So I’ve written it now and basically it adds spell checking support your WordPress write post page, using AJAX (no refreshing). Its quite nifty but its very beta at the moment and I’m about to check it into svn over at wp-plugins -> fxsp. […]

Groovy, you might want to try tweaking the code so the include (use include instead of require) and the ob_start hack are only triggered on the pages they should be within wp-admin.

Nice work, Dave! Some suggestions though (you said we could post them, right? ;)) Why not use single quotes for your PHP coding? They’re faster than using double quotes, and much easier to work with in situations like:

function fxsp_script() {
 echo ("
  <script src="/wp-content/plugins/fxsp/spell_checker.js" type="text/javascript"></script>
  <script>");
  sajax_show_javascript();
  echo ("</script>");
}

How about this instead?

function fxsp_script() {
 global $siteurl;
 echo '<script src="' . get_settings('siteurl') . '/wp-content/plugins/fxsp/spell_checker.js" type="text/javascript"></script>
  <script>");
  sajax_show_javascript();
  echo '</script>';
}

Anyway, you’re doing a great job. Ajax rocks. This script rocks. WordPress rocks. This plugin rocks. You rock.

It might be a good idea to try to solicit funds for setting up a fund to do bounties for those who complete such a feature. I’ve probably donated about $20-$30 and would be willing to give up another $20-$30 for such a fund even though I’m a poor college student.

Comments are closed.