Upgrade to Blockly v11 and respective plugin versions

[jsjames]

Moved to v11 to address issues with '@mit-app-inventor/blockly-plugin-workspace-multiselect' in port to vue3.

• adopted new required import syntax
• Addressed issue with 'workspace' being reactive (https://groups.google.com/g/blockly/c/myo3FXL3r_Y/m/NLgPZNc0CgAJVue3)
• @blockly/field-multilineinput now required to support multi-line
• @blockly/field-colour now required to support color blocks
• added ability to add comments (via context menu)

[relativeci]

#3962 Bundle Size — 12.53MiB (+1.78%).

50c9999(current) vs 47adde1 main#3958(baseline)

Warning

Bundle contains 2 duplicate packages – View duplicate packages

Warning

Bundle introduced 4 new packages: @mit-app-inventor/blockly-plugin-workspace-multiselect, dragselect, @blockly/field-colour and one more – View changed packages

Bundle metrics   3 changes 1 regression

	Current #3962	Baseline #3958
Initial JS	1.52MiB	1.52MiB
Initial CSS	0B	0B
Cache Invalidation	7.05%	7.11%
Chunks	619	619
Assets	701	701
Modules	2427(+0.5%)	2415
Duplicate Modules	0	0
Duplicate Code	0%	0%
Packages	130(+3.17%)	126
Duplicate Packages	1	1

Bundle size by type   2 changes 2 regressions

	Current #3962	Baseline #3958
JS	10.86MiB (+2.06%)	10.64MiB
CSS	845.74KiB (+0.01%)	845.64KiB
Fonts	526.1KiB	526.1KiB
Media	295.6KiB	295.6KiB
IMG	45.73KiB	45.73KiB
Other	847B	847B

Bundle analysis report Branch jsjames:blockly-v11 Project dashboard

---

^{Generated by RelativeCI Documentation Report issue}

[florian-h05]

As testing Blockly is always a larger effort for @stefan-hoehn, I wonder whether we shouldn't try to upgrade to Blockly 12 now, so we don't need to test twice. WDYT @jsjames?

[jsjames]

As testing Blockly is always a larger effort for @stefan-hoehn, I wonder whether we shouldn't try to upgrade to Blockly 12 now, so we don't need to test twice. WDYT @jsjames?

I did try, but the plugin @mit-app-inventor/blockly-plugin-workspace-multiselect does not yet support it .

Since there is an issue with our vue3 version where multi-select does not currently work (I recall it being a runtime issue in the @mit-app-inventor/blockly-plugin-workspace-multiselect ), this was the most expedient way to address. The question is how critical is it to get the multi-select feature working?

[florian-h05]

That’s quite unfortunate.
Looking at mit-cml/workspace-multiselect#106 & RaspberryPiFoundation/blockly#9261 it doesn’t seem the issue will be solved soon, so I guess we’ll stay with Blockly v11.

[jsjames]

That’s quite unfortunate. Looking at mit-cml/workspace-multiselect#106 & google/blockly#9261 it doesn’t seem the issue will be solved soon, so I guess we’ll stay with Blockly v11.

v11 does get rid of the remaining deprecated packages warnings in package.json!

[florian-h05]

I have now compared the code generation between this PR and 1ac744b for all tests from https://github.com/openhab/openhab-webui/tree/main/bundles/org.openhab.ui/web/test/blockly.

The generated code is identical, except for:

• blockly_datetime_creation_comparison due to #3361
• persistence code generation fails with:

  ReferenceError: Input "dayInfoUntil" doesn't exist on "oh_get_persistvalue"
  

This seems to be a direct consequence of:

Calling statementToCode or valueToCode on inputs that don't exist will now throw an error instead of returning an empty string.

from https://groups.google.com/g/blockly/c/Ai8C0tEiPbI?pli=1

I am working on a solution right now.