Define all blocks using translation message

GIRA / PhysicalBits

A web-based programming environment for educational robotics that supports live coding and autonomy using a hybrid blocks/text programming language.

https://gira.github.io/PhysicalBits/

MIT License

19 stars 5 forks source link

Define all blocks using translation message #13

Closed kristiank closed 4 years ago

kristiank commented 4 years ago

Although some blocks don't currently include any text (e.g. pins, numbers and variables) I think it would be wise to define them using the initBlock function and a translation text. One thing this would allow from my perspective is age-specific translations. For very young users it makes sense to add the word "number" on the number block.

RichoM commented 4 years ago

Yes, I agree.

kristiank commented 4 years ago

Here is a list of the blocks that are still not defined using the initBlock function:

[ ] comment blocks
[x] pin names (was added in 00128a6)
[x] number (was added in #21)
[x] variable (was added in 50b3484)
[x] procedure call blocks (was added in 4128be4)
[x] function evaluation blocks (was added in 4128be4)
[x] return block (was added in eb20441)
[x] return with value block (was added in eb20441)

kristiank commented 4 years ago

The comment blocks are actually already translatable (e.g. i18n.translate("This is a comment")), so I think the issue here could be closed after merging #22. But what is the status of the comment blocks, are you planning to use them?

RichoM commented 4 years ago

But what is the status of the comment blocks, are you planning to use them?

Not sure. The problem with the comment blocks is that they only allow to put blocks in some specific places while the language grammar is much more flexible. Also, Blockly has its own comment mechanism so maybe I'll use that. But I haven't decided yet.