BIG CHANGE COMMING SOON

[kdschlosser]

I have really grown tired of the API for the binding. It is a complete mess and really doesn't make hell of a lot of sense the way it is done. I have been working with the code generation script and close to be finished with flattening the API so it aligns with the LVGL C API. That means no more guessing at where things are. You will be able to easily use the LVGL API documentation to look up what you need. I believe this is going to speed up development time for people.

The way I am looking at it is if people want to continue to use the current API they can write wrapper classes in Python to handle it.

I have also spent some time working over the stub file generation script and that is really close to be spot on perfect with no errors in it. This is am really happy about as well because I am going to be able to develop a documentation build system using that stub file output. The developers of Sphinx have finally added support for reading stub files. They added it really fast too, only took 2-3 years from when I requested it 😮 😠 ... But now that it has finally been added I will be putting it to use if I can figure out how to. Hopefully it automatically does it but I have a suspicion that it's not going to be that easy...

The last compile run is done so I am going to check it out. If it has finished building the stub file and the file is the way it should be then I am going to move the code to a fresh pull of the repo and see if it compile properly without any kickbacks. Some changes I made are causing a failure before the generated C code compiles but after the stub file is created and the C code is generated. I need to make sure it compiles 100% before I commit the changes.

[Kalrkloss]

That sound very promising.

I'm currently having a hard time starting with LVGL on Micropython, because the documentation is a mess.
I'm spending my time fighting with things like the (Micropython) example code in the LVGL docs using lv.scr_act(), and throwing errors, only to find out that I actually have to use lv.screen_active().

This makes me want to bite someone.

Many thanks for doing this.
If you need help with hardware problems, just ask. I'm a hardware developer, so I can help with debugging busses and such things, but I'm unfortunately not a good coder.

[kdschlosser]

This project differs from the official binding which is lv_binding_micropython which the examples are made for lvgl v8.

when you compile this project there is what is called a stub file that is created. It gets placed into the root of the project. the filename is "lvgl.pyi" If you are using an IDE like VS Code, Visual Studio or PyCharm and you place that into the root of the project you are writing for MicroPython code completion and intellisense will start to work. Now the stub file is not perfect and it does have some issues with it. But ti will still help you when writing your code.

[glueckm]

Hi Kevin,
I wanted to know if you are still planing on chaning the bindings to a direct mapping to the C files and what the status of that is.

Thanks,
Martin

[kdschlosser]

been busy, so it's not high on my priorities to get done. I can tell you that I cannot upgrade the version of LVGL because they made some changes that completely tanked the code generator. So something needs to be done and I don't think spending more time into the existing generator is the right thing to do.

[sam0910]

This repo is the unique bridge between two essential worlds, MicroPython and LVGL.
Thank you for the hard work you put into this system every day.
I think we are all excitedly expecting good news and cheering you on.
You are a true hero to this unique job, just pure appreciation!

[kdschlosser]

It gonna be a while before I do anything to upgrade this repo to use the latest LVGL code. I am currently working on what will hopefully fund my retirement..

take a look...
https://github.com/HarnessDesigner/HarnessDesigner