JUCE Visual Designer — Foundation Build
This is the initial native JUCE C++ foundation for the planned visual designer / IDE.
Current implementation
- Native JUCE desktop window
- Professional dark workspace foundation
- Component palette (Label, Panel, Slider, Knob)
- Canvas with selectable and draggable design items
- Basic properties display
- C++ code editor using JUCE CodeEditorComponent
- Design / Code / Split workspace modes
- Initial environment scanner for JUCE, CMake, Visual Studio and Windows SDK
Not yet implemented
This is a foundation build, not the complete IDE. The following stages remain:
- True JUCE widget preview and full property editing
- Resize handles, multi-select, alignment, grid snapping
- JSON project persistence
- Generated-code ownership and safe manual-code regions
- JUCE-version-specific code generation
- Full CMake configure/build/run/debug pipeline
- Error-to-source navigation
- Portable single-EXE packaging and verification
Requirements
- Windows 10/11 x64
- CMake 3.22+
- A supported Visual Studio / MSVC installation
- JUCE source tree or JUCE CMake package
Configure with your installed Visual Studio
The project intentionally does not force Visual Studio 2022. Let CMake select its default generator, or explicitly select an installed generator.
Automatic CMake generator
cmake -S . -B build -DJUCE_ROOT=C:/JUCE
cmake --build build --config Release
Explicit Visual Studio 2019
cmake -S . -B build-vs2019 -G "Visual Studio 16 2019" -A x64 -DJUCE_ROOT=C:/JUCE
cmake --build build-vs2019 --config Release
Explicit Visual Studio 2022
cmake -S . -B build-vs2022 -G "Visual Studio 17 2022" -A x64 -DJUCE_ROOT=C:/JUCE
cmake --build build-vs2022 --config Release
Do not reuse the same build directory when switching CMake generators.
JUCE discovery
The CMake project checks, in order:
JUCE_ROOTCMake variableJUCE_ROOTenvironment variableC:/JUCEJUCE_DIRthroughfind_package(JUCE CONFIG)
Important
The environment scan is informational and does not install or modify Visual Studio, JUCE, CMake or Windows SDK. The current Build and Run buttons are UI placeholders; the actual asynchronous build pipeline is a subsequent implementation stage.
Portable project and settings storage
On first launch, the application creates data beside the running executable:
config.inistores the dark theme selection, last view, window size, panel widths/heights, and last project path.Projects/DefaultProject/is created as a starter JUCE CMake project.- Existing project files are never overwritten by startup initialization.
The auto-clean build script backs up config.ini and Projects/ before deleting the build folder, then restores them beside the newly built executable. If the executable folder is write-protected (for example, under Program Files), run it from a writable folder.