According to Geoff Hutchison:
> OK, I'm finally getting to a point where I have free time to code
> again. Hopefully people will see code going into the tree and become
> willing to contribute too? :-)
>
> I fixed the major bugs with the ParseTree code so that you can
> actually run the test program. Unfortunately, it became immediately
> apparent that I'll need to start in on the HtWordType subclasses so I
> can parse queries correctly. Right now it tosses out things like (
> and " and that's obviously a bad thing!
>
> But I'm going to need some help soon. While I can easily get the
> ParseTree code to start doing actual queries, it would be really nice
> if someone would volunteer to work on the Display.cc monster. I think
> we need to start working out where we're going to move the code
> around--any suggestions?
I can't think of a whole lot offhand. It seems that things like
buildMatchList() don't belong in Display.cc, but a lot of the other
code definitely is display-related. Perhaps a separate section to
deal with template variable creation would make sense. I would like
to see createURL() remain with the template variable stuff, it that's
alright, so that the code that deals with input parameter -> config
attribute -> htsearch output remains in the same module.
I guess I should apply my build_select_lists enhancement patch to 3.2
before you rearrange things, though.
--
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
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
