[quote=“Daven”]No, you’re probably not looking in the right places.
There’s more than adequate documentation of juce, google “juce api”[/quote]
You don’t talk about a doxygen generated documentation, do you? From my point of view this is not a real appropriate documentation.
It’s a real good thing if you already understood how things work and you just need some hints. I case you’re a noob you’ll probably need
to get a good understanding about the main concepts (I’ve seen there is a real good tutorial for building UIs but nothing equally for the audio stuff).
IMHO, using doxygen is the open source way to save time and it is not a good way for the usability of an API.
I am expecting sample codes for each task and a good developer documentation for all APIs we are using.
Since I wanted to help I started to write samples.
I am not sure why this is not clear. I sent a zipped package with my proposed sample code to Julian and he dind’t like the way I used JUCE.
Yes, english is not my first language but I don’t think that matters if you’re not picky
Yes, they are neccesarry sometimes. My question was, could we have a sample code without UI or is this just senseless since JUCE is always about UI?
Btw, I didn’t say that I am building a command line tool, we are just not using JUCE as a UI platform. Therefore the implementation of the backend is quite similar to a command line tool.
As Daven said there is a wealth of documentation built into the Juce library code itself. This is in Doxygen format and a html version can be found here.[/quote]
Hhm, As I said above I don’t see a doxygen generated HTML files as a real documentation. I am expecting much more especially for noobs. Currently, I think it’s way to hard to get first simple things done. I don’t say the API isn’t great It is great and you can do so much with it. Since it’s complex even tiny examples grow pretty fast. So I think the smaller an example is the better it is for beginners.
For example code the best resources are the Juce Demo and Audio Host programs located under “extras”. Otherwise there is the Juce wiki and the Useful Tools and Components forum for user provided examples.[/quote]
Sure this is really nice but I was expecting striped down examples. That’s why I decided to write some and contribute them to the project.
Ok, I see. Our approach is probably too far away from what “normal” Juce-users do. I am going to adapt the sample codes and submit them afterwards