Last modified: 2014-08-28 22:25:55 UTC
If an extension or module wanted the configuration available globally it could use the existing 'ResourceLoaderGetConfigVars' hook or associate it with the loaderScripts register. Otherwise configuration would just be delivered per module registration array.
Part of this patch of course checks localSettings.php modified time as part of "resources with configuration" max timestamp checks.
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Krinkle this would be a nice feature for RL2 efforts. So that if you have lots of modules with lots of configuration your startup module does not get overloaded with configuration.
Perhaps within the module definition you include a way to designate some configuration as global, with the default setting only packaging in the resource configuration once the module is loaded.
GSoC 2011 features per-gadget preferences. Once that is reviewed and merged back into trunk we should look at this for RL3 (too late imho for RL2, lots of stuff already).
Possible use cases:
* Ability to change configuration options that are for one module only.
* That ability for the site admin (from php) and (if module allows it) per-user as well from the preferences somewhere (ie. a sub pref-pane per module)
* ResourceLoader passes this to the front-end just like it does for other things (either as a 4th component (next to scripts/styles/messages), or as a separete module implementation (like is done for mw.config and mw.user.options)
* Moduel get can it's stuff via mw.loader.getConfig( 'modulename' ).someThing
(In reply to comment #3)
> too late imho for RL2, lots of stuff already
What a pity... =(