First, to give some context: I used Traktion back when it first came out and have been interested in JUCE ever since. :)
I'm now contemplating using JUCE to port a fairly complex scientific application I've written in C++ using a homegrown opengl-based gui system ( http://www.kintek-corp.com/kinetic_explorer/ - see screenshot on this page ). Our system can read complex hierarchical UI definitions from xml-like files, or create stuff dynamically in code. Importantly, it has a layout engine to help when you have a bunch of checkboxes or labels or sliders that should be lined up in a table format, or packed into container, etc.
I've done the tutorials and am looking for a guide or overview about building complex gui apps with JUCE. I don't find any discussion like this in the docs - in fact, I've only found an alphabetical listing of classes, which means GUI stuff is randomly sprinkled about - no technical overview of the GUI system that I can find.
I'm interested to learn about best practices for layout of serious GUI apps. E.g. apps with hundreds of controls, large sections of which that may get created dynamically based on content, etc. Hand-coding coordinates/bounds in c++ is fine for apps with a couple sliders, but it feels unwieldly for doing large apps.
Where can I find information like this? For example, "Here's how Traktion is put together." :)
Thanks in advance for any tips!
Thomas Blom in Austin, TX