Drupal Association members fund grants that make connections all over the world.
Most settings available for tweaking through the editor profile configuration GUI are currently implemented in wysiwyg.admin.inc even though most editors/integrations do not support them all. The widgets and settings descriptions available in the WysiwygGUI were originally based on the settings offered by TinyMCE and are thus very specific to that editor.
This is becoming a problem since the default state of the profile GUI has lots of widgets not relevant for many editors, confusing users as to which settings are actually possible to change. Editors not supporting some settings will simply not react in any way no matter which value a settings widget in the GUI is changed to, a major UX WTF!
settings form callback), defined in the editor metadata, for overriding the form generated by wysiwyg.admin.inc.
I intend to move as many settings as possible from wysiwyg.admin.inc out to the individual wysiwyg/editors/editorname.inc files and update the internal names of the settings to actually match those used by the editor (makes for saner code int the editor .inc files). Settings widgets which are not relevant for an editor will simply no longer exist or be visible for that editor.
Existing editor profiles will be updated to use the new names to avoid having to support two names for the same setting. New editor profiles will automatically use the correct names. This will not affect modules implementing
hook_wysiwyg_editor_settings_alter() because the editor .inc files are already converting the names of working settings (or the editors wouldn't understand them), and that hook has to expect the native names of settings for each editor to make sense anyway. This means you'll see PHP notices about missing settings if you update the code and forget to run update.php. The notices are harmless in themselves, but if you forget to run update.php before editing an editor profile, some settings will revert to their default values.