Post-SOC color.module update.
Commit
#135141
Most of these updates are fixes for the demonstration and documentation.
The major exception is the stylesheet engine update.
- Under the hood: Fixed bug with currenttheme + edit scheme button on color block sending to incorrect theme.
- Under the hood: Removed superfluous data from edit_scheme form and submit
- Under the hood: Changed permissions around. Color scheme is now available to those with user_access("administer access control")
- Under the hood: color_edit_scheme_form() uses $palette instead of $reference to main hue and shift correctly. However, I left a not in the comments to document how $reference and $palette acted with the picker.
- Under the hood: color_validate() action to the color_get_theme_info section.
- Under the hood: Put spaces around dot's (.) which concatenate
- Interface: For intuitive purposes, switching the "select" and "edit" buttons in the color_block_form
- Demo Theme -- Simpla: removed extra breadcrumb
- Demo Theme -- Friends Electric: Added default logo
- Demo Themes -- Fixed font sizes cleanstate and simpla
- Demo Users: Including a code of theme's color.inc on theme settings pages so viewers can take a look.
- Documentation. On demo themes: Added comments and spruced up the color.inc on the examples more.
- Stylesheet changing has been modularized into extensible color replacement engines.
- engines/shift.inc - for shift themes, with a 'base' color (Garland)
- engines/tag.inc - for custom CSS replacement
- In your theme's color.inc, you can use both these engines at once in either order.
- Developers can also add custom color replacement algorithms by adding their engines which hook in automatically. Create a engines/yourengine.inc with the function _color_engine_yourengine($style, $info, $palette, $options = NULL). Return the modified $style markup. You can input options in theme schemes (color.inc file) by adding 'yourengine' => array(MYVARS/ARRAY/ETC) to the 'engine' settings. Go crazy. :)
- The color.module DON'T TOUCH statement now separates from all engines/modification as expected. The DON'T TOUCH comment is for CSS markup in your stylesheet's you do not want to have colors modified on.
- Of course, this means, no more mode-cruft. :)
The major exception is the stylesheet engine update.
- Under the hood: Fixed bug with currenttheme + edit scheme button on color block sending to incorrect theme.
- Under the hood: Removed superfluous data from edit_scheme form and submit
- Under the hood: Changed permissions around. Color scheme is now available to those with user_access("administer access control")
- Under the hood: color_edit_scheme_form() uses $palette instead of $reference to main hue and shift correctly. However, I left a not in the comments to document how $reference and $palette acted with the picker.
- Under the hood: color_validate() action to the color_get_theme_info section.
- Under the hood: Put spaces around dot's (.) which concatenate
- Interface: For intuitive purposes, switching the "select" and "edit" buttons in the color_block_form
- Demo Theme -- Simpla: removed extra breadcrumb
- Demo Theme -- Friends Electric: Added default logo
- Demo Themes -- Fixed font sizes cleanstate and simpla
- Demo Users: Including a code of theme's color.inc on theme settings pages so viewers can take a look.
- Documentation. On demo themes: Added comments and spruced up the color.inc on the examples more.
- Stylesheet changing has been modularized into extensible color replacement engines.
- engines/shift.inc - for shift themes, with a 'base' color (Garland)
- engines/tag.inc - for custom CSS replacement
- In your theme's color.inc, you can use both these engines at once in either order.
- Developers can also add custom color replacement algorithms by adding their engines which hook in automatically. Create a engines/yourengine.inc with the function _color_engine_yourengine($style, $info, $palette, $options = NULL). Return the modified $style markup. You can input options in theme schemes (color.inc file) by adding 'yourengine' => array(MYVARS/ARRAY/ETC) to the 'engine' settings. Go crazy. :)
- The color.module DON'T TOUCH statement now separates from all engines/modification as expected. The DON'T TOUCH comment is for CSS markup in your stylesheet's you do not want to have colors modified on.
- Of course, this means, no more mode-cruft. :)
