Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it possible to define LVGL config in a higher level format #11

Open
rafaelcaricio opened this issue May 30, 2020 · 0 comments · May be fixed by #82
Open

Make it possible to define LVGL config in a higher level format #11

rafaelcaricio opened this issue May 30, 2020 · 0 comments · May be fixed by #82
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@rafaelcaricio
Copy link
Collaborator

rafaelcaricio commented May 30, 2020

Would be nice to define library properties in a high level format than lv_conf.h file. Possibly, a lv_conf.toml would be a better approach. We could do validations and consistency checks at build time (build.rs) and generate the final lv_conf.h dynamically right before compilation.

An example content of how the lv_conf.toml could look like:

# ====================
#  Graphical settings
# ====================
[graphical]
# Maximal horizontal and vertical resolution to support by the library.
hor_res_max=480
ver_res_max=320

Users would be required to define only what differs from the default values. That way, it is easier to spot differences or custom configurations.

@rafaelcaricio rafaelcaricio added the enhancement New feature or request label May 30, 2020
@rafaelcaricio rafaelcaricio changed the title Make it possible to define LvGL config in a higher level format Make it possible to define LVGL config in a higher level format Jun 2, 2020
@rafaelcaricio rafaelcaricio added the help wanted Extra attention is needed label Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
@rafaelcaricio and others