Ages ago I promised I would add work areas for plugins, so that they don't have to worry about where they can read and write files.
The spec is:
getWorkArea( $pluginName ) -> $directorypath
Gets a private directory for the plugin. The plugin is entirely responsible
for managing this directory; TWiki will not read from it, or write to it.
The directory is guaranteed to exist, and to be writable by the webserver user. By default it will not be web accessible.
The directory and its contents are permanent, so plugins must be careful
to keep their areas tidy.
For RcsWrap and RcsLite the directories will be saved under $cfg{RCS}{WorkAreaDir}
CC
SVN 6848
CC
OK, now we just have to get the plugin writers to re-write their plugins to use it. --
AJA
In addition, we have the convention that plugins can write to pub/Web/Topic/_PluginName. We should replace the naming convention with a workAreaDir call. e.g.
getWorkArea( $pluginName, $web, $topic ) -> $directoryPath
Returns
pub/Web/Topic/_PluginName
I suspect having both general and topic-specific spaces areas are important. Do you agree?
MC