Starting from the Wiki module, I modified it to use the PEAR Text_Wiki package http://pear.php.net/package/Text_Wiki.

Does it make sense for other users?

IMO, it greatly improves flexibility, as the Text_Wiki package supports different wiki dialects. It is also easy to modify existing syntaxes to create new ones - hmm... if you really need it! But I saw people asking for this option... this could be a solution. Moreover, why not to reuse good, generic code which already exists?

I'm attaching my work here, if the integration with Text_Wiki sounds interesting for someone else. Note that, right now, the code is not very clean, it's just to give you an idea. It requires the tinymce module for wysiwyg editing. A function converts to/from XHTML. Maybe this should all be removed for making it more general. Apart from this, there's very little code left in the module. Text_Wiki makes all the work.

Do you think the original Wiki module could go this way, also?

CommentFileSizeAuthor
textwiki.module8.94 KBtomamic
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

highermath’s picture

Version: master » 2.x-dev
Issue summary: View changes
Status: Active » Closed (won't fix)

Obsolete