On Tue, Aug 08, 2006 at 09:09:29AM +0100, Nick Collins wrote:
*snip*
> This just gives a list of all the commands in time, the History,
> which can then be stored in various document formats, and indeed,
> played back by reinterpreting the appropriate strings in order at
> the given times.
Ahh, thanks very much. So where you say that you can render back your
own performance you will get the audio part but not be able to see all
of the typeing (live bug fixing) that went into it?
I'm thinking that a collection of recorded sessions (edit history)
where we could watch code being written in real-time would be a very
useful learning tool. This is similar to people saying that we should
take videos of our screen, but storing it by programmer edits might
lead to things like...
> (it occurs that whilst it might lead to errors through undeclared or
> wrongly initialised vars, you could start permuting the playback
> order and/or timing and manipulate new patches out of existing ones-
> I could pretend to type a lot quicker than I actually do!)
...or if you could could code side-by-side with a replay of a previous
session and then merge the result. That might be fun and an
interesting way to share material.
Thanks again,
Rob.
--
Department of Computer Science and Software Engineering.
The University of Melbourne, Australia.
Received on Wed Aug 09 2006 - 01:01:29 BST