History of function_biticon

Version 8


Created by: xing, Last modification: 18 Aug 2005 (07:41 UTC) by xing
biticon is a new function availible to smarty templates to support two things:

1) Icon themes - biticon allows icons to be overidden in the same way that smarty allows templates to be over ridden. This allows a site to mix and match themes with icon sets for a more customized look with less work.
2) Better support of WAI accessibility for the handicapped - biticon automatically generates any additional HTML needed to enable accessibility devices to function.

biticon is used in your templates to replace the hard coded image tags that are used for icons through out Tiki. In a template it would look like this:

{$biticon ipackage="blogs" iname="admin" iexplain="Configure blog settings" class="somecssclass"}

Very similar to an image tag in usage. These are the defined attributes:

ipackage (required): This indicates which package is home to this icon. General purpous shared icons like delete, trash, smileys, ect come from the kernel package. This also allows us to have a seperate "nextPage" icon for forums, one for image galleries, and one for wiki.

iname (required): This is the base name of the icon that you want to use. Notice that there is no extension like .png, .gif, ect. This is intentional and biticon will allow any type of image to be used and find the correct file for you. It will also generate correctly formed HTML for that file class.

iexplain (optional): This is equivelent to the alt attribute in an img tag. This will generate the alt tag in the page, but will also be used to correctly generate HTML to allow screen readers and other accessibility devices for the physically challenged to function correctly. additionally it will add the same value to the title attribute, giving the user a hover tooltip.

ipath (optional): here you can specify a folder within the ipackage. for example the flags are stored in users/icons/flags, you would set:
note: ipath requires a trailing '/' to work correctly.

__iforce (optional): you can spcify how the icon is displayed. options include:
This will force the use of an icon regardless of the setting in the themes manager. this can be useful in menus and the like, where showing the iexplain text can be disruptive.
This will force the display of the iexplain text alongside the icon. useful in particular situations where you are too lazy to add the text next to the icon manually.

These are the only four attributes specific to biticon. Any other attributes, such as class above, are pased through to the HTML tag unaltered.

The image file used for the icon is selected by searching a defined set of folders including the current icon theme from the admin-general panel, the current site theme, and a default set of core Tiki icons. Each icon is treated seperately, so icon themes or site themes can overide only the individual icons they want to change. Tikicon will automatically fall back to the defaults if there is no override. It works much like the template override system that allows themes. So the above command might generate:

= if the icon theme is loveandkisses and it overides that icon.

= if the site theme is classicarcade and it overides that icon.

= if the neithier the icon theme or site theme override the admin icons.

Search Path!!

This is the search path used by biticon. The 1st match found is used.

    1. <bit_theme_path>/styles/<icon style="">/icons/<ipackage>/<ipath>/<iname>.*
    2. <bit_theme_path>/styles/<site style="">/icons/<ipackage>/<ipath>/<iname>
    3. <bit_root_path>/<ipackage>/icons/<ipath>/<iname>.*
    4. <bit_theme_path>/styles/default/icons/<ipackage>/<ipath>/<iname>.*

If the file is not found in any of these locations an image tage with a src of broken.<ipackage>/<iname> will be output.

note: if ipath is not set, this setting will be ignored

note: to use variables within Please provide an icon name as iname parameter. You can select icons here. you will have to 'escape' the variables with '`'.
e.g. `$userPrefs.flag`</iname></ipackage></iname></ipath></ipackage></bit_theme_path></iname></ipath></ipackage></bit_root_path></iname></ipath></ipackage></site></bit_theme_path></iname></ipath></ipackage></icon></bit_theme_path>
Page History
05 Aug 2008 (04:25 UTC)
Current • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source