<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I think that we are getting close to a 0.9.9 release.<br>
Here is what is left (according to Jira):<br>
(Beyond these, we will need to do a thorough testing to see what bugs
are present and fix those.)<br>
JS-1 Implement match in lucene using wild cards<br>
<blockquote>Joe, take a look at lucene's fuzzy match operator. It is
pretty cool. It will find words that are within a reasonable edit
distance to the word that is searched.<br>
</blockquote>
JS-8 Make index creation happen at a better time<br>
<blockquote>I think that this one has improved enough that it can be
moved to 1.1<br>
</blockquote>
BD-1 Cancel download is broken<br>
<blockquote>Indexing has the same problem. A simple interim fix would
be to remove the ability to cancel a download or indexing. This will
minimize the problem that if either of these do not go to completion
that the install will be corrupted, requiring manual intervention. It
will still happen if the user closes the program, the program
abnormally terminates, the computer reboots, ....<br>
<br>
A better solution would be to do the work to an alternate name and
rename upon completion. When the job starts it could look for previous
failed attempts and clean it up if needed.<br>
<br>
There are probably other solutions as well.<br>
<br>
What should we do for 0.9.9, for 1.0 and beyond?<br>
</blockquote>
BD-4 Just shows the version, seems kinda pointless<br>
<blockquote>I am willing to let this one slide to 1.1. But if we do
something for the release:<br>
<br>
What should this show? Some thoughts: credits, contact info, urls to
website, overview of program, date of build, copyright/license
statement. WRT to credits, a lot of people over time have contributed
small amounts that were individually significant and together were very
important. Having a list of key contributers, IMHO, would slight these
efforts. Besides, I don't care if my name is on the program or not.<br>
<br>
Whatever we do, our internationalization framework will need to be used.<br>
<br>
Should these be on separate tabs or in a scrolling box?<br>
</blockquote>
BD-5 Create help.<br>
<blockquote>I think that if we add the url to where on the web that
help can be found, this could be moved to 1.1 Under 1.1 we would be
adding the ability to bring up a document in an appropriate program. I
think that Java Activation Framework may provide the mechanism. We
could put the document in the jar and extract it to the ~/.jsword
directory and view it from there.<br>
</blockquote>
BD-8 some nt verses badly displayed in ot refs<br>
<blockquote>Not sure where this is, but if I had an example, I would be
glad to look at it. I think it is probably a trivial change to the xslt.<br>
</blockquote>
<br>
BD-9 Notify the user when a single testament bible is installed.<br>
<blockquote>I don't want to have a popup when the install is finished.
We had this and it led to some sneaky bugs. Either we know it before
hand (i.e. it is a reliable field in the conf) or we figure it out
before hand (i.e. check the website for the corresponding nt.* or ot.*
files), but we don't notify after the fact.<br>
<br>
The LCSH (Library of Congress Subject Heading) in the conf already
provides this. The problem is that this field can contain anything. So
it cannot be used programmatically. It typically is of the form:<br>
Bible. O. T. German<br>
It is not internationalizable.<br>
<br>
We could put the LCSH in the popup that provides the size of the
download. But, I would like an internationalizable solution.<br>
<br>
My vote would be to change the conf, but we have not gotten very far
with those suggestions before (i.e. download size, install size, ...)
Basic idea would be to add Scope= to the conf. This field would be a
listing of one of these forms:<br>
OSISref -- Just contains what is referred to by the OSISref: a single
book, chapter or verse.<br>
OSISref-OSISref -- Contains everything from the first OSISref to the
second OSISref, inclusively.<br>
or a comma separated list of these.<br>
The default would be Gen-Rev.<br>
<br>
If this is the direction we take, then I think that we should move it
to 1.1.<br>
</blockquote>
BD-11 Selection not maintained when blur button is clicked.<br>
<br>
BD-34 Switch to the right dictionary/commentary/... when a link is
activated.<br>
<blockquote>I am working on this one right now. Probably will take a
couple of weekends.<br>
</blockquote>
<br>
<br>
</body>
</html>