[dokuwiki] Re: Proposal: theme colour control

  • From: Chris Smith <chris@xxxxxxxxxxxxx>
  • To: dokuwiki@xxxxxxxxxxxxx
  • Date: Sun, 12 Mar 2006 17:25:53 +0000

Matthias Grimm wrote:

Furthermore the definition of a color like this: __lightgray__="#f5f5f5"
makes not much sense to me.
One of the problems with CSS is its not possible to define your own colour constants. So making a CSS results in using the same colour code in many places throughout the stylesheet. Simplifying that to a small number of constants makes that much easier to handle.
Easier for the theme editor to understand would be to name the patterns
according there function. For instance __link_external__ for an external
link or __tab_border__ for the table border. This could look like this:
I don't agree with moving the individual style colours. All these elements are defined in the style sheet, generally in one place only. It doesn't make sense to redefine them again, at least not to the detail implied in your example. Something in between your example and the current number of colours may make sense

e.g.

__border__ - apply to UI and buttons
__border_thickness__

One questions. Is order of processing the styles.ini file guaranteed. In which case can you use a style variable previously defined for another style variable.

__dark__      = #666
__border__  = __dark__

---- style.ini example (partly) ----
__link_visited__ = "Purple"
__link_extern__  = "#062efa
__text_headline__= "#000000"

__button_light__ = "#bfc9fa"
__button_back__ = "#5d77fa"
__button_dark__ = "#0524c1"
__button_text__ = "#ffffff"
__input_text__ = "#000000"
__input_back__ = "#e8ebfa"
In general these all are single style rules. As mentioned above, I can't see the point in shifting their place of definition.


In this context I have another question: How are plugins themeable? In
case of the user manager I tried to change the CSS for the disabled
button, but the default css file seems to be priviledged.
Maybe plugins should have ability to "add" to styles.ini. I thought about this briefly, but I reckon we have to watch the solutions becoming more complex than the problem. Especially as lots of people understand CSS but not so many understand dokuwiki style.ini files.

To override plugin styles, ensure your template places an id or class on an outer element - e.g body or some container div and make all your styles more specific than the plugin styles. ie, first paste a copy of the plugins style sheet into your template specific style sheet, then prefix all rules you want to change with the class or id mentioned above. Finally, delete any unchanged styles.


Chris
--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist

Other related posts:

  1. Home
  2. dokuwiki
  3. Archive
  4. 03-2006