The ZCS server application uses the substitution file(s) supplied with a theme to process all of the CSS files and apply colors, fonts, borders, etc to the ZCS applications and widgets. CSS files do not need to be encoded in this way - just list your CSS entries as if the file was as a separate link.Īll of the CSS files that are used within the ZCS application, as well as those defined in your theme, use a special substitution syntax to allow the theming process to work. tags around the actual Javascript content. For example, to include a Javascript file, name it foo.html and make sure it has. Make sure you include a file of the corresponding type as its category. Note that you can add extra entries in any of the categories in your manifest - the files will automatically be loaded in the order listed. Changes to the HTML and CSS files (as well as changes to private entries in the _subs file) are not guaranteed to survive upgrades. This way you can be assured that your theme will survive upgrades to the ZCS application. Although it is possible to completely redefine the HTML and CSS files for your theme, it is strongly recommended that you use the base HTML and CSS files and simply change the substitutions that are performed in the css. This is generally how you will set up your theme.
the theme does not specify its own CSS and HTML files, instead relying completely on the light theme for its HTML and CSS. for the substitutions, the file base_subs.txt will be loaded first, then light_subs.txt will be loaded (overriding any similarly-named entities in base_subs.txt), and then the entries in test_subs.txt will override the correspondingly named entries in both base files. This indicates that the light theme files should be used in addition to or in place of the corresponding files in this theme. For example, if theme test wanted to simply provide a small set of changes from theme _base/light, you might have: For a fully-specified theme named test, it would look like:Īlso, note that you can have more than one entry per category, and that these file entries can refer to other themes by locating them in the directory structure. The theme manifest (.xml) defines the location of the files that make up the theme. 
(Network Edition) For example, to fully create a theme named test, you might have the following directory structure: See The Theme Manifest section for details. Note that some of the files listed above are deemed (optional) - for these files, some you can omit entirely, and for some you can set things up in the manifest to use the corresponding file in another theme. In general, you will be pointing to a CSS file in the skins/_base directory rather than creating your own. css (optional): This is CSS definitions that are paired with the elements in. In general, you will be pointing to an HTML file in the skins/_base directory rather than creating your own. html (optional): This is the HTML responsible for drawing the theme, along with the javascript required to show or hide parts of the theme dynamically. See Editing Theme Substitution Files below.
For example, this is where the background color of elements are set, where fonts are defined, etc.
_subs.txt (mandatory): This sets up a number of substitutions which are performed in the other theme files that customizes their appearance. xml (mandatory): This is the "manifest" for your theme, which details all of the other files that make up the theme. Within this folder you can have the following files: Note that currently, spaces are not allowed in the folder name. (The examples will use the theme name test). To create a new theme, create a folder with the name of your theme in the. skin/_base/ are special directories used to create themes - these are not exposed as themes to the user. In general, each directory there corresponds with a single theme available to users of the ZCS. xml in the sand theme would really mean file sand.xml).Īll theme files live in the /opt/zimbra/tomcat/webapps/zimbra/skins/ directory. In this document, whenever you see in a file name, substitute the name of your theme (e.g. For example, for the theme named sand, you would use files sand.html, sand.xml, etc. Generally, the names of the text files are prefixed with the name of the theme. This gets into the gory details of how the theming mechanism works, probably explaining more than you'd really like to know, and definitely more than you need to know to create a theme.Ī theme is composed of a single directory which contains a number of text and image files. This article is a Work in Progress, and may be unfinished or missing sections.įor later release information about Themes (Skins), see ZWC 5.0, 6.0, and 7.0 Themes.
0 kommentar(er)
