Quote:
Originally Posted by TonE
Yes, and for your use case we have no diagram, we can not know what you want to achieve? What is the goal? Assuming those goals can not be reached by other means, how your solution does, in the diagram. Plus more importantly, which cases your solution does not care about? Now, and in 5 years, for the next 100000 new Reaper users?
|
Oh, now I get it.
You want a formal specification stretching out 5 years ?
Ok, no prob.
I'm presuming you would like a UML presentation.
What the hell, let's make it a bit more formal, what are the exact deliverables you expect and on what timeline ?
I am fully equipped and prepared to do something like this, but it ain't cheap.
I would suggest you get ready to donate about $100,000 or so every six months to keep this going.
Oh, and speaking of going, I'm a one man shop, so you should be prepared for a formal spec around the end of 2018
Or we could just go with stated goal: provide users the ability to map an arbitrary control surface widget to an arbitrary Reaper action, a lot simpler and a lot more Reaperry don't you think ?