On Sat, Jan 1, 2011 at 3:43 PM, David Gerard <dgerard(a)gmail.com> wrote:
On 1 January 2011 12:50, Magnus Manske
<magnusmanske(a)googlemail.com> wrote:
What I would like is some discussion about
* if this approach (working pseudo-WYSIWYG instead of unattainable
perfect WYSIWYG) is the way to go
The question is: can it be incrementally improved, new tags and ways
to deal with them etc, added as we go? Is it structured to make that a
reasonably straightforward thing to do?
I believe so, both for the parsing, where I actually have boolean
flags in the JavaScript to turn off, say, image parsing, which will
then just be rendered as wikitext, as well as for the display, where
the possibility of marrying my code to, say, the Usability
Initiative's template editor or multimedia assistant, has not escaped
me :-)
An easy example will be external links, which I just might implement
later today. Lists should be possible, tables a bit harder. HTML-like
tags, including <nowiki> and <ref>, are on the to-do-list, obviously.
Especially <ref>s could be collapsed like templates, which would again
improve readability significantly IMHO.
So, yes, I think this can deal with more current and future wiki
markup - no matter how complicated, it can catch the "safe" instances,
and just default to plain wikitext when in doubt.
Cheers,
Magnus