>>>>> "Matt" == Matt Sergeant <[EMAIL PROTECTED]> writes:
Matt> Speaking of Stonehenge::* modules - any chance you can put up a
Matt> repository of them on your web page - I just installed
Matt> Stonehenge::Pictures (which is very cool - but I'd like to
Matt> extend it to automatically do the thumbnails)
I thought of that during the initial development, but realized the
thumbnail directory would have to be separate from the main directory,
otherwise the timestamps would be modified and the directory needed to
be web-user writable. Oooh wait... I'd just have it try to write in
./thumb/foo.jpg, and if it failed it'd decline entirely, so if ./thumb
was not web-writable, then Stonehenge::Pictures would decline! oooh!!!!
echo add thumb sub directory to Stonehenge::Pictures >>WT-ideas
Matt> and I'd be
Matt> interested in seeing Stonehenge::Reload, but I don't fancy
Matt> searching the archives of this list (which you posted it to,
Matt> IIRC), and a central repository of all your mod_perl stuff would
Matt> be nice.
If they were documented independently of the context in which they
appeared, as in WT columns, I'd be happy to. As is, they'd be these
wonderously marvelful snippets of undocumented, slightly opaque code
with no operating guide. :)
Perhaps at least a pointer in my online WT repository to the columns
that include mod_perl goodies? Would that help?
I've often wanted to include a TOC beyond the simple titles, like
"these columns have mod_perl", "these columns have CGI.pm", "these
columns make HTTP requests", "these columns serve HTTP", etc. But
alas, the tuit server keeps coming up empty at my RealWorld Service
Provider. :)
But, seeing as my stuff seems to be getting used, even in absence of
my included docs, maybe I should just get the docs done and get'em out
there. I could even put them in the CPAN then. :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
