Go to file
2021-06-18 14:13:41 +02:00
.github chore(docs) always deploy master to docs/master as well 2021-06-07 13:09:16 -04:00
docs docs update lv_fs.h, layer and align.png to v8 2021-06-16 14:14:55 +02:00
examples docs list all examples on one page 2021-06-14 23:16:31 +02:00
scripts fix(style) use C files for style set functions instead of designated initializers 2021-05-31 19:27:35 +02:00
src fix(coords) fix using large coordinates 2021-06-17 11:32:49 +02:00
tests fix(test) silence make 2021-06-18 14:13:41 +02:00
zephyr Add support for Zephyr intergartion (#1979) 2021-01-04 14:18:11 +01:00
.editorconfig merge master 2021-01-23 23:50:00 +01:00
.gitignore chore(docs) upgrade to Sphinx 4 and use requirements.txt 2021-05-14 20:25:40 -04: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
CMakeLists.txt feat(cmake) Allow building LVGL without kconfig (#2165) 2021-03-25 20:15:39 +01:00
component.mk update to work with Arduino (#2200) 2021-05-03 20:26:10 +02:00
Kconfig add span widget (#2227) 2021-05-13 17:42:33 +02:00
library.json update version numbers to v8.1.0-dev 2021-06-14 13:51:45 +02:00
library.properties update version numbers to v8.1.0-dev 2021-06-14 13:51:45 +02:00
LICENCE.txt Update LICENCE.txt 2020-05-31 23:03:38 +02:00
lv_conf_template.h update version numbers to v8.1.0-dev 2021-06-14 13:51:45 +02:00
lvgl.h update version numbers to v8.1.0-dev 2021-06-14 13:51:45 +02:00
lvgl.mk update make files 2021-03-16 20:53:42 +01:00
README.md docs(README) update links, examples, and add services menu 2021-06-16 10:52:40 +02: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 · Docs · Forum · Services · Interactive exmamples


Table of content

Overview

Features

  • Powerful building blocks: buttons, charts, lists, sliders, images, etc.
  • Advanced graphics engine: animations, anti-aliasing, opacity, smooth scrolling, blending modes, etc
  • Supports various input devices: touchscreen, mouse, keyboard, encoder, buttons, etc.
  • Supports multiple displays
  • Hardware independent, can be use with any microcontroller and display
  • Scalable to operate with little memory (64 kB Flash, 16 kB RAM)
  • Multi-language support with UTF-8 handling, CJK, Bidirectional and Arabic script support
  • Fully customizable graphical elements via CSS-like styles
  • Powerfule layouts inspired by CSS: Flexbox and Grid
  • OS, External memory and GPU are supported but not required. (built in support for STM32 DMA2D, and NXP PXP and VGLite)
  • Smooth rendering even with a single frame buffer
  • Written in C and compatibile with C++
  • Micropython Binding exposes LVGL API in Micropython
  • Simulator to develop on PC without embedded hardware
  • 100+ simple Examples
  • Documentation and API references online and in PDF

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 > 16 kB > 48 kB
Draw buffer > 1 × hor. res. pixels > 1/10 screen size
Compiler C99 or newer

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

Supported platforms

LVGL is completely platform independent and can be used with any MCU that fulfills the requirements. Just to mention some platforms:

LVGL is also avaiable as:

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 examples folder.

LVGL button with label example

C

lv_obj_t * btn = lv_btn_create(lv_scr_act());                   /*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_add_event_cb(btn, btn_event_cb, LV_EVENT_CLICKED, NULL); /*Assign a callback to the button*/

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

void btn_event_cb(lv_event_t * e)
{
  printf("Clicked\n");
}

Micropython

Learn more about Micropython.

def btn_event_cb(e):
  print("Clicked")

# Create a Button and a Label
btn = lv.btn(lv.scr_act())
btn.set_pos(10, 10)
btn.set_size(100, 50)
btn.add_event_cb(btn_event_cb, lv.EVENT.CLICKED, None)

label = lv.label(btn)
label.set_text("Button")
label.center()

Services

LVGL Kft was established to provide a solid background for LVGL library. We offer several type of services to help you in UI development:

  • Graphics design
  • UI implementation
  • Consulting/Support

For more information see https://lvgl.io/services Feel free to contact us if you have any questions.

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 the LVGL organization.

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