> El 27 dic 2015, a las 12:00, David Barbour <dmbarbour_at_gmail.com> escribió:
>
> On Sun, Dec 27, 2015 at 5:38 AM, Tristan Strange <tristan.strange_at_gmail.com>
> wrote:
>
>> If you're using this definition what distinguishes just using a
>> programmable computer program (lets say Excel) from live coding?
>
> Live coding is using a powerful languages as an HCI. There is a spectrum
> for 'power', of course, and hence there is a spectrum for live coding.
>
> Excel is not what I'd consider powerful. It isn't easy to capture functions
> or tables as cells, for example, which would be necessary to express graphs
> or time-varying behavior in something other than first-order code (e.g. one
> row per time-step or space-step). Spreadsheets also tend to hinder
> expression of external effects, e.g. attaching control of a smart-home's
> lights to a spreadsheet, or observing the temperature to control a
> thermostat.
>
On the other hand, if I'd hooked spreadsheet software up to a sound generator and coded musical formulas live, I'd be happy to call that livecoding.
Tom
> Power puts Excel pretty low on the spectrum for live coding. But at least
> Excel does use the language as an HCI, e.g. with clear control over the
> computer within its limits (controlling numbers or graphs, by default).
> Most conventional programming environments do not use the language as an
> HCI.
>
> --
>
> Read the whole topic here: livecode:
> http://lurk.org/r/topic/7skAx2Gtu63kIWbbbGh9W0
>
> To leave livecode, email livecode_at_group.lurk.org with the following email subject: unsubscribe
--
Read the whole topic here: livecode:
http://lurk.org/r/topic/PO4KtvJa1XChfmvplBwwx
To leave livecode, email livecode_at_group.lurk.org with the following email subject: unsubscribe
Received on Sun Dec 27 2015 - 21:57:46 GMT