• NicEdit
• TinyMCE

Whilst a decision on which editor is the best for you’re project depends entirely on your own circumstances. I am only focusing on these two for now and don’t claim to be a master on either.

Downloading

There’s one thing that bugs me about the process of downloading NicEdit. It smells of the Mootools Javascript framework for one particular reason. There’s a range of additional extras and packages that are included in the download. The problem is that if you need to download it again for any reason. How can you be sure you include everything that you need?

I much prefer the editor to arrive as a complete core package, rather than it being a combination of various features. I feel that TinyMCE make it easier for you by offering the whole lot, even with a version designed entirely for the JQuery javascript framework.

Size

Looking at the downloads for each editor, I was impressed with NicEdit for having on single JS file and and sprite image for the buttons. Since CodeIgniter is super trim and lightweight, it immediately felt like the right thing to use. Some say that a full blown template library like smarty is overkill for CodeIgniter. I use smarty all the time in CodeIgniter, as such, perhaps TinyMCE is an acceptable size. Also, the TinyMCE folder structure includes a designated plugins directory. Which brings me onto my next topic.

Plugins

It’s clear for every developer that every wysiwyg editor needs to be customisable so it can meet its technical or design requirements. So the main questions are which offers the easiest integration and which offer the most power. I am afraid to confess that I have not written a plugin for TinyMCE yet so cannot comment on how it works out for that. However, I have been able to extend NicEdit quite easily. It’s possible to override the data that’s provided to buttons. For instance I have supplied my editor with a tree of available links and a library of images to choose from. I could post the code if the interest is there.

Documentation

There’s a wiki and a small section of demonstrations for NicEdit. The wiki includes some information about how to interact with it using plugins. But the content is limited. On the contrary, the TinyMCE api documentation is fantastic. I think those two points were the deciding factors in which wysiwyg to use for my CodeIgniter project. I wanted to pick it up and run with it. It felt like I could get everything done quicker using NicEdit as it was easier to digest. And thankfully. it all worked straight away.

Conclusion

I am yet to determine if it’s possible to isolate the cursor position within the content. That would be helpful for a range of tasks, like image insertion from an alternative source. I am happy with using NicEdit for now, it suites my needs. However, I am really worried that I will need a feature that it does not support. Even worse, it does, but was not downloaded with the package included.

Given that the existing home page has to remain the same until your ready to “activate” the new one. You can modify the .htaccess file so the Wordpress site will only respond if the homepage has been called with a particular query string. This means you can test the Wordpress build without interrupting the main index page.

In order to do this, you have to modify your .htaccess file in the website root. Below is the modified .htaccess file, take a backup before testing!


# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/wp-content/
RewriteCond %{REQUEST_URI} !^/wp-includes/
RewriteRule . /$1/?test=true [L]
# END WordPress


Replace your existing .htaccess file with the code above and you are half way. Next modify your index.php in the wordpress site.


if(isset($_GET["test"])){
define('WP_USE_THEMES', true);
/* Loads the WordPress Environment and Template */
require('./wp-blog-header.php');
}else{
/* Your holding page HTML / include file */
}


You can redirect to, or include the existing index page within the else clause as described above. The links should still be intact because the .htaccess file is appending your url with the required query string.

So when you visit the site your existing homepage should remain the same. When you visit http://yoursite.com/?test=true your wordpress site should wake up and run accordingly.