RE: [htdig-dev] Re: splitting attrs.html

[Budd, S. <s....@ic...>]

Just to butt in..  I have to agree wholeheartedly with what Gilles is saying
below.
Off line generation,, Good idea.  Generation at each site.  Difficult.






2) There's a learning curve associated with maintaining PHP files (one I
haven't personally climbed yet).  It's probably safe to say that most/all
developers know HTML, and are able to maintain the docs as they are.
Even defaults.cc/defaults.xml are pretty easy to get up to speed on,
and the conversion programs for these don't need a whole lot of ongoing
maintenance.  Going with PHP for all docs might complicate things and
reduce the amount of developers available to maintain the docs.

3) We're trying to minimize the amount of dependencies ht://Dig has.
As-is, it needs a few libraries, autoconf/automake, and Perl.  Adding PHP
to the list could conceivably complicate matters for those installing
the package, and consequently increase the amount of requests for help on
the mailing lists.  Using PHP just to generate the static HTML files for
the attributes docs should minimize this problem, requiring only active
developers to install PHP on their systems.  If we do things right,
end-users should not have to worry about doing this.

However, if we don't use PHP for on-the-fly generation of docs, but just
for building static HTML files, does this provide a big advantage over
Brian White's scripts?

-- 
Gilles R. Detillieux              E-mail: <gr...@sc...>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/
Dept. Physiology, U. of Manitoba  Winnipeg, MB  R3E 3J7  (Canada)


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
htdig-dev mailing list
htd...@li...
https://lists.sourceforge.net/lists/listinfo/htdig-dev