the OP here has said he has no actual need for this at this time.
However, the "OP" would like that capability as the "OP" teaches LiveCode
to various ill-assorted kiddos every summer.
After the initial 5-6 days of 3 hours a day they begin to develop
"dangerously independent" tendencies and start making noises about project work.
Of course the less imaginative ones all want to make a "shoot-em-up" game: but other more
switched-on kids have more switched-on ideas such as several that involve sound.
This is, already, a pain-in-the-bum as I use Linux boxes in my school, and LiveCode
and sound DON'T on Linux.
[And, I am not going to run out and buy 10 Microsoft Windows licences "just"
to have access to the rather rudimentary sound capabilities of LiveCode for
3-4 weeks each year.]
NOW I only run "silly wee intro" courses every summer for 3-4 weeks maximum:
but there are those who would teach LiveCode programming over several years
in a regular school (my school being somewhat irregular) and aim to do serious,
long-term project work . . .
A dependence on APIs ties one to specific platforms . . . and, of course this:
This allows you to build robust, flexible objects that work on
any platform with any type of user interaction you or your customer can imagine.
seems less and less to be the case.
Being capable of imaginative moments
I CAN IMAGINE a program where
an end-user can use a standalone to write music and export the end result
to .midi and .aif files on ALL the platforms LiveCode claims it works seemlessly on.
). I first came across it in sdl basic, but have also used it in pascal. It works pretty well.