5,838
edits
Cumulus.ini: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→Simplifications
| Line 32: | Line 32: | ||
== Simplifications == | == Simplifications == | ||
The MX configuration is very different to that used by the legacy software. MX has far more optional functionality than the legacy software, therefore MX requires far more parameters to tailor all these functionality options. | |||
The ongoing development of MX is focused on making configuration even simpler, by revising the pages for the setting of all parameters, and improving the labels/grouping. | The file is read into Internal Variables as Cumulus starts, and those variables are written back into the file when any settings are changed. | ||
In the MX releases covered by this Wiki page, almost all settings are edited from a number of web pages for settings included in the local web interface. | |||
To make it easier for the Cumulus MX user, the developer had to devise a way to make it easier to quickly assign the settings that might be best for those new to Cumulus to get the software working without needing to understand all the settings. This is achieved by introducing some "master" settings, these both determine which dependent settings are displayed, and what default values those dependent settings take. So a novice just has to get the "master" settings right and they then achieve a typical way of using that functionality! For those who are slightly more expert, full flexibility is available by adjusting the majority of dependent settings to what is required for more specialised requirements. | |||
The ongoing development of MX is focused on making configuration even simpler, by revising the pages for the setting of all parameters, and improving the labels/grouping. By moving away from legacy software terminology and the parameters it needed; the developer has started introducing parameters and labelling that fits the MX design. | |||
It may be worth remembering why the legacy software made life complicated: | It may be worth remembering why the legacy software made life complicated: | ||
# There could be more than one "cumulus.ini" file for the Legacy Cumulus up to 1.9.4, as explained [[Cumulus.ini_(Cumulus_1)#Configuration_File_names|here]]. | # There could be more than one "cumulus.ini" file for the Legacy Cumulus up to 1.9.4, as explained [[Cumulus.ini_(Cumulus_1)#Configuration_File_names|here]]. | ||
# The vast majority of parameters (that could appear in the file) could only be edited directly in the file. | # The vast majority of parameters (that could appear in the file) could only be edited directly in the file. | ||
#* To simplify the editing in-situ, the author (Steve Loft) recommended that, within | #* To simplify the editing in-situ, the author (Steve Loft) recommended that, within any "File section" you intended to change, you sorted the parameters into alphabetical order, before editing the file. | ||
#* That advice was given because having parameters in alphabetical order would prevent you inserting a parameter that already existed. | #* That advice was given because having parameters in alphabetical order would prevent you inserting a parameter that already existed. | ||
#* This would avoid the potential problem arising from the design that Cumulus 1 would ignore any duplicate parameter; (Cumulus would take the first one it found, and that might not be the last one you edited!) | #* This would avoid the potential problem arising from the design that Cumulus 1 would ignore any duplicate parameter; (Cumulus would take the first one it found, and that might not be the last one you edited!) | ||
