Justin Long wrote:
___________________________________ Justin writes: I never thought to search for a Strong's number, and I am technically literate (a programmer for over 15 years). I doubt must non-technically-literate people will. They expect a Hebrew/Greek concordance based either on KJV or ASV. So if that's the way you're going to implement it, then you should make it plain in the search box that you can search for a Strong's number. I wouldn't put it in the manual because many people don't read it.
Searching on strong's numbers needs to be improved still because there are some interface problems that were mentioned in a previous message to the list.
If people won't read the manual... remind me again why we should care about helping them?
Justin writes: If indexing doesn't improve the speed that much then it isn't good indexing! Seriously, an index search *should* beat a forced search hands down. That's why Godspeed could do a full text search of the Bible in less than a second, at least in its original incarnation, even on a 80286 (which is where I ran it). I have indexed databases at work that can scan over 2 million records in seconds; the same thing in full-text search would take over an hour.
I don't think anyone is arguing that indexes would be a nice addition, but they do need to work with the current API's exposed interface. Are you volunteering to take this project on?
--Chris
_______________________________________________ sword-devel mailing list [EMAIL PROTECTED] http://www.crosswire.org/mailman/listinfo/sword-devel
