tobias-wilfert / mindstorms-compiler

A compiler for Lego Mindstorms Robot Inventor Scratch-like language to Python.

Hi there 👋

$B \gt \frac{1}{N} \displaystyle\sum_{i=1} ^{N} x_i $

mindstorms-compiler's Issues

Add support for ports also being value nodes.

• Update the tests for all previous blocks.
• Add new tests for the previous blocks.
• Update the code so that this scenario can be handled.
• Test how this is handled by the program itself.

Add support for the 4 basic arithmetic blocks.

• Add tests for the parsing.
• Add the logic to parse them.
• Add tests for the AST generation.
• Add the logic for the AST generation.

Add support for the 'StopMoving' Block

Add support for the 11 'Sound' Blocks.

Add code generation for the the currently supported Blocks.

Get the functionality in place to generate code, for all the currently supported blocks.

• Will need to be tested.
• Will need to be designed in a way to support multiple 'Block Stacks' down the road.
• Also need to find a way to deal with which stack to generate first and how to deal with variables and motor stacks.
• Will also need some testing to find out how certain edge cases are handled.

Add support for the 12 Light blocks

4 of these might not be able to be supported.
Decide on whether to skip them and emit a warning or throw an error and stop.

Add Github Actions that run the tests and generate a badge.

• Maybe also add to that restrictions as to what can be pushed to the main branch 🤔

Add support for the 'SetMovementMotors' Block

Add parsing and AST support for the 'MotorPosition' Block

Add parsing and AST support for the 'Start Motor' Block

• Add test
• Add parsing logic
• Add AST logic

Add README and licence

Add a README outlining which features already supported ATM as well as a license.

Find a way to support the last few unsupported blocks.

There are still some blocks that are not supported because the Python API can't be used to translate their logic. However if that API is updated in the future it might be possible to support them.

Add Parsing and AST support for the 'Motor Go to Position' block

• Add test cases for both parsing and AST generation.
• Add the logic for parsing.
• Add the logic for the AST generation.

Add support for the 'StartMovingWithSteering' Block

Use typer to create the CL interface

• Design a basic interface
• Implement it using Typer

Add Support for the Variables and List blocks

This is necessary in order to retrospectively fix the port selection and be able to test it.
This is because both a string and a list of strings can be used as input for the Port field.
Note: Numbers technically also work but have no effect, so throw an error when that is detected to let the user know, something went wrong.

Add more test for the run motor for duration block.

• Add test for multiple ports (more than 2).
• Add test for all ports.
• Add tests for when the value field is a node.

Fix the pre-commits

They are currently not running the formatting.

Add support for the ' Set1MotorRotationtoDistance' Block

Add support for the 'SetMovementSpeed' Block

Make list of all the supported blocks so far.

• Make a list of all the supported blocks (maybe also configurations)
• Link to it from the README.md
• Add some code snippets to the README.md

Add support for the remaining 8 Variable blocks.

These where not added in the beginning, but this sprint seems like a good time to tackle them.

Add support for the 'MoveWithSteeringForDuration' Block

Add parsing and AST support for the 'SetMotorSpeed' Block

Add parsing and AST support for the 'Stop Motor' Block

• Add test
• Add parsing logic
• Add AST logic

Add support for the 16 Sensor blocks in their 44 configurations.

Add proper support for the Pick Number Block

• Add support for specifying a seed
• Add support for generating random floats

Add parsing and AST support for the 'MotorSpeed' Block

Update the README

• Include a full output
• Explain the flags
• Add a list of currently supported blocks (end-to-end)

Add flags to the program.

Now that there is some functionality it makes sense to add flags to the program:

• A flag to indicate wether the AST representation should be outputted
• A flag to decide where the AST should be outputted (file or printed out)
• A flag to decide whether the generated code should be printed or outputted to a file
• A flag to decide if safe or readable code should be generated.

Add support for the 'MovedForDuration' Block

Add support for the 16 Operators blocks in their 46 configurations

Add support for the 10 Control blocks in their 14 configurations.

Clean up the code generation.

The code generation file is currently neither efficient nor elegant, some cleaning up is thus necessary.

Clean up the code before starting on the Movement blocks

Both the AST and visitor file have become very big so it might be interesting to clean them up and add a bit more structure before the movement blocks are added.