Excellent work David - I was tossing up between Django and Turbogears for a few weeks before coming down on the Django side. Interesting to see the differences between the two frameworks ( & I think the Django-folks should chat to the Turbogears people too ).
Ian, etc: I've been slowly building a wiki in Django myself ( for a personal information wiki-thing ). I'm currently calling it "Mnemosyne" which is a bit daft, but it seemed like a good idea at 4am. Current features: 1) swappable parsers - there's nothing worse than getting stuck with a crappy syntax. So, it currently uses textile, but reStructured text should work and changing the syntax parser should be as easy as changing one line of code. 2) sensible database design (if I say so myself) - some of the wikis out there are just nightmares ( Mediawiki especially is terrible ). 3) versions - always good in a wiki 4) namespaces - Page:article is different to Something:article. Only one level deep namespaces so far. 5) Color coded links - i.e. red if page does not exist etc 6) Macros - write your own wiki functions. Don't like it ( it is a security risk ) - turn them off. 7) File attachments - attachments are placed in the filesystem ( no db stored binaries thanks! ), and in a sensible hierarchy mirroring the wiki structure. It's still a bit buggy, but I'll post it somewhere if anyone's interested ( It's my first non-trivial python app, and I'm coming from a PHP background so I would love criticism too ). Again - it's more of a personal app rather than run-live-on-the-web, but it should be mostly safe if you turn off files and macros. --Simon
