Work began on LVGL's UI Editor 🎉

[buccaneer-jak]

I would place the readability order as TOML, YAML (both close) followed by JSON then XML

[Bryght-Richard]

While we’re all painting the markup-barn, I say XML because if you make a merge error, it usually isn’t XML. With YAML, it’s usually still YAML, just wrong. That said, YAML is used already in lv_i18n for translation files.

On a different topic, how our code reference objects created by the LVGL UI editor? Will there be object pointers generated for each object, dynamically populated as screens are created, and freed and nulled as screens are destroyed? For each screen, then child-pointers? Just curious.

[kisvegabor]

@Bryght-Richard

On a different topic, how our code reference objects created by the LVGL UI editor? Will there be object pointers generated for each object, dynamically populated as screens are created, and freed and nulled as screens are destroyed? For each screen, then child-pointers? Just curious.

Great question! We can’t see all the details yet, but I’d like to focus on Observers to separate the UI and application logic.