Cor Bosman wrote:
Fallback to skins/default/ was added in r2514
Very cool! Thanks, been wondering about that feature for a while. Makes it a lot easier to create a derivative skin from default.
Hmm, i guess I misunderstood this. Looking at the code it's only a fallback for plugins. What would be cool is if any skin had fallbacks to default. So lets say i make a new skin that is marginally different from default skin, then i could just copy say 1 template to the new skin, and the rest would be taken from the default skin.
I have this requirement as well. My current solution is to create symlinks for most of the files.
That way, if new functionality is added that requires a new template (or css) existing skins wont necessarily break, but fall back to the default skin for that specific functionality.
Falling back to a template from the default skin folder isn't hard to implement. But the question now is where do all the links (to images and stylesheets) point to? To the active skin directory or to the directory the template was taken from? Does one of these possibilities really fit all needs?
~Thomas _______________________________________________ List info: http://lists.roundcube.net/dev/