[jsword-devel] sword proxy interface

[Joe Walker]

Hi,

The classes under java/sword are grabbed from jsword-old. I suspect it 
was before you rolled stuff back because the source was quite broken. 
I've done a few tidy ups since as well.

I suggest that we proceed as follows:
1. Merge CVS trees keeping java source separated (see below)
2. Merge java source where appropriate

Currently (excluding junit test classes) there are the following sets of 
source under the java directory
- common
- jsword (core code)
- sword (copied from jsword-old; prototype proxy classes)
- map (map stuff, ignore)

So the plan is to make the sword tree call the jsword tree to get stuff 
done.

How easy is it for you to separate library stuff from front-end stuff in 
your new project? Assuming it is easy we could replace java/sword with 
the most up to date jsword-old, and then move your new front end stuff 
into java/whatever.
Then as stuff needs to be added/altered in java/sword we can do any of:
- write it from scratch
- cut and paste from jsword
- proxy to jsword

I fear that our goal of merging this code will get harder if we are 
developing in separate areas so I'd like to at least start in the right 
direction. However I'm not going to be able to spend a huge amount of 
time helping out because I've got a lot on for the next few weeks.

Joe.

Troy A. Griffitts wrote:

> Hey guys.  An immediate need has arisen to write an online module 
> markup editor.  This means that I'm either gonna need to finish the 
> SWModule read/write interface in jsword-old or use your proxy interface.
>
> I looked at the directory hierarchy and there seems to be a number of 
> classes in there?  Are they ones that you grabbed from jsword-old at 
> one point in time, or are they new classes that work against your engine?
>
> Just wanted to ask before I dive back into the java world for the next 
> couple months.
>
>     -Troy.