server config files

[Reimar Bauer]

Currently the server needs a mix of cfg files like mss.topview.cfg in topview.MSSTopViewWindow and various config python scripts.

Somehow that should become simplified.

[Joern Ungermann]

The .cfg files are for the MSUI AFAIK. These are generated by QT. These should be placed into .config/mss or wherever the json is located.

The Server uses two python files for configuration, which should be merged into one. I think keeping it as Python has some advantageous, as it allows the implementation of data import classes inside the configuration Python file that otherwise would require a package change. Nevertheless I propose to move the current NWP-Data-import classes to the MSS module to have a "lean" config file.

[Reimar Bauer]

We have to keep python config files for the server setup.

hmm, I am not sure that these .cfg files are needed for execution of mss. Currently they can't load and the UI seems to work. If we don't need them, we should may be remove that line https://bitbucket.org/wxmetvis/mss/src/4fe6f7302f910c90102e9cef0c174b1614b908f5/mslib/msui/topview.py?at=develop&fileviewer=file-view-default#topview.py-208

[Reimar Bauer]

implemented .config/mss directory in user home directory as default path for config files. see issue #39 and issue #34

→ <<cset bac4b8525bef>>

[Reimar Bauer]

Simplified server configuration files. Resolves issue #39

Removed pickled cfg files from samples as they are not designed to be modified by the user. Joined mss_config and mss_wms_settings and moved complex functionality to own module. Further extensions may be placed into mss_wms_settings until they are integerated into MSS. Reworked WMS config sample to show new functionality.

→ <<cset 2d41e6703340>>