And… to answer my 1st question myself: just me being a newbee. Of course lv_xml_create() just accepts a parent node, I have to read the code before I ask questions! Anyway, created some bindings for xml-loader. Works great! Thanks!
Let me answer multiple questions here:
- Yes, there will be a VSCode plugin, planned for v0.2 so in a few month.
- You can choose to export C code and forget the XMLs. These are pure LVGL UI code.
- We are thinking hard about how get rid of Docker and provided a simpler getting started flow.
- The
expat
XML parser is only a few files ad you can build it with LVGL - We have selected XML and will stick to it for a while for sure. There is no plan to add support to YAML in the near future.
- With
lv_xml_create(parent, "widget_name", attributes_array)
you can create widgets on any parents to replace “innerHTML”. The widgets created bylv_xml_create
are identical to the widgets created bylv_..._create()
. So you can delete, move, adjust them as you wish. - I’ll add an
lv_obj_set/get_name
function very soon. The related discussion is here. There also should be anlv_obj_get_by_name(parent, "name")
function which returns the first child with that name (maybe not direct child, but grand child).