Re: [htdig-dev] Nearing first complete version of HtDig 4.0

[G. T. Stresen-R. <ted...@ma...>]

Neal:

It all sounds good to me. Now if I could _just_ clear up some time in  
my schedule to try building the code on Mac OS X then things would be  
great. We have two interns at our office for the next 3 weeks. They're  
neck deep in another project, but if, by chance, they finish early,  
I'll see if I can get them to work on fixing the documentation (they're  
into graphic arts besides having studied programming).

I suggest we model the htdig documentation on php.net. It's an  
excellent model.

I got a little chuckle out of this quote: "Nearly every system this  
will be installed on will have PHP, Perl or Python."

I can recall that not too long ago we dropped the option of providing  
documentation in anything other than plain HTML because we could not  
count on having things like PHP on the systems that htdig would be  
installed on, it was almost too much to ask people to have Perl (but  
not too much to ask them to have libstdc++)... funny world we live in!

Any feedback on this topic? Great documentation can do a lot for any  
project.

Gustave (Ted) Stresen-Reuter
Administrador/Webmaster

Clevernet
(Schlegel Ulrich 000420736K S.L.N.E. B35787027)
C/ Cronista Benitez Inglot 7-bajo
35011 Las Palmas de Gran Canaria

Tel.:  0034 928 28 90 27
Fax:   0034 928 25 92 37
Movil: 0034 696 07 25 17

http://www.clevernet.biz
http://www.tedmasterweb.com

On May 25, 2006, at 6:51 PM, Neal Richter wrote:

> Hey all,
>   Anthony Arnone and I are nearing the completion of the first version  
> of htDig 4.0.
>
>   At the moment we're fixing up the native Win32 build of it.  The  
> next few steps are as follows.
>
>   1) Polish new htdig.exe
>   2) Final code/directory cleanup
> 	(perhaps a reason to move htdig to subversion??)
>   3) Polish build process
>   4) Formal QA process
>
> When #4 is begun we'll formally announce the new version as beta and  
> update the htdig website.
>
>   We'll also be tracking & including the current changes to CLucene  
> 0.9 until we reach a point of pain to be determined later.  After that  
> we'll lock the version of CLucene used in htDig 4.0.
>
>   The tarball used to build HtDig 4.0 will include versions of  
> CLucene, HTML Tidy and Berkeley DB (already included in htDig 3.2).
>
> -------
>
> I would like some feedback on htsearch.exe.
>
> I actually think we should cease providing a compiled cgi for  
> searching. We should ship a polished PHP script for searching and  
> possibly Perl & Python scripts as well.  There are various bindings  
> for CLucene, so all of these can be made into htdig bindings by adding  
> a bit of glue code that looks at the htdig.conf file etc.
>
> Why?  Nearly every system this will be installed on will have PHP,  
> Perl or Python.  Any of these 3 scripts would allow much better  
> customization of the
> output by users.  Continuing to maintain cgi code in C/C++ is not very  
> attractive when these scripting languages do all the work for you.
>
> What do you think?  Any strong objections?
>
> Note that one of the most used contributions to htDig 3.1.6 & 3.2 is a  
> PHP script which calls the htsearch cgi/exe and parses the output to  
> allow customization...
>
> Thanks
>
> --  
> Neal Richter
> Sr. Researcher and Machine Learning Lead
> Software Development
> RightNow Technologies, Inc.
> Customer Service for Every Web Site
> Office: 406-522-1485
>
>
> -------------------------------------------------------
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat  
> certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=107521&bid=248729&dat=121642
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev