A case for Plug-ins / API

[Lillie_Harris]

@Michael_Seltenreich

simple features like “retrograde” or “transpose to scale”

For the benefit of the incredibly talented and diligent developer who implemented the new and comprehensive set of musical transformation tools, I hope they don’t mind me taking the opportunity to highlight how extensive and detailed their work on these features was.

I understand the wider point you’re making, though, Michael. You’re right though that it has been discussed before and the team have shared their position – e.g. here from January:

@dspreadbury

Designing a scripting API that will be fit for purpose and provides the correct levels of access to the data models and functionality of an application like Dorico is a huge job, and one that has to be given a lot of time and attention in order to be done properly. We are committed to adding scripting to Dorico in the future, but it has to fight for its place among everything else that we are working on, and the reality is that we have enough large-scale projects on the go that this isn’t something we are likely to be working on in a big way this year.