> OK, lets get back to this issue.  Nobody here seems to know why the
> forrest run takes so long, but it takes a significant fraction of the
> overall run.

Including me. ;-)

> It also produces thousands of web pages, only a small
> fraction of which are likely to ever be looked at.

Agreed.

> And none of these
> pages are produced until the run is complete.

Actually this is because of how long forrest takes, and being clean. To
fully automate a remote Gump we need it to clean up when projects [pages] go
away, and such. As such the xdocs are writing to a work directory, the pages
are built into a clean staging directory, and then the pages moved over. At
least this way the site isn't missing-in-action for the length of the
forrest run.

> A better approach would be to run forrest dynamically, i.e. produce (and
> possibly cache) the web page on demand.  I'm not sure what that would
> take to make happen, but it seems to me that the best way to get from
> here to there is to try to do both.

Agreed.

Things are closer than they were a while ago. I added a --xdocs option (that
sets options.isXDocs() to true) that makes forrest.py generate the xdocs,
and not run forrest -- but sync that work directory with the log directory.

BTW: Your request to have xdocs pages (for projects, etc.) built as the
come, really ought be doable w/o much change. Calling
ForrestDocumenter.documentModule or ForrestDocumenter.documentProject ought
have no dependencies. Either we write directly to the log directory
(possible) or we write to staging and sync. I don't quite know how to do
this to a staging area, and then sync ('cos there are N pages) but I'd like
to try, otherwise our site could accumulate a lot of flotsom and jetsom.

If you want to have a dig in, feel free. If this area is a little
'convoluted' and you'd like me to have a shot, no problem. I ought be get
there within the next week or so.

regards,

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to