I wonder, what are Dorico’s designers’ and developers’ stances on support for third party plug-ins? I’ve always wanted to write C++ or .NET add-ons to notation packages, to really get in there are trick out some of the features of the application. Sibelius offers something like this with its proprietary scripting language, and Finale has FinaleScript, but neither offers an actual API supporting a major programming language.
This has always seemed like an oversight, to me. Comprehensive applications like professional notation software really tend to have their doors blown off (in a good way) when their functionality is opened up for expansion by us outside developers. I can’t imagine that this is a feature that hasn’t been considered by developers of notation software, so why hasn’t anyone introduced a C++, .NET, or even Python API into any notation package after all these years of Finale, Sibelius, Dorico, and all of the other lesser music composition applications?
Is it insufficient demand? Is it insufficient time/resources? Is designing architecture that supports a C++/.NET/Python/whatever API too problematic? Is it wanting to maintain control over the evolution of the software? What?