Each application defines a default theme. This default theme is used as the base of all other themes. The default theme is not accessible to end users, and should not be altered when developing a new theme.
The default theme is then extended by the theme defined in the user's 'theme' preference entry.
Theme elements are inherited in the following order:
(The application entries listed above will not be skipped if horde is the current application.)
For images & sounds, the first matching item is used working down the inheritance tree.
For CSS, the inheritance order determines the order the stylesheets are output. CSS files located at the top of the inheritance tree will be loaded LAST, horde default stylesheets will be loaded FIRST.
Themes are located in the themes/[themename] directory.
Applications that have multiple views can also store files in a subdirectory (e.g. imp stores dynamic view formatting in the dimp subdirectory and minimal view formatting in the mimp subdirectory.
The following subdirectories are reserved for special Horde use:
|CSS to use for an application's portal block (as of Horde 4.1)
CSS files should normally go into the base theme directory. There are several filenames that have special meaning in Horde:
|The default CSS definition
|Styles to use if the current language is a Right-to-Left language
|Used for embedded display
Additionally, the following CSS files will be automatically added based on the current browser:
|Internet Explorer 8
|Internet Explorer 7
|Internet Explorer <= 6
|Mozilla-based browser (i.e. Firefox)
|Webkit-based browser (i.e. Google Chrome, Safari)
URLs contained in CSS should be relative URLs.
Graphics live in the graphics/ folder of your theme's base directory.
Sounds live in the sounds/ folder of your theme's base directory.
Sounds must be in WAV format (with a .wav file suffix).
This file is only needed in the horde theme directory. It is not needed in an applications' theme directory
The info.php contains information regarding the theme. It must be a file that can be parsed by PHP. It should contain the following variables:
|This is the theme name as it will appear in the theme list in the users' display options.
An example for info.php:
<?php /** * This is my personal theme. * It is based on the colors of my bike when I was five. * * @author John Doe <email@example.com> */ $theme_name = _("My Theme Name");