What should the relationship be between Freelinking and Input Formats? Currently, if the Freelinking Filter is enabled in a format, every Freelinking plugin is also enabled.
It would be nice if individual plugins could have their syntax enabled/disabled by Format. Even deeper would be attaching global configuration issues to individual formats. (For example, so a different plugin could be the Freelinking default in each format.)
Configuring each plugin by format might be too detailed, as it could lead to confusion if a given freelink syntax had different behaviors in different formats.
This functionality is postponed to Alpha 5, per the current #613236: Freelinking 3 - Roadmap.
Comments
Comment #1
Grayside commentedPlugins can include the following in their definition array:
Doing so will 'deactivate' their indicator, preventing them from being matched in syntax. This has the affect of preventing any text from directly "triggering" a given plugin.
Changes to
freelinking_get_plugins()make it possible for the enabled settings to be overridden by variable 'freelinking_<plugin_name>_enabled_format_<format_id>'. In this way, configuration settings by format could disable a given plugin.Comment #2
arhak commented+1 on per format config
this is a concern, but who setting up the monster? he/she is responsible of what is bringing
and I think there are a lot of cases where having this potential might be helpful a lot
think about different roles having different formats and therefore not knowing the other meanings of a specific syntax for other users
Comment #3
gisleThis is beyond the scope of Freelinking.