On Fri, 28 Jul 2000, Drew Taylor wrote:
> Ken Williams wrote:
> >
> > I suggest having not just a simple checkmark, but a 3-way check. A
> > system either supports a feature, or it doesn't, or it *optionally*
> > supports it (can be switched on and off). This is often very helpful to
> > know, and might let one get a good sense of the differences between
> > various systems at a glance.
> Another great idea! Should we go one farther and have a checkbox for
> "coming in next version", or is that going to far? I'm thinking it is
> too easy to get wrapped up in "forward looking statements" by having
> "coming soon".
This is getting too complex. Just do a couple of paragraphs on each, and
let everyone bang it out to a bit more than that. I guarantee that once
one template system designer says "Mine does X", the others will chime in
and say "Well mine can do X too, and optionally Y". Eventually you'll get
the perfect document...
However I suggest taking that stage off the list, and just let them send
patches direct to you, and announce when you've got a new version. A-la
guide. In fact it might be a nice addition to the guide. (here I am making
Stas and Eric's book even longer...)
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org
