MiniRubyWiki is for a PersonalInformationManager and for a team - not for the open Internet. For example, it cannot store page versions, and you can do things in-page that eat your server. But I'm not telling what.
PlannerMode? is a PersonalInformationManager built on top of EmacsWikiMode. Pages cannot be edited on the net (without an extension); they are all edited locally in Emacs. The nice thing is that the page in Emacs behaves just like a Wiki on the web (it's even much richer) - publishing is optional.
A nice tool [MRW]! Thanks for providing it. I use it on memory-constrained devices like my Zaurus. So it is easy to have my personal wiki/notebook always with me, and I can sync it with my PC.
In this case, it is an advantage that MRW doesn't have many dependencies and provides its own server.
Check out DidiWiki (tiny, written in c, built in webserver)
SdiDesk is a PIM application that works very, very like wiki.
Most PIMs have tickler (reminders). Does any WikiAsPim have similar features implemented nicely??
Moved from another page:
If the definition of a wiki is a "collective tool", then it should not matter whether the information was collected globally or locally. I now view a wiki as any informational environment which allows you to easily create, edit, and establish (hyper-linked) relationships between text documents. Indeed, I use many a personal wiki on my computer as "information centers". For example, think of a topic that interests you (baseball), then go out on the internet and collect text information about different aspects of baseball which you want to interlink together (For example, "The BaseballPitcher throws a FastBall whenever he wants to StrikeOut the BaseballBatter".) By creating information in this way, with the wiki effect of simply clicking on a term and describing it in a new document, you can create entire MindMaps of text data very effectively.
The point is, wikis have tons of uses outside of just internet collaberation. I suggest instead of limiting the term to a particular medium, it should be opened up to describe the process used, rather then the use itself.