forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gav...." <brightoncomput...@brightontown.com.au>
Subject RE: [jira] Commented: (FOR-970) Add a way to have plugin specific resources, such as its own CSS styling, independent of skin or theme
Date Sun, 25 Mar 2007 22:55:20 GMT


> -----Original Message-----
> From: Ross Gardler (JIRA) [mailto:jira@apache.org]
> Sent: Monday, 26 March 2007 6:39 AM
> To: dev@forrest.apache.org
> Subject: [jira] Commented: (FOR-970) Add a way to have plugin specific
> resources, such as its own CSS styling, independent of skin or theme
> 
> 
>     [ https://issues.apache.org/jira/browse/FOR-
> 970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel#action_12483983 ]
> 
> Ross Gardler commented on FOR-970:
> ----------------------------------
> 
> Can you provide a use case for this. When would a plugin be used
> independently of skins/themes?
> 
> As things stand at present plugins can provide CSS class attributes for
> generated elements. These classes can then be defined in skincon.xml (for
> skins) or in the theme definition in themes. Can you describe why this
> doesn't work out for your use case.

Hi Ross, you still up :)

I have linked two issues to this now as use cases, an old one and a newly 
created one. It was asked on Jira for FOR-412 and asked on list about
the new FOR-971.

The above use cases I believe are a need and not a result of flowery
CSS for the sake of it. I did not think that by cluttering up the main
skins and themes with plugin specific styling was efficient.

There will be those that never use these plugins, but they will to have the
extra burden of the extra plugin CSS cluttering up and making the CSS
stylesheets even bigger for them for no gain. Imagine if there was an
eventual need for say 10 plugins to have specific CSS requirements, will
we want to add all these to skinconf and/or common theme?

I'm not talking about making the plugins able to have the ability to produce
their own look and feel, the skin or theme already applied should do that.

Anyway, that's my interpretation of how it should be done, I do not know the
how, so at the end of the day if it can't be done or no one gets to find
out how to do it, or consensus says just do it in skins/themes, then I'm
happy either way as long as those linked issues can be resolved.

Gav...


> 
> > 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.
> 
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date: 3/22/2007
> 7:44 AM


Mime
View raw message