Re: Boost Documentation Template questions

From: bill_kempf (williamkempf_at_[hidden])
Date: 2002-02-11 15:14:18

--- In boost_at_y..., "David Abrahams" <david.abrahams_at_r...> wrote:
> 
> ----- Original Message -----
> From: "bill_kempf" <williamkempf_at_h...>
> 
> > Yes, I'd agree with that.  A python script could easily be 
written to
> > automate this, provided the {{...}} replacement sections used well
> > known documented names.  Other then that, I'm not sure what else 
we
> > can do, but if anyone has any ideas I'd love to hear them!
> 
> It ain't simple, but:
> 
> 1. Hijack Doxygen's parsing to extract definition elements from 
headers
> 2. Use special comments in the HTML to distinguish the auto-
generated
> sections from the sections to be edited by users
> 3. When the script is run again, it uses these comments to keep 
user edits
> which are still valid.

That's much more automation then I had in mind.  Would be nice, but 
it's well beyond the effort I'd care to put into it.

> How would the Python script you had in mind work?

I just imagined it would replace the most common and frequent 
template "macros", such as {{author}} and {{library}}.  The other 
macros seemed to me like stuff that would require hand editing 
regardless of automation (because I hadn't considered doxygen style 
parsing of the source files), and so didn't really need any 
automation.  It's the common ones that are tedious busy work.

Bill Kempf