[
https://issues.apache.org/jira/browse/FOR-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483987
]
Ross Gardler commented on FOR-970:
----------------------------------
I had the same need when I built the ecs input plugin (in whiteboard). The
index.xml page describes what I did (basically defined the available CSS and
expected the user to provide their own CSS). I opted for this because, since we
don't know the users skin/theme we can't really provide meaningful default CSS.
However, I see some defaults may be useful.
My initial thought is that the plugins could provide an "extra.css" or
"extra-css.xml" file. These can then be collated when the plugin is installed
at startup. The collated document is then embedded in skinconf.xml or a
dispatcher contract as appropriate.
> Add a way to have plugin specific resources, such as its own CSS styling,
> independent of skin or theme
> ------------------------------------------------------------------------------------------------------
>
> Key: FOR-970
> URL: https://issues.apache.org/jira/browse/FOR-970
> Project: Forrest
> Issue Type: New Feature
> Components: Plugins (general issues)
> Affects Versions: 0.7, 0.8-dev
> Reporter: Gavin
> Fix For: 0.9
>
>
> It would be nice if plugins could be a little more independent of core skins
> and themes for plugin specific styling.
> This could be CSS, or something else, I have only identified CSS needs at
> present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
