What is the juce tip? Wait…that means the bleeding edge code right?
Ok, some thoughts on the matter. Jules, I’m an experienced developer, which doesn’t mean I know it all, but I think some observations from an outside perspective might be in order at this point. From my perspective, and from what the posts I’ve seen indicate - On my new mac I expect that when I grab the introjucer.dmg and have it download the latest version of juce, which the website says compiles for osx - that it actually does that. And at this point it doesn’t.
Previously, and following the jucequake post I tried using git to move to the modules version, but the instructions didn’t work for me so when I had a window of opportunity to ‘get current’ - it didn’t work, thus I’m still on 1.54, which is what the introjucer grabbed (actually it grabbed 1.54.27 I believe). I had to make some modifications to the juce audio code for my application, so I’ve ‘branched’ a bit and will have to add those changes (hopefully done better than the first pass) to whatever I eventually get running on xcode. I’d like to get that over-n-done with.
But at this point things aren’t working all that well from an outside perspective, new to juce, from a ‘I want to code my application perspective’.
I was wondering if you would consider taking some time to write up a sort of ‘state of the union’ or ‘overview’ post, targeting a non-juce-expert developer in order to clarify these issues. As it stands I’m not sure how and where I got off the beaten path but it appears I am, and I suspect others are encountering the same issues. (I hope so at least - I don’t like being the slow-learner here but if the shoe fits…argghh) (grin).
What IS the latest version of juce?
Does introjucer actually grab it or not?
What version of osx/xcode will work?
Why does ‘jucer.exe’ expect to open .cpp files instead of files with .jucer (meant for introjucer)? It’s confusing!
How do you use the modules branch?
Do we now have multiple choices (since modules is in the main branch) amalgamated, non-amalgamated, modules?
These are some of the high-level confusing issues to me, and are meant to illustrate the the user experience of this developer. I think a wee bit of documentation from the boss might good about now.
Suggestion…consider writing us a quick start guide to address the immediate new-jucer confusions, then begin working on the outline of the ‘The Juce Usage and Architecture’ guide. WIth an outline to usage and understanding the architecture, written by the author, the community could then be enlisted to actually write the chapters. The wiki is pretty lean folks.
Thanks for listening,