Mario was asking in
this post why should we use a wiki instead of a word processor (WP), and I realized we didn't give too many reasons for the suggested approach.
To be honest,
FCKeditor would be my candidate for the Word Processing app, by two main reasons:
- Features set
- Recent announcements of Adobe and Oracle support
But then I think reality dictates...
Create content, not designWhen working on a company, most of the time you should follow the company guidelines for Document formatting. Font family, style, header size, alignment, etc., should be dictated by the company, and workers should simply adhere to that, and not waste time 'crafting' a document each time they work on it.
If you use a wiki, then you already know it is much faster to create a document than to use a Word processor.
Collaborating needs versioningThe Web Office is about collaborating. And when a single document is the work of a team, you need revision and version history. Most popular Open Source Web (OSW) wikis already deal with that. Word processors don't.
MaturityWikis are, at this stage, more mature than OSW Word processors.
You can embed a WP in a WikiFinally, I think that you could embed a Word Processor in a Wiki. Just like adobe is probably doing. Kind of what google does when you are writing an e-mail in gmail. That, I think, is the trend.
Wouldn't it be great to always use the same word processing toolbar, be you writing a blog post, a forum post, an e-mail, or a document? And, depending on the circumstances, you could chose between the complex or the simplified version.
And moreAnd, as usual, what I am missing. That's why your opinion is important. What arguments have not been discussed?