[sword-devel] ActiveDiatheke ocx: may have gotten working again

Lynn Allan sword-devel@crosswire.org
Mon, 20 Oct 2003 18:58:27 -0600


Gotta be careful not to bet expectation too high. Some mea culpa's

I have a series of questions reflecting my ignorance of Sword:

1. What is the "range" argument for the function "doquery"? This changed
from having 11 arguments to 12 arguments. The default is 0. I didn't see
what this variable was for. For the first cut at getting ActiveDiatheke to
work, I set it to 0. I don't know enough about what the software is supposed
to do to see if anything breaks (key of Eph 2:22-3:2 still works, which was
a guess on my part on what "range" might pertain to ???)

long CActiveDiathekeCtrl::query()
{
 ostrstream output;
  char *range = 0;  //lda
 unsigned char opt = ...
 doquery(m_maxverses,
          m_outputformat + 1,
          m_outputencoding + 1,
          opt,
          m_searchtype,
          range,                   //lda
          (LPCTSTR)m_book,
          (LPCTSTR)m_locale,
          (LPCTSTR)m_key,
          &output,
          (LPCTSTR)m_script,
          m_variants);
 output << '\0';
 char* versevalue = output.str();
 if (versevalue) {
  m_value = versevalue;
  delete versevalue;
  FireValueChanged();
  return TRUE;
 }
 return FALSE;
}


2. What is "ICU"? Is this for internationalization. The VisualC++ .dsp has
standard "Debug" and "Release" configurations, but also had "Debug with ICU"
and "Release with ICU". There were missing files like
#include <unicode/utypes.h>
(in utf8arshaping.h) that didn't show up with the CVS tree. Therefore, the
"Debug with ICU" and "Release with ICU" didn't compile.

3. Is there more to download beyond the basic "sword" using WinCVS 1.2? This
might explain the missing ICU files.

> Date: Mon, 20 Oct 2003 01:52:44 -0700
> From: "Troy A. Griffitts" <scribe@crosswire.org>
> To: sword-devel@crosswire.org
> Subject: Re: [sword-devel] ActiveDiatheke ocx: may have gotten working
again
> Reply-To: sword-devel@crosswire.org
>
> Lynn Allan,
> Usually, one can do a: cvs diff -u > patch.LynnAllan and send me the
> patch.LynnAllan file, but don't think this works on windows.  Maybe your
> CVS client will allow you to push a button that will run a 'unified'
> diff and output a file with the results.
>
> Otherwise you can just send me a zip file containing all the changed
> files.  If you can, keep them in the same path inside the zip file as
> they are in the CVS directories so I can just unzip it on top of my cvs
> checkout and I'll make the patch from that.
>
> This is great news!  I'm sure many people would love to take advantage
> of your hard work!  It's so awesome to have people come forward with
> gifts of silent service!  (Not that we don't want you to talk, as well!)
>
> Thank you,
>