| version 1.25, 2003/05/02 17:51:33 |
version 1.26, 2003/05/12 22:30:22 |
|
|
| <!-- $Platon: phpMyEdit/doc/sgml/configuration.fields.sgml,v 1.24 2003/04/19 09:31:50 nepto Exp $ --> |
<!-- $Platon: phpMyEdit/doc/sgml/configuration.fields.sgml,v 1.25 2003/05/02 17:51:33 nepto Exp $ --> |
| |
|
| <!-- Categories: |
<!-- Categories: |
| |
|
| Line 157 $opts['fdd']['topic']['help'] = 'Enter t |
|
| Line 157 $opts['fdd']['topic']['help'] = 'Enter t |
|
| |
|
| </para> |
</para> |
| |
|
| <bridgehead id="configuration.fields.css">CSS customization</bridgehead> |
|
| <para> |
|
| |
|
| Per field, you can define field CSS class names postfix. This is especially |
|
| useful in order to highlight one column in a table. |
|
| |
|
| <example><title>Field CSS customization</title> |
|
| <programlisting><![CDATA[ |
|
| $opts['fdd']['col_name']['css'] = array( |
|
| 'postfix' => 'ColName' |
|
| ); |
|
| ]]></programlisting> |
|
| </example> |
|
| |
|
| </para> |
|
| <para> |
|
| |
|
| More information about CSS handling can be found in the <xref |
|
| linkend="configuration.css" endterm="configuration.css.title"> section. |
|
| |
|
| </para> |
|
| |
|
| <bridgehead id="configuration.fields.select">Selection boxes</bridgehead> |
<bridgehead id="configuration.fields.select">Selection boxes</bridgehead> |
| <para> |
<para> |
| |
|
| Line 237 $opts['fdd']['col_name']['options'] = 'R |
|
| Line 215 $opts['fdd']['col_name']['options'] = 'R |
|
| </example> |
</example> |
| |
|
| </para> |
</para> |
| |
<bridgehead id="configuration.fields.css">CSS customization</bridgehead> |
| |
<para> |
| |
|
| |
Per field, you can define field CSS class names postfix. This is especially |
| |
useful in order to highlight one column in a table. |
| |
|
| |
<example><title>Field CSS customization</title> |
| |
<programlisting><![CDATA[ |
| |
$opts['fdd']['col_name']['css'] = array( |
| |
'postfix' => 'ColName' |
| |
); |
| |
]]></programlisting> |
| |
</example> |
| |
|
| |
</para> |
| |
<para> |
| |
|
| |
More information about CSS handling can be found in the <xref |
| |
linkend="configuration.css" endterm="configuration.css.title"> section. |
| |
|
| |
</para> |
| |
<bridgehead id="configuration.fields.sql">SQL expression</bridgehead> |
| |
<para> |
| |
|
| |
There is a possibility to define SQL expression that should be applied to |
| |
particular field when selecting data from database. This is very useful when |
| |
you want to interpret field's content in different way than it is stored in |
| |
database. To be more clear, see following examples. |
| |
|
| |
<example><title>SQL expressions</title> |
| |
<programlisting><![CDATA[ |
| |
$opts['fdd']['surname']['sql'] = 'CONCAT(surname, ', ', firstname)'; |
| |
$opts['fdd']['title']['sql'] = 'IF(TRIM(title) != "", title, title2)'; |
| |
]]></programlisting> |
| |
</example> |
| |
|
| |
</para> |
| |
<para> |
| |
|
| |
First example appends content of <varname>firstname</> field to |
| |
<varname>surname</> field. Because this is done on the database level, sorting |
| |
and searching (in table filtering page) on this field will properly work. |
| |
Similary in the second example, the <varname>title2</> field will be used if |
| |
<varname>title</> field is empty. Using this way you can define some special |
| |
static string, which should be printed in case a field is empty. Just |
| |
substitute <varname>title2</> with some quoted string. |
| |
|
| |
</para> |
| </sect1> |
</sect1> |
| |
|
| <sect1 id="configuration.booleans"> |
<sect1 id="configuration.booleans"> |