Currently, some modules require manual modification of local storage to enable or configure features. The user should be able to configure these values via the admin panel, based on the module config file. DSJAS should modify these values before the module code runs via a script at page startup.
Currently, there are at least two modules that I know which require you to enable or configure features by manually modifying local storage. This is a very good method of *storing* the configuration, but I see no reason why the user should do it manually. Instead, I propose that DSJAS expose these configuration values as specified in the module config file. Then, on request DSJAS will simply modify these values before the module code runs via a script which runs at page startup. Where there is currently just a link for "More Info" and "Uninstall" on the modules settings panel, I think we should add another link for "Settings" which then simply loads up the module configuration values. Additionally, we could add an abstraction via the new module API for module developers to have the settings loaded by the DSJAS API for them. To be clear, I envision this implemented in a completely backward compatible way such that users who are already using the local storage interfaces for the