We have three types of Java support :) The Swig bindings can be used to create Java-classes to work with Sword usig Java.
Joachim > Actually, we have 2 flavours of Java SWORD these days. We've gained an > independent project: Project B, that has decided to join our efforts and > has been relabeled: jsword, and we have our our older attempt at a class > by class port of the sword libraries that our website uses, now renamed > jsword-old. They are both still developed but one day may become one > project. > > -Troy. > > you can view the jsword page at: > > http://www.crosswire.org/jsword > > and view the code from either one in our cvs repository or viewcvs at: > > http://www.crosswire.org/ucgi-bin/dglassey/viewcvs.cgi > > > ModEdit still uses the C++ engine, though it seems to work quite nice > and might be advantagious for certain tasks like searching. > > -Troy. > > Eeli Kaikkonen wrote: > > On Fri, 13 Dec 2002, Keith Ralston wrote: > >>Sounds like a great Java project, ;-) > > > > And we already have a good start in form of well-organized, > > over-engineered ModEdit ;) :) > > > >>>-----Original Message----- > >>>From: [EMAIL PROTECTED] > >>>[mailto:[EMAIL PROTECTED]]On Behalf Of Brian Yoon > >>>Sent: Friday, December 13, 2002 2:24 PM > >>>To: [EMAIL PROTECTED] > >>>Subject: [sword-devel] Collaboration efforts for a front end > >>> > >>> > >>>With regards to Sword for Windows, BibleTime, & GnomeSword: > >>> > >>>Just some questions and thoughts... > >>> > >>>1) Has anyone considered using a cross-platform toolkit like wxWindows > >>>for this project so that we all can work on the same code, be able to > >>>compile on different platforms, and still maintain the look and feel of > >>>each respective OS? wxWindows is great and this would allow all of us > >>>to contribute to the same project. This would eliminate the need to > >>>re-invent the wheel for each OS. Therefore, instead of working on just > >>>an OS X port, we could port the existing front-end to wxWindows and then > >>>use it on all platforms. > >>> > >>>2) Are the goals for each of these different (ie. is one focused on just > >>>providing a Bible study tool and another focused on providing a > >>>full-featured Bible study and analysis tool like BibleWorks)? > >>> > >>>3) If someone wants to see an open source versin of a full-featured > >>>Bible study and analysis tool like the commercial software, BibleWorks, > >>>developed, what are the major components that are needed to be developed > >>>(ie. databases on morphologies, parsing, etc.)? > >>> > >>>-Brian Yoon > > > > Sincerely Yours, > > Eeli Kaikkonen <[EMAIL PROTECTED]> Suomi Finland -- Joachim Ansorg www.bibletime.de www.ansorgs.de