Here is a description of the proposed changes to accomodate for a more flexible and clear end-user control over the configuration of columns (i.e. selection of order and presence of columns in the result)
[default form for end user]
- replace the 'blank' choice from the drop-down list of column names with a more self-describing label describing what the option does (no more columns)
- add an additional choice to the list that caters for the extra option: 'just skip this column' . Since the rest of the values in the list are column names this option should be encoded with a value that cannot double as a column-name (suggested value: ? (U+2209) which is the mathematical symbol for 'not an element off')
[xreporter default style]
- change the columns.xsl so it generates the form in the above described way
[xreporter backend]
- check for this new column-value during definition-building --> don't allow for this column name
- check for this option choosen to skip to the next column in the /columns