Re: Wiki conversions
| From: | Justin Patrin | Date: | Thu, 05 May 2005 16:40:51 +0000 |
| Subject: | Re: Wiki conversions | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37502@lists.php.net to get a copy of this message | ||
On 5/5/05, Bertrand Mansion <bmansion@mamasam.com> wrote:
> Justin Patrin wrote:
>
> >I've made a preliminary TIkiWiki parser for Text_Wiki and CoWiki and
> >DokuWiki renderers. You can see them in action here:
> >
> >http://pear.reversefold.com/wiki/index.php
> >
> >Is anyone interested in this? Should I bother creating CoWiki /
> >DokuWIki parsers or a TikiWiki renderer?
>
> Hi Justin,
>
> Could you summarize quickly what makes tiki, cowiki, dokuwiki different from
> just wiki ?
Well, a wiki is (basically) just a quickly editable website.
Text_Wiki is a PEAR package for parsing and rendering Wiki syntaxt
(although it could do other syntaxes as well, such as BBCode). It does
not do any page storing and such, it is only a parser / renderer.
TikiWiki, CoWiki, and DokuWiki are all complete wiki packages which
you can use to put a wiki up on the web. None of them (currently) use
Text_Wiki. However, I used Text_Wiki for my project because its parser
/ renderer setup (and its general architecture) make it easy to do
translations. My intended purpose was to convert TikiWiki syntax into
DokuWiki and CoWiki syntax, which does work mostly right now.
CoWiki is a simple PHP5 wiki based around a plugin architecture.
http://cowiki.org/
DikuWiki is a simple PHP4 wiki which uses the filesystem for storage.
http://wiki.splitbrain.org/wiki:dokuwiki
TikiWiki is a *huge* system which is based around a wiki. It has
blogs, forums, image galleries, and all sorts of other stuff in it.
From looking at the code, it looks like it was grown instead of
planned and it has some structure as well as security problems. I used
it for a time, but my box was almost rooted because of it, so I
decided to switch to DokuWiki.
FYI I *may* have convinced some of the TikiWIki developers to use
Text_Wiki as their parsing / rendering engine in the future. They have
been looking to restructure their system for quite a while and
Text_Wiki already supports some of the features they wanted but
haven't gotten into their own system.
--
Justin Patrin