|
From: David G. <go...@us...> - 2002-10-12 00:33:30
|
> On Sat, 12 Oct 2002 8:45 am, David Goodger wrote: Actually, Tibs wrote it. I just checked it in to CVS. Read it here: http://docutils.sf.net/sandbox/tibs/pysource/notes/thoughts.html >> Each layout is represented by a class that walks the >> Python-specific doctree, replacing the Python-specific nodes with >> appropriate generic nodes. The output of the Layout Transformer >> is thus a generic doctree. Richard Jones wrote: > It's going to have to be many generic doctrees though. That is, the "stylist > transforms" are likely to produce multiple output doctrees (an index, a > package page, multiple module pages, ...) I don't know how this will work yet. Perhaps the Writer and/or I/O object will handle forests (multiple trees). Perhaps the doctree will remain monolithic, and a transform will insert "split here" indicators. It's all up in the air. >> One specific thing to be decided, particularly for HTML, is >> whether one is outputting a "cluster" of files (e.g., as javadoc >> does). > > Haven't looked at javadoc for a while - what's this mean? I think "cluster" here just means multiple files as opposed to one monolithic file. -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |