Bill Moseley wrote:
At 11:55 AM 01/28/02 +0800, Stas Bekman wrote:
Maybe when you can't sleep some night think about separating DocSet from
the HTML generation. It might be nice. DocSet -> ttree -> html output.
DocSet might write a tt config file, or provide a plugin to read the cache.
You might end up with a more powerful solution where DocSet, CGI, and
mod_perl could be used together in a site.
Nope, not DocSet. That's how Andy's TT docs get built - in two passes. I don't like this approach because his templates look like hell (the first pass need to generate templates for the second pass) and if you look at the pods, they have loads of TT markup in there.
He's suggested to me lately to do that two-step process to build the templates that are used as templates (TT builds TT's templates from templtes ;). Things get confusing with too many layers in the same application.
Well, I've started going Andy's way but then I was horrified by all the escaping that I had to do. So I've taken a new way.
In any case DocSet *is* doing it in 2 passes, but the first one doesn't need the templates.
This drives me crazy! The solution is: RedirectMatch Permanent /guide/ /docs/1.0/guide/
Maybe it's my version of Apache?
Apache/1.3.20 (Unix) mod_perl/1.25_01
weird :(
_____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
