Export Architecture

Understand the boundary between generated LVGL, stable hooks, developer logic and ESP-IDF.

Architecture flow

text

ForgeUI Studio
  → generated LVGL UI
  → stable event and control API
  → developer application logic
  → ESP-IDF
  → ESP32-P4

File roles

File	Role
90_Studio_Export.c / .h	Studio-managed, generated and replaceable UI/runtime code.
95_UserEvents.c / .h	Generated stubs in live firmware; developer-owned integration layer in a standalone export.
app_main.c or main.c	Application startup and developer-owned integration, depending on the exported template.
CMakeLists.txt	ESP-IDF source, asset and dependency registration generated by the exporter.
assets/*/.c	Converted image data and LVGL descriptors compiled into firmware.

API direction

Generated inputs call developer code through FG_On_* hooks. Developer code controls generated outputs through FG_Set_* functions. This directional contract prevents product behavior from being embedded inside replaceable UI generation.