Well, I’m originally from Ireland, what can I say! :mrgreen:
Creating good documentation makes a significant contribution to “improving the product”, and often is the most significant piece. Great code is useless if it’s too hard (i.e. takes too long to figure out how) to use it.
Seriously, though, let me explain from where I’m coming.
As a software developer with over 35 years experience (and as a manager of software teams over much of that time), I’ve long understood the tradeoff between time and money. Let’s say the hourly rate for a great developer is $200 and assume there are deadlines with deliverables. If I can buy a tool such that the time to become productive with it is less than the number of hours I would have to spend doing it myself (including learning it), then it’s a no brainer to buy the tool. I’ll save money as well as the ability to get other stuff done. This is even more critical if I need to do something where learning it deeply is an unnecessary distraction from the task at hand. For example, I don’t really care how AUs or VSTs actually work, nor do I want to have to learn yet another GUI framework…I simply want to leverage what you’ve done to get my job done as painlessly as possible and it SEEMS that your libraries can make that possible, with a little bit of guidance.
I have found in practice that high quality support is often worth far more than feature-complete libraries. If there had been an easily found document/tutorial that showed me exactly how to do basic stuff such as creating a cross-platform AU/VST with my own GUI in 10 or 15 minutes using the tools that you have in your library, I would have bought commercial licenses for my team without a second thought.
But I ended up futzing with stuff much of the day (and evening) yesterday and still apparently ended up with the wrong approach.
Those member functions you mentioned that I should have searched for (BTW how is one supposed to know their names up front without a lot of studying first) look like they are adding GUI widgets (components) manually at run time. But you have a GUI component tool that looks like it can create the whole dialog in one go, which is very nice in principle, but useless if it’s not clear how to then “embed” that dialog into the PluginEditor.
It seems to me that a trivial document (or even a movie capture tool) could have been created in a couple of hours to get new users up to speed quickly. THEN you will capture those peoples’ interest as they will be able to determine instantly that the product is worth the effort (and up front cost) even if they haven’t tried it yet, and that’s how one gets paying customers…(at least that’s how I’ve gotten them in the companies I’ve created in the past).