MicroPython Forum (Archive)

Mike Teachman wrote: ↑

Wed Nov 21, 2018 3:01 pm

...I wrote a C file providing examples of the patterns used to map uPy calls to C, for both module functions and class methods...

That is excellent - it would have saved me a lot of time if I'd known it existed Researching it must have taken a lot of work.

Thanks Mike

Maybe some of this info might find it's way into the official MP docs under a firmware developer section.

I've long thought that such a guide would be useful. The question is who has sufficient experience to write it - plus the time and motivation to do so. I lack sufficient know-how

It would be really awesome if such a guide included details of DMA and IRQ interfacing - for the Pyboard at least.

mattyt wrote: ↑

Sat Nov 24, 2018 11:06 pm

This is a fantastic resource, thanks Mike! Just what I needed.

Cool. Thanks for letting me know it was useful! If you see anything amiss please let me know and I'll tune it up. I'll post it to the dev thread as well.

[/quote]

pythoncoder wrote: ↑

Sun Nov 25, 2018 8:58 am

I've long thought that such a guide would be useful

I couldn't agree more. Guides are so helpful. For example, your uasyncio tutorial is golden. It's changed how I program in uPy.
Sometimes I wonder if lack of developer "how-to" resources are constraining the development of MicroPython ports. Take the ESP32 port for example. Very little of the ESP-IDF is implemented in the mainline. If better learning aids were available perhaps we'd see developers inspired to expose more ESP32 features in the mainline of uPy?

Would it help to start a new topic in the developers thread to see if there is interest in collaborative work on a developer's guide? (we should likely move out of this GUI topic anyhow ...)

Mike Teachman wrote: ↑

Mon Nov 26, 2018 4:19 pm

...
Would it help to start a new topic in the developers thread to see if there is interest in collaborative work on a developer's guide? ...

Good idea, worth a try.

Thank you for your kind comment about my uasyncio effort. I keep banging the drum for asynchronous programming because that's how most nontrivial firmware is written. Including (to get back on topic) GUI's

There is an effort going to port LittlevGL to Micropython.

Open issue: https://github.com/littlevgl/lvgl/issues/557
Micropython fork (work on progresss): https://github.com/kisvegabor/lv_mpy

agonnen wrote: ↑

Mon Jan 21, 2019 8:25 pm

There is an effort going to port LittlevGL to Micropython.

Open issue: https://github.com/littlevgl/lvgl/issues/557
Micropython fork (work on progresss): https://github.com/kisvegabor/lv_mpy

Very interesting project. Is my understanding correct that for now it is possible to test only with Unix port?

Yes.
The plan is to include it as part of lvgl release soon.

What are your plans for integration with ESP32 port?

Actually I'm testing it with my ESP32 Micropython port which is a fork of MicroPython_ESP32_psRAM_LoBo.
After lvgl release is out, I might take the effort to create a "pure" ESP32 Micropython port with lvgl example, it should be quite easy.