I think this should be easy to add to what I'm developing. It could also
solve a problem for me.
I wasn't sure how I was going to handle pretty printing of the code
fragments, but if I keep a
dynamically tangled view around then I can pull the pretty printed
formatting (i.e. keyword coloring)
from that version. I'll keep you posted.

I should be able to allow the programmer to edit the tangled version as
well. They can in fact do this
now by manually unfolding all of the macro invocations - it just isn't in a
separate window.
There may be some scaling/performance problems here eventually, but I'm
trying not to let such
things get in my way now. New chips will solve that problem right?

At 10:39 PM 12/1/2002 +0000, you wrote:
>The key addition I would also like to see is "live" tangling, so that as well
>as your documentation window, you could have several source windows open
>showing how the tangled sources will look. As you edit the macros in the
>literate document, you would see live updating of the tangler output in the
>source windows, hopefully with the colour coding and incorrect syntax
>detection
>that mainstream programming IDEs now provide. Live tangling would
>overcome the
>(very real) problem of programmers not being sure if they have assembled their
>macros correctly or not.

Charlie McDowell, Professor (831) 459-4772 (w)
Computer Science Department (831) 427-2076 (h)
University of California (831) 459-4829 (fax)
School of Engineering http://www.cse.ucsc.edu/~charlie
1156 High Street
Santa Cruz, CA 95064-1077