Page Type Icons
| calendar |
 |
| email |
 |
| email list |
 |
| event |
 |
| field |
 |
| folder |
 |
| form |
 |
| home page |
 |
| keyword |
 |
site map / table of contents |
 |
| message |
 |
| page |
 |
| page type |
 |
| person |
 |
| phrase |
 |
| report |
 |
| search index |
 |
| section |
 |
| setup |
 |
| user |
 |
| user type |
 |
| XML |
 |
This is a list of all active icons that come with a Presto install by default. Icons for custom page types can be added by a Presto Programmer.
Some of the listed icons (calendar, message, email list) are specific to Presto modules which are purchased and added to a Presto installation.
Some icons share the same upper or lower case letter; this is done where such icons would be difficult to confuse in context (usually one of the two page types is referenced only inside the Presto Configuration area for example).
Currently icons are not multilingual; they are only in english.
Technical Programming Notes:
When a page type is edited (in the Presto Configuration / Page Types section), its "Icon" field text is used as a key to retrieve an icon for the page type. E.g. a field value of "email" causes the i_email[icon state].gif to be displayed for that page type.
If there is no icon in the images folder for that page type, then an attempt is made to generate one. This will only succeed if the custom <CFX_image> tag has been installed along with Presto on the webserver.
The icon is generated by taking the first (upper or lower case) character of the icon name and placing it in an icon template automatically, and generating a graphic on the fly. Then different versions of this graphic are made so that all the selected states of the item can be represented.
Non-alphabetical icons can represent page types of course (the "home page" house for example). This is achieved by preparing a graphical icon and placing it in the presto_pub/img/ folder as i_[page_type]1.gif . Clear out all i_[page_type][index greater than 1].gif icons. Then edit the page type's icon text field, and the selected state variations of that first template will automatically be generated.
<- ->
|