I'v read the idea on how to implement the settings management and I completely agree and I'd have suggested the same approach. Till now, though.

While playing with some stuff I've got to do, I realised I need different configurations per-plugin per-format.

Therefore, I think settings should be split across two different places. The Inline module's settings (e.g. enable/disable plugins, to adjust the processing order of all plugins) should have their own page, whereas each plugin's settings should be available at admin/settings/filters/__FILTER_ID__/configure.

This way, if I develop a plugin and I want to provide a default set of settings, I can have different default settings per input format, in case I use different input formats per content-type, for example.

This arises from an actual requirement, and I've seen the problem tackled the way I explained by other modules too (e.g. video_filter, which provides default Width and Height settings customisable per input format).

Having said that, it's my understanding that the Inline 2.x-dev doesn't yet provide the support for globally managed settings, am I right?

Anyway, what do you think of my proposal?

Thanks,

Vincenzo