separate concerns between $conf systemstatus and $settings

[bwl21]

Request

clarify and separate the concerns between conf, systemstatus and settings and presets

• sytemstatus was first and mixes status and runtime settings
• conf was introduced later - double check if there is something which should go to settings
• settings is very new and controls the runtime behavior of zupfnoter.
• settings should eventually be provided by a permanent form
• presets are part of config but they put a performance burdon on config processing

Current status

Configuration

• is saved with the abc code
• is persistent
• has influence to visible result

systemstatus

• is a instance attribute of Controller
• is computed by zupfnoter
• reflects the current status (e.g. dirty)
• is persisted partly in localstorage
  • debug level
  • view
  • autorefresh

settings

• is a global object (in contrast to sytemstatus)
• is a setting for zupfnoter to control its behavior at runime
• has no impact on visible results
• is cleared upon reload
• example
  • validate
  • edit flowline
  • scroll to selection
  • follow play

solution approach

• merge settings and systemstatus
• handle persinstence in :save_to_localstorage
• make settings global

candidate for settings

• systemstatus : mode, view
• conf: none

presets

• should be moved out of $conf, maybe there is not even a need for a global here