0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
/
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
/
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
ANNO·​TRICESIMO·​DIE·​CENTESIMO·​SEPTVAGESIMO·​OCTAVO·​VITÆ·​POVYA
Native Context Menus for @orchestra

One of the things I could only have dreamed about was for the Orchestra to have uniform context menus that are native. Electron provides such functionality, but I had to modify Blockly when I were trying to do it, and it was beyond my abilities. It wasn’t for the agents, and so mimo did it for me as well.

Native Context Menus for @orchestra

Native Context Menus for Orchestra Language (2/2)

Reviving @orchestra

I was playing with the Xiaomi Mimo system, and then I thought why not reviving Orchestra Language with it? Orchestra was made in Electron version 1 where you had access to the whole node in the window. And then when I didn’t use it for a while, Electron changed, its all API changed, and it had no support with Apple Silicon. So reviving meant rewriting the whole logic, moving so much from the render process to the server process and restructuring. Actually amazingly enough, the LLM did it.

Day's Context
Open Books