At 2004-11-03T12:28:10+1300, Jim Cheetham wrote:
> http://phpwiki.sf.net is undergoing active development at the moment,
> and versions between 1.3.11 (not yet released, but good in CVS) and
> 1.3.4 are probably not very stable.
No version I've seen is particularly stable. I'm not a big fan of
web-based applications that regularly barfing errors out to the user.
> you are not *forced* to preview before saving (as in twiki)
It's trivial to change this behaviour in TWiki.
> Twiki is, ihmo, clunky and ugly.
The default configuration is certainly ugly, and it's a few days worth
of work to do a decent job at changing that, unless you install one of
the available "skins". I'm not sure why you'd say it was clunky...
There are a lot of different wiki implementations available, each with
positive and negative aspects. If you're not really sure what you want,
I'd suggest using the simplest wiki available that stores the wiki pages
in plain text format. That way, once you have a better idea of what you
really need, it should be easy to migrate the data from the old wiki to
whatever system you end up using.
> The big problem with wikis is maintaining the access points to
> documents. If you don't keep the hierarchy clear, you can loose gems
> in the morass.
Yep. While a wiki will help you collaborate with others editing
documents, it won't cause you to be significantly better at
organisation. You need to either plan things carefully, or operate like
the c2.com wiki users and refactor mercilessly.
Cheers,
-mjg
--
Matthew Gregan |/
/| [EMAIL PROTECTED]
