ctools exportables support

You took the words right out of my mouth. Creating a solid WYSIWYG configuration can often rely on a lot of small settings. Having exportables for those settings would be a god send.

Good point. Bumping this to 7.x-3.x-dev as that's where the new major features will be added first. Note that this is not a promise that it will be added, but we'll look at it.

+1 this would be great, in order to build features, like catch said.

Yes this is an excellent feature. But, if settings of wysiwyg are related to an input format, export settings will mean export the input format too?

@dagmar You bring up a good point. Especially since input filters are set numerically, making them problematic to import and export reliably. I'm hoping that this is not the case in D7 seeing as how much of the filter module API has changed. The Exportables project may be a good place to tack on an exportable API for this. If not, WYSIWYG could always implement its own work around. In the end, I would hope that this complication doesn't side track any incremental improvements. WYSIWYG configuration exportables would still be helpful for install profiles and other use cases without input format exportables.

I'm using features on a large site upgrade to avoid having to write and rewrite custom hook_update_N() for as many things as possible, so I took an hour or so to write very, very basic features integration for wysiwyg-6.x-2.0. This doesn't attempt to resolve any of the bigger issues around exporting input formats + wysiwyg, just allows you to put the contents of the wysywig table into code and version control / revert / override it.

So I'm deliberately not even marking this needs work, but in case someone else is hoping to do the same thing, maybe it'll be useful. It's also implemented as a self-contained module rather than a patch, since that's how I'm handling these temporary upgrade feature implementations.

Tagging.