How to contribute to code editor?

[DerFuchs]

Hey there,

I'm coaching a WRO team. The kids aren't ready to use pure code yet, so they stick to the visual block editor. I noticed some challenges when using the editor and I'm missing some features, too. As I'm a web developer, I planned to implement these features by myself and then make a pull request to contribute to the project. But unfortunately it seems like there's no version with the block editing feature available publicly.

What I planned to implement:

• disable ( = comment out) single blocks to not having them to be dragged out of the code
• possibility to move multiple selected blocks without moving the blocks below as well
• folders for the file selector
• "versioning" by copying files into a sub folder
• maybe even make it an electron app to gain access to the computer's file system to achieve versioning with git
• keep the listed blocks within the selection menu the same size, independent from block editor zoom
• Nameable visually distinguishable areas for putting in related functions (tasks) AND
• Listing functions based on the area where they have been put in
• Option to disable the auto-arrange button

I don't know if I can achieve implementing all of these features but Is there any chance to get access to an actual version of Pybricks code with the visual editor feature included?

Greetings from Germany,
Michael

[dlech]

How to contribute to code editor?

This is the best first step. We have limited resources, so best to discus features first before spending time implementing them.

• folders for the file selector
• "versioning" by copying files into a sub folder

So far, we've tried to keep Pybricks Code as simple as possible which is why we don't have folders currently. So we would really need to be convinced that this is something that >50% of users would actually use or explore other solutions before seriously considering this. (We unfortunately can't just say yes to every useful idea!)

It's not really clear to me how this could help with versioning. Could you perhaps explain in a bit more detail?

• maybe even make it an electron app to gain access to the computer's file system to achieve versioning with git

For this, I would be interested in creating a VS Code extension rather than a standalone app. This way, we get all of the features like git, monitoring file system for external changes, better code completion and linting, etc. that is already in VS Code, so would save us tons of work. I think this would be the best solution for folks that find Pybricks Code too simple and need these more advanced features without having to put too many features in Pybricks Code itself.

I don't know if I can achieve implementing all of these features but Is there any chance to get access to an actual version of Pybricks code with the visual editor feature included?

The code for Pybricks Blocks is intentionally private since that is how we are funding continued development of Pybricks. Please reach out to [email protected] for inquiries about possibly collaborating. (Even I don't know what the answer will be!)

• disable ( = comment out) single blocks to not having them to be dragged out of the code

Out of all of the block language suggestions, I especially like this suggestion - it is both very simple and very useful.

[DerFuchs]

Thank you for your reply!

This is the best first step. We have limited resources, so best to discus features first before spending time implementing them.

That's reasonable. I was thinking about simply playing around a bit for myself to get familiar with the code base and the whole system. Me playing is not necessarily ending up in new features :D

• folders for the file selector
• "versioning" by copying files into a sub folder

So far, we've tried to keep Pybricks Code as simple as possible which is why we don't have folders currently. So we would really need to be convinced that this is something that >50% of users would actually use or explore other solutions before seriously considering this. (We unfortunately can't just say yes to every useful idea!)

It's not really clear to me how this could help with versioning. Could you perhaps explain in a bit more detail?

I totally get the idea of the editor. It is the go-to solution for everyone who wants to give it a quick try OR who relies on building visual block code - Especially for kids. That's why the kids in my WRO team use visual block code. They will transition to Micro Python at some point in the future. And that's when they'll use VS Code because the Pybricks Editor is not really meant for writing code in the first place. But until then, they'll stick to the block code and that's where my thoughts originate.

This is how they currently work: In a competitive environment - but also outside of that - they organize themselves by building several evolutionary versions of their software. Every time when they are happy with the current solution, they make it a "major" version by renaming the file in a specific scheme and then duplicating the file to work on for the next feature. In the case they screw up, they then always can go back to the last working version.

But this comes with limitations. They'd like to split their code in different files. But it's extremely messy because they then also produce even more versions of files. And on top of that, they have to correctly link them in their main file. That's not very handy, especially in the mentioned competition environment. Too much room for error. That's why we stick to a single file which contains all the main logic as visual block code. This gets very confusing pretty fast. Particular parts are getting harder and harder to find with increasing complexity. That's why I'd like to have a feature which is capable of doing some kind of versioning in a very simple way - I don't want them to use git. That's way too much. They won't get it yet. But what they understand is how folders work and what files are.

I have been thinking further about this problem since yesterday. And I came up with another idea.
Instead of implementing folders, a "project manager" function would be more versatile and less confusing for the kids.
In some words:

• The project manager aims to better organize code files by putting them into projects.
• Projects can be switched via UI, which then only shows the files within the particular project
• Project manager could be accessible as another entry in the left vertical bar

Functionality:

1. The user must be able to create, rename, duplicate, export, import and delete projects
2. One project can contain an unlimited number of files
3. Two different projects can contain files of the same name (hello_world.py in Project 1 and hello_world.py in Project 2, but with different content)
4. The file explorer only shows files of the current project
5. The user can add existing files to projects
6. The user can move files between projects
7. The user can copy files to other projects
8. When the user executes his code, ensure that only the files of the currently loaded project are being used

This would enable users to work on different projects without being confused by too much files. And my WRO kids in particular could finally spilt their work into files and then use this feature to version their work by simply duplicating a project and naming it WRO_2025_v1, WRO_2025_v1.1, WRO_2025_v2, WRO_2025_DEV and so on.

• maybe even make it an electron app to gain access to the computer's file system to achieve versioning with git

For this, I would be interested in creating a VS Code extension rather than a standalone app. This way, we get all of the features like git, monitoring file system for external changes, better code completion and linting, etc. that is already in VS Code, so would save us tons of work. I think this would be the best solution for folks that find Pybricks Code too simple and need these more advanced features without having to put too many features in Pybricks Code itself.

OMG, yes! There are some easy to follow instructions for setting up an environment including VS Code. But having a VS Code extension which is doing the heavy lifting would be nice. I also thought about this but I assumed that you'd like to stick to the editor you're offering.
The best possible thing for me would be a VS Code extension which also includes visual block code.

I don't know if I can achieve implementing all of these features but Is there any chance to get access to an actual version of Pybricks code with the visual editor feature included?

The code for Pybricks Blocks is intentionally private since that is how we are funding continued development of Pybricks. Please reach out to [email protected] for inquiries about possibly collaborating. (Even I don't know what the answer will be!)

Alright, that's reasonable. I'll give it a try, thank you!

• disable ( = comment out) single blocks to not having them to be dragged out of the code

Out of all of the block language suggestions, I especially like this suggestion - it is both very simple and very useful.

Would be fantastic! As well as a comment block for the setup section, as well as that suggested disable feature over there

I have been playing around with the code base a bit. I'm not super familiar with React because I decided to go the Vue.js route years ago. But I wanted to give it a try because I'd like to give my kids some more headroom to avoid fighting with the tool when they want to utilize it to solve problems.

[dlech]

Instead of implementing folders, a "project manager" function would be more versatile and less confusing for the kids.
In some words:

There is a discussion at #1903 for a very simple way to essentially select the current "project" of a multi file project. Your suggestions are essentially a fancier way of solving the same issue. So would be good to copy and paste your ideas there to have them all in one place.

I like the idea of having a sort of "focused mode" where only files relevant to your project are visible, but I do have some concerns about that making it more difficult to share code between projects.

[zus2]

Hi David - pointless trying to emulate VS Code and other IDEs  - so for me a way to autosave to directly to my file system cloud linked folders , without using backups , would allow me to work from different locations / desktops and laptopI suspect web apps cannot do that though ? 

[dlech]

For that, we already have a discussion started here: #1004