Alternate wiki-implementations: Difference between revisions

pear and smarty are requirements not something implemented in TikiWiki. Link to Python from MoinMoin
(excellent reference - but doesn't cover application side issues, only installation/integration)
(pear and smarty are requirements not something implemented in TikiWiki. Link to Python from MoinMoin)
Line 14: Line 14:
<th>[[MediaWiki]]</th><th>[[TikiWiki]]</th><th>[[MoinMoin]]</th>
<th>[[MediaWiki]]</th><th>[[TikiWiki]]</th><th>[[MoinMoin]]</th>
</tr>
</tr>
<td>
<td>
*Not humanly possible for [[end user feedback]] to reach developers reliably
*Not humanly possible for [[end user feedback]] to reach developers reliably
Line 25: Line 26:
*supports [[MySQL]] only
*supports [[MySQL]] only
</td>
</td>
<td>
<td>
*Not humanly possible for [[end user feedback]] to reach developers at all - form for describing [[wiki feature request]] incomprehensible even to a [[usability guru]]
*Not humanly possible for [[end user feedback]] to reach developers at all - form for describing [[wiki feature request]] incomprehensible even to a [[usability guru]]
*PHP based
*PHP based
*meets ''many'' standards ([[CSS]], [[XHTML]], [[pear.php.net]], [[smarty.php.net]], [[RDF]]
*meets ''many'' standards ([[CSS]], [[XHTML]], [[RDF]]
*Relies on [[pear.php.net]], [[smarty.php.net]]
*email/forums (and integration) built-in
*email/forums (and integration) built-in
*Group management built-in
*Group management built-in
Line 38: Line 41:
*developers [[eat their own dog food]] = run current beta as their live site for all development, so any problem is immediately obvious to every developer
*developers [[eat their own dog food]] = run current beta as their live site for all development, so any problem is immediately obvious to every developer
</td>
</td>
<td>
<td>
*[[End user feedback]] directly solicited in a public wiki
*[[End user feedback]] directly solicited in a public wiki
*Python language
*[[Python]] language, useful for possible future development of advanced [[UI]] and [[Consumer Agent]]-program(s) on mobile platforms
*excellent architecture making extensibility very simple - [[Market Model]] separating [[ActionMarket]], [[ProcessorMarket]], [[SkinMarket]] and [[ParserMarket]] - each of which runs in strict [[Request and Offer form]].
*excellent architecture making extensibility very simple - [[Market Model]] separating [[ActionMarket]], [[ProcessorMarket]], [[SkinMarket]] and [[ParserMarket]] - each of which runs in strict [[Request and Offer form]].
*thanks to [[ParserMarket]], it's easy to write parsers to meet [[wikitext standard]] or read [[MediaWiki]] or [[TikiWiki]] formats
*thanks to [[ParserMarket]], it's easy to write parsers to meet [[wikitext standard]] or read [[MediaWiki]] or [[TikiWiki]] formats
Line 47: Line 51:
*no need for *any* SQL - relies on [[Unix file system]] only - fewer glitches, fewer reports (most of which are turned off in the heavy-load wikis anyway)
*no need for *any* SQL - relies on [[Unix file system]] only - fewer glitches, fewer reports (most of which are turned off in the heavy-load wikis anyway)
</td>
</td>
</tr>
</tr>
</table>
</table>
9,854

edits