Columns sets

[TomaszGasior]

Introduce columns sets. User is able to set custom columns order and visibility. But there are a lot of colums now. With predefined sets user will have better start and easier organization.

after #116

after #213

[HyperDX]

Well I think "must have" is
Channel
Frequency
MUX Name, Package Name (?)
MUX content (List of stations)
And some other columns which are implemented: distance, country, location etc.)

[TomaszGasior]

My idea is to collect here some ideas about how these "sets" would actually be organized. I would like to keep ability to define columns custom order and visibility. But there are a lot of columns and probably there will be more in the future. What I call "set" is named predefined collection of columns like "DAB bandscan" or "FM bandscan" or "private list" or "regular reception". After choosing one set, user will still be able to customize order and visibility of each column. The set is just some kind of starting point to make configuration easier.

@HyperDX Basing on your experience, could you please provide some ideas about these sets, some concrete examples? :)

[HyperDX]

Ok, so here are my basic sets

DAB bandscan (done only once):
Frequency
Channel
Polarization
MUX Name
Country
Transmitter location
ERP Power (kW)
Distance

FM bandscan (done only once):
Frequency
Polarization
Station name
Country
Transmitter location
RDS
ERP Power (kW)
Distance

DX list (Tropo-log)
For FM
Frequency
Polarization
Station name
Country
Transmitter location
RDS
ERP Power (kW)
Distance
1st log date
Reception type

For DAB
Frequency
Channel
Polarization
MUX Name
Country
Transmitter location
ERP Power (kW)
Distance
1st log date
Reception type

Regular reception
For DAB
Frequency
Channel
MUX Name
Country
Transmitter location

For FM
Frequency
Station name
Country
Transmitter location
RDS

[TomaszGasior]

This may be implemented as part of new design.

[TomaszGasior]

I postponed this feature. It will be implemented after #213