[sword-devel] Introduction

Scott and Roxanne Munns srmunns at charter.net
Thu Sep 7 20:42:24 MST 2006


Thanks for your answers.  I'll try to look into the CLucene and ICU issues
closer this weekend or very early next week, and will report back with more
info if necessary.

Your comments about API changes make perfect sense.  I'm glad to see a patch
is pending for BT - I'll try it out and let you know what I find.

I'll have to experiment with IRC - I haven't really used it.  Though I used
Unix "talk" to send sweet-nothings to my wife-to-be when she was away from
college working for a semester!  ;-)  I will also check the other to-do
lists and see what strikes me.

Thanks again,

-----Original Message-----
From: Troy A. Griffitts [mailto:scribe at crosswire.org] 
Sent: Thursday, September 07, 2006 2:19 AM
To: munns at uwalumni.com; SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] Introduction

Welcome Scott,

	I'll try to answer a few of your questions.

> CLucene had the issue
> with "lib/CLucene/clucene-config.h" instead of 
> "include/CLucene/clucene-config.h" mentioned in earlier e-mails,

There is a note about this problem in the SWORD INSTALL doc.  Search for
clucene and you should find it.

> also got a compile error when using ICU 3.4.1 (I'm assuming no ICU 3.6 
> support yet, since it was only released Sept. 1).

I have 3.4 on my box.  The latest Windows software was compiled against 
3.6.  Both seem to work with latest SVN.  I'd be interested to hear what 
problem you had with 3.4.1.

>  I guess my question 
> is, how often is compatibility with CLucene and ICU checked, and how 
> important is it?

We usually check the latest available versions before a release.

>  - Latest BibleTime won't compile with latest Sword due to API breakage 
> between 1.5.8 and 1.5.9.  What is your policy (or rule of thumb) for 
> deprecating/obsoleting APIs?

We usually mark a method deprecated for quite some time before removing 
it.  2.0 is planned to be a final normalization of the API which will 
have all deprecated methods removed.

> I guess I was surprised that APIs changed 
> enough between minor revisions that applications wouldn't build.  Or did 
> I make a mistake somewhere?

Well, it's not your mistake.  Like the Linux kernel, we haven't followed 
even/odd release/development nomenclature for some time.  We usually 
release 1, or at best 2 revs a year, so 1.5.9 is not a 'minor' revision.

>  Is someone working on updating BibleTime to 
> work with Sword 1.5.9?

Yeah, I submitted a patch a fews days back to bring Bibletime up to 
SWORD 1.5.9.  It should be posted in the mailing list archives of 
bt-devel, here:


>  - Any ideas on where I could help out?

Scott, my suggestion for getting involved would be to frequent

irc.freenode.net #sword

and also check out the dated, but still sortof current roadmap in our 
bug database at:


my personal desires:


and an old wiki todo at:


Hope this was sortof helpful.  Looking forward to sharing together in 


No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.12.1/440 - Release Date: 9/6/2006

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.12.1/440 - Release Date: 9/6/2006

More information about the sword-devel mailing list