Add a "Click" action and the ability to "Call" events from one component to another.
Thanks to fellow JustinMind user Maciej Sawicki, we have learned a technique (which I took the liberty of naming the "Sawicki Indirection Technique" in his honor), by which an event on one component can trigger an event on another component.
This has numerous applications, not the least of which is the ability to delayed triggering of tooltips.
The technique involves adding (otherwise unneeded) Text Input components and adding "on Focus In" events to trigger actions "remotely" from another component by way of the "set Focus On" action. The Text Input serves as a kind of public method that can be called from other components.
As remarkable a feat of inspired hackery as it is, it is still a hack.
Better would be the ability to trigger events in one component via actions within events in other components.
A natural first choice would be a new "Click" action.
This new Action type would simulate clicking another component, triggering its existing "on Click" event.
Going further, an entirely new Action type could be a "Call" action, with a corresponding "on Call" event trigger. This would allow components to "Call" another component to trigger its "on Call" event, just as giving focus to an input triggers its "on Focus In" event.
A further refinement of this idea could be "named calls" — essentially, public methods that could be called from another component to trigger a set of defined actions.
Finally, if these new "named calls" could be attached to the prototype (rather than to a specific page or component), this would provide the functionality requested almost four years ago by regis.remillien: global and page functions.