On Mon, May 2, 2011 at 1:29 PM, Tim Starling tstarling@wikimedia.org wrote:
What about using a kind of document tree representation of wikitext? You could have an intermediate representation which precisely represents all of the source wikitext, but was easy to convert to displayable HTML. Kind of like HTML, but annotated to show which of the multiple options for HTML to wikitext transformation should be chosen on the return trip in order to preserve unchanged wikitext precisely.
That's what Wikia's editor does. It uses a subclass of the core MediaWiki parser to generate HTML-like output which is richly annotated with comments and custom attributes, allowing precise round-trip transformation of unchanged text.
The client side is not a generic HTML editor, rather it responds to UI events by editing the intermediate DOM representation, using code which is aware of the special structure of that document tree.
Maybe there are remaining round-trip bugs, but there's no obvious reason why they couldn't be fixed using this general approach.
Yeah that sounds good. I was unaware that Wikia had moved to this approach.
So that's what I know about the issues when introducing FCKeditor to an existing wikitext 'codebase'. I hear it's fairly decent when used from the start, but I'm not familiar enough with it to comment on that.
That's not what I hear. I hear that there were some teething problems, especially related to round-trip conversion, but that those were sorted out long ago.
By the way, it's not FCKEditor. The server side seems to have been rewritten from scratch by Wikia, and the client side has been extended and patched. RTE is probably a good name for it, since that's what they call it.
Well that just speaks to how ancient my experience with it is, I guess.
Roan Kattouw (Catrope)