[ewiki] more spages/ instead of page plugins

Hi @all,

The ewiki distribution will further ship with a small spages/ directory
containing the so called StaticPages. And I plan to eventually replace
some of the page plugins with spages. The reason is, that page_* plugins
usually get included() even if they aren't needed and thus most of the
time only consume memory.
StaticPages on the other hand are just plain .php scripts, that get
activated by the 'spages.php' plugin, when they're requested by $id.

However, one of the ewiki project goals was (and still is) the "everything-
in-one-script-file" idea, or short to built a "monsterwiki.php" script from
the ewiki.php core script and all needed plugins. This remains possible
even if some extensions are further distributed as StaticPages, because
these can easily be converted into page plugin again (and vice versa).

Also I'm going to add pseudo-spages, that in fact load page_* plugins and
therefore save memory, and make it in future unnecessary to include()
page plugins, if the 'spages' plugin is already active (which then works
much like the 'pluginloader' plugin).

A question that came to my mind is, if it was senseful to rewrite our
currently external (www accessible) tools/ to get StaticPages, too? They
already can be used via the spages plugin, but my concern is, if we should
integrate the database+administration tools/ fully, or keep them a bit
external to the Wiki - for security reasons - like it currently is?


mario

Other related posts: