David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
It is also creating a maintenance problem for the
Forrest project. Synchronising and updating those is hell.
Can you expand on the problems?
If we make a change to the forrest.properties e.g.
add a new parameter. The main example is at
main/fresh-site/forrest.properties but the changes
need to be replicated to every plugin. Same with
skinconf.xml
Put the new config in default.forrest.properties (or
default.forrest.properties.xml if we adopt the new system). You only
need to add it to other themes/plugins/sites if you want to use
something other than the default.
Since it is a new property and therefore the theme/plugin/site knows
nothing about what it does it is highly unlikely it will want anything
other than the default.
Yes i realize that we can do that. However at the moment
the pluginTemplate and all current plugins have full
copies of all the full configuration stuff. We need to
rationalise that prior to 0.8 release.
I'm proposing using the plugin download mechanism for themese, not using
the plugin template for themes.
Sorry, I wasn't clear enough. I would imagine a different template for
themes.
Ross
