Well apart from the slight hiccup about not being able to see the .chm file due to IE7.0 security which is fixed by following this post.

One thing it did highlight is that using .wsp packages makes installing new features to the SharePoint platform childs play! The control in Central Administration of which web applications you deploy the package too is very nice. I even retracted the solution to see what the difference was between the RAD Editor and standard as it wasn't all that obvious!

What I didn't realise is that all this does is give you the ability to add a new Web Part which mimicks the basic Rich Text Editor Web Part with a Telerik one.

You can also activate them on a site wide basis to replace things like Item editing e.g.

to this:

It doesn't replace, for instance, when you create a new blog post the text editor area in that. To do this you need to follow these instructions.

to this:

The problem with this component, as with others, is that if you then want to stop using Telerik controls and use original MOSS components - you need then go back and roll out all the references to the template changes and also any web parts you are using.