Terminal Commands, these run with the "program itself" as an a object.
Create Variable "string" with (value) -- Creates a variable
display(value) -- sort of like the print command in python or console.log in JS
wait (value) sec -- You know what this is, simply pause 1 second
make Object called "string" -- Makes a sprite appear at x:0 y:0, it appears as a TURTLE.
Change (variable name) to (value)
set (object name) to (picture)
do [ -- The Old REPEAT BLOCK
//code
] 10 times
Object Commands, these run with the Object in mind.
tell "object name" to [
//code
] --Tells object to do this.
go to 0, 0, -- go to x, y
pen("down or up") -- Toggles Pen
//what more could I do?
1 reports 1 right? what if we created a variable called 1 and set it to 2?
1 would report 1 and $1 would report 2. The dollar sign is to let the computer know that it is a variable
How will it handle variable names with spaces?
I suggest using brackets or something to signify variables:
create script var [1]
display [1]
create script var [1 hello world]
display [1 hello world]
As for the loops, I think the do ... end/done system might work better. It's more englishy than using brackets for that, and won't get confused with the variable getters. You could say that about this variable system, but something like this is basically required to support all ways to write variables.
But if you really want the loops to still have brackets, maybe put 2 brackets around them instead of 1: