Very cool idea. I've been bummed after live-coding sessions to have
lost some of the places the code had gone, so I completely agree with
you. As a first draft, I just hacked up a bash script that will do
the job in linux. Install the inotify tools:
sudo apt-get install inotify-tools
Then for each session make a git project:
mkdir jam
cd jam
git init
touch session.clj
hack-watch session.clj
Then in another terminal edit session.clj. (Or whatever you named the
file.) Each time the file is saved the hack-watch script will add and
commit it to the git repository. With this data it should be possible
to create replays, timelines, etc. Not sure how to transform it into
polar coordinates though :-)
Cheers,
Jeff
On Wed, Mar 30, 2011 at 2:13 PM, alex <alex_at_lurk.org> 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 Wed Mar 30 2011 - 15:20:43 BST