What about if it were to support inheritance similar to the way that a child theme works with either style.css or calendar.css:
A plugin developer would create the following file:
htdocs/artefact/foo/bar.css
A Theme developer would create the following file:
htdocs/theme/default/artefact/foo/bar.css
then Mahara would do one of the following:
1) Load the plugin style then load the theme style (similar to style.css)
2) check for a theme style if it exists load it, if it doesn't then fall back to the plugin style (similar to calendar.css).
What about if it were to support inheritance similar to the way that a child theme works with either style.css or calendar.css:
A plugin developer would create the following file:
htdocs/ artefact/ foo/bar. css
A Theme developer would create the following file:
htdocs/ theme/default/ artefact/ foo/bar. css
then Mahara would do one of the following:
1) Load the plugin style then load the theme style (similar to style.css)
2) check for a theme style if it exists load it, if it doesn't then fall back to the plugin style (similar to calendar.css).