kisvegabor
commented
3 years ago The initial list and the features ideas are not written into stone, please tell what you think about them.
Fix/Release scripts
IMO it has the highest priority. I meant these:
- a CI action to merge commits with
fix*message tostaging/v8.*branches - a CI or script to merge
staging/v8.*torelease/v8.*periodically or triggered manually - add CI to
portto automatically update submodules and conf files and minor and patch releases - add a simple build CI test to the
portprojects
Widgets to image buffer
Make possible to buffer widgets with all children into a single image to
- speed up rendering at the cost of memory usage
- allow transformation on any widgets (rotate, scale)
Scenes
It's a brand new concept about how a UI can be managed. It's a very simple but very powerful thing. Each widget has an int scene_active field and there is an lv_obj_set_scene(obj, secene_id) function which sends LV_EVENT_SCENE_UNLOAD, saves the scene_id and sends LV_EVENT_SCENE_LOAD to the widget. In other words, the scenes can be considered as "states" of the widget (I do NOT mean pressed, focused, etc style states here).
Use cases:
- There is a parent that can display 3 types of content, each is considered a scene. On scene load/unload you can hide/unhide, fade, etc between the possible contents
- There is a screen with "error" and "normal" scenes: on error, some styles are changed, and an error message is displayed. On "normal" these are reverted.
-
A list has 2 scenes: hidden, visible. On scene load instead of hiding/unhiding, any complex animation can be started.
The gist is, this way the widgets encapsulate their scenes and there is a uniform API for changing scenes. As the current scene is saved it can be automatically unloaded. Without this feature, the user needed to keep track of the current state to know what to unload, but now it'd be backed into the widgets.
Add/Subtract/exclusive mask types
Now the masks of LVGL can only subtract from an 0xff filled mask. It'd be great to allow "building back" parts too.
Style components
Right now it's a little bit cumbersome to manage differently looking versions of the same widget type. E.g. button, error button, warning button, border only button, border only error button, rounded button, rounded error button, etc. To manage it effectively there should be btn, btn_border_only, btn_rounded, btn_error, btn_warning styles. The combination of these styles needs to be added manually to the created buttons. It's possible to create btn_error_create() and similar functions but it's also cumbersome. If the "role" of the button changes meanwhile, it's also hard to manage now (i.e. remove styles and add new ones). The idea to solve it looks like this:
uint32_t ERROR_BTN_ROUNDED = lv_component_create_from(LV_COMPONENT_BTN);
lv_component_add_style(ERROR_BTN_ROUNDED, &error_btn_style, LV_PART_MAIN);
lv_component_add_style(ERROR_BTN_ROUNDED, &rounded_btn_style, LV_PART_MAIN);
lv_obj_t * btn = lv_btn_create(parent);
lv_obj_set_component_type(btn, ERROR_BTN_ROUNDED);lv_obj_set_component_type can be called any time to change the type and ERROR_BTN_ROUNDED can be updated anytime too, and all objects will be updated.
The implementation is quite simple: If functions like lv_obj_style_get_bg_color don't find a style on the object, they check the styles assigned to the component ID too.
It will save memory and give more performance because the styles with the same selector can be merged in ERROR_BTN_ROUNDED and only the component ID needs to be saved in the object, instead of many styles.
Overflow:visible
Same as in HTML
Hover
Same as in HTML
More grid features
I'm specifically thinking about repeat(auto-fill, minmax( <value> px, 1fr)) but ideas are welcome
lishaoenxm
guoweilkd
embeddedt
C47D
puzrin
xiaoxiang781216
mysterywolf
amirgon
X-Ryl669
tyler-gilbert
rzr
MouriNaruto
tore-espressif
lanistor
v8.1 is released so I open this issue to plan v8.2. In order really have a "Planning phase" for the next release I'm about to leave this issue open until 31 December and focus on implementation after that.
I add my current ideas here (see explanation in the next comment), please comment if you also have some features ideas in mind or share your opinion about the planned features.
Rendering
Features
Add/Subtract/exclusive mask types #2668(postponed for the next release)Others