On Wed, May 19, 2010 at 8:16 PM, Wade Balzer wrote:
>
> Thanks,
>
> From what I can tell, the "only" way to create the bindings in C# is to make
> a c++ managed code wrapper that will call the unmanaged libsword.dll. That
> is basically doing all the heavy lifting that swig was doing for you, exc
eone who knows what they are doing needs to do that.
Thanks,
Wade
-Original Message-
From: Wolfgang Schultz [mailto:woschu...@googlemail.com]
Sent: Wednesday, May 19, 2010 2:10 PM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] ztext file format...
2010/5/19 Wad
2010/5/19 Wade Balzer :
[[..]
> Anyway, if you or someone can write a sample c# program that calls the
> libsword.dll to display Jn.3.16, I will be greatly helped.
>
> I agree that we don't need to provide every single implementation of every
> method, but currently we have nothing that works in th
riginal Message-
From: Troy A. Griffitts [mailto:scr...@crosswire.org]
Sent: Wednesday, May 19, 2010 2:20 AM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] ztext file format...
Dear Wade,
I understand your frustration and desire to get something working.
I can't
On Wed, May 19, 2010 at 3:20 AM, Troy A. Griffitts wrote:
>
> Dear Wade,
>
> I understand your frustration and desire to get something working.
>
> I can't stress enough that making bindings to the existing engine is the
> way forward for .net developers. We have multiple storage formats
> beside
ch,
>
> Wade
>
>
> -----Original Message-
> From: Troy A. Griffitts [mailto:scr...@crosswire.org]
> Sent: Tuesday, May 18, 2010 6:37 PM
> To: SWORD Developers' Collaboration Forum
> Subject: Re: [sword-devel] ztext file format...
>
> On 05/18/2010 01:41 PM, Matth
rated and burned out before I can get it done.
Thanks so much,
Wade
-Original Message-
From: Troy A. Griffitts [mailto:scr...@crosswire.org]
Sent: Tuesday, May 18, 2010 6:37 PM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] ztext file format...
On 05/18/2010
On 05/18/2010 01:41 PM, Matthew Talbert wrote:
>>> I have looked, but I cannot seem to find any information regarding the
>>> structure of the ztext file format.
>>>
>> The module format is essentially undocumented (other than via the source
>> code) and we have little intention to change th
>> I have looked, but I cannot seem to find any information regarding the
>> structure of the ztext file format.
>
> The module format is essentially undocumented (other than via the source
> code) and we have little intention to change that. The format is subject
> to occasional smaller or larger
On 18/05/10 17:09, Wade Balzer wrote:
>
>
> I have looked, but I cannot seem to find any information regarding the
> structure of the ztext file format.
The module format is essentially undocumented (other than via the source
code) and we have little intention to change that. The format is subje
I have looked, but I cannot seem to find any information regarding the
structure of the ztext file format.
I understand that there are 3 files. For example, looking at the KJV New
Testament, there are:
nt.bzs
nt.bzv
nt.bzz
I can only look at so much C++ code before I get lost in wha
11 matches
Mail list logo
