Sharepoint 2007 Wiki WYSIWYG editor

Well, that was a very underwhelming experience. First of all, the WYSIWYG editor doesn’t work at all in Chrome (or Firefox, or Safari, or any other web browser, besides IE). Second of all, these are the options I have after switching to IE:

So what do we have there?

  • Cut, Copy and Paste
  • Clear Formatting
  • Undo and Redo
  • Insert Table and 4 table maintenance buttons
  • Insert HTML link
  • Insert Picture
  • Edit HTML code
  • Font and Font size
  • Bold, Italic and Underline
  • Left, center and right alignment
  • Numbered and bulleted lists
  • Indent and Unindent
  • Text color, Highlight color
  • Left-to-right and Right-to-left

And this is what I have in the WordPress editor:

Which is:

  • Upload/Insert Image, Video, Audio, Media, Gravity Form (the last one through a plug-in)
  • Bold, Italic, Strikethrough (hey, no underline? Wait for it)
  • Bulleted and numbered lists
  • Quoted text
  • Left, center and right align
  • Create or break link
  • Insert “more” tag
  • Spellcheck toggle and language selector
  • Toggle for full screen mode
  • Kitchen sink switch (“on” to display the second row of icons)
  • Formatting (H1-H6, Paragraph, Address and Preformatted)
  • Underline (Ah!)
  • Align Full
  • Select Text color
  • Paste as:
    • Plain text
    • From Word
    • Remove formatting
  • Insert/Edit embedded media
  • Insert Custom character
  • Indent/Unindent
  • Undo/Redo
  • Help
  • Google Wave (through a plugin)

So, a free product like WordPress has very comparable features, and manages to work with pretty much every browser – no discrimination or Tier 1/Tier 2 distinctions. And on top of that, allows extensions to enhance and expand the standard toolbar.

There are so many WYSIWYG editors available, how come Microsoft decides to ignore half of the users in the world, even though they claim that in Sharepoint 2007 “new features such as wikis, blogs, and RSS would make us very attractive for Internet facing sites.” Not if you’re not supporting more than your own bug-riddled browser. And how about updating that functionality in the 4 years it has been out now, and the browser landscape has changed considerably?

Nice going, multi-billion dollar company. But since this is Microsoft, I’m afraid this will be our corporate standard… sigh…

We used Google Wave in a conference call…

… and were mildly impressed.

We set up an agenda before the call started, and used that as our base document. It was then filled out as we discussed the various points, and comments were posted to capture remarks, questions and clarifications.

A couple of observations:

  • If your participants don’t have a Google account, you can’t add them with their regular Email address (even though that is somehow linked to their googlewave.com account), but you have to use their googlewave.com address.
  • The Ribbit plugin didn’t work.
  • There is a reluctance to edit other people’s blips. It seems to be more “polite” to comment on the blip and say that something isn’t correct than to go in and just edit the blip to correct it. Cultural thing – I’m sure it will change once more people have used Google Wave or even a Wiki.
  • It’s hard to make a comment in the conference call, and record it in the wave at the same time. However, a conference call is far superior in hammering out a discussion quickly. Maybe a designated typer would be an idea in a conference call?

We didn’t run into any software problems. There were 5 people on the call and the wave, and we never saw a slow-down or a crash. The only disappointment was the Reddit plugin, but that was easily overcome.

I think Wave is still looking for a good application. Minutes and collaborative documents seem the most obvious application, but I have the feeling there are more exciting applications for the Wave technique in the future.