David Hall wrote:...I thought of you at least four times while I was writing my post...
All bad thoughts too, eh?

Actually, I'm glad you didn't take my response the wrong way.
I agree that a free API/SDK would be difficult to justify for a free product such as eCabinets, but just look at the number of open source products that do just that. This forum software (phpBB) is a great example.
My thoughts are to publish the API but not necessarily an SDK. The added value provided by add-ins/plugins would make eCabinets even more valuable to shops and thus, to Thermwood. Each install is a potential router sale or business for a production sharing shop such as yours.
By encouraging developers to create add-ins/plugins for eCabinets, Thermwood could free up their developers to concentrate on the core cabinet design software, making it the hands-down best available anywhere at any price.
Your idea of paying a royalty to Thermwood for each add-in unit sold is not a bad idea. It would give Thermwood a monetary incentive to publish the API. I have seen similar arrangements where the vendor gives independent developers exclusivity for the type of add-in they create in return for royalties to the vendor. I don't know if that is such a good plan as it would tend to stifle competition between developers. Competition, after all, is what drives developers to create better products.
Again, look to phpBB for proof that this works. The phpBB owners don't get any royalties from independent developers but there are hunndreds, if not thousands, of enhancements available for the base forum software. The base forum software in and of itself is great but the availibility of add-ins make it the most widely used forum software in the world. Even the programming language its written in (PHP) is open source and free to the public.
I don't want to see eCabinets to go open source for a number of reasons. Probably foremost is that the original developers of open source software tend to "lose control" of the software and I certainly don't want to see that happen to eCabinets.
I do think there are methods of making something like this work is a way that is beneficial for Thermwood, independent developers and eCabinets users.
Good idea...thanks for posting it.