22.07.2013 Views

Sausalito Developer's Guide - Parent Directory

Sausalito Developer's Guide - Parent Directory

Sausalito Developer's Guide - Parent Directory

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3—10 Chapter 3: User Interface<br />

Beta Draft 11. Copyright ' 2001. Cobalt Networks, Inc. All Rights Reserved.<br />

Changing the User Interface Style<br />

Style interacts with the UIFC that are described in Appendix A. Most of the widgets depend<br />

on Style to set background images and colors, font size and weight, and other parts of the<br />

visual elements.<br />

<strong>Sausalito</strong> ships with one style file: trueBlue.xml. You can modify this file and save it as<br />

your own style file. You must give it a new name and create a new directory for your own<br />

style. The following example gives you high level instructions for creating a directory for<br />

your new style sheet, copying and modifying the style file.<br />

IMPORTANT! You must make a copy of trueBlue.xml.<br />

1. Change directories to /usr/sausalito/ui/style.<br />

2. Copy the style file, trueBlue.xml, to vendor_style.xml.<br />

3. Add any graphics or other files needed for your style file.<br />

The following is an example of modifying the trueBlue.xml file. In this example, the<br />

following UI properties were changed, as shown in Figure 3—3 on page 3—11.<br />

¥ trueBlue.xml was copied to test.xml; the word test is shown adjacent to Style<br />

in Figure 3—3 on page 3—11.<br />

¥ The color value for the aLinkColor value was changed to #0033CC.<br />

¥ The title alignment was changes from left to right by modifying the tabAlign value.<br />

¥ The font size was changed by modifying to .<br />

Similarly, changes were made to the background and divider colors of the table cells, and to<br />

the button font and colors, and to the alignment of the image.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!