plattysoft / beret Goto Github PK

To provide some maintainability, we should migrate to the current supported version.

Link to the example: https://github.com/google/blockly/tree/develop/demos/mobile/android

Current Android UI is suboptimal.

• Save and load icons are confusing
• No confirmation to clean workspace
• On screen icons not really useful (except trashcan)
• More prominent, maybe FAB, run actions

When working on the mobile editor, there should be a possibility to test the code in a web emulator, just in case you do not have a Rainbow HAT at hand.

• Ask per session, remember setting.
• Allow override of the deploy via menu.

Only blocks with a "head" should be generated.

Additionally, blocks that are "headless" should be displayed as disabled (50% alpha)

Currently there is no permission request, it should be done on runtime.

Add the blocks related to servos:

• setAngleRange
• setPulseDurationRange
• setAngle
• getMinimumAngle
• getMaximumAngle

Currently only global brightness is supported (and not even exposed via blocks)

This would make the name have much more sense.
The current graphics for having hats on Android does not look good, we need to reimplement it.

Related to only generate code from blocks with headers.
Related to allow multiple instances of the same header block.

Some of the blocks can have sane defaults such as:
-Number for "repeat each [] milliseconds"
-Number for "play [] frequency"
-Text for "show [] on LCD"
-Display colors [] [] [] [] [] [] [] -> Can replace the other block with colors as insets if we provide shadows

Based on the code sample for marquee.

Currently deploy progress is done with a set of Toasts

It should be a dialog with a progress indicator and a button to cancel it.

At the moment, blockly-android does only support a single save file.
We should allow multiple file saves, picking the same of the project, asking for overwrite and allowing selecting directory (potentially external)
Also, add xml handling to the intent filters so we can import a workspace.

Consider having save files on Firebase