| | | |
| ( "summary", "status", { 'column': 'tagcol', ' | | ( "summary", "status", { 'column': 'tagcol', ' |
| tagcategory': 'priority' }, ) | | tagcategory': 'priority' }, ) |
| | | |
| the following conditions must be met: | | the following conditions must be met: |
| | | |
| t | - only columns listed in the configuration are | t | - only columns listed in the configuration are dis |
| displayed | | played |
| - ... in the order they are configured | | - ... in the order they are configured |
| - if the config value is a dictionary the valu | | - if the config value is a dictionary the values m |
| es must be passed 1:1 to the column who's name is | | ust be passed 1:1 to the column who's name is defi |
| defined in 'column' | | ned in 'column' |
| - if the config value is a list it should be c | | - if the config value is a list it should be consi |
| onsidered nested columns (two values in one column | | dered nested columns (two values in one column) |
| ) | | |
| - another implementation possibility would | | - another implementation possibility would be |
| be to create a 'MultiValueColumn' and pass a dict | | to create a 'MultiValueColumn' and pass a dict val |
| value to it configuring "sub columns" .. but i th | | ue to it configuring "sub columns" .. but i think |
| ink mult-value columns should be integrated right | | mult-value columns should be integrated right into |
| into the 'advanced object list'. | | the 'advanced object list'. |
