Open AGlass0fMilk opened 5 years ago
Sounds very reasonable. However, I'm not sure we can estimate the ROM usage because it depends on the compiler optimization, architecture etc.
But telling that by placing an lv_win
object, lv_btn
, lv_label
, lv_cont
and lv_page
will be also enabled might be useful.
I think a nice feature of the GUI builder would be to automatically disable/enable lvgl modules based on the widgets that are included in a design. This would save the user time of going through and determining all the dependencies for a widget and configuring it themselves.
When a user places a widget that relies on a module that is not currently enabled, we can pop up a prompt that asks the user if they want to enable the required modules and include estimates on how much ROM/RAM the addition will use.
Kind of like when you build a car online, and when you add options sometimes it will require other options to be added as well (and more money too :laughing:)
I think embedded developers will appreciate the focus on resource constraints and making usage more visible during design rather than at build-time.