|
Size: 3780
Comment: Filled in answers on Pikie features
|
Size: 3764
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 20: | Line 20: |
| ||Cache Pages for Faster Loading?||not yet||no|| || || | ||Cache Pages for Faster Loading?||yes||no|| || || |
| Line 23: | Line 23: |
| ||Page Permissions||CVS version: yes||no||yes|| ||Templating/Page Skins/CSS support||no||yes||yes|| || |
||Page Permissions||yes||no||yes|| ||Templating/Page Skins/CSS support||yes||yes||yes|| || |
List
Here is a list of known Python-based WikiEngines.
CMFWiki -- a ZwiKi variant; old but compatible with Zope's CMF (Content Management Framework).
CyberPublishing -- a wiki-based web publishing framework written in Python; GPL
MoinMoin -- A PythonLanguage SourceForge project, based on PikiPiki (VNIHF)
PyWiki -- Python-based, uses RCS, GPL license
PikiPiki -- Python-based, will run completely standalone
PikiePikie -- Python-based, lets you put a WebLog on any page (based on PikiPiki)
PyleWiki -- Python-based, optional CVS backend, Unix-like rwxrwxrwx permissions on pages
WikiForNow -- a ZwiKi variant; used at zope.org
WikiNehesa -- Many features, including images, headerbars, TEXT centering, image inventory/previewer, image uploader. Modular. $FREE$. GNU GPL.
WyPy -- a ShortestWikiContest contender, 23 lines
ZwiKi -- ZoPe-based, powerful, GPL.
Comparison of Features
Existing or Desired Features |
add others here |
|||
Cache Pages for Faster Loading? |
yes |
no |
|
|
Page storage |
flat files |
plaintext files |
|
|
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 |
yes |
no |
yes |
|
Templating/Page Skins/CSS support |
yes |
yes |
yes |
|
Link icons, colorblind-friendly |
yes |
no, ? |
|
|
Supports HTML tags |
no |
no |
yes |
|
export RSS |
recentchanges only |
recentchanges & weblogs |
|
|
import/display RSS |
no |
no |
|
|
add feature here |
|
InternalTransclusion (as of 0.5x) |
|
|
Comment: "Support HTML tags" is more of an anti-feature in wiki. (so is table markup 
Comments, Ratings, Reviews, Wishlists
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.
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.