0 Comments

Just this moment, I am writing this sentence in a rich text editor here on my blog. It let’s me format text, insert images, tables and a lot of other great stuff as well. I can do bold or italic fonts, which helps clearing up the text and underline my point and what not.

I do have a lot of years of experience in using these kinds of online text editors like RichTextBox and FCKeditor. In fact, I build my own 3 years ago. I spend a lot of hours perfecting it, but even then, it only worked in IE and it was error prone. Writing massive amounts of JavaScript and make it work is incredibly difficult. I take my hat off for people who do that for a living. I couldn’t. Nor would I ever do it again. I lost too many nights of sleep on that account.

What are really cool about these kinds of editors, all kinds, are also the things that make them bad. And I mean really bad; to the point where they suck and I want to stop writing because of the bad editor. That’s not true, because I know how to use them. I use my knowledge about HTML to do tables and float images to the left or right in CSS. To do the floating of images I have to switch from regular WYSIWYG layout to HTML code layout. Then I manually add the style attribute to the image and make it float to the left. Could my mother do that? No chance. Could yours?? I doubt it.

For me as a web developer I have no problem switching between design and code view. But the average secretary has. She is used to Word and also know how to insert images and tables. She is an intermediate user of Word; in fact she is a little better. She also knows how to make hyperlinks and header formatting. When she sees the online rich text editors with their Microsoft Office style buttons and menus, she finds herself at home right away.

What she didn’t realize is that the online editor is nothing like Word. It looks like Word, but under the hood, a whole different ballgame is in play – HTML. She cannot place an image wherever she wants, text wrapping isn’t working and I could go on.

I’ve worked a couple of years developing content management systems, and the online editors were always a weak spot for the reasons I just mentioned. What the end customer wants is Word. Not an online editor, but Word. They know it very well and they feel at home.

Then I was thinking about the new Visual Studio Tools for Office (VSTO). Using these tools, it is possible to create a Word document with a direct link to a web service – it could be your blog engine or CMS system for that matter. Instead of using the online editors for editing blog posts, we could use Word. Think of the added benefit your customers would get when they can stay in their favourite text editor to create their HTML content? They probably write their content in Word before copying it to the online editor anyway.

It actually sounds too good to be true so why haven’t anybody done it already? Maybe they have and I just don’t know about it yet. Then why not make it my self? Well, I don’t think it is that easy to implement in an existing CMS/blogging application. If it is a CMS, you still need the online editors for people that haven’t got Office 2003 and .NET Framework 2.0 installed. On the other hand, I estimate it to be a fairly straight forward task, with little surprises for the experienced programmer. Of course, it also depends on the amount of functionally you want as well as the overall scope of the project.

The added benefits you gain from this have potential. After all, it let’s your customers use what they believe to by the one true text editor.