Okay, time to start rocking the FCKW plugin to extend into the wonderful world of wysiwyg posting. I had to have a CPAN module installed on the server in order for this to possibly work… that's cool.

Here's some links I'm working off of for this FCKW testing:

FCKW page FCKW installation instructions FCK Editor page (don't need this too much at the moment; but will need it for other software I'm developing.

Right now I'm ftping the plugin files up. It feels like it's taking forever. Interesting the way it requires a Perl module, isn't it? I was thinking about learning Perl. I've actually sat down with Perl books a few times over the years.

Okay, let's test it out. Okay, let me read the site…that didn't work.

Okay, cool, I got it to work. It has two folders: .svn + fckw … put both folders right in your plugins folder and voila!

Let's try to insert a picture:

Okay, that worked out pretty well….. we could hack around this interface some more too.

Things to change (let's me try an unordered list):

• Could use buttons for text size.
• Could stand to make return single space rather than double space by default.
• Seems like the image upload could have one less step.
• Seems like the ordered list text is too light
• Little bit of a delay when it first loads
• Could use a button to toggle between wysiwyg and wikitext
• Think there might be some sort of bug that I lost an image at one point after reediting + saving. Actually, I think that was an error on my part for not saving the draft.
• Spell check to highlight misspelled world like how FireFox rocks
• Yep, there is a little bit of jankiness going on when pictures are posted and then you go back to edit that page. No doubt about it. The wikitext gets rewritten a tiny bit… will have to look at this with Michael.

But, all things considered pretty cool!

Let's see what happens if I try to upload a really wide image that's wider than the site layout.

Okay, what it does is put in scrollbars. i can live with that. That's better than it breaking the layout. The other thing to see would be tacking on the crunch compression that WP uses when uploading.