|
Hi Steve,
>> I can send you a file I wrote that might help get it working
again.
>> HowTo_BuildAndUseActiveDiatheke.rtf > Please. Thanks. After "lurking" several months on
sword-develop and reading about a years worth of posts on
it and jsword-devel, I thought I could contribute a fix to Active
Diatheke (AD). I was interested in the InVerse Scripture memorization
freeware program having access to ./sword/modules/texts but was reluctant to
confront the "worthless until proven useful" mentality about newbies that
occasionaly was noticeable. Not wanting to appear uselessly "empty handed", I
proposed fixes to AD. Per a sword maintainers guidance, I put together
to send to them using C++ com code rather than VB.
This has the .rft file mentioned above, the changes to actual ActiveDiatheke
code, and the complete Visual C++ 6.0 package to exercise the revised
ActiveDiatheke. There was also some code for ./sword/examples/cmdline to
exercise the changes.
You would probably need to merge the AD changes
from what is currently in CVS. The compile error was related to a missing
parameter to "query" for "range", which I didn't understand and simply used
NULL. I believe "range" became a new feature of 1.5.6 code, but many of the apps
such as AD didn't stay in sync and thus "broke". My impression is that 1.5.7
will remove the apps from the distribution, and I speculate it is for a related
reason for sync issues.
As far as I could tell, the AD code was fixed with
something meaningful for "range", then applied, then overwritten sometime later
and thus returned to broken status. I think the AD Demo VB code was changed
to have something related to "range", so that might explain why it doesn't work
anymore.
I gave up on AD and started wrestling with
sword-api code directly.
> ActiveDiatheke.ocx is only 311k in size - this makes me think that the > working routines reside in some other file(s) - swicu20.dll perhaps. > I wonder if it might be an easier idea to try to tag along with those vs. > trying to keep the ocx up. This is the nature of static linking. The linker
pulls in those routines from 2.5+meg swordlib that are actually referenced.
Unfortuately, the VerseKey code has "octopus tentacles" with many
parsing dependencies (listkey and beyond) that bloat it's size. It could be
about 50kb otherwise, including references to compressed Bible texts. This is
the "point" of my experiments with CanonVersifier and an "experimental plug-in
subset" of the sword-api. The entire statically linked LcdBible.exe is 32kb
using CanonVersifier instead of VerseKey.
ActiveDiatheke is relatively independent of icu,
and it greatly simplifies the whole thing to use the non-icu project in the
.dsp.
> Steve Tang... I haven't been able to find your direct eMail
address. It generally isn't included when you post to sword-devel, so some
people include their eMail address to facilitate offline
communications.
Sharing the reason for the season, Lynn A.
|
Title: [sword-devel] ActiveDiatheke 1.2 question.html
