Differences between revisions 1 and 7 (spanning 6 versions)
Revision 1 as of 2003-09-17 18:13:32
Size: 2880
Editor: pcp02530593pcs
Comment:
Revision 7 as of 2003-11-09 02:15:17
Size: 3681
Editor: pcp02530593pcs
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 * MoinMoin -- A PythonLanguage SourceForge project, based on PikiPiki (VNIHF)  * MoinMoin -- A PythonLanguage SourceForge project, based on Wiki:PikiPiki (VNIHF)
Line 10: Line 10:
 * Wiki:PikiePikie -- Python-based, lets you put a '''WebLog''' on any page (based on PikiPiki)  * Wiki:PikiePikie -- Python-based, lets you put a Wiki:WebLog on any page (based on Wiki:PikiPiki)
Line 12: Line 12:
 * Wiki:WikiForNow -- a ZwiKi variant; used at zope.org  * Wiki:WikiForNow -- a Wiki:ZwiKi variant; used at zope.org
Line 14: Line 14:
 * Wiki:WyPy -- a ShortestWikiContest contender, 23 lines
 * Wiki:ZwiKi -- ZoPe-based, powerful, GPL.
 * Wiki:WyPy -- a Wiki:ShortestWikiContest contender, 23 lines
 * Wiki:ZwiKi -- Wiki:ZoPe-based, powerful, GPL.
Line 20: Line 20:
||Cache Pages for Faster Loading?||no|| || || ||
||Store Pages in Database or as Files||flat files|| || || ||
||Support for Blogs ([http://ourpla.net/cgi/pikie?WikiWeblogs WikiLogs])||[http://www.seapig.org/BlogEditCode partially]||yes|| || ||
||Page Permissions||no|| ||yes||
||Templating/Page Skins/CSS support||no||yes|| || ||
||Cache Pages for Faster Loading?||not yet|| || || ||
||Page storage||flat files|| ||ZoDb|| ||
||Support for Blogs ([http://ourpla.net/cgi/pikie?WikiWeblogs WikiLogs])||[http://www.seapig.org/BlogEditCode partially]||yes||[http://webseitz.fluxent.com/wiki/ZwikiCustomizations possible]|| ||
||Page Permissions||CVS version: yes|| ||yes||
||Templating/Page Skins/CSS support||no||yes||yes|| ||
Line 26: Line 26:
||Allowed HTML tags||no|| || || || ||Supports HTML tags||no|| ||yes || ||
Line 31: Line 31:
Comment: "Support HTML tags" is more of an anti-feature in wiki.
Line 33: Line 35:
Elements for building a full-featured wiki engine:
 * ''Page templating system like [http://smarty.php.net/ Smarty].'' Possible options include [http://www.alcyone.com/pyos/empy/ EmPy] or others listed at WebProgramming [http://www.python.org/cgi-bin/moinmoin/WebProgramming#head-9d0636d6da8e88f8f09de1454c5961b44183b04d here]. Which one would you recommend?
 * ''Cache HTML versions of pages for faster loading.'' Ideally the page templating tool would handle cacheing.
== Elements for building a full-featured wiki engine: ==
 * ''Page templating system like [http://smarty.php.net/ Smarty].'' Possible options include [http://www.alcyone.com/pyos/empy/ EmPy] or others listed in the [http://www.python.org/cgi-bin/moinmoin/WebProgramming#head-9d0636d6da8e88f8f09de1454c5961b44183b04d templating section] of the WebProgramming page. Which one would you recommend?
 * ''Cache HTML versions of pages for faster loading.'' Ideally the page templating tool would handle caching.
Line 41: Line 43:
Line 43: Line 46:
=== Arguments that MoinMoin is a candidate ===

  * in a really dynamic context like wiki, you can't simply cache the HTML.
   * There are parts of the page that definitely can be cached. And most wiki pages do not use any dynamic macros.
  * Moin has user / password auth in CVS. Groups and page ACLs also.
  * Database integration is more of an anti-feature, see the next 2 points.
   * The best tool would have ''flexibility.'' Be able to run standalone with an easy install, or integrated with Apache and a fast database server. In PHP, this is incredibily simple if you use ADODB or PEAR.

List

Here is a list of known Python-based WikiEngines.

Comparison of Features

Existing or Desired Features

MoinMoin

PikiePikie

Zwiki

add others here

Cache Pages for Faster Loading?

not yet

Page storage

flat files

ZoDb

Support for Blogs ([http://ourpla.net/cgi/pikie?WikiWeblogs WikiLogs])

[http://www.seapig.org/BlogEditCode partially]

yes

[http://webseitz.fluxent.com/wiki/ZwikiCustomizations possible]

Page Permissions

CVS version: yes

yes

Templating/Page Skins/CSS support

no

yes

yes

Link icons, colorblind-friendly

yes

Supports HTML tags

no

yes

export RSS

recentchanges only

import/display RSS

no

add feature here

Comment: "Support HTML tags" is more of an anti-feature in wiki.

Comments, Ratings, Reviews, Wishlists

  • Page templating system like [http://smarty.php.net/ Smarty]. Possible options include [http://www.alcyone.com/pyos/empy/ EmPy] or others listed in the [http://www.python.org/cgi-bin/moinmoin/WebProgramming#head-9d0636d6da8e88f8f09de1454c5961b44183b04d templating section] of the WebProgramming page. Which one would you recommend?

  • Cache HTML versions of pages for faster loading. Ideally the page templating tool would handle caching.

  • User Authentication. A user authentication system perhaps integrated with MySQL or possibly even LDAP. Allow for different user groups and permission levels. Any recommendations?

  • Database Integration. Can store data in mysql, postgresql, etc. or work without a database.

  • Easy Install. Works completely in Python, and installs in one folder location. Doesn't necessarily require a database or mod_python. Doesn't require root privileges for install.

  • Small but Scalable. Doesn't require a huge server to run.

See the [http://colorstudy.com/docs/shootout.html Web Framework shootout] where different Python WebProgramming frameworks are used to implement a bare bones wiki.

Arguments that MoinMoin is a candidate

  • in a really dynamic context like wiki, you can't simply cache the HTML.
    • There are parts of the page that definitely can be cached. And most wiki pages do not use any dynamic macros.
  • Moin has user / password auth in CVS. Groups and page ACLs also.
  • Database integration is more of an anti-feature, see the next 2 points.
    • The best tool would have flexibility. Be able to run standalone with an easy install, or integrated with Apache and a fast database server. In PHP, this is incredibily simple if you use ADODB or PEAR.

PythonWikiEngines (last edited 2022-05-07 15:38:06 by AlexBrea)

Unable to edit the page? See the FrontPage for instructions.