project
project summary freshmeat entry development infos mailing list WebInstaller database tools ChangeLog
page plugins
ProtectedEmail PowerSearch README README.config README.plugins README.fragments ProtectedMode INTERNALS WordIndex AboutPlugins PhpInfo OrphanedPages ListOfPluginHooks RSS RecentChanges PageIndex NewestPages SearchPages MostVisitedPages MostOftenChangedPages UpdatedPages
usage hint
9OTUNE YOGURT SÜREER AYRAN OLANA KADAR SİKERİMxD
Instead of embedding this into comments in plugin scripts, there will be accopmanying .meta files in the future. This is necessary to make the various *PluginManagers more workable (right now such data is hardcoded into some).
- SetupWizard, *ConfigurationWizard (makes monsterwiki and config.php, ewiki.ini)
- WebInstaller
- the *PluginLoader (info collection before done by separate script)
- mkxpi, XpiPlugins
- an internal ewiki_load_plugin() which resolves dependencies automatically
- the new SetupTool
Because names, descriptions and config settings will be readily available then, plugin dependencies can be resolved more automatically. So we can live without hardwired include_once() calls much better.
There is some terse documentation excerpt in the CVS doc/ directory.
2005-05-04: Work on new setup tool started (console/terminal/X11).
2005-04-25: First step is halfway done. Most plugins are now accompanied by a .meta file as described by the new documentation on it. Most only lack the correct dependency settings (what was the main intent for this).
2005-04-26: Most .meta files uploaded now and titles fixed. Ambigious plugin names. Meta-data resolving.
things to fix
Entry names were changed from "inclusion:" to "priority:". The "category" entry was however kept in favor of "section:"
Ambigious filenames are a problem, every basename can be used only once in the new system. There are only four right now, and so it's easier to fix that, than to complicate the dependency code:
- downloads
- subpages
- timestamp
- wikinews
done
plugin policy change
- include_once() will be used now for all plugin loading
- require() forbidden from now
- plugin set loading scripts are now recommended (MUST NOT come with an accompanying .meta description, so they remain ignored by the *PluginManagers)