xtc/docs/GUI.md

GUI guidelines

Use FLTK/C++ for windows, menus, dialogs, and the event loop. Keep all audio engine and project-domain logic in C.

Main views:

• Sequencer: tracks, clips, ruler, playhead, selection, zoom and scrolling.
• Mixer: channels, faders, pan, mute/solo and meters.
• Modular graph: nodes, ports, connections, validation feedback.
• Transport: play/stop/record, tempo, meter, loop and position.

Use custom-drawn widgets where ordinary controls are not a good fit: timeline, waveforms, piano roll, mixer strips and graph canvas. Keep drawing separate from project mutation. Never call FLTK from the audio thread.

Visual direction: compact, high-contrast, restrained dark interface. Avoid excessive animation and modal configuration. Recreate broad usability ideas, not energyXT's exact artwork or proprietary resources.