|
From: Richard J. <rj...@ek...> - 2002-10-12 00:44:38
|
On Sat, 12 Oct 2002 10:37 am, David Goodger wrote: > > On Sat, 12 Oct 2002 8:45 am, David Goodger wrote: > > Actually, Tibs wrote it. I just checked it in to CVS. Sorry, slackness on my part there. > >> 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. The "split here" part worries me - that then implies the HTML Writer knows how to output multiple files, which I don't believe it should. It should be the job of the pysource "framework" (the bit that drives the parse -> transform -> writer mechanisms) to decide what files need to be written and how they should be written. > >> 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. Then this is definitely an issue that must be resolved now ;) Richard |