Hi Bjørnar,
comments in-line...
Bjørnar Grip Fjær wrote:
> Hello,
>
>
>
>> For FSKEditor and MediaWiki, we took a look at that before venturing
>> down the path of making our own. Here are some of the things I saw on
>> the FSKEditor extension page that led us to our decision:
>>
>
> I assume this is a typo, and it's FCKEditor being discussed?
>
Correct, my mistake.
>
>
>> * On a per-page-basis: Do not add the token "__USE_EDITOR__" on an
>> existing page which contains standard wiki syntax. The fckeditor
>> removes line breaks which corrupts your page layout. (But don't
>> panic, the history function is always available.)The text is
>> stored as *HTML* in the database.
>>
>
> If you run $wgParser->parse(...) in the getContent function under
> includes/EditPage.php you can give the FCKEditor HTMLcode instead of
> Wikicode, so it doesn't mess up anything. This ofcourse gives you a
> table of contents etc as well, but that's easilly removed with a
> couple of preg_replace. It also removes the categories, which can be
> gathered with a preg_match before the content is parsed and appended
> or prepended (whichever you preffer) after the content is parsed.
> There's also the issue with templates, one way to do this is when you
> get the content before you parse it to HTML you use:
> $content = preg_replace('/({{[\w\d\ ]*}})/i', '<nowiki>$1</nowiki>',
> $this-mArticle->getContent());
>
>
>
>> * Removal of unwanted, hidden text properties can be a hard job in
>> some cases.
>>
>
> Do you have any examples?
>
>
>
>> * Using Netscape 7.1 browser, you cannot use the "browser page-back"
>> navigation function beyond a page, where the WYSIWYG editor was
>> invoked for page editing.
>> * /Paste/ function (pasting clipboard content) seems to be
>> prohibited - at least when using Netscape 7.1 browser.
>>
>
> Haven't had this problem with any other browsers.
>
All the comments above were from the FCKEditor description pages
themselves... so for examples, they would be the best people. :)
But in the note I just sent, we're going to talk to them more closely as
soon as Emil is back in Poland.
>
>
>> The biggest issue for us, obviously, was that it stored data as HTML.
>> However, I see this page created as of July 17th, 2007(
>> http://mediawiki.fckeditor.net/index.php/Main_Page ) that discusses it
>> storing wikitext, so we need to take another look.
>>
>
> A simple XML parser can parse the content to Wikicode before it's
> saved in the database. PHPs xml_parse should work fine.
>
This part is not so simple with all the cases the wikitext parser
handles. Brion, et al., were just talking about this and that to take
advantage of most existing tools there would need to be a fixed
grammar... but the current wikitext parser has lots of special handling
which presents such a fixed grammar beening easily developed. Not being
a wikitext parser expert... I'll take his word for it. The way that the
FCKEditor guys have done this is making a round-trip to the back-end to
run things through the parser... an approach we discussed for some other
wysiwyg code we had before we started working with the SocialText code.
I wish it were that easy (I really really wish it were that easy)... but
I don't believe it is.
>
>
>> Thanks,
>> John Q.
>>
>
>
>
_______________________________________________
Wikia-l mailing list
[email protected]
http://lists.wikia.com/mailman/listinfo/wikia-l
