Go to file
Xiang Xiao c20d5d81f2
Minor fix found in Kconfig (#2005)
* Trim trailing whitespace from Kconfig

* Replace all tab to space in Kconfig

* Add more dependence between opions to Kconfig

* Add LV_USE_FONT_SUBPX for LV_FONT_SUBPX_BGR in Kconfig

* Fix typo error(LV_USE_DROPBOX->LV_USE_DROPDOWN) in Kconfig

* Remove LV_THEME_MATERIAL dependence from the child of LV_THEME_DEFAULT_FLAG

since LV_THEME_DEFAULT_FLAG already depends on LV_THEME_MATERIAL

* Rename LV_MEM_SIZE_BYTES to LV_MEM_SIZE_KILOBYTES

since this opion use KiB as the unit
2021-01-11 14:38:17 +01:00
.github Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00
docs Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00
examples Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00
scripts Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00
src Minor fix found in Kconfig (#2005) 2021-01-11 14:38:17 +01:00
tests Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00
zephyr Add support for Zephyr intergartion (#1979) 2021-01-04 14:18:11 +01:00
.editorconfig Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00
.gitignore reorganize release script 2020-10-21 14:06:48 +02:00
.gitmodules remove historic pycparser. It is here before micropython sources moved to another repository and history rewritten 2019-01-24 00:17:37 +02:00
CHANGELOG.md Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00
CMakeLists.txt Add support for Zephyr intergartion (#1979) 2021-01-04 14:18:11 +01:00
Kconfig Minor fix found in Kconfig (#2005) 2021-01-11 14:38:17 +01:00
library.json Update master version 2021-01-05 16:04:29 +01:00
library.properties Update master version 2021-01-05 16:04:29 +01:00
LICENCE.txt Update LICENCE.txt 2020-05-31 23:03:38 +02:00
lv_conf_template.h Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00
lvgl.h Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00
lvgl.mk Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00
README.md Remove the double empty lines from all source files (#2009) 2021-01-11 14:28:00 +01:00

LVGL - Light and Versatile Graphics Library

LVGL provides everything you need to create embedded GUI with easy-to-use graphical elements, beautiful visual effects and low memory footprint.

Website · Online demo · Nightly demos · Docs · Forum


Features

  • Powerful building blocks: buttons, charts, lists, sliders, images, etc.
  • Advanced graphics: animations, anti-aliasing, opacity, smooth scrolling
  • Use various input devices: touchscreen, mouse, keyboard, encoder, buttons, etc.
  • Use multiple displays: e.g. monochrome and color display
  • Hardware independent to use with any microcontroller or display
  • Scalable to operate with little memory (64 kB Flash, 10 kB RAM)
  • Multi-language support with UTF-8 handling, Bidirectional and Arabic script support
  • Fully customizable graphical elements via CSS-like styles
  • OS, External memory and GPU are supported but not required
  • Smooth rendering even with a single frame buffer
  • Written in C for maximal compatibility (C++ compatible)
  • Micropython Binding exposes LVGL API in Micropython
  • Simulator to develop on PC without embedded hardware
  • Examples and tutorials for rapid development
  • Documentation and API references

Requirements

Basically, every modern controller (which is able to drive a display) is suitable to run LVGL. The minimal requirements are:

Name Minimal Recommended
Architecture 16, 32 or 64 bit microcontroller or processor
Clock > 16 MHz > 48 MHz
Flash/ROM > 64 kB > 180 kB
Static RAM > 2 kB > 4 kB
Stack > 2 kB > 8 kB
Heap > 2 kB > 8 kB
Display buffer > 1 × hor. res. pixels > 10 × hor. res. pixels
Compiler C99 or newer

Note that the memory usage might vary depending on the architecture, compiler and build options.

Just to mention some platforms:

Get started

This list shows the recommended way of learning the library:

  1. Check the Online demos to see LVGL in action (3 minutes)
  2. Read the Introduction page of the documentation (5 minutes)
  3. Get familiar with the basics on the Quick overview page (15 minutes)
  4. Set up a Simulator (10 minutes)
  5. Try out some Examples
  6. Port LVGL to a board. See the Porting guide or check the ready to use Projects
  7. Read the Overview page to get a better understanding of the library (2-3 hours)
  8. Check the documentation of the Widgets to see their features and usage
  9. If you have questions go to the Forum
  10. Read the Contributing guide to see how you can help to improve LVGL (15 minutes)

Examples

For more examples see the lv_examples repository.

Button with label

lv_obj_t * btn = lv_btn_create(lv_scr_act(), NULL);     /*Add a button to the current screen*/
lv_obj_set_pos(btn, 10, 10);                            /*Set its position*/
lv_obj_set_size(btn, 100, 50);                          /*Set its size*/
lv_obj_set_event_cb(btn, btn_event_cb);                 /*Assign a callback to the button*/

lv_obj_t * label = lv_label_create(btn, NULL);          /*Add a label to the button*/
lv_label_set_text(label, "Button");                     /*Set the labels text*/

...

void btn_event_cb(lv_obj_t * btn, lv_event_t event)
{
    if(event == LV_EVENT_CLICKED) {
        printf("Clicked\n");
    }
}

LVGL button with label example

LVGL from Micropython

Learn more about Micropython.

# Create a Button and a Label
scr = lv.obj()
btn = lv.btn(scr)
btn.align(lv.scr_act(), lv.ALIGN.CENTER, 0, 0)
label = lv.label(btn)
label.set_text("Button")

# Load the screen
lv.scr_load(scr)

Contributing

LVGL is an open project and contribution is very welcome. There are many ways to contribute from simply speaking about your project, through writing examples, improving the documentation, fixing bugs to hosing your own project under in LVGL.

For a detailed description of contribution opportunities visit the Contributing section of the documentation.