slajar wrote:For my personal use I will definetely go forward using the Non-UI code
Should I rewrite the Code to use JuceUI or should I leave it like that and we have a somewhat tweaked command line example?
Daven wrote:No, you're probably not looking in the right places.
There's more than adequate documentation of juce, google "juce api"
Daven wrote:It's not clear what you're talking about regarding sample code.
"I sent the first one to Julian and he wasn't really enthusastic about my way of implementing this sample" -- what are you talking about?
Daven wrote:I mean no offense, but you might have more luck if you got someone to help proofread these messages, assuming English is a second language.
dave96 wrote:If you are developing a command line app, there is no point in building a UI just to post code here as it will just overcomplicate the issue. Sometimes interface elements are useful/necessary when developing and testing for the visual representation of audio but that will depend on your use case.
dave96 wrote: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.
Werner wrote:I'd like to see more examples, but please with GUI.
My question was, could we have a sample code without UI or is this just senseless since JUCE is always about UI?
jules wrote:My question was, could we have a sample code without UI or is this just senseless since JUCE is always about UI?
If you only use classes that don't require an event loop to be running, then of course you can write a non-UI app with a main() function, etc.
But what you were trying to do was to use a bunch of UI-based classes without actually providing an event loop to service them, so they're not going to stand much chance of working correctly. And the only sensible way to provide an event loop is just to build a normal GUI app, even if you don't intend to make it open any windows.
Users browsing this forum: Google Feedfetcher, TheVinn and 0 guests