Something vaguely related was the topic of one of the talks I gave in Sheffield (I think it was programming programming) - where I showed "eternal return". It accounts for the two-dimensionality of live coding time, of course inevitably adding another dimension. Currently it has a preorder of events (a timeline) in which you can jump around however, reprogramming your past.
On 30.03.2011, at 14:13, alex wrote:
> Hi all,
>
> I've just blagged again, this time on cyclic revision control:
> http://yaxu.org/cyclic-revision-control/
>
> The idea is to try to make revision control tools where the goal is
> not to develop code towards future featuresets, but to work your code
> back to where it started. Has anyone been experimenting in this area?
> It seems to me that live coding performances (I have my own in mind)
> are quite linear, not repeating past developments. I did integrate
> RCS in feedback.pl, so it was possible to jump back in time, but this
> idea is more an interface that helps develop forwards to a previous
> state, if that makes sense.
>
> Cheers,
>
> alex
Received on Mon Apr 04 2011 - 22:51:05 BST