Lines Matching +full:runs +full:- +full:on
9 --------------------
12 code and run it even on a bare metal architecture with limited resources.
18 - **Compact**: Fits and runs within just 256k of code space and 16k of RAM. No OS is needed, althou…
20 - **Compatible**: Strives to be as compatible as possible with normal Python (known as CPython).
21 - **Versatile**: Supports many architectures (x86, x86-64, ARM, ARM Thumb, Xtensa).
22 - **Interactive**: No need for the compile-flash-boot cycle. With the REPL (interactive prompt) you…
24 - **Popular**: Many platforms are supported. The user base is growing bigger. Notable forks:
26 - `MicroPython <https://github.com/micropython/micropython>`__
27 - `CircuitPython <https://github.com/adafruit/circuitpython>`__
28 - `MicroPython_ESP32_psRAM_LoBo <https://github.com/loboris/MicroPython_ESP32_psRAM_LoBo>`__
30 - **Embedded Oriented**: Comes with modules specifically for embedded systems, such as the
32 for accessing low-level hardware (I/O pins, ADC, UART, SPI, I2C, RTC, Timers etc.)
35 --------------
39 -----------------------
41 MicroPython `does not have a good native high-level GUI library <https://forum.micropython.org/view…
42 LVGL is an `Object-Oriented Component Based <https://blog.lvgl.io/2018-12-13/extend-lvgl-objects>`__
43 high-level GUI library, which seems to be a natural candidate to map into a higher level language, …
50 - Develop GUI in Python, a very popular high level language. Use paradigms such as Object-Oriented …
51 - Usually, GUI development requires multiple iterations to get things right. With C, each iteration…
60 - Fast prototyping GUI.
61 - Shortening the cycle of changing and fine-tuning the GUI.
62 - Modelling the GUI in a more abstract way by defining reusable composite Widgets, taking advantage…
64 - Make LVGL accessible to a larger audience. No need to know C to create a nice GUI on an embedded …
65 …`CircuitPython vision <https://learn.adafruit.com/welcome-to-circuitpython/what-is-circuitpython>`…
68 - Creating tools to work with LVGL at a higher level (e.g. drag-and-drop designer).
71 --------------
75 --------------------------
77 It's very much like the C API, but Object-Oriented for LVGL components.
85 .. code-block:: python
101 -----------------
108 simulator! It's a fully functional LVGL + MicroPython that runs entirely in the browser and allows …
111 `Click here to experiment on the online simulator <https://sim.lvgl.io/>`__
120 (+LVGL) on a Linux machine. (On a Windows machine you might need Virtual Box or WSL or MinGW or Cyg…
128 In the end, the goal is to run it all on an embedded platform. Both MicroPython and LVGL can be use…
132 - You would also need display and input drivers. You can either use one of the existing drivers pro…
134 - Drivers can be implemented either in C as a MicroPython module, or in pure Python!
139 - Display drivers:
141 - SDL on Linux
142 - X11 on Linux
143 - ESP32 specific:
145 - ILI9341
146 - ILI9488
147 - GC9A01
148 - ST7789
149 - ST7735
151 - Generic (pure Python):
153 - ILI9341
154 - ST7789
155 - ST7735
157 - Input drivers:
159 - SDL
160 - X11
161 - XPT2046
162 - FT6X36
163 - ESP32 ADC with resistive touch
167 ----------------------------------
169 - ``lv_micropython`` `README <https://github.com/lvgl/lv_micropython>`__
170 - ``lv_binding_micropython`` `README <https://github.com/lvgl/lv_binding_micropython>`__
171 - The `LVGL micropython forum <https://forum.lvgl.io/c/micropython>`__ (Feel free to ask anything!)
172 - At MicroPython: `docs <http://docs.micropython.org/en/latest/>`__ and `forum <https://forum.micro…
173 - `Blog Post <https://blog.lvgl.io/2019-02-20/micropython-bindings>`__, a little outdated.
177 ------------------------------------------
179 - LVGL is a git submodule inside `lv_micropython <https://github.com/lvgl/lv_micropython>`__
182 - When building lv_micropython, the public LVGL C API is scanned and MicroPython API is auto-genera…
189 For a summary of coding conventions to follow see the :ref:`coding-style`.
197 - When LVGL runs in MicroPython, all dynamic memory allocations (:cpp:func:`lv_malloc`) are handled…
198 …manager which is `garbage-collected <https://en.wikipedia.org/wiki/Garbage_collection_(computer_sc…
199 - To prevent GC from collecting memory prematurely, all dynamic allocated RAM must be reachable by …
200 - GC is aware of most allocations, except from pointers on the `Data Segment <https://en.wikipedia.…
202 - Pointers which are global variables
203 - Pointers which are static global variables
204 - Pointers which are static local variables
220 - Replace the global/static local var with :cpp:expr:`(LV_GLOBAL_DEFAULT()->_var)`
221 - Include ``lv_global.h`` on files that use ``LV_GLOBAL_DEFAULT``
222 - Add ``_var`` to ``lv_global_t`` on ``lv_global.h``
232 - `In the README <https://github.com/lvgl/lv_binding_micropython#memory-management>`__
233 - `In the Blog <https://blog.lvgl.io/2019-02-20/micropython-bindings#i-need-to-allocate-a-littlevgl…
248 - The basic idea is that we have ``void * user_data`` field that is used automatically by the Micro…
251 - Although called "user_data", the user is not expected to read/write that field. Instead, the Micr…
258 - Option 1: ``user_data`` in a struct
260 - There's a struct that contains a field called ``void * user_data``
262 …- A pointer to that struct is provided as the **first** argument of a callback registration functi…
263 - A pointer to that struct is provided as the **first** argument of the callback itself
265 - Option 2: ``user_data`` as a function argument
267 …- A parameter called ``void * user_data`` is provided to the registration function as the **last**…
269 - The callback itself receives ``void *`` as the **last** argument
271 - Option 3: both callback and ``user_data`` are struct fields
273 - The API exposes a struct with both function pointer member and ``user_data`` member
275 - The function pointer member receives the same struct as its **first** argument
286 - :cpp:type:`lv_anim_t` contains ``user_data`` field. :cpp:func:`lv_anim_set_path_cb` registers `pa…
288 - ``path_cb`` field can also be assigned directly in the Python code because it's a member of :cpp:…
290 - :cpp:func:`lv_imgfont_create` registers ``path_cb`` and receives ``user_data`` as the last argume…
294 .. _more-information-1:
299 - In the `Blog <https://blog.lvgl.io/2019-08-05/micropython-pure-display-driver#using-callbacks>`__
301 - `[v6.0] Callback conventions #1036 <https://github.com/lvgl/lvgl/issues/1036>`__
302 - Various discussions: `here <https://github.com/lvgl/lvgl/pull/3294#issuecomment-1184895335>`__
303 and `here <https://github.com/lvgl/lvgl/issues/1763#issuecomment-762247629>`__
304 and`here <https://github.com/lvgl/lvgl/issues/316#issuecomment-467221587>`__