According to Ferenc VERES:
> Hello There!
>
> I am not sure this is the right emailing list for this, but I don't
> intend
> to subscribe to all lists. Ok?
This is fine. Either htdig-general or htdig-dev is appropriate for patches.
> For html template files you can set up 1 file per option. We have 12 kilobytes
> long header with divs+text menus, would be bad to repeat it in all template
> files (especially for changing). With my change you can use the same header.html
> file for all of search_results, syntax and nomatch files. See:
>
> search_results_header: /home/httpd/html/www.tetrapak.hu/hun/header.html \
> /home/httpd/html/www.tetrapak.hu/templates/header-search.html
> search_results_footer: /home/httpd/html/www.tetrapak.hu/templates/footer-search.html
>\
> /home/httpd/html/www.tetrapak.hu/hun/footer.html
>
> nothing_found_file: /home/httpd/html/www.tetrapak.hu/hun/header.html \
> /home/httpd/html/www.tetrapak.hu/templates/nomatch.html \
> /home/httpd/html/www.tetrapak.hu/hun/footer.html
> syntax_error_file: /home/httpd/html/www.tetrapak.hu/hun/header.html \
> /home/httpd/html/www.tetrapak.hu/templates/syntax.html \
> /home/httpd/html/www.tetrapak.hu/hun/footer.html
>
> Cool, isn't it?
Yes, very neat idea!
> (In nomatch and syntax.html I just have a few lines. And the headers/footers
> are exactly the same as we use on the site with ssi.)
>
> The modified functions are in htsearch/Display.cc and included down here.
> Maybe there could be a nicer way, changing displayParsedFile() but don't
> understand c++ code clearly ;-)
>
> If I knocked on the bad door, please tell me and sorry for the mail.
> It would be good to have this kind of improvement in the upcoming versions,
> especially coz this kind of complex header/footer files! (changes are
> nightmare, if you have 3-4-5 copies of the header!)
Well, you could always have separate "source" files for the templates, just
as you have, but then use a Makefile with "cat" commands to build the final
templates you need for htsearch. That simplifies the maintenance a great
deal. Your fix just does the concatenation on the fly. It's simpler, but
there's a bit more of a performance penalty because htsearch has to open and
read a few more files this way. (Probably not a big deal.)
I think a cleaner implementation would be to put the loop once in
displayParsedFile(), and once in readFile() for handling the wrapper file
should you be inclined to use that instead.
> Thanks for the cool program. This is the first time I use it, and I like
> it very much! Will put it on the production site in some days.
>
> Ferenc Veres
> Hungary
>
> Modified functions are fully listed here. The original source was
> VERSTION 3.2.0b3.
For a production system, I'd actually recommend the latest snapshot of
3.1.6 or 3.2.0b4 (http://www.htdig.org/files/snapshots/) as these are more
stable and debugged than earlier releases.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
