I still haven't started working with this module.
I'm currently trying to integrate LVGL into Annex, but not on this display.
This module has a specific display that requires a dedicated driver, which is not yet widely supported.
In the meantime, I'm working on implementing a new GUI based on LVGL and LovyanGFX (for the display driver).
However, LVGL is so comprehensive (and complex at the same time) that it can quickly become overwhelming due to the huge number of available functions. I'm trying to explore its real capabilities.
As for video, it's certainly not a priority and is of relatively low interest at the moment.
That said, LVGL includes some animation features, and it might be worth exploring what can be done with them.
JC3248W535EN
- cicciocb
- Site Admin
- Posts: 2792
- Joined: Mon Feb 03, 2020 1:15 pm
- Location: Toulouse
- Has thanked: 592 times
- Been thanked: 1993 times
- Contact:
Re: JC3248W535EN
Wow, you sound busy.
I think that one of the advantages of LVGL is the availability of GUI editors.
While it's fun to build GUIs by hand with Annex, it gets somewhat tedious, and when you want something that looks slick and modern, without putting a lot of work into it, you end up with LVGL or similar libraries.
About the drivers: Recently every new ESP32 module with touch seems to use a different driver, often some that I've never heard of.
I hate it.
I'm still searching for the ONE module that will become the standard for my projects, but so far all of them have their disadvantages.
I'm thinking about just using bare touch display boards, like this one:
https://spotpear.com/shop/Raspberry-Pi- ... 0x320.html
and conneting to whatever ESP32 board that fits my current needs.
But of course, they're using uncommon touch ICs.
What do you prefer?
I think that one of the advantages of LVGL is the availability of GUI editors.
While it's fun to build GUIs by hand with Annex, it gets somewhat tedious, and when you want something that looks slick and modern, without putting a lot of work into it, you end up with LVGL or similar libraries.
About the drivers: Recently every new ESP32 module with touch seems to use a different driver, often some that I've never heard of.
I hate it.
I'm still searching for the ONE module that will become the standard for my projects, but so far all of them have their disadvantages.
I'm thinking about just using bare touch display boards, like this one:
https://spotpear.com/shop/Raspberry-Pi- ... 0x320.html
and conneting to whatever ESP32 board that fits my current needs.
But of course, they're using uncommon touch ICs.
What do you prefer?
- cicciocb
- Site Admin
- Posts: 2792
- Joined: Mon Feb 03, 2020 1:15 pm
- Location: Toulouse
- Has thanked: 592 times
- Been thanked: 1993 times
- Contact:
Re: JC3248W535EN
I'm actually playing with a ILI9341 and a resistive touch, a very low level configuration that I want challenge to see what can be done.
Yes, there are some editors for LVGL but I think that they generate source code in C that, unluckily, cannot be used directly with Annex.
I think that is probably easier to integrate LVGL using a C environment than trying to integrate with an interpreted environment like Annex so I'm still not sure if this "target" will be achieved.
About the touchscreen, the idea is to implement lovyanGFX that supports many TFT and many Touchscreen but, for sure, the best results will come from capacitive touchscreen.
If the device is supported by lovyanGFX, it will be supported
Yes, there are some editors for LVGL but I think that they generate source code in C that, unluckily, cannot be used directly with Annex.

I think that is probably easier to integrate LVGL using a C environment than trying to integrate with an interpreted environment like Annex so I'm still not sure if this "target" will be achieved.
About the touchscreen, the idea is to implement lovyanGFX that supports many TFT and many Touchscreen but, for sure, the best results will come from capacitive touchscreen.
If the device is supported by lovyanGFX, it will be supported
Re: JC3248W535EN
lovyanGFX already supports a bunch of graphics and touch drivers, and it seems to be not too difficult to add new ones.
Also, it has some nice fonts.
You know what I really want?
Something like a lightweight X Window for embedded systems, to abstract the GUI completely from the hardware, so you have to build the GUI only once, and can display it on a TFT connected to a microcontroller, in a web browser, a native app, on two devices simultaneously, etc.
Also, it has some nice fonts.
You know what I really want?
Something like a lightweight X Window for embedded systems, to abstract the GUI completely from the hardware, so you have to build the GUI only once, and can display it on a TFT connected to a microcontroller, in a web browser, a native app, on two devices simultaneously, etc.