I like the idea but I see immediate issues - referencing objects and making simple calls.
Let’s take the example of @moshe_caine “Toggle the visibility of an object.”
OK - which object? The object to hide may not necessarily be the one acted upon.
How do You reference this other object? What is being shown above is more of the HyperTalk approach - now we have another layer - a second language - to create and implement. This type of scenario seems to invite complexity rather than simplicity - and it will always be crippled by limited capabilities (you’ll always wish it did more).
On the other hand this situation is easily handled by jQuery using toggle().
Clicking the “Button” shows/hides paragraphs (in this case) based on current visibility… could be triggered by a timeline function instead (no “click” function obviously).
You could substitute fadeToggle() or slideToggle() for toggle().
This is not hard or arcane. I am a visual~design oriented person - even I can cover these scenarios.
Ditto the other examples - basic jQuery coding that also offers far more extensibility.
HyperTalk is still the “Gold” standard in my opinion for the ease of use/power ratio:
Send "doMenu" to card btn "Total"
So easy to envision & create - I wish it wasn’t a thing of the past. Thank You Dan Winkler & Kevin Calhoun - simply brilliant.