App settings again

[infeeeee]

This PR monster will be separated to smaller separate requests:

• Small fixes on entities Small entity fixes #100
• Editing existing configuration Edit configuration in menu #103
• ClassManager Rewrite ClassManager Rewrite #101
• Logger rewrite and LogSettings Log rewrite #107
• AppSettings AppSettings, set update interval #104

Changes:

• New items in Configurator Menu: Log Settings and App Settings under a common menu item Settings.
• On App Settings you can change the update interval of all entities. Default is 10 seconds as before.
• Log Settings: Change log level separately for console and file logging, enable/disable file logging (disabled by default), and change the folder of file logs. Default paths are form Implement Configuration and Log dirs classes #61
• Change existing configuration of any entities and warehouses. (This is actually a side product of the new settings, after I wrote that code, I figured out it could be used here as well)
• Configuration is now a separate class, not just a dict
• TerminalDetection class for terminal related methods.

Changes for existing users:

• The default file log path is changed, and file logging is disabled by default.

Secondary Update interval is commented out yet. I figured out that you cannot change the update interval on sensor level, only on entity level, and I think it would make more sense if it could be changed on a sensor level. That way an entity could have one frequent sensor and one infrequent. What do you think?

Retry #84

TODO:
- [x] Logging starts with a default log level before loading the configuration
- [x] After config loaded log level changes to the one in setting
- [x] Add setting to enable/disable file logging
- [x] Add setting for path to logdir
- [x] Logging should be saved to some cache at the beginning. If file logging is enabled, save the cache to file, so nothing is lost. If file logging is not enabled drop the cache.
- [ ] Implement secondary update interval in some sensors.

[infeeeee]

@richibrics Take a look, I think it's working now. I copied the code for the default Logs folder paths from #61

I will update the top posts with listing what actually changed. E.g. you can edit settings in the UI now.

[infeeeee]

There is some code in Configurator where it calculates the the height of the terminal, it could be moved here. Also the width of the terminal could be calculated here for Logging

[richibrics]

Yes it could be moved there since it's a terminal related class and we would free the Configurator of extra things

[richibrics]

Hi @infeeeee , sorry for the late reply.
I though I wanted to check if what I did in the Path configuration classes was correct but I have never found the time for it unfortunately.
Do you think we could integrate the classes I was preparing or keep them away for now ?

[infeeeee]

Keep them away for now.

I'm not sure they are needed at all, simply using pathlib solves most of the problems, and I use it everywhere where I have to work with paths. But let's see at the end.

[infeeeee]

Rewrote ClassManager.

Settings work similarly to Warehouses and Entities. Settings are loaded to the SettingsManager singleton on startup, entities can ask configuration from there. Log settings loaded separately to Logger.

@richibrics Take look, I consider this ready to be pulled now.

[infeeeee]

Not singleton, should update docstring

[infeeeee]

@richibrics This PR grew huge. Should I separate it to smaller ones, so it's easier to review? I can create 2 or maybe 3 smaller PRs instead of this beast. What do you think?

[richibrics]

Well if it's splittable it would be better for the understanding, but is it doable ?

[infeeeee]

Yes, I think I can separate to these parts:

• Small fixes on entities
• Editing existing configuration
• ClassManager Rewrite
• Logger rewrite and LogSettings
• AppSettings

I won't close this so I can track changes in the other PRs.