Propsal: further refactoring on DataTable/TreeTable column related state

Currently we have the following state, which is also stored in the MVS:

    private Map<String, SortMeta> sortBy;
    private Map<String, FilterMeta> filterBy;
    private String orderedColumnsAsString;
    private Map<String, Boolean> visibleColumns;
    private Map<String, String> resizableColumns;

and orderedColumns is still not refactored.

TBH i dont like further refactorings for 100% as our current code is quite nice and stable compared to 8.0 BUT the next version will be 10.0 and i dont like to refactor everything again. And we have at least 3-4 weeks before a RC1.

we could merge and unify many many code if we would create a

private Map<String, ColumnState> columnState;

which would contain all those info on sorting and filtering, width, ordering, resize etc. etc. we could also unify the SortBuilder and FilterBuidler and attributes, we would only have something like:

<p:dataTable columnsConfigs="..." />

with

ColumnStateBuilder......sortOrder(...).filterValue(....).width(200).visible(false).build();

maybe the same on p:column for a single entry.

@Rapster @christophs78 @melloware WDYT?

[tandraschko]

Lets wait, primetek will do it when releasing RC1

[tandraschko]

more managable and more unified columnSettings instead of X builder, just 1 for all