I lowercased the file names. I've separated the code to generate an overlay menu out into a module called overlay_page, it is the same code as is in my other pull request for the keyboard shortcuts menu. It should be easy enough to change the way it looks and behaves without worrying about breaking anything. I've pulled code out into a module called element_generator because it is pretty generic and isn't concerned with gathering data for the settings menu. The element generator can be reused and augmented but there is the possibility that modules depending on it could break. show_settings_menu depends on the element_generator. As it collects data it generates generic elements and attaches event listeners to them. The massive list of options has been moved into its own module for two reasons (1) it makes maintaining show_settings_menu much easier and (2) this is the only part of the menu which has to be updated manually. We may be able to add something to the build system to automatically generate this module based on which modes and themes are found to alleviate us from having to remember to add said options in when new themes and modes are added. |
||
|---|---|---|
| .. | ||
| ace | ||