Micropython plugin NOVA

[elmot]

Let's build another UI for the plugin, closer to ideas implemented in Thonny:

• Migrate from outdated and buggy adafruit-ampy, use direct connection via serial line and websockets instead
  • Webrepl support (see Wireless Programming for micropython #42)
    • Run webrepl commands under progress indicator #302
    • Implement automatic reconnect(ex. after target board reset) #307
    • Fix sudden board disconnect #305
    • Connect URL and password UI persistence. Password should be saved securely. #308
    • Communication failure handling #304
    • Make file transfer chunk-by-chunk in case of a large file #306
  • Native serial line support #303
• File manager (see File Watcher Support!!! #239, File Explorer like Thonny #178)
  • Implement "Create folder" on the device in the file manager #298
  • Delete folder/tree of files on the device #299
  • When a file in the file manager is clicked, open the file in editor. If the file is already open, activate the editor tab. #301
  • Implement context menu in the file tree #300
  • Disable the file manager if the target device is disconnected #309
  • Support drag-n-drop files in the file manager(low priority)
• UI improvements
  • New tool window #310
  • Instant code fragment execution ( see [Feature Request] Add "Execute Selection on Micropython device" context menu to code editor #182)
  • Rework settings UI
  • Drop unnecessary parts of old UI
• Misc tasks
  • Investigate if we can use linux port for testing(No)
  • Investigate if we can use qemu port for testing(No)
• New run configurations #311
  • Upload single file
  • Upload whole project
  • Activate REPL after upload
  • Soft reset after upload
• Rewrite documentation #334

[lukaskremla]

Thank you for picking up support of this useful plugin again! The list of upcoming features looks great, I am really looking forward to the update.

Only two things to add, could we also get standalone support for ESP32 devices? They work through ESP8266 but I am not sure if that is the way they are meant to work. And talking about making the plugin more like Thonny, the flashing speed is sometimes quite slow for uploading larger files (websites that have over 1 mb can take a while to upload. Speeding up the flashing would also make working with this plugin more pleasant.

[elmot]

Thanks, that's our plan, but we have a very low manpower now.
So any contribution, especially in testing, is more than welcome.

Standalone ESP32

Well, I tried ESP32 as ESP8266, and it more or less works.
Actually we hardly can keep up with all the boards and board variants, so I'd prefer make boards support more generic.
For best boards support, please push micropython guys to publish better stubs for their libraries.

flashing speed
Yeah, that's a problem. I hope that getting rid of adafruit-ampy should help a lot.
Out of my experiments, webrepl upload is drastically faster than serial, and I am focusing on that first. Thanks to ESP32 nature, that platform is going to be improved a lot.

[Josverl]

For best boards support, please push micropython guys to publish better stubs for their libraries.

micropython-stubs maintainer here;
@elmot Can you be a little bit more specific on what you need ?
As far as I am aware you are currently bundling stubs that are mostly a few years old , while there are much newer versions that already work in PyCharm.

Im sure they are not perfect , but neither are outdated stubs.
If I know what you want , then it may be possible to close the gap with , and reduce effort overall.

[elmot]

@Josverl, that's cool to see your encourage.
Yeah, now the stubs shipped are quite old, there were no active maintainers for a while.

I'd prefer to download the stubs from somewhere rather than keep ours inside the plugin. But don't see a reliable way to do that.

I think I have seen your repository, and I could not find the algorithm to find the best stub for a particular board.
Please help and give me the algorithm I can use.

[Josverl]

Pip is your friend.

The stubs for all released versions are published to PyPI, so if you know the port, and optionally the board, you can use pip to install the stubs into a venv or folder.
pip install -U micropython-<port>[-<board>]stubs --no-user --target ./typings

For both boards and ports you need the identical names as used in the micropython repo.

Adding a version or requirements-dev.txt file makes that more repeatable.
see

I have rolled-my-own docs for pycharm configuration, But more than happy to add or integrate with this project on specific or alternate instructions.

Update:
I have automated the generation of the docpage that lists of all stub packages available on PyPI.
https://micropython-stubs.readthedocs.io/en/main/packages.html

[Josverl]

One thing that is good about the manual updates that have been done on the stubs in this repo is that there contributors have taken the effort to improve the paramater and return type annotations beyond what I am able to generate automatically.
This was started by Howard Lovatt and continued by others, partly based on the micropython-stubs as is clear in several if not most of the stubs.
I do note that corresponding license has not been included, but I assume this has been an unintentional oversight.

I have ben considering to merge these annotations and @Overloads (back) into the micropython-stubs.
They will need to be verified against drift/differences with the current v1.23.0 ( and -preview) interfaces, either manually or automated. Whether or not I will actually do this will depend on the licensing , as I aim to keep the stubs under MIT license.

The plans in the MicroPython org are to 'adopt' the micropython-stubs and use them as the base for documentation (rather than the reverse) . While the the timelines are not quite clear, the intent is.

In the mean time I keep looking for improvements , this is something that could possibly reduce the effort here, while improving the quality overall.

[elmot]

Thanks, that's goldy.
I am afraid this piece of work is a bit out of scope of NOVA, that's next step.
I'd now focus on the new UI and the communication level, and then to a new stub approach.

[Josverl]

Makes sense, there are a few other options as well,
Tracking progress in the stubs repo : Josverl/micropython-stubs#762