While adding IR-to-project compilation support for the LVGL widget palette, I noticed that several widgets can be placed on a page but have no editing capability at all — empty property grid, and code generation is just the bare create call:
| widget |
properties |
codegen |
| Chart |
none |
lv_chart_create only — no series/range/point-count |
| Table |
none |
lv_table_create only — no col/row count, no cells |
| List |
none |
lv_list_create only — no items |
| Menu |
none |
lv_menu_create only — no menu structure |
| TileView |
none |
lv_tileview_create only — no tiles |
By contrast Tabview is fully modeled (tabs as editable children, ~40 lines of codegen), as are Roller, Dropdown, QRCode etc. — so the infrastructure clearly exists.
Is native editing support for any of these on the roadmap? I'm especially interested in Chart and Table (the most commonly needed on MCUs).
Context: we currently bridge the gap outside the project file — our IR compiler validates the structure (series/ranges, table header, ...) and emits a generated ui_ext.c that configures the bare objects at runtime via the objects.<id> handles from screens.h. That works, but it means the structure lives outside the .eez-project and is invisible in the editor.
If any of these are wanted but unplanned, I'd be happy to look into a contribution (the Chart/Table property surface, in the spirit of #1049).
While adding IR-to-project compilation support for the LVGL widget palette, I noticed that several widgets can be placed on a page but have no editing capability at all — empty property grid, and code generation is just the bare create call:
lv_chart_createonly — no series/range/point-countlv_table_createonly — no col/row count, no cellslv_list_createonly — no itemslv_menu_createonly — no menu structurelv_tileview_createonly — no tilesBy contrast Tabview is fully modeled (tabs as editable children, ~40 lines of codegen), as are Roller, Dropdown, QRCode etc. — so the infrastructure clearly exists.
Is native editing support for any of these on the roadmap? I'm especially interested in Chart and Table (the most commonly needed on MCUs).
Context: we currently bridge the gap outside the project file — our IR compiler validates the structure (series/ranges, table header, ...) and emits a generated
ui_ext.cthat configures the bare objects at runtime via theobjects.<id>handles fromscreens.h. That works, but it means the structure lives outside the .eez-project and is invisible in the editor.If any of these are wanted but unplanned, I'd be happy to look into a contribution (the Chart/Table property surface, in the spirit of #1049).