[jsword-devel] JSword list

[Joe Walker]

Hi,

(I'm not sure which is the correct address:
jsword-devel@bibletechnologieswg.org or jsword-devel@crosswire.org, I used
the reply-to address this time)

> > We still need a place to put the work.  Troy, are we going to use
> > Crosswire resources or SourceForge?  Perhaps this should be the first
> > todo on the list.
>
> I'll split the jsword repository off so we can admin it separately from
> the sword repository.  Definitely would like to host the project on
> CrossWire's hardware.

I'm happy with this. If there are lots of people involved then it makes
sense.

> > It appears the most popular approach is to take the 1.5.3 and "port" it
> > to Java.  Once that is done, refactoring can begin.  The only one really
> > impacted by this will be Joe at Project B if he decides to use the
> > JSword engine.  I'm comfortable with this approach.
>
> I'm obviously most comfortable with this approach, but comfortable might
> not be the best route :)

I guess I'm bound to be concerned because it means throwing ProjectB away.
I've been working on Java for 6 years or so and I can honestly say that
ProjectB represents some of the best written and documented code I've
written or been involved in. So it would be a shame to throw it away.

ProjectB works now. I've not touched the Sword stuff recently but not long
ago it supported Sword modules. Given a weeks work or so it would probably
fulfill 1, 2 and 3 of the JSwordGoals, and given a few more weeks we may
well be able to have an interface that was close to the C++ interface too.

> Me and Joe are gonna have 3 days together, in
> a week or so to sit down face to face and talk about this stuff.  I'm
> hoping for a cool, in person demo of ProjectB and vice versa, and I'm
> sure we'll have good stuff to report back to everyone.

Looking forward to it.

Joe.