Yes, that's an important distinction - one which I perhaps didn't make
as clear as I could have.
Cheers
Ben
andrew_at_moso.com.au writes:
> Sure, although it is important to distinguish the semantic issues from the
> practical issues. Both are harmful, but in different ways - and the practical
> issues tend to be more obvious.
>
> Andrew.
>
> -----Original Message-----
> From: "Ben Swift" <ben_at_benswift.me>
> Sent: Thursday, 31 January, 2019 2:41pm
> To: "livecode" <livecode_at_we.lurk.org>
> Subject: [livecode] Re: interactive essay on annotations / visualizations in
> live coding
>
>
>
> Yep - *I* certainly still think of it as [c e g] with a random transformation
> -
> especially since the order does have some semantic meaning (when I hear a C
> major triad in my mind's ear, I hear it in root position, arpeggiatted
> upwards).
>
> I think it's just a subset of the bigger challenge, though - which is
> having annotations which at worst aren't harmful when the code is
> executing and being edited simultaneously, and at best are even
> beneficial in that situation.
>
> Cheers
> Ben
>
>
> andrew_at_moso.com.au writes:
>
>> Hey Ben,
>>
>> Something that I've always questioned about inline editing is this:
>>
>> Let's say you have a cell of some kind - let's say [c e g] - and then you add
>> a 'live transformation':
>>
>> random([c e g])
>>
>> Do you really think of the cell as [e g c] and [g e c] and ... Or do you
>> think of it as the cell [c e g] with a 'random' transform. In which case
>> changing [c e g] inline just seems incorrect to me. i.e. it's a question of
>> intention.
>>
>> Cheers,
>> Andrew.
>>
>>
>>
>> -----Original Message-----
>> From: "Ben Swift" <ben_at_benswift.me>
>> Sent: Thursday, 31 January, 2019 10:52am
>> To: "livecode" <livecode_at_we.lurk.org>
>> Subject: [livecode] Re: interactive essay on annotations / visualizations in
>> live coding
>>
>>
>>
>> Hi Charlie
>>
>> Thanks for putting this out there, I had lots of fun poking around with the
>> examples.
>>
>> I've jotted down some thoughts in response here:
>>
>> http://benswift.me/blog/2019/01/31/on-livecoding-annotations-and-visualisations/
>>
>> Cheers,
>> Ben
>>
>> Charlie Roberts <bigbadotis_at_gmail.com> writes:
>>
>>> Hi everyone,
>>>
>>> I've been meaning to send this essay to the list for a while; It provides
>>> interactive examples of the annotations and visualizations used in Gibber /
>>> gibberwocky to display the current state of patterns and function output.
>>> Currently works in Chrome only... any feedback would be appreciated!
>>>
>>> https://charlieroberts.github.io/annotationsAndVisualizations/
>>>
>>> - Charlie
>>> _______________________________________________
>>> Livecode mailing list -- livecode_at_we.lurk.org
>>> To unsubscribe send an email to livecode-leave_at_we.lurk.org
>> _______________________________________________
>> Livecode mailing list -- livecode_at_we.lurk.org
>> To unsubscribe send an email to
>> livecode-leave_at_we.lurk.org_______________________________________________
>> Livecode mailing list -- livecode_at_we.lurk.org
>> To unsubscribe send an email to livecode-leave_at_we.lurk.org
> _______________________________________________
> Livecode mailing list -- livecode_at_we.lurk.org
> To unsubscribe send an email to
> livecode-leave_at_we.lurk.org_______________________________________________
> Livecode mailing list -- livecode_at_we.lurk.org
> To unsubscribe send an email to livecode-leave_at_we.lurk.org
_______________________________________________
Livecode mailing list -- livecode_at_we.lurk.org
To unsubscribe send an email to livecode-leave_at_we.lurk.org
Received on Thu Jan 31 2019 - 05:32:59 GMT