Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.
10. QHQ and libsimple
libsimple
Simple is the independent widget toolkit
extracted from Quinzee and TRIGLAV Setup. QHQ links its installed CMake target
simple::simple; sources, assets and licences live in the dependency cache
(build notes (source checkout required)). It renders into one ARGB surface
and talks to the machine through a platform (display + input):
| Backend | Use |
|---|---|
rasta |
Development: an SDL2 window (bin/tools/rasta) shows a shared framebuffer file and sends input over UDP |
framebuffer |
Native console: /dev/fb0 + evdev |
offscreen |
Tests and --screenshot |
Key pieces QHQ uses: application (event loop, timers, focus), app_shell
(header, navigator, content host, footer), navigator in hierarchical mode,
panel, form, label, text_field, combo_box, list_view, button,
stack. Make toolkit changes in the Simple project, then update Quinzee's
pinned revision. QHQ uses flat includes such as simple/button.hpp.
QHQ structure
| File | Role |
|---|---|
main.cpp |
Options, platform, application, window; screenshot mode; signal flag |
qhq_window.* |
Shell, navigation catalogue, pages, controller actions |
qhq_provisioning.cpp, qhq_queues.cpp, qhq_observability.cpp |
Deployment/engine, queue and diagnostics/query pages |
qhq_service_bus.cpp, qhq_functions.cpp |
Messaging inventory and function-app lifecycle using public ARM APIs |
qhq_identity*.cpp, qhq_hosting_settings.cpp |
Graph identities/roles and hosting settings, public API mutations and private input handling |
tab_view.* |
Tab buttons over a stack |
background_jobs.* |
Worker threads with UI-thread delivery |
cloud_client.* |
HTTP client for the emulator's public APIs |
assets/logos/quinzee_mark.svg |
Header brand mark |
Threading model
UI thread worker (std::async)
button → qhq_window action
jobs_->run(work, done) ───────► cloud_client call (blocking, ≤10 s)
timer (40 ms, only while │
jobs are pending) ◄──────────────── result
done(result) → update widgets
Callbacks check that the client they used is still the current one, so a
reconnect discards stale answers. background_jobs is destroyed before
anything else in the window and waits for running work.
Adding a page
- Add the service (and, if new, its category) to
navigation_catalogue(). - Write
*_page()returning apage_column()ofsection()panels; usetab_viewif it has several parts, and register it intabs_. - Register it in
build()withadd(id, page). - Add
cloud_clientcalls and a controller action that runs them as jobs. - Extend
integration.qhqto drive the action and visit the page.
Visual checks
qhq --screenshot renders any page offscreen after the emulator has
answered; make qhq-screenshots produces all of them. During F5 the Rasta
framebuffer file build/qhq/rasta.fb holds the live frame (BGRA), which
ffmpeg -f rawvideo -pix_fmt bgra -video_size 1440x900 -i build/qhq/rasta.fb frame.png converts.
The observability page uses authenticated public diagnostics and workspace-query APIs. It validates result shape before rendering, bounds displayed rows and discards replies from an earlier connection. Monitoring resource creation stays in ARM/Bicep; QHQ does not expose a separate workspace/component wizard.