External requirements: This plugin requires the following additional plugin that must be installed separately:

• the struct plugin

Search and install the plugin using the Extension Manager. Refer to Plugins on how to install plugins manually.

The plugin adds a new keyword to the definition of struct aggregations (see Struct Plugin: Aggregation), which allows the user to add a style to the rendered table, depending on specific column values. The syntax idea is simple: the keyword condstyle: is followed by a ternary operator, specifying the condition and the the styles related to the condition being true or false:

Basic syntax:

---- struct table----
schema: schema1
cols: *
condstyle: COLUMN NAME = ARGUMENT ? "STYLE TRUE" : "STYLE FALSE"
----
The conditional part (// COLUMN = ARGUMENT//) compares the current row's value in the //COLUMN// to the argument, using a (boolean) operator. If the condition is true, the //STYLE TRUE// will be applied to the row, otherwise the //STYLE FALSE// will be applied. The style are plain CSS code (multiple statements, each ended with a semicolon) and have to be allways wrapped within quotation marks. 
Currently, the following operators are recognized:
^ Operator  ^ Description                                                ^ Works for...          ^
| =         | Row value has to be equal to the argument                  | text, dates, decimal  |
| != / not  | Row value has to be not equal to the argument              | text, dates, decimal  |
| <         | Row value has to be less than the argument                 | dates, decimal        |
| >         | Row value has to be greater than the argument              | dates, decimal        |
| <=        | Row value has to be less than or equal to the argument     | dates, decimal        |
| >=        | Row value has to be greater than or equal to the argument  | dates, decimal        |
| contains  | Row value has to contain the argument                      | text, dates, decimal  |

[also CSS style tips]

[downloadable blocks, development comments]

[preferable GitHub RSS feed or similar]

• 2009-01-01
  • Initial release

[this section might not be needed in case of external bug manager, or use RSS feed]

[developers roadmap]

[discussions should ideally be deleted and turned into FAQ entries along the way]

Could be placed on an external page (e.g. plugin:pluginname:discussion) to have a distinction between user comments and author docs