HTMLArea is a wonderful piece of web software. It takes any existing textarea field and converts it to an HTML enabled, easy-to-use, WYSIWYG text editing field. The interface is completely configurable, and you can even add custom buttons and actions to its toolbar.
Version 2 only supports IE, but the new version 3 (in beta) supports Mozilla as well. It’s been pretty good for me so far. In fact, I hacked bBlog to allow me to use it when editing posts (which made me dislike bBlog a little more) so I’m using it right now.
There are a few problems that I’ve seen. First of all, the link creation button is a bit hard to use. I figured out that you have to type the text for the link, highlight the text, and then press the button. However, if you happen to do this to the last word you typed, you have no way, that I can tell, of getting out of link mode. The same sort of thing happens with the bold button. If I press the bold button and then type, the text is bold. If I then press it again, the text stops being bold. If I then backspace over all of the bold text, I get locked into a loop where there is a bold place holder after everything I type. Additionally, when I hit ENTER twice, it should make a new paragraph. However, it inserts a line break and then closes the current paragraph and opens a new one. There doesn’t seem to be any of stopping it from doing this. But it only seems to do it for the first paragraph I type. Regardless, as long as I save all of the formatting for after I’ve finished typing, it seems to work pretty well. If (or when) these annoyances are fixed, I might enable HTML comments on revjim.net and use this to power them for those that don’t know HTML.
It has a few problems with the image locations for the buttons. It expects that the images will fall in a directory called "images" that is a child of the directory the page you are viewing is in. If this doesn’t happen, it doesn’t work so well. I had to modify the source code to make it work for me. There are a few plugins for it as well (table editor, spell checker, etc), but I haven’t got those to work. It’s most likely a pathing issue based on the same problem as the image issue.
Regardless of those things, it’s certainly worth a shot if you’re in need of something like this.