This really is on the line with bugs/features, and since requirements DNE at this time, I'll put it here.

There is no deletion, only all is stored.   A file can be erased only by saving it with no information, and that only means the MOST RECENT version holds no information.
Older ones are always stored.

This is a feature--USERS ARE TRUSTED (like any real desktop application).


The architecture of MiniWiki is open to a point.   Much is unavailable outside of the programming.

A real test of the project is whether a framework can be built in itself, and MiniWiki is currently NOT built with MiniWiki.

What is necessary to achieve this goal is:

todo:

associate files with pages
   (files may be images, sourcecode, configuration files, etc.)
   associating files allows editing of the file, but the file
   is stored and retrieved in a way appropriate to the filetype
   rather than the text wiki engine

The file links are maintained in connection with the recent changes system of MiniWiki, so they are always up to date.

Comments, descriptions, tests, requirements, data, and associated files may be centered around common language wiki pages, rather than a JavaDoc style comment extractor in the supposed file-of-interest.