Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

Hi.

The build scripts are deprecated and should be removed altogether.
Try building using the ObjCSword Xcode project.
I just made some code changes lately so it should still work.


Manfred

Am 23.01.2013 um 15:31 schrieb Jeff Barnes :

> Thanks for the quick response, Greg.
> 
> PACCPL-334LAGYA:trunk jbarne200$ which autoconf
> /usr/bin/autoconf
> PACCPL-334LAGYA:trunk jbarne200$ which automake
> /usr/bin/automake
> PACCPL-334LAGYA:trunk jbarne200$ which libtool
> /usr/bin/libtool
> PACCPL-334LAGYA:trunk jbarne200$ which aclocal
> /usr/bin/aclocal
> PACCPL-334LAGYA:trunk jbarne200$ which autoheader
> /usr/bin/autoheader
> 
> I was originally missing pkg-config. I installed it (for some reason the mac 
> flavor is installed in /opt) and created a symbolic link to it in /usr/bin. I 
> also created a sym link to /usr/bin/glibtoolize in /usr/bin. At that point, I 
> was able to build using trunk/autogen.sh.
> 
> Still not able to build using bindings/objc/build_sword/build_mac_sword.sh. I 
> get the error mentioned in my original post.
> 
> It might help mac users to have an environment check script (I still don't 
> have a full command of gnu on mac). Something like the following might be 
> useful.
> 
> #!/bin/sh
> echo "Checking build environment"
> autoconf --help >/dev/null || exit $?
> automake --help >/dev/null || exit $?
> ...
> etc
> 
> Jeff
> 
> 
>> 
>> From: Greg Hellings 
>> To: Jeff Barnes ; SWORD Developers' Collaboration 
>> Forum  
>> Sent: Wednesday, January 23, 2013 8:49 AM
>> Subject: Re: [sword-devel] bindings/objc build broken
>> 
>> 
>> The Obj-C bindings have not been updated since Troy's major commit to 
>> deprecate methods and the like. However, the error you're seeing appears to 
>> be a result of missing some of the autofoo material that you need. Do you 
>> have any information on the state of your autotools package? That might help 
>> the Obj-C maintainer with your problem.
>> 
>> 
>> --Greg
>> 
>> 
>> 
>> On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes  wrote:
>> 
>> Did a fresh checkout of https://crosswire.org/svn/sword/trunk. Changed to 
>> bindings/objc.
>>> 
>>> 1) The bindings/objc/README instructions are inaccurate. There is no 
>>> Makefile in build_sword.
>>> 2) The build breaks in build_sword/build_mac_sword.sh.
>>> 
>>> $ cd build_clucene
>>> 
>>> $ make release-fat
>>> ...
>>> looks like successful build for 3 platforms
>>> 
>>> $ cd ../build_sword
>>> $ ./build_mac_sword.sh -a fat -c
>>> 
>>> ...
>>> 
>>> ./configure: line 15671: syntax error near unexpected token `CLUCENE2,'
>>> ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, libclucene-core >= 
>>> 2.3,,true)'
>>> 
>>> $ pkg-config --cflags --libs libclucene-core
>>> -I/usr/local/include -I/usr/local/include/CLucene/ext  -L/usr/local/lib/ 
>>> -lclucene-core
>>> 
>>> $ which pkg-config
>>> /usr/bin/pkg-config
>>> 
>>>   System Version:Mac OS X 10.6.8 (10K549)
>>> ...
>>>   Model Name:MacBook Pro
>>>   Model Identifier:MacBookPro6,2
>>>   Processor Name:Intel Core i5
>>>  
>>> Any help appreciated.
>>> 
>>> Jeff
>>> 
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>> 
>> 
>> 
>> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

If you want to build from command line you can also use something like this:
# xcodebuild -target "" -configuration "" clean build

The pre-lion Xcode project may also be outdated as I didn't have the time to 
maintain it.



Manfred

Am 23.01.2013 um 15:45 schrieb Manfred Bergmann :

> Hi.
> 
> The build scripts are deprecated and should be removed altogether.
> Try building using the ObjCSword Xcode project.
> I just made some code changes lately so it should still work.
> 
> 
> Manfred
> 
> Am 23.01.2013 um 15:31 schrieb Jeff Barnes :
> 
>> Thanks for the quick response, Greg.
>> 
>> PACCPL-334LAGYA:trunk jbarne200$ which autoconf
>> /usr/bin/autoconf
>> PACCPL-334LAGYA:trunk jbarne200$ which automake
>> /usr/bin/automake
>> PACCPL-334LAGYA:trunk jbarne200$ which libtool
>> /usr/bin/libtool
>> PACCPL-334LAGYA:trunk jbarne200$ which aclocal
>> /usr/bin/aclocal
>> PACCPL-334LAGYA:trunk jbarne200$ which autoheader
>> /usr/bin/autoheader
>> 
>> I was originally missing pkg-config. I installed it (for some reason the mac 
>> flavor is installed in /opt) and created a symbolic link to it in /usr/bin. 
>> I also created a sym link to /usr/bin/glibtoolize in /usr/bin. At that 
>> point, I was able to build using trunk/autogen.sh.
>> 
>> Still not able to build using bindings/objc/build_sword/build_mac_sword.sh. 
>> I get the error mentioned in my original post.
>> 
>> It might help mac users to have an environment check script (I still don't 
>> have a full command of gnu on mac). Something like the following might be 
>> useful.
>> 
>> #!/bin/sh
>> echo "Checking build environment"
>> autoconf --help >/dev/null || exit $?
>> automake --help >/dev/null || exit $?
>> ...
>> etc
>> 
>> Jeff
>> 
>> 
>>> 
>>> From: Greg Hellings 
>>> To: Jeff Barnes ; SWORD Developers' Collaboration 
>>> Forum  
>>> Sent: Wednesday, January 23, 2013 8:49 AM
>>> Subject: Re: [sword-devel] bindings/objc build broken
>>> 
>>> 
>>> The Obj-C bindings have not been updated since Troy's major commit to 
>>> deprecate methods and the like. However, the error you're seeing appears to 
>>> be a result of missing some of the autofoo material that you need. Do you 
>>> have any information on the state of your autotools package? That might 
>>> help the Obj-C maintainer with your problem.
>>> 
>>> 
>>> --Greg
>>> 
>>> 
>>> 
>>> On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes  wrote:
>>> 
>>> Did a fresh checkout of https://crosswire.org/svn/sword/trunk. Changed to 
>>> bindings/objc.
>>>> 
>>>> 1) The bindings/objc/README instructions are inaccurate. There is no 
>>>> Makefile in build_sword.
>>>> 2) The build breaks in build_sword/build_mac_sword.sh.
>>>> 
>>>> $ cd build_clucene
>>>> 
>>>> $ make release-fat
>>>> ...
>>>> looks like successful build for 3 platforms
>>>> 
>>>> $ cd ../build_sword
>>>> $ ./build_mac_sword.sh -a fat -c
>>>> 
>>>> ...
>>>> 
>>>> ./configure: line 15671: syntax error near unexpected token `CLUCENE2,'
>>>> ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, libclucene-core >= 
>>>> 2.3,,true)'
>>>> 
>>>> $ pkg-config --cflags --libs libclucene-core
>>>> -I/usr/local/include -I/usr/local/include/CLucene/ext  -L/usr/local/lib/ 
>>>> -lclucene-core
>>>> 
>>>> $ which pkg-config
>>>> /usr/bin/pkg-config
>>>> 
>>>>  System Version:Mac OS X 10.6.8 (10K549)
>>>> ...
>>>>  Model Name:MacBook Pro
>>>>  Model Identifier:MacBookPro6,2
>>>>  Processor Name:Intel Core i5
>>>> 
>>>> Any help appreciated.
>>>> 
>>>> Jeff
>>>> 
>>>> ___
>>>> sword-devel mailing list: sword-devel@crosswire.org
>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>> Instructions to unsubscribe/change your settings at above page
>>>> 
>>> 
>>> 
>>> 
>> 
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

Am 23.01.2013 um 19:41 schrieb "Barnes, Jeffrey" :

> 
> On Jan 23, 2013, at 12:05:20PM, Manfred Bergmann  
> wrote:
> 
>> Just out of curiosity, what do you need the objc wrappers for?
>> 
> 
> Just want to play around with the API. Develop a simple client. Curiosity 
> while I learn to code in Objective-C/Cocoa.

OK. Can you upgrade to Lion at least?
That would probably be the easiest because the this Xcode project is maintained.



Manfred


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

Am 23.01.2013 um 21:54 schrieb "Barnes, Jeffrey" :

> 
> On Jan 23, 2013, at 2:21:09PM, Manfred Bergmann  
> wrote:
> 
>> 
>> OK. Can you upgrade to Lion at least?
>> That would probably be the easiest because the this Xcode project is 
>> maintained.
>> 
> 
> Last night, while we were asleep, my wife poked me in the eye when she rolled 
> over. I upgraded to Mountain Lion today. I must say, the poke in the eye was 
> less painful. It only lasted a few minutes.
> 
> Gcc? gone
> Java? gone
> XCode? gone
> Subversion client? gone
> XWindows?
> 
> Well, you get the idea. But now, I've got the new Xcode and I'm building 
> ObjCSword. So far it's been about 15 minutes… (Not counting the 2 hour 
> download / install / fix of Mountain Lion)
> 
> More to follow.
> Jeff
> 

Well, you know how Apple is. Much changes, especially over on two major 
versions.
Many things have their advantages. Installing Xcode over App Store is pretty 
much painless (except the download). You get gcc, subversion, git and many 
other goodies once you've installed it.
The OS X Java port is now maintained by Oracle which IMO is a good thing as 
well.


Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

Am 23.01.2013 um 23:21 schrieb Jeff Barnes :

> 
> 
> Sent from my iPhone
> 
> On Jan 23, 2013, at 4:20 PM, Manfred Bergmann  wrote:
> 
>> 
>> Well, you know how Apple is. Much changes, especially over on two major 
>> versions.
>> Many things have their advantages. Installing Xcode over App Store is pretty 
>> much painless (except the download). You get gcc, subversion, git and many 
>> other goodies once you've installed it.
>> The OS X Java port is now maintained by Oracle which IMO is a good thing as 
>> well.
>> 
>> 
>> Manfred
> 
> I downloaded fink to get gcc. I read all the blogs, etc. that said gcc 
> doesn't come with Xcode anymore. Did I misread something?

No need to do that. As Nic pointed out, the command line tools can be installed 
from Xcode Preferences.
And unless you want to compile something from command line directly via issuing 
gcc you don't need the command line tools to build Xcode projects.


Manfred

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

Indeed, there are a lot of warnings, not mentioning CLucene.

I'll do a clean checkout of the sources and see if I can replicate your errors.
You should however build with ICU. CLucene it not necessarily needed since on 
Mac the index is built using SearchKit framework.


Manfred

Am 24.01.2013 um 15:59 schrieb "Barnes, Jeffrey" :

> 
> On Jan 24, 2013, at 9:52:37AM, "Barnes, Jeffrey"  wrote:
> 
>> 
>> I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2.
>> 
>> I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran the 
>> build. It failed on Lucene dependency. Just to try to get it to build, I 
>> removed the lucene define and ran the build again. It failed on the ICU 
>> dependency. I removed the ICU define.
>> 
>> Now it fails on the AnalysisHeader step. Here's the last line of the build 
>> output.
>> 
>> clang: error: no such file or directory: 
>> '/Users/jbarne200/sword/trunk/bindings/objc/dependencies/clucene/CLucene/analysis/AnalysisHeader.cpp'
>> clang: error: no input files
>> Command 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
>>  failed with exit code 1
>> 
>> Regards,
>> Jeff
> 
> Also, there are compiler warnings on almost every file. The most common one 
> being like the following:
> 
> /Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit conversion 
> loses integer precision: 'unsigned long' to 'unsigned int'
> 
> etc.
> 
> I have a gut wrench every time I see a compiler warning. I have to maintain 
> code at work and one of the first things my boss told me to do was clean up 
> the compiler warnings. I have to encourage the other members of my team 
> constantly to keep trunk pristine. Forgive me if I'm being pedantic, but "Me 
> no like compiler warnings!"
> 


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

Alright.
Here is what you need to do.
in "objc" folder go to "dependencies" and execute "retrieve.sh".
This downloads the icu and clucene sources and headers which are required for 
the Xcode build.

I've done some adaptions to the latest sword src changes. One method was 
removed which gave an error. And there are now a lot of deprecation warnings 
which I have to go through.
I've also removed two old library search paths from the project which pointed 
to a folder that doesn't exist.

If you update your sources it should build fine now.



Manfred

Am 24.01.2013 um 18:18 schrieb Manfred Bergmann :

> Indeed, there are a lot of warnings, not mentioning CLucene.
> 
> I'll do a clean checkout of the sources and see if I can replicate your 
> errors.
> You should however build with ICU. CLucene it not necessarily needed since on 
> Mac the index is built using SearchKit framework.
> 
> 
> Manfred
> 
> Am 24.01.2013 um 15:59 schrieb "Barnes, Jeffrey" :
> 
>> 
>> On Jan 24, 2013, at 9:52:37AM, "Barnes, Jeffrey"  
>> wrote:
>> 
>>> 
>>> I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2.
>>> 
>>> I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran 
>>> the build. It failed on Lucene dependency. Just to try to get it to build, 
>>> I removed the lucene define and ran the build again. It failed on the ICU 
>>> dependency. I removed the ICU define.
>>> 
>>> Now it fails on the AnalysisHeader step. Here's the last line of the build 
>>> output.
>>> 
>>> clang: error: no such file or directory: 
>>> '/Users/jbarne200/sword/trunk/bindings/objc/dependencies/clucene/CLucene/analysis/AnalysisHeader.cpp'
>>> clang: error: no input files
>>> Command 
>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
>>>  failed with exit code 1
>>> 
>>> Regards,
>>> Jeff
>> 
>> Also, there are compiler warnings on almost every file. The most common one 
>> being like the following:
>> 
>> /Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit conversion 
>> loses integer precision: 'unsigned long' to 'unsigned int'
>> 
>> etc.
>> 
>> I have a gut wrench every time I see a compiler warning. I have to maintain 
>> code at work and one of the first things my boss told me to do was clean up 
>> the compiler warnings. I have to encourage the other members of my team 
>> constantly to keep trunk pristine. Forgive me if I'm being pedantic, but "Me 
>> no like compiler warnings!"
>> 
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

Am 24.01.2013 um 20:02 schrieb "Barnes, Jeffrey" :

> 
> On Jan 24, 2013, at 12:18:18PM, Manfred Bergmann  
> wrote:
> 
>> I'll do a clean checkout of the sources and see if I can replicate your 
>> errors.
>> You should however build with ICU. CLucene it not necessarily needed since 
>> on Mac the index is built using SearchKit framework.
> 
> How do I link against ICU? Are the .h/.cpp files in trunk?

The project links against libicu-core which is shipped with OS X.
The ICU headers are in the dependencies once "retrieve.sh" is executed.


Manfred

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

I'm not sure. Maybe try plain http?
It's also enough to rm objc and do svn update. It will fetch objc folder again.


Manfred

Am 24.01.2013 um 21:06 schrieb "Barnes, Jeffrey" :

> I had trouble updating, so I blew away my local trunk directory.
> 
> I tried the command line.
> 
> PACCPL-334LAGYA:sword jbarne200$ svn co https://crosswire.org/svn/sword/trunk
> Error validating server certificate for 'https://crosswire.org:443':
> - The certificate is not issued by a trusted authority. Use the
>   fingerprint to validate the certificate manually!
> - The certificate hostname does not match.
> Certificate information:
> - Hostname: www.crosswire.org
> - Valid: from Fri, 04 May 2012 23:03:07 GMT until Sat, 04 May 2013 23:03:07 
> GMT
> - Issuer: SomeOrganizationalUnit, SomeOrganization, SomeCity, SomeState, --
> - Fingerprint: 60:d4:77:54:37:d3:37:ed:42:92:7b:eb:1a:f0:25:f7:50:ff:c2:57
> (R)eject, accept (t)emporarily or accept (p)ermanently? p
> svn: PROPFIND of '/svn/sword/trunk': SSL handshake failed: Secure connection 
> truncated (https://crosswire.org)
> 
> I tried from Xcode. It told me to validate the fingerprint (where do I do 
> that?).
> 
> Is the repository down? I thought the command line version should have worked.
> 
> Jeff
> 
> On Jan 24, 2013, at 2:27:58PM, Manfred Bergmann  
> wrote:
> 
>> Alright.
>> Here is what you need to do.
>> in "objc" folder go to "dependencies" and execute "retrieve.sh".
>> This downloads the icu and clucene sources and headers which are required 
>> for the Xcode build.
>> 
>> I've done some adaptions to the latest sword src changes. One method was 
>> removed which gave an error. And there are now a lot of deprecation warnings 
>> which I have to go through.
>> I've also removed two old library search paths from the project which 
>> pointed to a folder that doesn't exist.
>> 
>> If you update your sources it should build fine now.
>> 
>> 
>> 
>> Manfred
>> 
>> Am 24.01.2013 um 18:18 schrieb Manfred Bergmann :
>> 
>>> Indeed, there are a lot of warnings, not mentioning CLucene.
>>> 
>>> I'll do a clean checkout of the sources and see if I can replicate your 
>>> errors.
>>> You should however build with ICU. CLucene it not necessarily needed since 
>>> on Mac the index is built using SearchKit framework.
>>> 
>>> 
>>> Manfred
>>> 
>>> Am 24.01.2013 um 15:59 schrieb "Barnes, Jeffrey" :
>>> 
>>>> 
>>>> On Jan 24, 2013, at 9:52:37AM, "Barnes, Jeffrey"  
>>>> wrote:
>>>> 
>>>>> 
>>>>> I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2.
>>>>> 
>>>>> I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran 
>>>>> the build. It failed on Lucene dependency. Just to try to get it to 
>>>>> build, I removed the lucene define and ran the build again. It failed on 
>>>>> the ICU dependency. I removed the ICU define.
>>>>> 
>>>>> Now it fails on the AnalysisHeader step. Here's the last line of the 
>>>>> build output.
>>>>> 
>>>>> clang: error: no such file or directory: 
>>>>> '/Users/jbarne200/sword/trunk/bindings/objc/dependencies/clucene/CLucene/analysis/AnalysisHeader.cpp'
>>>>> clang: error: no input files
>>>>> Command 
>>>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
>>>>>  failed with exit code 1
>>>>> 
>>>>> Regards,
>>>>> Jeff
>>>> 
>>>> Also, there are compiler warnings on almost every file. The most common 
>>>> one being like the following:
>>>> 
>>>> /Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit 
>>>> conversion loses integer precision: 'unsigned long' to 'unsigned int'
>>>> 
>>>> etc.
>>>> 
>>>> I have a gut wrench every time I see a compiler warning. I have to 
>>>> maintain code at work and one of the first things my boss told me to do 
>>>> was clean up the compiler warnings. I have to encourage the other members 
>>>> of my team constantly to keep trunk pristine. Forgive me if I'm being 
>>>> pedantic, but "Me no like compiler warnings!"
>>>> 
>>> 
>>> 
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>> 
> 


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

Yep, thanks. I will update the README.

You can now use the result (ObjCSword.framework) as a dependency in another 
project.
Or you add the whole Xcode project to another Xcode project.
If you build the outer project the inner project is built as well or actually 
the inner one is built first.

You can also have a look at the (too few) OCUnit tests (i.e. SwordModuleTest) 
in ObjCSword, at least regarding the API usage.



Manfred


Am 24.01.2013 um 22:04 schrieb "Barnes, Jeffrey" :

> Ok, everything built. (Hooray!)
> 
> I recommend updating bindings/objc/README to the following.
> 
> Building ObjCSword wrapper framework howto
> ==
> 
> Mac OS X target:
> This project can only be built on OS X 10.8 (Mountain Lion) or later.
> 
> To build for Mac OS X:
> 
> 1) Change to the dependencies directory.
> 2) Run retrieve.sh. This downloads the icu and clucene sources and headers 
> which are required for the Xcode build.
> 
> To build from inside Xcode double-click the ObjCSword.xcodeproj in Finder. 
> This opens Xcode and loads the Sword Project. Press  + B to build 
> (or select Build from the Product menu).
> 
> To build from the command line, enter xcodebuild -project 
> ./ObjCSword.xcodeproj.
> 
> 
> +
> 
> How can I reference this new ObjCSword in another project?
> 
> Thanks so much for your help Manfred.
> 
> Jeff
> 
> 


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Personal Commentary and Dropbox.

[Manfred Bergmann]

Hi Nic.

I wouldn't use Dropbox instead but additionally.
iCloud is the standard for synching user properties and settings across OS X 
and iOS devices. Most people if not all using OS X or iOS already have an 
iCloud account. Many people do not have a Dropbox account and this shouldn't be 
a requirement.
Is it possible to store a larger content on iCloud like personal commentary 
modules. Well, they may not get that large but what's the iCloud limit?



Manfred



Am 12.02.2013 um 08:17 schrieb Nic Carter :

> 
> Hi team,
> 
> I think I may have mentioned this in the past, but I'm almost ready to go, 
> and so have a few comments/questions about personal commentaries.
> 
> Different front-ends do things differently, but there is the Personal 
> Commentary module that we can use for the user to write their own notes to. 
> This is stored as a "normal module", stored in the usual modules location 
> (or, at least, some "usual" location on the local filesystem).
> PocketSword currently doesn't support the Personal Commentary module due to 
> the fact that I haven't written any UI by which the user can write to it.
> 
> However, once the user can write notes, they must be able to sync. Right now 
> users can have an iPhone and an iPad & have PocketSword on both & ideally any 
> user created content should be sync'd across both.
> [In fact, I received yet another user email about this earlier today.]
> 
> The next version of PS (almost out of beta) will sync Bible browsing history 
> across devices via iCloud.
> For the version following I was planning on adding sync of Bookmarks via 
> iCloud as well.
> However, Dropbox have recently released an API for iOS (& Android) for native 
> sync: https://www.dropbox.com/developers/sync
> So I am looking into sync of bookmarks via Dropbox instead.
> This way I am not limiting a user's data to Apple products only, and sync is 
> possible with other front-ends, if there was any desire for that to happen 
> from other front-end developers.
> 
> And this then presents an idea of having user notes/Personal Commentary 
> located on Dropbox. I am not sure how well the SWORD module format would 
> function over a remote filesystem, and so I am putting this thought out there 
> for comments from others.
> 
> 
> So, my proposal is for real-time sync of bookmarks & user notes across 
> front-ends via Dropbox.
> 
> 
> Thanks heaps, ybic
>   nic...  :)
> 
> 
> 
> 
> 
> 
> [Aside: Dropbox comes with plenty of space for a free account, so it's no 
> financial burden for users. Anyone on the list who doesn't have it yet (but 
> you all should, cause it's pretty nifty) can sign up for free via 
> http://db.tt/F8p526B and then both you and I get a bonus 500MB of free space. 
> If you feel uncomfortable with me posting this link to this list, please 
> don't use the link and instead sign up the normal free way!]
> 
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Personal Commentary and Dropbox.

[Manfred Bergmann]

No, haven't tried iCloud yet. Many apps use it though (Contacts, Calendar, 
Pages, Number, ...) and I'm quite happy with it most of the time.
The advantage to the user is that there is zero configuration overhead, nothing 
to configure.
Where on Dropbox there must be some settings which define where, to which 
folder or file the data should be synched, or?


Manfred

Am 12.02.2013 um 10:08 schrieb Nic Carter :

> 
> Having a local copy, iCloud copy & Dropbox copy may be a little bit of 
> overkill? and three copies of the data means if one version gets corrupted, 
> that will replicate across all copies? And the effort to do 3-way sync is a 
> lot more than 2-way...
> Dropbox sync would be off by default, the user would have to switch it on 
> (authenticate it) and otherwise it would only have a local copy.
> 
> I agree that having iCloud sync would be much simpler, as almost every iOS 
> user would already have an account, but all my recent research on it has 
> shown that it's not quite "finished" yet, in any of the 3 sync iterations 
> that exist. For example, for a conversation that focuses on Core Data, take a 
> look at http://storify.com/Jury/the-trials-of-icloud
> Plus, Dropbox has stuff like versioning built-in. If iCloud stuffs up, which 
> it does some of the time for no apparent reason, there is only one solution: 
> delete all iCloud data connected with the app. For Dropbox, you can at least 
> revert to an older version of the data that did work. 
> 
> Hence I am thinking of providing sync for those users who really want it. And 
> they are more likely to have a Dropbox account already. If they don't switch 
> on Dropbox syncing, it'll all be just local & they can put up with that. ;)
> 
> What do you think?
> 
> Have you tried iCloud stuff yet?
> 
> 
> Thanks, ybic
>   nic...  :)
> 
> On 12/02/2013, at 7:15 PM, Manfred Bergmann  wrote:
> 
>> Hi Nic.
>> 
>> I wouldn't use Dropbox instead but additionally.
>> iCloud is the standard for synching user properties and settings across OS X 
>> and iOS devices. Most people if not all using OS X or iOS already have an 
>> iCloud account. Many people do not have a Dropbox account and this shouldn't 
>> be a requirement.
>> Is it possible to store a larger content on iCloud like personal commentary 
>> modules. Well, they may not get that large but what's the iCloud limit?
>> 
>> 
>> 
>> Manfred
>> 
>> 
>> 
>> Am 12.02.2013 um 08:17 schrieb Nic Carter :
>> 
>>> 
>>> Hi team,
>>> 
>>> I think I may have mentioned this in the past, but I'm almost ready to go, 
>>> and so have a few comments/questions about personal commentaries.
>>> 
>>> Different front-ends do things differently, but there is the Personal 
>>> Commentary module that we can use for the user to write their own notes to. 
>>> This is stored as a "normal module", stored in the usual modules location 
>>> (or, at least, some "usual" location on the local filesystem).
>>> PocketSword currently doesn't support the Personal Commentary module due to 
>>> the fact that I haven't written any UI by which the user can write to it.
>>> 
>>> However, once the user can write notes, they must be able to sync. Right 
>>> now users can have an iPhone and an iPad & have PocketSword on both & 
>>> ideally any user created content should be sync'd across both.
>>> [In fact, I received yet another user email about this earlier today.]
>>> 
>>> The next version of PS (almost out of beta) will sync Bible browsing 
>>> history across devices via iCloud.
>>> For the version following I was planning on adding sync of Bookmarks via 
>>> iCloud as well.
>>> However, Dropbox have recently released an API for iOS (& Android) for 
>>> native sync: https://www.dropbox.com/developers/sync
>>> So I am looking into sync of bookmarks via Dropbox instead.
>>> This way I am not limiting a user's data to Apple products only, and sync 
>>> is possible with other front-ends, if there was any desire for that to 
>>> happen from other front-end developers.
>>> 
>>> And this then presents an idea of having user notes/Personal Commentary 
>>> located on Dropbox. I am not sure how well the SWORD module format would 
>>> function over a remote filesystem, and so I am putting this thought out 
>>> there for comments from others.
>>> 
>>> 
>&g

Re: [sword-devel] Personal Commentary and Dropbox.

[Manfred Bergmann]

I think that on iOS synching to EverNote, Dropbox or other services feel like 
foreigners.
This is probably different on Android or other platforms.


Manfred


Am 12.02.2013 um 10:36 schrieb Martin Denham :

> Currently And Bible notes and bookmarks are stored locally but I have had a 
> lot of requests to be able to sync them with other Sword apps.
> 
> It would be good to have an architecture such as Dropbox that allowed sync 
> between different platforms.  Somebody suggested EverNote to me but Dropbox 
> looks good.
> 
> Martin
> 
> On 12 February 2013 09:08, Nic Carter  wrote:
> 
> Having a local copy, iCloud copy & Dropbox copy may be a little bit of 
> overkill? and three copies of the data means if one version gets corrupted, 
> that will replicate across all copies? And the effort to do 3-way sync is a 
> lot more than 2-way...
> Dropbox sync would be off by default, the user would have to switch it on 
> (authenticate it) and otherwise it would only have a local copy.
> 
> I agree that having iCloud sync would be much simpler, as almost every iOS 
> user would already have an account, but all my recent research on it has 
> shown that it's not quite "finished" yet, in any of the 3 sync iterations 
> that exist. For example, for a conversation that focuses on Core Data, take a 
> look at http://storify.com/Jury/the-trials-of-icloud
> Plus, Dropbox has stuff like versioning built-in. If iCloud stuffs up, which 
> it does some of the time for no apparent reason, there is only one solution: 
> delete all iCloud data connected with the app. For Dropbox, you can at least 
> revert to an older version of the data that did work.
> 
> Hence I am thinking of providing sync for those users who really want it. And 
> they are more likely to have a Dropbox account already. If they don't switch 
> on Dropbox syncing, it'll all be just local & they can put up with that. ;)
> 
> What do you think?
> 
> Have you tried iCloud stuff yet?
> 
> 
> Thanks, ybic
> nic...  :)
> 
> On 12/02/2013, at 7:15 PM, Manfred Bergmann  wrote:
> 
> > Hi Nic.
> >
> > I wouldn't use Dropbox instead but additionally.
> > iCloud is the standard for synching user properties and settings across OS 
> > X and iOS devices. Most people if not all using OS X or iOS already have an 
> > iCloud account. Many people do not have a Dropbox account and this 
> > shouldn't be a requirement.
> > Is it possible to store a larger content on iCloud like personal commentary 
> > modules. Well, they may not get that large but what's the iCloud limit?
> >
> >
> >
> > Manfred
> >
> >
> >
> > Am 12.02.2013 um 08:17 schrieb Nic Carter :
> >
> >>
> >> Hi team,
> >>
> >> I think I may have mentioned this in the past, but I'm almost ready to go, 
> >> and so have a few comments/questions about personal commentaries.
> >>
> >> Different front-ends do things differently, but there is the Personal 
> >> Commentary module that we can use for the user to write their own notes 
> >> to. This is stored as a "normal module", stored in the usual modules 
> >> location (or, at least, some "usual" location on the local filesystem).
> >> PocketSword currently doesn't support the Personal Commentary module due 
> >> to the fact that I haven't written any UI by which the user can write to 
> >> it.
> >>
> >> However, once the user can write notes, they must be able to sync. Right 
> >> now users can have an iPhone and an iPad & have PocketSword on both & 
> >> ideally any user created content should be sync'd across both.
> >> [In fact, I received yet another user email about this earlier today.]
> >>
> >> The next version of PS (almost out of beta) will sync Bible browsing 
> >> history across devices via iCloud.
> >> For the version following I was planning on adding sync of Bookmarks via 
> >> iCloud as well.
> >> However, Dropbox have recently released an API for iOS (& Android) for 
> >> native sync: https://www.dropbox.com/developers/sync
> >> So I am looking into sync of bookmarks via Dropbox instead.
> >> This way I am not limiting a user's data to Apple products only, and sync 
> >> is possible with other front-ends, if there was any desire for that to 
> >> happen from other front-end developers.
> >>
> >> And this then presents an idea of having user notes/Personal Commentary 
> >> located on Dropbox. I am not sure how well the SWORD modul

Re: [sword-devel] bindings/objc build broken

[Manfred Bergmann]

Hello.

AFAIR you were able to built it in January this year when there was the last 
discussion about this.
Does the Xcode project not work anymore?
Unfortunately I think I haven't yet updated the README file as you suggested in 
your mail from January below.


Manfred


> Ok, everything built. (Hooray!)
> 
> I recommend updating bindings/objc/README to the following.
> 
> Building ObjCSword wrapper framework howto
> ==
> 
> Mac OS X target:
> This project can only be built on OS X 10.8 (Mountain Lion) or later.
> 
> To build for Mac OS X:
> 
> 1) Change to the dependencies directory.
> 2) Run retrieve.sh. This downloads the icu and clucene sources and headers 
> which are required for the Xcode build.
> 
> To build from inside Xcode double-click the ObjCSword.xcodeproj in Finder. 
> This opens Xcode and loads the Sword Project. Press  + B to build 
> (or select Build from the Product menu).
> 
> To build from the command line, enter xcodebuild -project 
> ./ObjCSword.xcodeproj.
> 
> 
> +
> 
> How can I reference this new ObjCSword in another project?
> 
> Thanks so much for your help Manfred.
> 
> Jeff



Am 23.01.2013 um 06:34 schrieb Jeff Barnes :

> Did a fresh checkout of https://crosswire.org/svn/sword/trunk. Changed to 
> bindings/objc.
> 
> 1) The bindings/objc/README instructions are inaccurate. There is no Makefile 
> in build_sword.
> 2) The build breaks in build_sword/build_mac_sword.sh.
> 
> $ cd build_clucene
> 
> $ make release-fat
> ...
> looks like successful build for 3 platforms
> 
> $ cd ../build_sword
> $ ./build_mac_sword.sh -a fat -c
> 
> ...
> 
> ./configure: line 15671: syntax error near unexpected token `CLUCENE2,'
> ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, libclucene-core >= 
> 2.3,,true)'
> 
> $ pkg-config --cflags --libs libclucene-core
> -I/usr/local/include -I/usr/local/include/CLucene/ext  -L/usr/local/lib/ 
> -lclucene-core
> 
> $ which pkg-config
> /usr/bin/pkg-config
> 
>   System Version:Mac OS X 10.6.8 (10K549)
> ...
>   Model Name:MacBook Pro
>   Model Identifier:MacBookPro6,2
>   Processor Name:Intel Core i5
>  
> Any help appreciated.
> 
> Jeff
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Current SVN

[Manfred Bergmann]

Getting this error on compile:
/src/mgr/ftplibftpt.cpp:79:80: Member initializer 'FTPTransport' does not name 
a non-static data member or base class

Any idea how to fix?


Manfred


Am 13.06.2013 um 23:58 schrieb Troy A. Griffitts :

> Have projects had a chance to test against the latest SVN HEAD?
> I believe I still have a patch from Greg to find and we still have something 
> outstanding for Peter to fix. Is anything else outstanding?
> 
> Chris, I'd like to finish our discussion about the LXX v12n. What do you 
> think about having a 4 pattern book naming scheme for the double books: A, B, 
> without a suffix, and Alt. The without a suffix book name would map to the 
> primary column in Ralfs, as you have it, and either A or B would map to the 
> other, as you have it, but we would also include abbrevs which would map the 
> explicit A and B always, and then have an Alt abbrev which would map to the 
> non-primary reading. Thoughts?
> -- 
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Current SVN

[Manfred Bergmann]

OK, I've commited fixes for the objc bindings Xcode project.
Compiles and works ok.



Manfred

Am 14.06.2013 um 08:53 schrieb Jaak Ristioja :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Yes. The base class of FTPLibFTPTransport is RemoteTransport not
> FTPTransport, hence the correct initializer list would probably be:
> 
>  : RemoteTransport(host, sr)
> 
> Blessings,
> Jaak
> 
> On 14.06.2013 09:44, Manfred Bergmann wrote:
>> Getting this error on compile: /src/mgr/ftplibftpt.cpp:79:80:
>> Member initializer 'FTPTransport' does not name a non-static data
>> member or base class
>> 
>> Any idea how to fix?
>> 
>> 
>> Manfred
>> 
>> 
>> Am 13.06.2013 um 23:58 schrieb Troy A. Griffitts
>> :
>> 
>>> Have projects had a chance to test against the latest SVN HEAD? I
>>> believe I still have a patch from Greg to find and we still have
>>> something outstanding for Peter to fix. Is anything else
>>> outstanding?
>>> 
>>> Chris, I'd like to finish our discussion about the LXX v12n. What
>>> do you think about having a 4 pattern book naming scheme for the
>>> double books: A, B, without a suffix, and Alt. The without a
>>> suffix book name would map to the primary column in Ralfs, as you
>>> have it, and either A or B would map to the other, as you have
>>> it, but we would also include abbrevs which would map the
>>> explicit A and B always, and then have an Alt abbrev which would
>>> map to the non-primary reading. Thoughts? -- Sent from my Android
>>> phone with K-9 Mail. Please excuse my brevity. 
>>> ___ sword-devel
>>> mailing list: sword-devel@crosswire.org 
>>> http://www.crosswire.org/mailman/listinfo/sword-devel 
>>> Instructions to unsubscribe/change your settings at above page
>> 
>> 
>> ___ sword-devel mailing
>> list: sword-devel@crosswire.org 
>> http://www.crosswire.org/mailman/listinfo/sword-devel Instructions
>> to unsubscribe/change your settings at above page
>> 
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.20 (GNU/Linux)
> 
> iQgcBAEBAgAGBQJRur3bAAoJEEqsYmEt1rCOC68//1Cd9U1qwowlybTmBo4IViEL
> hXcvGKsvTcgI2lMSfmJmntOFdtoY6eM9pWfRAsIR6Dnyf4UPp4SyNihwR9KzZu/i
> Ju/Ztx/J1OBL2o/0/B7005pg0rre23b3uTwS4KytpH8eGW5blxcoicOFUxQt+56Q
> z8DOrpcT1PL2CKSZhN9lthp//lp0Ex2dd+n6edSmTjJx3bWtTWjUhQ69FFHQT11S
> z19L5OpXnk6CNtTpi4+QolTHKfxy4yP+e77z0pme2zdUTCAXERdMn6S5BYNZhwXN
> /gvcoCrM05/C+5OT7sVgloHrjNp0F4GvuSf+SpnnSj+zTCpsXl3YsIQbbhjkXg6M
> ZHKwRsIifBVm/fRo8lvMG8T6uznDdCy0J2n3ha0DFYa0kNXLgJbmiXCkqj4FzeqV
> XgKy12slmB+0/IBsCsqAuCI9zT1cuLgT12Dq81QhVbQxWFFsVt/HWmkHJtQ8+8Yu
> yFW+esw3Zf96XZUB1kgb3qRP2k+ILk4n1Peuog+g0Zr14dGM2RZtVgoWSPfRylcv
> 1UJeURSqjY1pAKajR1YdpjJXUMM8wjD96tC9APqIjIsbVNxIhgej1x7iq5kobIOT
> Re3UyF9TBv6qdTN3p2QxKEf2sxwPq5hQrLcjjxQjINQu1bUpxkWuTYwtB9pLoyIX
> NoWdQbLAyr8um2o96GQjwQEYamDAVBkjC8t60pt1u2FTUSsRO4O1uyawgH5VCPKS
> szSDiAQySgGuA1gOLOPLBOWDwsKrW+HLBRQAT8PRuBIVLsrp7VDF7znaHCZI1r2n
> jzgK3vHMqEY+wCXZqUsZTsPUU2IRuFB5jxtmvLbgo5oy4JtnBvKRxcng9dPw4j0D
> jPMdcyAIi4ygZaQ8U9Tiz5l+RZIQvb4c8Ay4hcMW/TcXnk507urrHLPJrWzE6SBK
> lFGjY8avfddSPgAiI/GzeLrLGDQ6y2jykbOb/NjCW4Lh5BQx9g/TwG8BBUGyFXl4
> dE6qRZMq1E0rNbr1/No218XM2mzsRpXCuRYI//Hkrf6+ZJtgO07LWeLaFf4s9fhh
> tC3BWskRNfm9rtYlOzo/asWaxR+n8QdgcNKNo1/U0BwVA2U8A8vFjFaxqafz99MA
> 9bERTiCZn3EuyuwgOPVtMIIn3RgskalkyHgtrG4sG7c8bPHZotkjnXdcY9/p+4Sf
> WlIwcziU7iq/eLGUGbh9TyUdPE2E9337KL2llkxXevD2Eue0qd8sSKL7Azrjo6qd
> gVp0XsIQPpg9y36SP8yR0omme8YUlqUEZvndG7qwr8EoBodBg3o3RHz4K75468oW
> EQf8ZhAaYQelXUi14XFO/EEB+Tcs7GDj84EDjyaZAflg+vRO/0k8HLonNo78GCja
> ib/6CavRNGWsinRHfny1Kv0BYZTNND9vJVJRWbXMp43huE1wbAXe2QDBX8caAzHx
> Nm4ygDE/Afe1jcihdr96X+0xPR9L8M9NdqXnuljOyJarUhbW8eaPYtC7d4p3jrCH
> /OyzDZE1nF3RPk4ZS27C9kXukZ+iqq+YuWvR1wJIQPsa9Zk7zrN3vriVCMNhrJsX
> t8stAbcBFi5q/uEqWKU4u6IRIrsWj0zSmyw//tEaF4Nx3WtJNbeBeIpOzRWPSNWj
> 4aZbtgsAsBrohYl99JHJROflukWcchblHS1xb7Q1cChtiyflRHzIdy9ffI/Afh+h
> 9AeJ7+SHumjKj1Itbwd0xXVdGszWw4IrHzCZcq46Y4rZ5/2Q3PU630uh/OHKXZzW
> ULq0ILwHaSv+wmpoOfpu/6btIvXLQUp6ZORsKVW8xOkUaXUn1Z62stwAhxaiGndW
> dR8RQjqI8qw7ztSSd6bGyeG5pHF6Ar+HZUnf5POrdDUJpYid7EDW6rgkxdpfZJej
> Oh3rCsMG919XWJ+A28Jj0pjsTo8+m9064rKZ/r3qJ4nECcWLWIuH+PkWidckQskQ
> ErapKGCV63cDsAUH09e82BWwM49EgzkiIGQto0qAtmUlNqpkyPHPGhNi9SH5pZtB
> Ekwmr/IwIF+sx66caekr3T240sXwBNgUPNrSgJj+fVZDf1fvUH2oacSF9ISB6vy9
> IV2MT0MwR/MGjkKEUWiSDrd80//ZG221pFdND27ERRdF2LXG8hbBF1aAG28tnG71
> cw9ePHmoy/NKXPpChwabS+XtLBrzGdtAK/RnBTUAhUJ0uKLUohbisYPcaC+Vs5VK
> JfIODaOGCy6yZ2+XiIEZTcAgQf+745L67WCZZdUqDx/jUSIUnPr5F+25sG/uD3Nz
> 1+NnFrdgdh9cE63FvFdLCTe7/fLqdIvcyvBx

Re: [sword-devel] SWORD 1.7.0 final stretch

[Manfred Bergmann]

That's all right.
The ObjC wrapper user probably expects that it builds against the current SWORD 
sources.
Saying that, I had to update the Xcode project as more files had been 
removed/added in SWORD.



Manfred


Am 16.07.2013 um 07:49 schrieb Troy A. Griffitts :

> It seems we've all been negligent updating ChangeLog.
> 
> I've seeded it will the svn log since the last release.  I spent a while 
> reviewing the entries and deleted about 70% of them that had to do with 
> "fixed this, improved that" or entries where I saw something like "added iOS 
> XCode Project" with a later "removed iOS XCode Project" (sorry Manfred) :)
> 
> Anyway, we only want stuff in there that a use of the API might actually care 
> about reading.  Each release comes with the general "lots of bugs fixed and 
> things optimized," so we don't need these entries.
> 
> Can I ask you to review your entries from the svn log which I've added to 
> ChangeLog, delete the ones I've left which you still don't think important to 
> include, and reformat your remaining entries into our standard ChangeLog 
> entry format and make the wording read a little better than our usual svn log 
> informalities.
> 
> Thanks!
> 
> Troy
> 
> 
> 
> On 07/16/2013 05:15 AM, Troy A. Griffitts wrote:
>> OK, wrapping up final things for packaging up 1.7.0.
>> 
>> Jaak, I've normalized ListKey for you, so you should have your getCount 
>> const and added getElement const and non-const methods.  Other method names 
>> have been normalized with old names deprecated, so this will almost 
>> certainly cause deprecation warning in clients.
>> 
>> Does anyone have Ubuntu installed and can try building the swig bindings to 
>> confirm or deny they have the same problem as Peter?  This is using 
>> autotools.  Simply compile and install sword, then cd to 
>> bindings/swig/package and follow the short README.  Thank for any testing.
>> 
>> Troy
>> 
>> 
>> On 07/12/2013 12:27 AM, Peter von Kaehne wrote:
 Von: "Troy A. Griffitts" 
 Just to confirm, you're building and installing sword, then building the 
 bindings, yes?
 
>>> Yes
>>> 
>>> 
 pkg-config sword --libs
 
>>> peter@peter-ThinkPad-Twist:~$ pkg-config sword --libs
>>> -Wl,-Bsymbolic-functions -Wl,-z,relro -L/usr/local/lib -lsword -lz -lcurl 
>>> -lclucene -licui18n -licuuc -licudata -ldl -lm -licuio  
>>> 
>>> 
 and also when you build the python bindings, could you send me the build 
 output lines for the compile, 
 
>>> Please see attached build.log. The order of commands was
>>>  
>>> ./autogen.sh > build.log
>>> ./configure >>build.log
>>> make pythonswig >>build.log 2>&1
>>> make python_make >>build.log 2>&1
>>> 
>>> I added empty lines to separate the bits, but you will recognise the 
>>> relevant anyway.
>>> 
>>> Peter
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> sword-devel mailing list: 
>>> sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> 
>>> Instructions to unsubscribe/change your settings at above page
>>> 
>> 
>> 
>> 
>> ___
>> sword-devel mailing list: 
>> sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> 
>> Instructions to unsubscribe/change your settings at above page
>> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Forum software (was Re: mvnForum on HTTPS)

[Manfred Bergmann]

Am 22.10.2013 um 06:57 schrieb Raoul Snyman :

> 
> 
>> No one whose opinion is of any worth likes the forum software.
> 
> For what it's worth, we're using Vanilla for the OpenLP forums and it works 
> well for us. It also has a built in mobile theme which works quite well. 
> Having said that, it is written in PHP.
> 
> My 2c

I think we should define which features it should have (like voting would be 
nice), then we can look which software is suitable.
As much as I would have liked a Java based forum software there is none (at 
least none that came across our research that we did on new forum software a 
while back) that is really good.



Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Project "Free Scriptures" started

[Manfred Bergmann]

I can fully understand you.
I don't like git as well. Though I use Bazaar for all I'm developing. And yet, 
Bazaar is said to be dead or at least not much effort is put into it any 
longer. I'm still using it because I don't like git.
People who wish to contribute do contribute which ever VCS or DVCS there is.



Manfred

Am 26.02.2014 um 15:24 schrieb Troy A. Griffitts :

> Quickly, regarding DVCS, the argument to keeping SVN over a DVCS isn't that a 
> DVCS isn't 'better' in some ways or as Peter has suggested, wouldn't let us 
> maintain tight review of our code or that we simply don't ever want to change 
> anything. We eventually switched from CVS to SVN :) The reason the core 
> engine uses SVN is because it was the best and most popular choice 12 years 
> ago or so when we chose to use it, and basically I don't like git (yet). It's 
> pretty simple really. Other CrossWire projects use various choices for source 
> control. You can argue about the popularity of DVCS all you want, but the 
> truth is, there is not one ubiquitous opensource development choice today 
> like there was 12 years ago when we switched to SVN, so I'm not yet motivated 
> by popularity. And the counter argument is, if you like git, use it. Many 
> contributors to the core engine do. Sure you don't get absolutely all the 
> benefits like pull requests, but if you're concerned about that, attach your 
> patch to 
 the bug report. VCS is a choice, I'm typically conservative (if you haven't 
guessed) and haven't chosen to change the part of CrossWire I maintain. It is 
not keeping contributors from contributing.
> 
> Though as an aside, just from a personal query, how do you guys get Windows 
> and GUI Mac users to use git? I have at least 2 ancillary projects with SVN 
> repos on CrossWire's server where the users are not programmers, the command 
> line scares them, and they had no clue what a versioning system was before I 
> installed TortoiseSVN for them. They are HTML designers, flash programmers, 
> transcription editors, etc. It was a real task to get them to even begin to 
> use SVN, but the integration right into the OS helped (and we found some 
> Mac-y GUI thingy that was simple to use on OSX). I don't want to train them 
> about a stash as well. That's just one more obstacle. Are there really mature 
> GUI clients like these for the simple VC users. I know there are power GUIs. 
> That is not my question. I'm asking about tools integrated into the OS which 
> make VC simpler for the simple use?
> 
> On February 26, 2014 3:50:23 AM MST, Nic Carter  wrote:
> 
> Sorry for the top-post-reply, but here it is, so I guess I'm not all that 
> sorry ;)
> 
> The main bit of code you are referring to (parsing the HTML) is my code. 
> There is other code that parses the return from an FTP server, which is 
> ancient code. My code is (relatively) new, only about 3 years old? (I'm sure 
> you can look it up?)
> I agree it is completely a hack. I have had no time to fix it, but TBH, when 
> I do "fix" it I will be ripping curl out of PocketSword and using native iOS 
> stuff and will do all downloads that way. (Currently I download various bits 
> using the build-in SWORD methods & various bits using native iOS Obj-C 
> methods.)
> 
> I agree that switching to DVCS is a sane move & that sticking with SVN is 
> like shooting yourself in the foot. However, it seems like it's never going 
> to change, so I'm not going to fight that battle (insert comment about 
> loosing battles in order to win the war, and the "war" is producing excellent 
> software for iOS, which I'm actually currently loosing, but that has nothing 
> to do with CrossWire and everything to do with myself and lack of time right 
> now).
> 
> Backstory (I tell my students at school stories all the time and, sadly, they 
> always pay more attention to me in the classroom when I pre-empt what I'm 
> about to say with saying it's a story from my past): when I took over 
> PocketSword, there was an SVN repo for it. If you go look for it you'll see 
> that I never did a single commit to it. I pulled and forked & threw it in 
> Mercurial (doesn't matter what I threw it in except to say it was a DVCS). 
> The bonus tools I get by having it (freely) hosted on BitBucket are awesome 
> and I get notifications when people fork it & submit a pull-request.
> 
> FWIW, I have given up on submitting patches because they appear to get lost. 
> They may just be rejected, ignored or simply lost, but the appearance is that 
> they generally aren't worth doing. And when I'm asked to resubmit them I 
> generally don't bother. Using something where there are pull-requests, such 
> as Jaak has suggested, would mean that these aren't lost. Also, the 
> appearance will also be the reality because you can look up the request, see 
> if it's still open, rejected or commented up and then know where the request 
> is at in the merge process. But in this scenario I can be sure it's not lost 
> as l

[sword-devel] Can't build on OS X (undefined reference to UnicodeString)

[Manfred Bergmann]

Hi.

Anyone successfully built the current trunk on OS X (Mavericks)?
I get the above error. "UnicodeString" doesn't seem to be part of libicucore?



Manfred

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Can't build on OS X (undefined reference to UnicodeString)

[Manfred Bergmann]

Hmm, weird stuff.
UnicodeString seems to be in icucore. And I've got -licucore.
But it seems to be references not correctly:

Undefined symbols for architecture x86_64:
  "icu::UnicodeString::UnicodeString()", referenced from:
  sword::UTF8NFC::processText(sword::SWBuf&, sword::SWKey const*, 
sword::SWModule const*) in utf8nfc.o

Any ideas?

Manfred

Am 18.08.2014 um 17:34 schrieb Manfred Bergmann :

> Hi.
> 
> Anyone successfully built the current trunk on OS X (Mavericks)?
> I get the above error. "UnicodeString" doesn't seem to be part of libicucore?
> 
> 
> 
> Manfred
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Can't build on OS X (undefined reference to UnicodeString)

[Manfred Bergmann]

Building Sword from within Xcode after svn update.

But I'll try the following, initiate the configure procedure and see how the 
build goes, which defines are set, etc. Maybe I'm missing something.


Manfred


Am 19.08.2014 um 17:11 schrieb Greg Hellings :

> Is this while building Sword or BibleTime?
> 
> --Greg
> 
> 
> On Mon, Aug 18, 2014 at 12:16 PM, Manfred Bergmann  
> wrote:
> Hmm, weird stuff.
> UnicodeString seems to be in icucore. And I've got -licucore.
> But it seems to be references not correctly:
> 
> Undefined symbols for architecture x86_64:
>   "icu::UnicodeString::UnicodeString()", referenced from:
>   sword::UTF8NFC::processText(sword::SWBuf&, sword::SWKey const*, 
> sword::SWModule const*) in utf8nfc.o
> 
> Any ideas?
> 
> Manfred
> 
> Am 18.08.2014 um 17:34 schrieb Manfred Bergmann :
> 
> > Hi.
> >
> > Anyone successfully built the current trunk on OS X (Mavericks)?
> > I get the above error. "UnicodeString" doesn't seem to be part of 
> > libicucore?
> >
> >
> >
> > Manfred
> >
> > ___
> > sword-devel mailing list: sword-devel@crosswire.org
> > http://www.crosswire.org/mailman/listinfo/sword-devel
> > Instructions to unsubscribe/change your settings at above page
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Can't build on OS X (undefined reference to UnicodeString)

[Manfred Bergmann]

Hmm. Don't know this doesn't work.

tried cmake, called cmake/build-release.sh, got the following:
---
pacsaar:sword-trunk mbergmann$ cmake/build-release.sh
-- The CXX compiler identification is AppleClang 5.1.0.5030040
-- The C compiler identification is AppleClang 5.1.0.5030040
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Configuring your system to build libsword.
-- SWORD Version 1007003000
--
-- SEARCHING FOR SYTEM PACKAGES
-- System regex.h: Yes
--
-- CONFIGURING SOURCE LIST
-- ZLib: system /usr/lib/libz.dylib
-- bzip2: system /usr/lib/libbz2.dylib
-- xz: system /usr/lib/liblzma.dylib
-- cURL: system /usr/lib/libcurl.dylib and /usr/include
-- CLucene: no
-- PkgConfig: no
-- ICU: no
-- Regex.h: system /usr/include
-- Building Shared library.
-- Building Static library.
-- Setting SOVERSION to 1.7.3
-- cURL SFTP Support: No
-- Setting link libraries to 
/usr/lib/libz.dylib;/usr/lib/libbz2.dylib;/usr/lib/liblzma.dylib;/usr/lib/libcurl.dylib
--
-- CONFIGURING INSTALLATION DESTINATIONS
-- Destination: /opt/sword
--
-- CONFIGURING SWIG BINDINGS
-- Could NOT find SWIG (missing:  SWIG_EXECUTABLE SWIG_DIR)
CMake Error at bindings/swig/CMakeLists.txt:15 (MESSAGE):
  Swig: no


-- Configuring incomplete, errors occurred!
See also 
"/Users/mbergmann/Development/MySources/crosswire/sword-trunk/build/CMakeFiles/CMakeOutput.log".
make: *** No targets specified and no makefile found.  Stop.
---

No ICU seems to be found on the system. Though there is libicucore in /usr/lib/.

Also a standard configure, make I get the following error:
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../include -I../include 
-I/opt/sword/include -DUSE_AUTOTOOLS -DUNIX -Dunix -D__unix__ 
-DSWICU_DATA=\"/opt/sword/lib/sword/1.6.1_icu_2.1\" 
-DGLOBCONFPATH=\"/opt/sword/etc/sword.conf\" -D_FTPLIB_NO_COMPAT -O3 -D_ICU_ 
-ftemplate-depth-25 -DCURLAVAILABLE -DNO_VSNPRINTF -MT utilxml.lo -MD -MP -MF 
.deps/utilxml.Tpo -c ../src/utilfuns/utilxml.cpp -o utilxml.o >/dev/null 2>&1
mv -f .deps/utilxml.Tpo .deps/utilxml.Plo
make[1]: *** No rule to make target `../src/utilfuns/swunicod.cpp', needed by 
`swunicod.lo'.  Stop.
make: *** [all-recursive] Error 1


Now putting all that aside I can build the current trunk all right in Xcode 
when manually putting the stuff together. I'm doing that for a couple of years 
now in the objc binding.
But building with _ICU_ doesn't work anymore since I've done svn update (see 
error below).
I can run a version without ICU but I'm not exactly certain which other 
problems this might bring.

What about the BibleTime guys. Did they build all right on Mac with ICU?



Manfred


Am 19.08.2014 um 17:17 schrieb Manfred Bergmann :

> Building Sword from within Xcode after svn update.
> 
> But I'll try the following, initiate the configure procedure and see how the 
> build goes, which defines are set, etc. Maybe I'm missing something.
> 
> 
> Manfred
> 
> 
> Am 19.08.2014 um 17:11 schrieb Greg Hellings :
> 
>> Is this while building Sword or BibleTime?
>> 
>> --Greg
>> 
>> 
>> On Mon, Aug 18, 2014 at 12:16 PM, Manfred Bergmann  
>> wrote:
>> Hmm, weird stuff.
>> UnicodeString seems to be in icucore. And I've got -licucore.
>> But it seems to be references not correctly:
>> 
>> Undefined symbols for architecture x86_64:
>>  "icu::UnicodeString::UnicodeString()", referenced from:
>>  sword::UTF8NFC::processText(sword::SWBuf&, sword::SWKey const*, 
>> sword::SWModule const*) in utf8nfc.o
>> 
>> Any ideas?
>> 
>> Manfred
>> 
>> Am 18.08.2014 um 17:34 schrieb Manfred Bergmann :
>> 
>>> Hi.
>>> 
>>> Anyone successfully built the current trunk on OS X (Mavericks)?
>>> I get the above error. "UnicodeString" doesn't seem to be part of 
>>> libicucore?
>>> 
>>> 
>>> 
>>> Manfred
>>> 
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>> 
>> 
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>> 
&g

Re: [sword-devel] Can't build on OS X (undefined reference to UnicodeString)

[Manfred Bergmann]

If possible I don't want to install libraries (Homebrew, MacPorts, etc) used 
for building Sword which are not part of the stock OS X.

How can ICU be replaced with Qt?



Manfred

Am 19.08.2014 um 21:56 schrieb Greg Hellings :

> On my own system I get:
> 
> -- CLucene: yes /opt/local/lib/libclucene-core.dylib in /opt/local/include 
> and /opt/local/include;/opt/local/include
> 
> -- PkgConfig: yes
> 
> -- ICU: yes /opt/local/lib/libicuuc.dylib and /opt/local/include
> 
> 
> 
> I have installed them from MacPorts. I believe, however, that BibleTime 
> builds without them as Qt is used in place of ICU and CLucene is linked 
> directly into BibleTime for its custom search functionality. Obviously, feel 
> free to edit your local .sh script. Those are only given there for examples 
> of how to build with CMake for people who are not familiar with the system 
> much as usrinst.sh is more of a guideline. For instance, I doubt you're 
> looking to build the Python or Perl extensions.
> 
> 
> 
> --Greg
> 
> 
> 
> On Tue, Aug 19, 2014 at 12:28 PM, Manfred Bergmann  
> wrote:
> Hmm. Don't know this doesn't work.
> 
> tried cmake, called cmake/build-release.sh, got the following:
> ---
> pacsaar:sword-trunk mbergmann$ cmake/build-release.sh
> -- The CXX compiler identification is AppleClang 5.1.0.5030040
> -- The C compiler identification is AppleClang 5.1.0.5030040
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Configuring your system to build libsword.
> -- SWORD Version 1007003000
> --
> -- SEARCHING FOR SYTEM PACKAGES
> -- System regex.h: Yes
> --
> -- CONFIGURING SOURCE LIST
> -- ZLib: system /usr/lib/libz.dylib
> -- bzip2: system /usr/lib/libbz2.dylib
> -- xz: system /usr/lib/liblzma.dylib
> -- cURL: system /usr/lib/libcurl.dylib and /usr/include
> -- CLucene: no
> -- PkgConfig: no
> -- ICU: no
> -- Regex.h: system /usr/include
> -- Building Shared library.
> -- Building Static library.
> -- Setting SOVERSION to 1.7.3
> -- cURL SFTP Support: No
> -- Setting link libraries to 
> /usr/lib/libz.dylib;/usr/lib/libbz2.dylib;/usr/lib/liblzma.dylib;/usr/lib/libcurl.dylib
> --
> -- CONFIGURING INSTALLATION DESTINATIONS
> -- Destination: /opt/sword
> --
> -- CONFIGURING SWIG BINDINGS
> -- Could NOT find SWIG (missing:  SWIG_EXECUTABLE SWIG_DIR)
> CMake Error at bindings/swig/CMakeLists.txt:15 (MESSAGE):
>   Swig: no
> 
> 
> -- Configuring incomplete, errors occurred!
> See also 
> "/Users/mbergmann/Development/MySources/crosswire/sword-trunk/build/CMakeFiles/CMakeOutput.log".
> make: *** No targets specified and no makefile found.  Stop.
> ---
> 
> No ICU seems to be found on the system. Though there is libicucore in 
> /usr/lib/.
> 
> Also a standard configure, make I get the following error:
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../include -I../include 
> -I/opt/sword/include -DUSE_AUTOTOOLS -DUNIX -Dunix -D__unix__ 
> -DSWICU_DATA=\"/opt/sword/lib/sword/1.6.1_icu_2.1\" 
> -DGLOBCONFPATH=\"/opt/sword/etc/sword.conf\" -D_FTPLIB_NO_COMPAT -O3 -D_ICU_ 
> -ftemplate-depth-25 -DCURLAVAILABLE -DNO_VSNPRINTF -MT utilxml.lo -MD -MP -MF 
> .deps/utilxml.Tpo -c ../src/utilfuns/utilxml.cpp -o utilxml.o >/dev/null 2>&1
> mv -f .deps/utilxml.Tpo .deps/utilxml.Plo
> make[1]: *** No rule to make target `../src/utilfuns/swunicod.cpp', needed by 
> `swunicod.lo'.  Stop.
> make: *** [all-recursive] Error 1
> 
> 
> Now putting all that aside I can build the current trunk all right in Xcode 
> when manually putting the stuff together. I'm doing that for a couple of 
> years now in the objc binding.
> But building with _ICU_ doesn't work anymore since I've done svn update (see 
> error below).
> I can run a version without ICU but I'm not exactly certain which other 
> problems this might bring.
> 
> What about the BibleTime guys. Did they build all right on Mac with ICU?
> 
> 
> 
> Manfred
> 
> 
> Am 19.08.2014 um 17:17 schrieb Manfred Bergmann :
> 
> > Building Sword from within Xcode after svn update.
> >
> > But I'll try the following, initiate the configure procedure and see how 
> > the build goes, which defines are set, etc. Maybe I'm missing something.
> >
> >
> > Manfred
> >
> >
> > Am 19.08.2014 um 17:11 sch

Re: [sword-devel] Can't build on OS X (undefined reference to UnicodeString)

[Manfred Bergmann]

Thanks for the clarification.

Right, OS X didn't ship the headers for ICU, don't know exactly when that 
changed.
Currently, since 10.7 (AFAIR) it ships with ICU however only libicucore + the 
headers required for that.
The weird thing is that UnicodeString is present in the headers (unistr.h) also 
seems to be present in libicucore (when making an object dump of libicucore).
But still linking doesn't work.
I guess it needs some more digging.


Manfred



Am 20.08.2014 um 22:16 schrieb Greg Hellings :

> ICU is largely (exclusively?) used for transliteration within Sword. Qt 
> offers the same functionality (it has both its own built-in functionality for 
> that or it can be built on top of ICU). Since Qt already comes with the 
> functionality built in, BibleTime distributes its OS X binary without the 
> extra size of ICU.
> 
> As for wanting to build without MacPorts, you'd have to either find or 
> install the development headers for both of those libraries if you want that 
> support (In the distant past ICU was available on Mac but not development 
> headers for it, so MacPorts just installed headers for the system library 
> back then. Not sure what the story is now). If you have the headers and the 
> link library, you'll need to specify the proper search path. For ICU, you can 
> add the standard search directories to your CMake invocation using the 
> standard mechanism for appending library and header search paths. For CLucene 
> you can use that method, or specify CLUCENE_HOME in your environment 
> variables before invocation.
> 
> Another option entirely is to run CMake until it fails to find them, then 
> edit your CMakeCache.txt file to manually specify the path for the 
> appropriate CLUCENE and ICU variables, then rerun CMake to generate the build 
> files with the modified options.
> 
> There are lots of paths to get you where you're going, and I'm willing to 
> accept patches or pull requests (http://github.com/greg-hellings/sword.git) 
> to improve detection on OS X. The relevant files are 
> cmake/Find{ICU,CLucene}.cmake in the Sword source tree.
> 
> --Greg
> 
> 
> On Wed, Aug 20, 2014 at 2:57 PM, Manfred Bergmann  
> wrote:
> If possible I don't want to install libraries (Homebrew, MacPorts, etc) used 
> for building Sword which are not part of the stock OS X.
> 
> How can ICU be replaced with Qt?
> 
> 
> 
> Manfred
> 
> Am 19.08.2014 um 21:56 schrieb Greg Hellings :
> 
> > On my own system I get:
> >
> > -- CLucene: yes /opt/local/lib/libclucene-core.dylib in /opt/local/include 
> > and /opt/local/include;/opt/local/include
> >
> > -- PkgConfig: yes
> >
> > -- ICU: yes /opt/local/lib/libicuuc.dylib and /opt/local/include
> >
> >
> >
> > I have installed them from MacPorts. I believe, however, that BibleTime 
> > builds without them as Qt is used in place of ICU and CLucene is linked 
> > directly into BibleTime for its custom search functionality. Obviously, 
> > feel free to edit your local .sh script. Those are only given there for 
> > examples of how to build with CMake for people who are not familiar with 
> > the system much as usrinst.sh is more of a guideline. For instance, I doubt 
> > you're looking to build the Python or Perl extensions.
> >
> >
> >
> > --Greg
> >
> >
> >
> > On Tue, Aug 19, 2014 at 12:28 PM, Manfred Bergmann 
> >  wrote:
> > Hmm. Don't know this doesn't work.
> >
> > tried cmake, called cmake/build-release.sh, got the following:
> > ---
> > pacsaar:sword-trunk mbergmann$ cmake/build-release.sh
> > -- The CXX compiler identification is AppleClang 5.1.0.5030040
> > -- The C compiler identification is AppleClang 5.1.0.5030040
> > -- Check for working CXX compiler: /usr/bin/c++
> > -- Check for working CXX compiler: /usr/bin/c++ -- works
> > -- Detecting CXX compiler ABI info
> > -- Detecting CXX compiler ABI info - done
> > -- Check for working C compiler: /usr/bin/cc
> > -- Check for working C compiler: /usr/bin/cc -- works
> > -- Detecting C compiler ABI info
> > -- Detecting C compiler ABI info - done
> > -- Configuring your system to build libsword.
> > -- SWORD Version 1007003000
> > --
> > -- SEARCHING FOR SYTEM PACKAGES
> > -- System regex.h: Yes
> > --
> > -- CONFIGURING SOURCE LIST
> > -- ZLib: system /usr/lib/libz.dylib
> > -- bzip2: system /usr/lib/libbz2.dylib
> > -- xz: system /usr/lib/liblzma.dylib
> > -- cURL: system /usr/lib/libcurl.dylib and /usr/include
> > -- CLucene: no
> > -- PkgConfig: no
> > -- ICU: no
> > -- Re

Re: [sword-devel] Can't build on OS X (undefined reference to UnicodeString)

[Manfred Bergmann]

All right.
I've modified the Xcode project to build complete ICU from sources together 
with Sword. This seems to be working fine.


Manfred


Am 21.08.2014 um 08:30 schrieb Manfred Bergmann :

> Thanks for the clarification.
> 
> Right, OS X didn't ship the headers for ICU, don't know exactly when that 
> changed.
> Currently, since 10.7 (AFAIR) it ships with ICU however only libicucore + the 
> headers required for that.
> The weird thing is that UnicodeString is present in the headers (unistr.h) 
> also seems to be present in libicucore (when making an object dump of 
> libicucore).
> But still linking doesn't work.
> I guess it needs some more digging.
> 
> 
> Manfred
> 
> 
> 
> Am 20.08.2014 um 22:16 schrieb Greg Hellings :
> 
>> ICU is largely (exclusively?) used for transliteration within Sword. Qt 
>> offers the same functionality (it has both its own built-in functionality 
>> for that or it can be built on top of ICU). Since Qt already comes with the 
>> functionality built in, BibleTime distributes its OS X binary without the 
>> extra size of ICU.
>> 
>> As for wanting to build without MacPorts, you'd have to either find or 
>> install the development headers for both of those libraries if you want that 
>> support (In the distant past ICU was available on Mac but not development 
>> headers for it, so MacPorts just installed headers for the system library 
>> back then. Not sure what the story is now). If you have the headers and the 
>> link library, you'll need to specify the proper search path. For ICU, you 
>> can add the standard search directories to your CMake invocation using the 
>> standard mechanism for appending library and header search paths. For 
>> CLucene you can use that method, or specify CLUCENE_HOME in your environment 
>> variables before invocation.
>> 
>> Another option entirely is to run CMake until it fails to find them, then 
>> edit your CMakeCache.txt file to manually specify the path for the 
>> appropriate CLUCENE and ICU variables, then rerun CMake to generate the 
>> build files with the modified options.
>> 
>> There are lots of paths to get you where you're going, and I'm willing to 
>> accept patches or pull requests (http://github.com/greg-hellings/sword.git) 
>> to improve detection on OS X. The relevant files are 
>> cmake/Find{ICU,CLucene}.cmake in the Sword source tree.
>> 
>> --Greg
>> 
>> 
>> On Wed, Aug 20, 2014 at 2:57 PM, Manfred Bergmann  
>> wrote:
>> If possible I don't want to install libraries (Homebrew, MacPorts, etc) used 
>> for building Sword which are not part of the stock OS X.
>> 
>> How can ICU be replaced with Qt?
>> 
>> 
>> 
>> Manfred
>> 
>> Am 19.08.2014 um 21:56 schrieb Greg Hellings :
>> 
>>> On my own system I get:
>>> 
>>> -- CLucene: yes /opt/local/lib/libclucene-core.dylib in /opt/local/include 
>>> and /opt/local/include;/opt/local/include
>>> 
>>> -- PkgConfig: yes
>>> 
>>> -- ICU: yes /opt/local/lib/libicuuc.dylib and /opt/local/include
>>> 
>>> 
>>> 
>>> I have installed them from MacPorts. I believe, however, that BibleTime 
>>> builds without them as Qt is used in place of ICU and CLucene is linked 
>>> directly into BibleTime for its custom search functionality. Obviously, 
>>> feel free to edit your local .sh script. Those are only given there for 
>>> examples of how to build with CMake for people who are not familiar with 
>>> the system much as usrinst.sh is more of a guideline. For instance, I doubt 
>>> you're looking to build the Python or Perl extensions.
>>> 
>>> 
>>> 
>>> --Greg
>>> 
>>> 
>>> 
>>> On Tue, Aug 19, 2014 at 12:28 PM, Manfred Bergmann 
>>>  wrote:
>>> Hmm. Don't know this doesn't work.
>>> 
>>> tried cmake, called cmake/build-release.sh, got the following:
>>> ---
>>> pacsaar:sword-trunk mbergmann$ cmake/build-release.sh
>>> -- The CXX compiler identification is AppleClang 5.1.0.5030040
>>> -- The C compiler identification is AppleClang 5.1.0.5030040
>>> -- Check for working CXX compiler: /usr/bin/c++
>>> -- Check for working CXX compiler: /usr/bin/c++ -- works
>>> -- Detecting CXX compiler ABI info
>>> -- Detecting CXX compiler ABI info - done
>>> -- Check for working C compiler: /usr/bin/cc
>>> -- Check for working C compiler: /usr/bin/cc -- works
>>> -- Detect

[sword-devel] Problem with Intros

[Manfred Bergmann]

Hi.

Since once of the larger refactorings in SWORD my code for retrieving mod, 
book, chapter introductions doesn't work anymore.
So I've tried to adapt according to introtest.cpp.
But I can only get it to work for book introductions. Chapter and module 
doesn't work.
This basically is the code for module introductions:

- (NSString *)moduleIntro {
sword::VerseKey key;
key.setIntros(true);
key.setPersist(true);
key.setAutoNormalize(false);
[self setSwordKey:[SwordKey swordKeyWithSWKey:&key]];

key.setVerse(0);
key.setChapter(0);
key.setBook(0);
key.setTestament(0);

return [self renderedText];
}

But -renderedText or the SWORD function it calls: renderText() returns nothing.

Are there any known issues I have to be aware of?



Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Problem with Intros

[Manfred Bergmann]

Got it sorted, thanks.


Manfred


> Am 07.10.2014 um 02:17 schrieb Troy A. Griffitts :
> 
> Hi Manfred,
> 
> I am not sure if this has anything to do with your problems but the code 
> snippet you sent uses the old methodology of constructing a standalone 
> VerseKey and using setPersist, which has been deprecated due to av11n. When 
> you construct an instance of VerseKey standalone like that, the best we can 
> do is assume KJV versification scheme. It's best to either simply grab the 
> module's key with module.getKey(), which will already have v11n set 
> appropriately for the module and changing this key's position will adjust 
> your module location, as in the old persist methodology before, or else 
> construct and delete a new key if you need a separate one using 
> module.createKey().
> 
> Hope this helps some,
> 
> Troy
> 
> On October 6, 2014 3:41:48 PM CEST, Manfred Bergmann 
>  wrote:
> Hi.
> 
> Since once of the larger refactorings in SWORD my code for retrieving mod, 
> book, chapter introductions doesn't work anymore.
> So I've tried to adapt according to introtest.cpp.
> But I can only get it to work for book introductions. Chapter and module 
> doesn't work.
> This basically is the code for module introductions:
> 
> - (NSString *)moduleIntro {
> sword::VerseKey key;
> key.setIntros(true);
> key.setPersist(true);
> key.setAutoNormalize(false);
> [self setSwordKey:[SwordKey swordKeyWithSWKey:&key]];
> 
> key.setVerse(0);
> key.setChapter(0);
> key.setBook(0);
> key.setTestament(0);
> 
> return [self renderedText];
> }
> 
> But -renderedText or the SWORD function it calls: renderText() returns 
> nothing.
> 
> Are there any known issues I have to be aware of?
> 
> 
> 
> Manfred
> 
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Installed on a Mac, OS X 10.9.2!

[Manfred Bergmann]

Great stuff.

Just for your information:
Eloquent (former MacSword) comes with SWORD utilities bundled.
Just use "Install sword utilities" from the main menu under "Help".
After that the sword utils are available from command line.


Regards,
Manfred


> Am 05.12.2014 um 15:45 schrieb Shane Cooke :
> 
> Reposting this as it seemed to not have gone live last time.
> 
> On Apr 7, 2014, at 1:32 PM, Shane Cooke  wrote:
> 
>> Hello everyone.
>> 
>> Praise God, I have version 2893 of osis2mod installed and running on my late 
>> 2012 Retina Macbook Pro, 13”, OS X 10.9.2, 2.5 GHz Intel Core i5, 8 GB RAM! 
>> I can now generate modules right from my own Mac. 
>> 
>> I had been using a Sword installation on my Ubuntu 12.04 on a VM.  It wasn’t 
>> convenient to hop back and forth, using the soon to be discontinued Ubuntu 
>> One cloud storage to sync my source file on my Mac to the VM Ubuntu.
>> 
>> Well, I downloaded the source, and after the first run was notified I needed 
>> ICU. I decided to try to install ICU, despite previous apparent failures, by 
>> reading this blog:
>> http://themidnightprogrammer.blogspot.ca/2010/09/unicode-with-icu.html and 
>> he seemed to have done it,  it made me think, why not me? Part of his post 
>> noted  which was an error that also appeared when I first 
>> tried to install the Sword 1.7.2 engine  
>> “../include/utf8transliterator.h:41:10: fatal error: 'unicode/unistr.h' file 
>> not found” and he solved it by installed the ICU library, something I had 
>> previously tried to do, but failed (for what reason, I can’t recall). I 
>> followed the steps at 
>> http://freddyduarte.com/2013/08/14/installing-the-icu-libraries-and-the-php-intl-extension-on-a-mac/,
>>  and what do you know, ICU installed. I ran the sword installation again and 
>> voila, it installed. With some trepidation I then tried using osis2mod on my 
>> XML files, but it didn’t work (I was still seeing a strange paragraph number 
>> misplacement).
>> 
>> Then I realized that my osis2mod was still symlinked to the utilities in the 
>> the Eloquent app folders! So I looked to see where the new Sword utilities 
>> were installed and it was /us/bin/osis2mod.
>> 
>> So, in case anyone has previously tried to use the latest Sword engine 1.7.2 
>> utilities on their Mac and it didn’t install or work, give it another try. 
>> They are now! There must be something in the OS X 10.9.2 update which 
>> changed something for the better-I had previously tried installed while on 
>> 10.8.x, and the first 10.9 update)
>> 
>> Shane
>> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Installed on a Mac, OS X 10.9.2!

[Manfred Bergmann]

Great stuff.

Just for your information:
Eloquent (former MacSword) comes with compiled SWORD utilities bundled.
Just use "Install sword utilities" from the main menu under "Help".
After that the sword utils are available from command line.


Regards,
Manfred


> Am 05.12.2014 um 15:45 schrieb Shane Cooke :
> 
> Reposting this as it seemed to not have gone live last time.
> 
> On Apr 7, 2014, at 1:32 PM, Shane Cooke  wrote:
> 
>> Hello everyone.
>> 
>> Praise God, I have version 2893 of osis2mod installed and running on my late 
>> 2012 Retina Macbook Pro, 13”, OS X 10.9.2, 2.5 GHz Intel Core i5, 8 GB RAM! 
>> I can now generate modules right from my own Mac. 
>> 
>> I had been using a Sword installation on my Ubuntu 12.04 on a VM.  It wasn’t 
>> convenient to hop back and forth, using the soon to be discontinued Ubuntu 
>> One cloud storage to sync my source file on my Mac to the VM Ubuntu.
>> 
>> Well, I downloaded the source, and after the first run was notified I needed 
>> ICU. I decided to try to install ICU, despite previous apparent failures, by 
>> reading this blog:
>> http://themidnightprogrammer.blogspot.ca/2010/09/unicode-with-icu.html and 
>> he seemed to have done it,  it made me think, why not me? Part of his post 
>> noted  which was an error that also appeared when I first 
>> tried to install the Sword 1.7.2 engine  
>> “../include/utf8transliterator.h:41:10: fatal error: 'unicode/unistr.h' file 
>> not found” and he solved it by installed the ICU library, something I had 
>> previously tried to do, but failed (for what reason, I can’t recall). I 
>> followed the steps at 
>> http://freddyduarte.com/2013/08/14/installing-the-icu-libraries-and-the-php-intl-extension-on-a-mac/,
>>  and what do you know, ICU installed. I ran the sword installation again and 
>> voila, it installed. With some trepidation I then tried using osis2mod on my 
>> XML files, but it didn’t work (I was still seeing a strange paragraph number 
>> misplacement).
>> 
>> Then I realized that my osis2mod was still symlinked to the utilities in the 
>> the Eloquent app folders! So I looked to see where the new Sword utilities 
>> were installed and it was /us/bin/osis2mod.
>> 
>> So, in case anyone has previously tried to use the latest Sword engine 1.7.2 
>> utilities on their Mac and it didn’t install or work, give it another try. 
>> They are now! There must be something in the OS X 10.9.2 update which 
>> changed something for the better-I had previously tried installed while on 
>> 10.8.x, and the first 10.9 update)
>> 
>> Shane
>> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] how dead are the apps?

[Manfred Bergmann]

Eloquent sees minor updates. Last one was 2014 for OS X Yosemite compatibility 
and the latest SWORD lib.
The whole Objective-C SWORD wrapper has been updated in this process. Removed 
usage of deprecated methods and such.
Project management will be moved from Launchpad to GitHub in the near future.



Manfred


> Am 11.03.2015 um 17:57 schrieb Karl Kleinpaste :
> 
> It's been observed to me more than once recently that most of the apps have 
> gone stagnant, dead, no ongoing development.  How true is this assertion?
> 
> Personally I know about only Xiphos, which has been relatively busy other 
> than the last couple weeks, and PocketSword, whose 1.4.7 was released in late 
> January.
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] PocketSword's index generator

[Manfred Bergmann]

I’m on vacation next week.
If no one takes this until I’m back I’ll have a look at the problem.


Manfred


> Am 07.01.2016 um 12:35 schrieb David Haslam :
> 
> Michael just mentioned PocketSword's index generator.
> 
> The situation is more complicated than merely generating the downloadable
> search index for each module.
> cf. Peter already does that for new modules he builds for CrossWire.
> 
> Until and including iOS 8.x this install feature of PS worked OK.
> Installing a module was followed immediately by installing its index.
> For any module without an index, PS gave a graceful error message.
> 
> After iOS 9.0 was released, things changed.
> Installing a module with an index worked OK.
> For any module without an index, PS crashes while attempting to get the
> index.
> 
> Now with iOS 9.2, it's got much worse.
> Installing a module with an index, PS now crashes while attempting to get
> the index.
> This is a serious situation for one of our most popular front-ends.
> 
> Nic's proposal would be to update PS so that it can generate its own index
> for a module.
> This wasn't a good prospect for the earliest iOS devices, but it should be
> quite feasible and fast with the latest hardware.
> 
> The difficulty is that he doesn't have the free time he used to have, so PS
> software development is on hold.
> 
> His plea for volunteers seems to have been unheeded, but there's no harm in
> repeating it.
> 
> As an iPad Mini & iPhone user of PS, I'd welcome seeing some progress
> towards fixing this.
> 
> Best regards,
> 
> David
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/PocketSword-s-index-generator-tp4655633.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] 64 bit operating system support?

[Manfred Bergmann]

Hi David.

Eloquent is 64 bit (including libsword) for a long time actually.
PocketSword should compile to 64 bit all right.
I’ll check the other dependencies for PocketSword.


Manfred


> Am 11.01.2016 um 17:32 schrieb David Haslam :
> 
> Are there any libraries used by SWORD that get compiled into PocketSword for
> which as yet there is no support for 64 bit hardware platforms?
> 
> cf. From February this year, Apple will not accept any app updates that do
> not have 64 bit hardware support.
> 
> If the answer is "yes", are any of these libraries under our control?
> 
> Best regards,
> 
> David
> 
> 
> 
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/64-bit-operating-system-support-tp4655699.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Jesus red letter words

[Manfred Bergmann]

Hi.

Has there anything been changed regarding ‚Jesus red letter words‘?
I remember, this used to be a global option set as „Words of Christ in Red“ to 
swmgr->setGlobalOption(„Words of Christ in Red“, SW_ON) or similar.


Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Jesus red letter words

[Manfred Bergmann]

Well, I guess I mean has changed within the last two years or so.
I’ve updated Eloquent couple of months ago and it seems that this feature 
doesn’t work anymore where as it has worked two years ago.


Manfred

> Am 09.02.2016 um 18:13 schrieb Karl Kleinpaste :
> 
> On 02/09/2016 11:24 AM, Manfred Bergmann wrote:
>> Has there anything been changed regarding ‚Jesus red letter words‘?
> Just updated from svn and rebuilt. I see no change, it works as before.
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Unicode and the lack of

[Manfred Bergmann]

Hi.

Now many of the new modules are unicode encoded.
What if on a platform is no ICU available? Can SWORD deal with unicode texts 
itself, without ICU?
What are the compile options available for this?
What if a custom unicode library must be used on some platform. How would this 
be done?


Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Unicode and the lack of

[Manfred Bergmann]

What type of unicode are they?
I assume UTF-8. Are there modules having other types (chinese, japan, etc.)?


Manfred

> Am 09.02.2016 um 22:06 schrieb Peter von Kaehne :
> 
> Re the first question, i would treat any report re a new module not being 
> unicode as a bug report
> 
> On 9 February 2016 20:43:45 GMT+00:00, Manfred Bergmann 
>  wrote:
> Hi.
> 
> Now many of the new modules are unicode encoded.
> What if on a platform is no ICU available? Can SWORD deal with unicode texts 
> itself, without ICU?
> What are the compile options available for this?
> What if a custom unicode library must be used on some platform. How would 
> this be done?
> 
> 
> Manfred
> 
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Unicode and the lack of

[Manfred Bergmann]

> Am 09.02.2016 um 22:52 schrieb David Haslam :
> 
> Having ICU, but lacking a suitable Unicode font for aspects of a writing
> system is another thing.

AFAIK TrueType fonts are available.

> Having a source text supplied in a non-Unicode font is a challenge.
> Suppose [say] you had to convert Times Roman Armenian to Unicode?
> Reverse engineering the character mapping table, and scripting the
> conversion, yes, it’s feasible.

Na, I wouldn’t do that.
The amount of effort involved should be manageable.

> What platform does Manfred have in mind?  or is the answer still hush hush?
> 

Does „Amiga" still ring a bell?
I thought I’d open up another platform for the NG Amiga systems.
That is:
- MorphOS: http://www.morphos.de
- AmigaOS 4: http://www.amigaos.net
- AROS: https://en.wikipedia.org/wiki/AROS_Research_Operating_System

All have become pretty neat, considering the resources available. With a user 
base of 10s of thousands still.
There is also still new hardware for MorphOS and AmigaOS 4. Both are (still) 
PPC based.
MorphOS managed to support all the old PPC Apple hardware (iBook, PowerBook, G4 
and G5 desktop systems).

There is some Unicode support in either of them.
I’m currently figuring out what options there are for displaying text.
The SWORD library I’ve already compiled OK with a manually hacked makefile.



Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Jesus red letter words

[Manfred Bergmann]

OK, I got it figured.
For some reason I have used the XHtml Osis filter instead of the HtmlRef Osis 
filter.


Manfred

> Am 09.02.2016 um 18:36 schrieb Manfred Bergmann :
> 
> Well, I guess I mean has changed within the last two years or so.
> I’ve updated Eloquent couple of months ago and it seems that this feature 
> doesn’t work anymore where as it has worked two years ago.
> 
> 
> Manfred
> 
>> Am 09.02.2016 um 18:13 schrieb Karl Kleinpaste :
>> 
>> On 02/09/2016 11:24 AM, Manfred Bergmann wrote:
>>> Has there anything been changed regarding ‚Jesus red letter words‘?
>> Just updated from svn and rebuilt. I see no change, it works as before.
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] iOS apps will require secure HTTPS connections by 2017

[Manfred Bergmann]

Yep. That's the least if the problems, I fear.

Manfred

Von meinem iPhone gesendet

> Am 15.06.2016 um 14:51 schrieb Greg Hellings :
> 
> The library has support for HTTPS transports, now. I added that some
> time ago. So as long as the repositories you are connecting to with
> PocketSword support HTTPS, then it should be a trivial task to connect
> via that mechanism.
> 
> --Greg
> 
>> On Wed, Jun 15, 2016 at 8:08 AM, David Haslam  wrote:
>> Our iOS app developers will need to plan ahead to meet this requirement.
>> 
>> http://www.cnet.com/news/ios-apps-will-require-secure-https-connections-by-2017/
>> 
>> Heads up for Nic C and Manfred B in the context of PocketSword.
>> 
>> PocketSword urgently needs further help for program development.
>> 
>> If there are any iOS developers in this list who are not already involved,
>> please view this message as a further call for volunteers.
>> 
>> Head over to https://bitbucket.org/niccarter/pocketsword
>> 
>> Also http://twitter.com/pocketsword
>> 
>> Being only an iOS device user, not an Objective C programmer, my potential
>> contribution to the project is merely by way of testing and feedback.
>> 
>> Blessings,
>> 
>> David
>> 
>> 
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://sword-dev.350566.n4.nabble.com/iOS-apps-will-require-secure-HTTPS-connections-by-2017-tp4656339.html
>> Sent from the SWORD Dev mailing list archive at Nabble.com.
>> 
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Eloquent beta testers

[Manfred Bergmann]

Hi.

I’m working on a new release for Eloquent (2.6).
It addresses a couple of issues and includes UI adaption for the latest OS X 
versions.
The goal is also to put this version into the Mac App store. The code and the 
Xcode project as such is already prepared for dual build.

Are there OS X users out there willing to help in finding issues? There are 
probably a number of them.

The project is now hosted on GitHub:
https://github.com/mdbergmann/Eloquent

A 2.6 beta release can also be found there.


Cheers,
Manfred


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Apple Plans To Boot Orphaned Apps From its App Store

[Manfred Bergmann]

Hi.

Yeah, I got my second child last year in August. And he kind of makes us all 
busy (and happy of course). :)

The app has to be build against the latest SDK version. Anything else Apple 
won’t approve.
However, it’s still possible to make the app run on iOS 7 for example. The only 
limit is which API functions are available.
OK, going further back with compatibility may not work as well due to API 
functions being marked deprecated.

What causes problems, and that is what we see now, is that an app that was 
build against iOS 6 SDK, doesn’t necessarily work properly on the latest 
versions of iOS.
So we’ll have to build against the latest SDK and do lots of testing and 
adaptions to the latest development patterns (like GCD - Grand Central 
Dispatching, etc.).

In the mobile world there is a lot of happening. That is good and bad, but at 
least it requires to constantly keep the apps up-to-date.



Manfred


> Am 08.09.2016 um 09:24 schrieb David Haslam :
> 
> Hi Tim,
> 
> Thanks for contacting me.
> 
> Please understand that in terms of skills and acquired knowledge, I'm not an 
> iOS app developer, nor do I have a Mac platform. cf. I imagine it would be 
> much harder to develop and test iOS apps from a Windows PC.
> 
> It's great that you've got involved. We know why Nic is busy. I think 
> Mannfred Bergman is also pretty tied up in terms of spare time since he 
> became a father.
> 
> After iOS 9 was released was the time when issues began to arise with 
> installing search index. It's only got worse with subsequent versions. Also 
> from what Nic has written before, maintaining backwards compatibility is 
> desirable, as one cannot assume that every PS user keeps his device up to 
> date. Sometimes that's an impossible goal to implement though.
> 
> cf. The same goes for modules in a different way. One cannot assume that 
> every user has the most recent version of an installed module. This is why 
> Nic also maintained a separate search index for older module releases.
> 
> Also since we gained access to the huge Bible modules repository at 
> eBible.org, none of these yet have an installable index, AFAIK. NB. Updates 
> to such modules can occur quite often, as Michael improves things with Haiola.
> 
> Nic had hoped to move away from downloading and installing the search index 
> for each module, and implement the creation of the search index using the 
> device itself. This was beyond the capability of the earliest iOS devices in 
> terms of speed and efficiency. That no longer is the case. cf. AndBible has 
> always done the index creation within the Android device. All the more recent 
> types of iPhone and iPad should be able to do this speedily if someone can 
> write the code.
> 
> btw. Another unpublicised issue is why installing a module in Maintainer Mode 
> along with its Lucene search index as created using Xiphos, and included 
> within the same Zip archive usually leaves the index as not found by PS. 
> According to Nic, an index made using Xiphos should be compatible with PS. 
> I've only seen the compatibility demonstrated for two private Bible modules 
> that I made for my own personal use, one of which was the English Revised 
> Version of 1885.
> 
> I have TestFlight installed in my iPad Mini. It's a long time since I last 
> used it to try out prerelease of PS for Nic.
> 
> Final thought.  When he was active in PS development, Nic used Twitter as the 
> main support communications channel. I'm not a tweeter.
> 
> Best regards,
> 
> David Haslam
> 
> 
> 
> On Thursday, 8 September 2016, Timothy Shen-McCullough  
> wrote:
> Hi,
>  I’m trying to reach David Haslam. I’m interested in helping out 
> programming for the PocketSword iPhone app. and have actually written in the 
> past to Nic so I know from his reply that he’s quite busy. I’m also very 
> concerned about the development of PocketSword. Months ago due to changes in 
> the iOS code or ?? the app stopped being able to download searching modules. 
> I posted the bug on the tracker. I eventually wrote a fixed version months 
> ago and emailed Nic about it. This is the version I use now. The version that 
> I edited though was before a contributor named Mannfred worked on the code. 
> So, I don’t think that my version can be used due to it being pre-ARC support 
> and pre-64 bit compliance and etc. I have however been looking at his newer 
> version. I am slowly working my way through it. I can’t compile the code and 
> it seems that more updates are required to the code, but I don’t feel 
> comfortable going into details as I’m not sure exactly where this email is 
> going. I’ve never used a newsgroup before and so I don’t want to violate any 
> rules or etc. without knowing it.
> 
> -Tim
> 
> 
> --
> Best regards,
> 
> David F. Haslam



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.cr

Re: [sword-devel] Apple Plans To Boot Orphaned Apps From its App Store

[Manfred Bergmann]

Hi Tim.

> Am 10.09.2016 um 04:26 schrieb TS :
> 
> I have used many of the modules from the Xiphos project, but I do not believe 
> that I have used the actual program itself. I didn’t know that it could 
> create search indexes. I may run a virtual instance of Linux just to try out 
> Xiphos. 
> 

Eloquent can create indices of modules that can be used in PocketSword.
At least that was the case where I have added this functionality.
And you wouldn’t need to set up a Linux.
The latest version can  be found here:
https://github.com/mdbergmann/Eloquent/releases


Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Apple Plans To Boot Orphaned Apps From its App Store

[Manfred Bergmann]

Hi.

Yeah, it’s a challenge.
I have developed a few iOS and Android apps for the company I work for.
A high amount of maintenance work is required to keep the apps up-to-date.

I had worked on the code and integrated ARC and 64bit. It did build and almost 
all seemed OK.
AFAIR the problem was that some of the code just didn’t run properly on the new 
iOS runtime when built against the latest SDK.
So that’s we’re we were stuck.


Manfred



> Am 10.09.2016 um 05:21 schrieb TS :
> 
> Hi,
> 
> Congratulations on your second child  :)
> 
> Thank you also for writing about the submittal and backwards compatibility of 
> PocketSword. So much in iOS alone keeps changing…ARC, 64bit, and etc., I 
> wonder how people keep up? but yes, at least it requires to constantly keep 
> the apps up-to-date. :)
> 
> -Tim
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] What is the lowest version of iOS to be currently supported in PocketSword?

[Manfred Bergmann]

Hi Tim.

I thought actually I had updated libcurl (build for 64bit and latest versions).
Also I had updated MBProgressHUD to the latest version.
I can’t remember for which OS version libcurl was build.

I would not go back to 5.1 with compatibility as overall this means a higher 
work on maintenance.
And you can’t use any new features of the OS.

For anyone still using iOS 5.1 the current PocketSword app should still work?


Manfred


> Am 20.09.2016 um 22:59 schrieb TS :
> 
> I've been going through the code and making fixes, and in the process XCode 
> has warned me that libcurl is for version iOS 6 and higher and also I've 
> discovered that MBProgressHUD was also written for iOS 6 and higher. It seems 
> that the external frameworks were updated from the previous release of 
> PocketSword. So, is the lowest version supported iOS 6 now? or is it still 
> 5.1.1 and I can ignore the warnings? If 5.1.1 should still be supported, do 
> all of the newer frameworks still work with this version of the iOS or does 
> compatibility need to be tested between iOS ver. 5.1.1 and the newer 
> frameworks (and workarounds be implemented if need be)?
> 
> - Timothy
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Announcing Sword++

[Manfred Bergmann]

If you want a nice new, clean and convenient API, why don’t you build one on 
top of the current API?


Manfred


> Am 28.09.2016 um 16:49 schrieb Konstantin Maslyuk :
> 
> Thank you, Jaak, for your good starting. I still hope that your knowledge in 
> C++ development and Troy's experience in Sword development would unite in 
> development of next major libsword iteration (reword libsword2). I think you 
> both have many great ideas for that. 
> 
> I also expect from libsword2 more convenient api. Since we managed to work 
> with existing, it leave many questions and unobvious things (SWMgr that is 
> actually iterator, Upper/Lower bound that do not say where is module 
> beginning for new ones). A lot of code in Sword is hard to maintain, only few 
> people knows how it actually works. It is not look like good C++ code. And it 
> will never evolve if we will focus on elder devices.
> 
> So I suggest to not extinguish any kind of energy here but to support. It is 
> so little here.
> 
> As for me, i like elder devices, and at this moment they are in my priority.
> 
> 
> Blessings.
> От: Jaak Ristioja 
> Отправлено: ‎25.‎09.‎2016 21:56
> Кому: SWORD Developers' Collaboration Forum 
> Тема: [sword-devel] Announcing Sword++
> 
> Hello!
> 
> Sometime in May this year my efforts to improve the Sword library as the
> backend for BibleTime led me to create branch or fork of the Sword
> codebase, which I eventually called Sword++. The main goals for this
> were to (with respect to BibleTime development) improve the API, build
> system and overall code quality, modernize, and to try to fix any bugs I
> find when refactoring and reviewing the code. With experience as a C++
> backend engineer and being no Sword expert, my refactoring effort also
> serves the purpose of educating myself about Sword and its internals.
> While I'm just starting out and have barely touched the amount of work
> that needs to be done, I've already accumulated over 200 new commits to
> the Sword++ repository so far. So this seems to be a more-or-less
> reasonable time to publicly announce my publicly before the situation
> gets too awkward.
> 
> Before I proceed, I want to emphasize that none of this is meant to
> split or even stir up anything negative in the community. However,
> Sword++ is an initiative to stop and reverse the current bit-rot; it is
> more of a rescue effort and not a rebel event. Due to the sheer amount
> of work that needs to and can be done to reach these goals, it is
> evidently impractical for me to push and wait for every such change to
> work its way through the issue tracker and/or sword-devel and reach SVN
> trunk. To work around this costly threshold for contributing to the
> Sword library, Sword++ is now here.
> 
> Sword++ is not officially related to CrossWire. The code currently lives
> at https://github.com/swordxx/swordxx and as the initiator I'm currently
> idling alone on the #sword++ channel on FreeNode IRC. Feel free to
> contribute, file bug reports, pull requests etc. Also feel free to
> cherry-pick or merge any fixes back to Sword. I don't think I will (or
> have time to) flood sword-devel with emails about every bug (or
> technical, design or architectural issue) I find. I will try to notify
> about most severe security issues. Follow the git log if you're interested.
> 
> The code is in sync with enhancements in the Sword SVN trunk and for now
> I'll try to keep it that way, although I've changed the layout of source
> files etc extensively which makes merging harder. I'm currently
> targeting standard C++14, POSIX and Linux, with everything else having
> lower priority due to Sword++ currently having only one active
> developer. I've also dropped all the language bindings (which I don't
> intend on maintaining together with the Sword++ master branch), a bunch
> of legacy and unused code, tools and utilities etc. MSVC project files
> and autotools were dropped from the build system, which is now only
> based on CMake. Ftplib support was also dropped, cURL, CLucene 2, bzip2,
> xz and zlib are now unconditionally required by Sword++. There are also
> some API changes so switching from Sword to Sword++ requires some
> effort. See the git log for details and more.
> 
> There is a lot of uncertainty because this is just the beginning of the
> process. Currently Sword++ must be considered unstable. I haven't tested
> it much at runtime. I'm mostly doing code review, modernizing, fixing
> bugs and compiler warnings and static analysis warnings,
> despaghettification and deduplication of code, improving the API etc etc
> etc. Sword++ will try to stay compatible with existing Sword modules,
> but will probably propose amendments to the file formats and download
> protocols (e.g. to get rid of parsing the potentially fragile HTML of
> directory listings generated by the Apache HTTP server).
> 
> I hold in high respect both CrossWire and all who made

Re: [sword-devel] swld.cpp at line 111 - is this a bug?

[Manfred Bergmann]

> Am 12.10.2016 um 01:34 schrieb Jaak Ristioja :
> 
> Hi!
> 
> On 12.10.2016 01:08, TS wrote:
>> Xcode was warning me that in PocketSword's Sword framework, swld.cpp at
>> line 111 with
>> 
>> "delete buf;"
>> may be wrong and it should perhaps be
>> 
>> "delete[] buf;"
>> instead. Is this correct? I looked at the code and I think Xcode is
>> correct in that the variable is an array and needs the brackets to
>> delete properly.
> 
> Yes, Xcode has it correct. It should be `delete[] buf;`. This was also
> fixed in Sword++ in March.

Despite the warning, would but not be deleted completely?


Manfred

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] swld.cpp at line 111 - is this a bug?

[Manfred Bergmann]

> Am 12.10.2016 um 08:57 schrieb Jaak Ristioja :
> 
> On 12.10.2016 09:37, Manfred Bergmann wrote:
>>> On 12.10.2016 01:08, TS wrote:
>>>> Xcode was warning me that in PocketSword's Sword framework, swld.cpp at
>>>> line 111 with
>>>> 
>>>> "delete buf;"
>>>> may be wrong and it should perhaps be
>>>> 
>>>> "delete[] buf;"
>>>> instead. Is this correct? I looked at the code and I think Xcode is
>>>> correct in that the variable is an array and needs the brackets to
>>>> delete properly.
>>> 
>>> Yes, Xcode has it correct. It should be `delete[] buf;`. This was also
>>> fixed in Sword++ in March.
>> 
>> Despite the warning, would but not be deleted completely?
> 
> It is undefined behavior, as stated by §3.7.4.2.3 in C++11. However, the
> C++ draft at https://github.com/cplusplus/draft doesn't have this
> wording since e51a2152 [1] for some reason.
> 

Yeah, don’t get me wrong. It should be corrected.
But is it indeed a memory leak or does the runtime still collect and destroy 
all array elements?
Depends on the runtime probably.


Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] swld.cpp at line 111 - is this a bug?

[Manfred Bergmann]

Hi.


> Am 13.10.2016 um 20:28 schrieb TS :
> 
>  Thank you all for your replies and confirmation. I will use the delete 
> with the square brackets.

I would suggest to stick to the upstream code as much as possible. That means, 
have someone fix this in the main SWORD repo and pull a copy of it for PS.
Otherwise it’s hard to reason what exactly is used in PS.


Manfred


> 
>  I also had already looked at the Sword++ code and saw that it had the 
> brackets which suggested to me that it was correct that something should be 
> there.
>  I had some confusion because in Apple's ObjC framework, they also have a 
> "new" function and Xcode was directing me to it when I was asking it to show 
> me where "new" came.(The "new" use to created the variable which needed 
> delete[]). As a result, I was uncertain as to how Xcode was implementing the 
> code. I think though that it may be an error for Xcode to be directing me to 
> the Cocoa definition of "new" since the file has the "cpp" file extension and 
> so Xcode should know to expect c++ code. Also, "new" isn't being applied here 
> in the code as a proper objective-c method call (I don't think?), so I'm 
> thinking that it's being compiled as the "new" from the c++ library.
> 
> Thanks again,
> -TS
> 
> On Oct 12, 2016, at 05:16 AM, DM Smith  wrote:
> 
>> 
>>> On Oct 12, 2016, at 3:22 AM, Jaak Ristioja >> <mailto:j...@ristioja.ee>> wrote:
>>> On 12.10.2016 10:02, Manfred Bergmann wrote:
>>>> 
>>>>> Am 12.10.2016 um 08:57 schrieb Jaak Ristioja >>>> <mailto:j...@ristioja.ee>>:
>>>>> 
>>>>> On 12.10.2016 09:37, Manfred Bergmann wrote:
>>>>>>> On 12.10.2016 01:08, TS wrote:
>>>>>>>> Xcode was warning me that in PocketSword's Sword framework, swld.cpp at
>>>>>>>> line 111 with
>>>>>>>> 
>>>>>>>> "delete buf;"
>>>>>>>> may be wrong and it should perhaps be
>>>>>>>> 
>>>>>>>> "delete[] buf;"
>>>>>>>> instead. Is this correct? I looked at the code and I think Xcode is
>>>>>>>> correct in that the variable is an array and needs the brackets to
>>>>>>>> delete properly.
>>>>>>> 
>>>>>>> Yes, Xcode has it correct. It should be `delete[] buf;`. This was also
>>>>>>> fixed in Sword++ in March.
>>>>>> 
>>>>>> Despite the warning, would but not be deleted completely?
>>>>> 
>>>>> It is undefined behavior, as stated by §3.7.4.2.3 in C++11. However, the
>>>>> C++ draft at https://github.com/cplusplus/draft 
>>>>> <https://github.com/cplusplus/draft> doesn't have this
>>>>> wording since e51a2152 [1] for some reason.
>>>>> 
>>>> 
>>>> Yeah, don’t get me wrong. It should be corrected.
>>>> But is it indeed a memory leak or does the runtime still collect and 
>>>> destroy all array elements?
>>>> Depends on the runtime probably.
>>> 
>>> It is undefined behavior (see http://stackoverflow.com/q/2397984/3919155 
>>> <http://stackoverflow.com/q/2397984/3919155>
>>> ). So as far as the C++ standard is concerned, this might yield
>>> different behavior depending on the toolchain, the runtime, the
>>> environment or the phase of the moon... There are also no defined bounds
>>> to what may happen: it may leak, crash, hang, corrupt memory, whatever...
>>> 
>>> J
>>> 
>> 
>> If I recall delete without the brackets will delete the object. That is the 
>> array. When called with the brackets will call delete on the elements in the 
>> array. In some cases the semantic difference does not matter, such as an 
>> array of char or int. I didn’t look at the code to see if it mattered here.
>> 
>> DM
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org 
>> <mailto:sword-devel@crosswire.org>
>> http://www.crosswire.org/mailman/listinfo/sword-devel 
>> <http://www.crosswire.org/mailman/listinfo/sword-devel>
>> Instructions to unsubscribe/change your settings at above page
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How do you make the Sword framework work in 64bit mode? (My compiler is giving me hundreds of warnings.)

[Manfred Bergmann]

I’m also having tons of warnings when compiling SWORD in Xcode for 64 bit.
The precision warnings can be ignored IMO. But due to the sheer number of 
warnings it’s very hard to detect warnings that shouldn’t be ignored.

Btw: there is a Objective-C wrapper for the SWORD library under bindings/objc 
which I maintain and use in Eloquent.
AFAIK some form of the wrapper in used in PS.
It would be great if efforts could be shared in using only one codebase.



Manfred


> Am 13.10.2016 um 22:30 schrieb TS :
> 
>  So, Xcode gives me hundreds of warnings when I try to build for 64 bit 
> mode. I've also tried searching the mailing list so I see that some people 
> earlier in the year may be have seen the same warnings (for PocketSword), so 
> I think I better understand why I've seen that some of the libraries were 
> updated(I don't know if all were updated or ?). However, I'm still getting 
> errors and some of it is in the Sword framework. My impression so far of 
> what's going on is that Xcode is telling me is that there are datatypes which 
> are not being converted properly. I think this is happening due to things 
> like "int" and "long" not occupying the same amount of space or something 
> like they use to do in 32 bit and so need a casting in order to be converted 
> properly?
>  An example is listkey.h at line 147 in which "index" is a "long", but 
> then setToElement is for an "int".
>  Another is swbuf.h at line 448 "...const { unsigned int psize = 
> strlen(postfix); ..." where Xcode warns that there's a loss of precision. 
> That an unsigned long is converting to an unsigned int. I think that unsigned 
> long occupies 64 bits when run in 64 bit mode, but the int stays in 32 bits 
> when run in 64 bit mode.
> I have compared the Sword framework that it's using against the last 
> stable one and there's doesn't seem to be changes to address the issues I'm 
> seeing.
> Any suggestions on how to proceed?
> 
> -TS
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How do you make the Sword framework work in 64bit mode? (My compiler is giving me hundreds of warnings.)

[Manfred Bergmann]

> Am 19.10.2016 um 10:00 schrieb Peter Von Kaehne :
> 
>> Von: "Peter Von Kaehne" 
>> I am compiling on Debian testing in 64 bit mode with no warnings, using the 
>> standard flags. 
> 
> As I understand xcode uses gcc just as we use on Linux. Is it possible that 

Per default Xcode uses the C compiler of LLVM.
That may be the reason why we have other warnings.
Usually, and that may< be the same for PocketSword and Eloquent, the SWORD 
sources are compiled as part of the parent project.
That means there is no makefile involved.


Manfred


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Older iOS devices and future PocketSword releases?

[Manfred Bergmann]

32 + 64 bit is not a problem.
Xcode will usually build multiple architectures and combine them in one app.

The issue is API compatibility.
When building with the latest Xcode the oldest iOS target version is iOS 8.
That means any new build of PocketSword will probably not be able to target 
anything below that.


Manfred

> Am 22.10.2016 um 12:29 schrieb David Haslam :
> 
> Assuming that the programmers eventually succeed in getting the 64bit version
> of PocketSword compiled without errors, may I remind developers that there
> are still many users who, like me, have older iOS devices that are only
> 32bit. 
> 
> We don't want to abandon PocketSword users that have older machines. It's
> impossible to install a 64bit app into a 32bit device.
> 
> Some app developers therefore have two editions of each app, one for 64bit
> devices and one for 32bit devices. For example, the iOS app called VPN
> Unlimited from KeepSolid.
> 
> Not being an iOS app developer, I don't know if there is an alternative way
> to resolve this, other than having two separate apps. 
> 
> (I've seen Windows apps that detect whether the processor is 32bit or 64bit,
> and which proceed with the installation accordingly. There are further
> complications in 64bit PCs, as the updater ideally needs to detect any
> previous 32bit version of the program, and offer to first delete that before
> installing the 64bit version.)
> 
> Please remember this as the project proceeds. Thanks.
> 
> 
> Best regards,
> 
> David
> 
> 
> 
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/Older-iOS-devices-and-future-PocketSword-releases-tp4656505.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Older iOS devices and future PocketSword releases?

[Manfred Bergmann]

I believe that Apple ships multiple versions of the runtime (or parts of it 
which are bridged to the latest) in iOS and the app is executed in the highest 
version possible.
That depends on which SDK version is was compiled against.
They are always introducing a lot of stuff in new runtime/SDK versions. One of 
which, as you mentioned, is the restriction to not allow UI updates from the 
main thread.
Then they changed the way how this is to handled by introducing GCD (Grand 
Central Dispatch). Now, since apps that were compiled against a SDK version 
that doesn’t support GCD it must be run in a different runtime.
It seems that the older runtimes or the bridge code is not always totally 
accurate, or at least older apps may run into problems when new devices.
That’s possibly the reason why Apple is eager to reduce the maintenance for all 
this and to enforce re-compiling apps against newer SDKs.

Xcode 8 will only allow a deployment target of >= iOS 8.0.
If you want to still be able to deploy to iOS 7.1 then you shouldn’t use Xcode 
8.


Manfred


> Am 25.10.2016 um 09:22 schrieb TS :
> 
> Regarding the API compatibility, I’m still not sure if I fully understand it. 
> My current understanding is that each iPhone/iPad will interpret the app’s 
> code based on the iOS it’s running. So, if a lot of code is completely 
> deprecated and replaced in a new SDK (or API) release, you still need to keep 
> the old code so that the iPhone/iPad’s still running on the older iOS’s will 
> still work correctly. I think that when things like that happen the code 
> should be commented or explained or etc. so that the code is organized and 
> not confusing or hard to follow or etc. 
>  On a related note though, updated API’s seem to also allow for changes 
> to functions (methods) behind the scenes. I think that the current iTunes 
> version of PocketSword can’t download certain search indices due to an issue 
> like this. The methods for downloading data from the internet were completely 
> reworked and somewhere along the line, it was no longer allowed to block the 
> main thread which I think may be at least part of the reason why it stopped 
> working.
> 
> Here’s some results of some experiments I did running PocketSword 1.4.7 on an 
> older version of Xcode:
> With Xcode 6.2 using iPhone 5s as the model to simulate on and using a base 
> SDK of iOS 8.2 for every test.
> Simulating on an iPhone running iOS 7.1  YES - search index downloads
> Simulating on an iPhone running iOS 8.1  NO - will not download search index
> Simulating on an iPhone running iOS 8.2  NO - will not download search index
> 
> Also, on a related note, I saw some articles online which say that Apple 
> allows developers to offer older versions of their app through the store so 
> that devices running an older iOS can download those versions which are still 
> compatible. Here’s a stack overflow link which has some pictures:
> http://stackoverflow.com/questions/19147885/app-store-managing-availability-of-your-apps-previous-versions
> 
> Hope this helps,
> TS
> 
> 
> 
>> On Oct 22, 2016, at 3:50 AM, Manfred Bergmann  
>> wrote:
>> 
>> 32 + 64 bit is not a problem.
>> Xcode will usually build multiple architectures and combine them in one app.
>> 
>> The issue is API compatibility.
>> When building with the latest Xcode the oldest iOS target version is iOS 8.
>> That means any new build of PocketSword will probably not be able to target 
>> anything below that.
>> 
>> 
>> Manfred
>> 
>>> Am 22.10.2016 um 12:29 schrieb David Haslam :
>>> 
>>> Assuming that the programmers eventually succeed in getting the 64bit 
>>> version
>>> of PocketSword compiled without errors, may I remind developers that there
>>> are still many users who, like me, have older iOS devices that are only
>>> 32bit. 
>>> 
>>> We don't want to abandon PocketSword users that have older machines. It's
>>> impossible to install a 64bit app into a 32bit device.
>>> 
>>> Some app developers therefore have two editions of each app, one for 64bit
>>> devices and one for 32bit devices. For example, the iOS app called VPN
>>> Unlimited from KeepSolid.
>>> 
>>> Not being an iOS app developer, I don't know if there is an alternative way
>>> to resolve this, other than having two separate apps. 
>>> 
>>> (I've seen Windows apps that detect whether the processor is 32bit or 64bit,
>>> and which proceed with the installation accordingly. There are further
>>> complications in 64bit PCs, as the updater ideally needs to detect any
>>> previous 32bit version of th

Re: [sword-devel] How do you make the Sword framework work in 64bit mode? (My compiler is giving me hundreds of warnings.)

[Manfred Bergmann]

Hi TS.

They were the same once. Both started out in the MacSword app.
Then they were extracted from MacSword and made it’s own project which found 
the home in the bindings/objc folder of the SWORD source tree.
Nic decided to not use the files bindings/objc but his own fork.
And myself maintained the wrapper files there for Eloquent.
Since then it has diverged quite a bit as you have found out. Though many of 
the classes and the much of the API should still be similar.
Nevertheless I would like to see some common effort in maintaining those 
„official“ Objective-C bindings.



Manfred

> Am 03.11.2016 um 04:19 schrieb TS :
> 
> Hi Manfred,
>   I took a look at these wrapper files in the bindings/objc for Revision 
> 3441 of the SWORD framework. Using FileMerge I compared it to what seems to 
> be the wrapper files in PocketSword. Upon at least a simple comparison, there 
> seems to be some similarities, but also some huge differences as well. 
> FileMerge highlighted quite a lot of things. I remember that at least one 
> header file has the same name, but other than that the header seems to have 
> completely different code. It was a surprise.
>   
> -TS
> 
>> On Oct 14, 2016, at 4:15 AM, Manfred Bergmann  
>> wrote:
>> 
>> I’m also having tons of warnings when compiling SWORD in Xcode for 64 bit.
>> The precision warnings can be ignored IMO. But due to the sheer number of 
>> warnings it’s very hard to detect warnings that shouldn’t be ignored.
>> 
>> Btw: there is a Objective-C wrapper for the SWORD library under 
>> bindings/objc which I maintain and use in Eloquent.
>> AFAIK some form of the wrapper in used in PS.
>> It would be great if efforts could be shared in using only one codebase.
>> 
>> 
>> 
>> Manfred
>> 
>> 
>>> Am 13.10.2016 um 22:30 schrieb TS :
>>> 
>>>  So, Xcode gives me hundreds of warnings when I try to build for 64 bit 
>>> mode. I've also tried searching the mailing list so I see that some people 
>>> earlier in the year may be have seen the same warnings (for PocketSword), 
>>> so I think I better understand why I've seen that some of the libraries 
>>> were updated(I don't know if all were updated or ?). However, I'm still 
>>> getting errors and some of it is in the Sword framework. My impression so 
>>> far of what's going on is that Xcode is telling me is that there are 
>>> datatypes which are not being converted properly. I think this is happening 
>>> due to things like "int" and "long" not occupying the same amount of space 
>>> or something like they use to do in 32 bit and so need a casting in order 
>>> to be converted properly?
>>>  An example is listkey.h at line 147 in which "index" is a "long", but 
>>> then setToElement is for an "int".
>>>  Another is swbuf.h at line 448 "...const { unsigned int psize = 
>>> strlen(postfix); ..." where Xcode warns that there's a loss of precision. 
>>> That an unsigned long is converting to an unsigned int. I think that 
>>> unsigned long occupies 64 bits when run in 64 bit mode, but the int stays 
>>> in 32 bits when run in 64 bit mode.
>>> I have compared the Sword framework that it's using against the last 
>>> stable one and there's doesn't seem to be changes to address the issues I'm 
>>> seeing.
>>> Any suggestions on how to proceed?
>>> 
>>> -TS
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>> 
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Does Eloquent use only the core library of SWORD or more than that? e.g. the clucene library, zlib, etc.

[Manfred Bergmann]

Hi TS.

It uses the zlib which is bundled with SWORD.
It also uses clucene, but only to create index files to be used for PocketSword.
Otherwise Eloquent uses Apple Spotlight for indexing and searching.

The framework is built from the project and sources in bindings/objc.
Btw: iOS from version 8 can also use frameworks now.


Manfred


> Am 24.11.2016 um 01:30 schrieb TS :
> 
> Does Eloquent use only the core library of SWORD or more than that? e.g. the 
> clucene library, zlib, etc. 
> 
> I took a look at its source code, but the Sword code is pre-bundled into what 
> Apple defines as a framework for Xcode and this seems to hide away everything 
> except for header files. 
> 
> I'm interested in finding this info out because of the recent 64 bit issues 
> I've written earlier about and because, for example, it seems that nether the 
> clucene code nor zlib code is being maintained anymore. Since I've been 
> trying to work on the PocketSword code, I'm curious as to how its desktop 
> counterpart handles tasks. Does it use the same libraries of code that comes 
> with the SWORD code or if not, which ones are used and which ones are not?
> 
> zlib btw is somewhat odd on iOS. It is not plug and play. A file needs to be 
> modified in zlib folder in order for it to work. However, when 
> troubleshooting the issues on the internet, a lot of people with similar 
> problems got replies back that zlib already comes in one of Apple's 
> libraries. 
> 
> -TS
> 
> --Sent from phone--
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Are the code libraries which come with the SWORD library such as clucene, zlib, etc. the same as from the source or are they modified?

[Manfred Bergmann]

Hi TS.

> Am 24.11.2016 um 03:25 schrieb TS :
> 
> There's also the Clucene library. It's riddled right now with 64 bit 
> warnings. Besides it being bad practice based on my understanding to leave it 
> that way or use it that way for a long period of time, there's also a 
> significant difference between iOS apps and most other software. That is, 
> that the apps can only go through Apple's App Store and must conform to 
> Apple's requirements else risk being denied. Apple's already made it clear 
> that apps should be 64bit compatible. So, if PocketSword was submitted with 
> the current Clucene library I do not know how they would take it. It seems to 
> me that it may be skating on thin ice with them. If they saw the numerous 
> 64bit warnings, I do not think it would be unreasonable for them to question 
> why the app was submitted that way. I posted a list last month or so of all 
> the 64 bit warnings  Xcode gave me including ones in the clucene files. A lot 
> of the code creating the warnings was fixed as a result, but only I think in 
> Sword files. I think

I think Apple does not have all the compiler warning details when you submit 
the app. They only have your compiled binary code and they run tests for which 
API you use.
Usually they reject apps that use private API. But that’s about it.
If the app crashes because of long to int conversion it’s not really their 
problem. The app will get bad feedback and that’s it.
I believe some newer version of Clucene is used in the latest SWORD? Not sure.
Core Spotlight is only available in iOS 9, so not really an option?


Manfred


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Possible problem in unorm_normalize?

[Manfred Bergmann]

Hi.

Someone reported that he didn’t see any text output for module SBLGNT v1.3.1

Interestingly text is shows when greek accents option is enabled.

I have pinpointed where the text disappears:
utf8nfkd.cpp
char UTF8NFKD::processText(SWBuf &text, const SWKey *key, const SWModule 
*module)
//compatability decomposition
ulen = unorm_normalize(source, ulen, UNORM_NFKD, 0, target, len, &err);

This sets ulen to 0 and the next call basically removes the text.

Can someone reproduce this? Maybe it’s because of ICU on macOS?

I use SVN version r3443.



Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] GerSch2000

[Manfred Bergmann]

Hi.

I just got a query for the German Schlachter2000 bible module.
AFAIR is was in the making. Has it ever be released?



Manfred

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Fwd: GerSch2000

[Manfred Bergmann]

I think this mail never received the list.
So here it is again.


Manfred


> Anfang der weitergeleiteten Nachricht:
> 
> Von: Manfred Bergmann 
> Betreff: GerSch2000
> Datum: 9. Januar 2017 um 08:58:59 MEZ
> An: SWORD Developers' Collaboration Forum 
> 
> Hi.
> 
> I just got a query for the German Schlachter2000 bible module.
> AFAIR is was in the making. Has it ever be released?
> 
> 
> 
> Manfred

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] PocketSword can speak!

[Manfred Bergmann]

I think that’s a standard functionality on iOS and macOS.
You can have the system speak any text anywhere, almost.


Manfred


> Am 10.02.2017 um 12:43 schrieb David Haslam :
> 
> After all these years of owning an iPad Mini & iPhone 5, I just found out
> that iOS devices do have TTS capability.
> 
> So I just updated this section of our wiki page.
> 
> https://crosswire.org/wiki/Choosing_a_SWORD_program#Other
> 
> Quite a number of languages are supported when you select Voice.
> I've just installed the English (UK) voice called Daniel (Enhanced) 188 MB,
> but the default voice was quite acceptable.
> 
> Of course, being quite general, you can't make it exclude the verse numbers
> in the selected passage.
> 
> Best regards,
> 
> David
> 
> 
> 
> 
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/PocketSword-can-speak-tp4656672.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] In Windows command shell, diatheke search is restricted to ASCII for the query key!

[Manfred Bergmann]

This wchar in Windows is UTF-16.
https://msdn.microsoft.com/en-us/library/windows/desktop/ff381407(v=vs.85).aspx


Manfred


> Am 02.03.2017 um 19:51 schrieb Greg Hellings :
> 
> My only thought is that Windows doesn't use UTF-8 internally (it uses 
> UTF-16), while Sword assumes and demands UTF-8. Perhaps diatheke just blindly 
> consumes its input as UTF-8, and goes along its merry way?
> 
> --Greg
> 
> On Thu, Mar 2, 2017 at 11:48 AM, David Haslam  wrote:
> Greg,
> 
> It was worth a test inside cygwin and the result was also a fail:
> 
> $ xiphos/diatheke -b KJV -s regex -k Æneas
> Verses containing "ãneas"-- none (KJV)
> 
> I tried it with this too, and that fare no better:
> 
> $ utils/diatheke -b KJV -s phrase -k Æneas
> Verses containing "ãneas"-- none (KJV)
> 
> That's my link to where the utils from our ftpmirror had been downloaded.
> 
> Is it even worth installing PowerShell ?
> 
> I'm beginning to think that diatheke.exe was never designed to cope with
> non-ASCII searches.
> 
> 
> David
> 
> 
> 
> 
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/In-Windows-command-shell-diatheke-search-is-restricted-to-ASCII-for-the-query-key-tp4656866p4656876.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Objective-C wrapper and new release

[Manfred Bergmann]

Hi.

For being able to bind the Objective-C wrapper to a certain release of SWORD I 
have created a GitHub repo for it.
https://github.com/mdbergmann/ObjCSword

Also, for anyone interested I have released a new beta version of Eloquent, 
also at GitHub.
https://github.com/mdbergmann/Eloquent/releases


Happy easter and God bless,

Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Process entry attributes.

[Manfred Bergmann]

Hello.

For a while now the pre-verse rendering doesn’t work anymore in Eloquent.
So I thought I’d have a look.
Has there something been changed?
I’m doing this to retrieve the attribute:
getEntryAttributes()["Heading"]["Preverse"]["0"].c_str()

But that is empty.
Are there any pre-requisites?
What about this setProcessEntryAttributes(BOOL) function?



Manfred


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Process entry attributes.

[Manfred Bergmann]

Hi David.

Thanks for your links.
But the question for is not how to model a pre-verse title in a module but how 
to retrieve that using the SWORD API.
I haven’t found any code examples and I can’t remember where the code was from 
that I have in ObjCSword. Possibly from old MacSword.
So it’s likely something has changed in the API in the meantime.

If anyone can point me to a source that can act as an example I’d be happy.



Manfred



> Am 16.04.2017 um 21:04 schrieb David Haslam :
> 
> I'm not a code developer, I merely help to keep the wiki up to date.
> 
> These pages may help:
> 
> https://www.crosswire.org/wiki/Sword_library_versions
> 
> https://crosswire.org/wiki/OSIS_pre-verse_titles
> 
> https://crosswire.org/wiki/OSIS_Bibles#Marking_pre-verse_titles
> 
> Best regards,
> 
> David
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/Process-entry-attributes-tp4657074p4657075.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Eloquent for iPad

[Manfred Bergmann]

Pretty much, yes.
I still have the source code here but had no time to follow up on it.
This project can be deleted in Jira.


Manfred


> Am 11.05.2017 um 14:27 schrieb David Haslam :
> 
> While visiting the tracker, I just spotted that back in 2011, Manfred had
> been working on a new front-end called *Eloquent for iPad*.
> 
> http://tracker.crosswire.org/projects/ELOIPAD/
> 
> Was this project completely abandonned after PocketSword was first released?
> 
> Best regards,
> 
> David
> 
> 
> 
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/Eloquent-for-iPad-tp4657149.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Verse ranges and linkage information

[Manfred Bergmann]

Hi.

Not entirely sure I’m understanding correctly.

In Eloquent I’m maintaining a map/dictionary per ’show verses’ request where 
basically only the reference is stored in some normalized way.
So I can check on that dictionary and see whether a certain verse was already 
added to the output buffer.



Manfred


> Am 22.05.2017 um 08:56 schrieb ref...@gmx.net:
> 
> How do front-ends know not to double/triple/quadruple...a verse range? 
> Diatheke fails at that right now and I would like to fix this. 
> 
> Peter
> 
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] WoC red letter text problem

[Manfred Bergmann]

Appears to be OK in Eloquent.
Tried ESV2001 and ESV2011 each version 1.0.2.


Manfred

> Am 02.07.2017 um 18:02 schrieb Karl Kleinpaste :
> 
> On 07/02/2017 11:45 AM, DM Smith wrote:
>> Would someone check some of the other SWORD frontends, please?
> Looks normal in Xiphos.  Using latest ("903") Sword.
> 
> http://karl.kleinpaste.org/.../xiphos-esv2011-luke-4-18.gif
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] News page - we are still alive.... Other website stuff

[Manfred Bergmann]

Hi.

> Am 19.08.2017 um 16:57 schrieb Peter von Kaehne :
> 
> I have updated a lot of news bits on the our news page. Maybe we will soon 
> add the release of 1.8...?
> 
> Eloquent - this has surely been updated a few times since - who is 
> responsible for the news admin there?

I don’t know.
Can I mail someone when there are news?



Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] SWORD 1.8.0RC5 Final RC

[Manfred Bergmann]

OK.
I believe those bindings are kind of developed in their own pace.
So I had create a GitHub project for them which target a certain SWORD version.

Maybe we can remove them alltogether from the SWORD sources.


Manfred

> Am 26.11.2017 um 11:27 schrieb Troy A. Griffitts :
> 
> I've moved the objc
> dependencies out of the bundle replace with a Makefile which downloads
> them and unpacks them from crosswire.org .

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] SWORD 1.8.0RC5 Final RC

[Manfred Bergmann]

> Am 27.11.2017 um 14:02 schrieb Cyrille :
> 
> 
> 
> Le 27/11/2017 à 10:58, Manfred Bergmann a écrit :
>> OK.
>> I believe those bindings are kind of developed in their own pace.
>> So I had create a GitHub project for them which target a certain SWORD 
>> version.
> Is Github the good choice? Gitlab is completely open-source, Github no.

Why is it not a good choice? Just because it’s not open-source?


Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] canon.bible.xml and alternate versification questions

[Manfred Bergmann]

Hi Vince.

> Am 17.02.2018 um 20:10 schrieb Vince LaRue :
> 
> In my use of Eloquent, I've noticed that the book names always display in 
> English, not in the language of the module. Is this a limitation of the 
> front-end itself, or due to a lack of a canon.bible.xml file as part of the 
> configuration?

The book names should be localized. In my Eloquent they are in german.
However, it does not depend on the language of the module but on the language 
of the operating system.


Manfred



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Bishop for Android and iOS / JavaScript bindings

[Manfred Bergmann]

TestFlight not an option to make it installable for testers?



Manfred


> Am 04.03.2018 um 16:36 schrieb DM Smith :
> 
> David,
> I’ve installed it on my iPhone 6. Will do my iPad 2 later today.
> 
> I don’t think the iOS app store supports 32-bit only any more, but they might 
> allow dual 32/64. I have an old iPhone 5 on which I can test. I don’t have a 
> 32-bit iPad like yours.
> 
> It’s not something you’ll be willing to do. I’m describing the process that I 
> went through in case others are interested.
> 
> To install it, you need to be running MacOS. This is possible to do in a VM 
> on Windows or Linux. I think that’s what Troy does. I have a Mac, so it isn’t 
> a difficulty for me.
> 
> Within MacOS you have to install XCode from the Mac App Store and in XCode 
> open Window->Devices and Simulators with your iOS device attached to your 
> “Mac". Make the window wide enough to see the entire device “Identifier”. 
> Right click on that, select copy and send that to Troy.
> 
> Troy will have to add that to the list of authorized devices and rebuild 
> Bishop.ipa.
> 
> Download that ipa and in the same window, click + under INSTALLED APPS, 
> navigate to that download and “Open” it. This will install it to your device.
> 
> Later, I think it’ll be possible to build from source in XCode.
> 
> DM
> 
>> On Mar 4, 2018, at 3:26 AM, David Haslam  wrote:
>> 
>> Hi Troy,
>> 
>> I've been ignoring Bishop on the grounds that I'd only ever seen it 
>> described as being an Android OS app.
>> 
>> This is the first time I've seen it mentioned in connection with iOS devices.
>> 
>> My devices are iPhone 5 and iPad Mini. My wife has an iPhone 5S and iPad 
>> Mini.
>> 
>> Even so, unless it's in the Apple iStore, only users who jailbreak could 
>> install it?  AFAICT, it's not there.
>> 
>> btw.  Is it a 64-bit app ?
>> 
>> Best regards,
>> 
>> David
>> 
>> Sent from ProtonMail Mobile
>> 
>> 
>> On Sat, Mar 3, 2018 at 21:53, Troy A. Griffitts  wrote:
>>> Thanks for the feedback Michael,
>>> 
>>> I have added a new menu choice:
>>> 
>>> [ Settings ]
>>> 
>>>   -   Font Size  +
>>> 
>>> It seems to work well on both iOS and Android.  Please let me know if it 
>>> makes the app more usable for you.  The update should now be available for 
>>> your phone.
>>> 
>>> Thank you again for taking the time to provide valuable feedback.
>>> 
>>> Troy
>>> 
>>> 
>>> 
>>> On 03/03/2018 04:05 AM, Michael H wrote: 
 I already had AndBible installed.  
 
 Bishop installed and recognized all the modules (at least 20+ bibles, i 
 haven't confirmed "ALL") that AndBible has present. I haven't attempted 
 any more module installs after installing Bishop, either from AndBible or 
 Bishop. 
 
 The text is small on my Samsung Galaxy On5. Not horribly unreadably small, 
 but small for me to use for any length of time. I don't see settings to 
 adjust that, so I haven't spent much time on it. I can and will test more 
 if you have something specific.. But this isn't ready for my eyes yet. 
 Very promising tho. :-) Based on the images in the store screen, I would 
 be using it more if the text had size adjustment.  
 
 
 On Fri, Mar 2, 2018 at 11:05 PM, Troy A. Griffitts  
 wrote: 
 I've had 2 instances of problems running the app.  One was a report from a 
 user here, and another was trying to install the app on my TV.  In both 
 cases, the app showed a blank gray screen after install and and startup.
 
 I have had debug versions on all my devices here at some point, so I'm not 
 a very good clean test case.  Has anyone had any luck installing and 
 getting the basic set of modules running? Or any problems?  Thanks for any 
 feedback.
 
 https://play.google.com/store/apps/details?id=org.crosswire.bishop
 
 Troy
 
 On 03/02/2018 01:31 PM, David Haslam wrote: 
> Suggestion: 
> Please edit https://wiki.crosswire.org/Frontends:Bishop 
> and add these details. 
> 
> Best regards, 
> 
> David 
> 
> Sent with ProtonMail Secure Email. 
> 
> ‐‐‐ Original Message ‐‐‐ 
> On 1 March 2018 2:26 AM, Troy A. Griffitts  wrote: 
> 
>> Dear team, 
>> You all know we've been working on Cordova bindings for SWORD for quite 
>> some time now.  We now have a simple reader written in JavaScript which 
>> will run unchanged on both Android and iOS.Bishop includes an InstallMgr 
>> to auto-discover remote installation sources and let a user install 
>> SWORD content. 
>> I've kept the development code name "Bishop", my favorite android (from 
>> Aliens) and almost appropriate for a Bible app :)  I've also tacked on 
>> our boring moniker from our Windows app, "Bishop: The SWORD Project for 
>> Android".  Long name but should get more search hits. 
>> Basically, Bishop's UI has 2 basic modes: 
>> 
>> Reader: which simply shows 1 chapte

Re: [sword-devel] Bishop for Android and iOS 1.0.4

[Manfred Bergmann]

Just as additional information:

Deployments via TestFlight are equal to deployments via the Apple App Store.
Whereas AdHoc builds are not.

I had several cases where AdHoc builds worked but when downloaded from the 
Store the app would crash.
When apps are downloaded via the App store Apple actually pushes optimized 
binaries to your device.
This technique is called „App Thinning“.
Sometimes it can happen that this process strips something away which is 
required and makes the app crash.
To avoid that iOS apps should be tested using TestFlight.



Manfred


> I believe I've added the Apple UDIDs for everyone who sent them.  I
> haven't looked into TestFlight yet, but thank you for the suggestion.
> 

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Crash in VersificationMgr::System::getBookCount (SWORD 1.8.1)

[Manfred Bergmann]

Hi.

I’ve received one report where SWORD seems to crash on the above method for 
modules:
- eBible.org/Biblical Texts/rusSYN1876eb (version 3.32)
- IBT/Commentaries/BARC (version 1.0)
- IBT/Commentaries/NGSB (version 1.0)

I could reproduce that for rusSYN1876eb where in the code „p“ is NULL and hence 
the crash.

Can that be reproduced in Xiphos or other frontends?



Regards,
Manfred


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Possibility of using Slack

[Manfred Bergmann]

Hi.

We use Slack at work.
It's better than Skype nowadays, since the Skype version is hardly 
usable anymore, at least on Mac.


However, it has a few problems:
- it needs vast amount of RAM (> 700MB) on my Mac.
- Notifications of channel activity are not sent sometimes
- there is a 'number-of-messages' limit. Don't know the size out of my 
head. Basically it means that you have to move to a paid scheme if you 
don't want to loose messages.

Which kind of disqualifies it for Crosswire.



Manfred


Daniel Bennett schrieb am 28.06.18 um 21:29:

Hi everyone,

Just wanted to float the possibility of creating a Slack group for sword 
development?


If you haven’t seen Slack, it’s a group messaging service, which gives 
you control over notifications.


It’s private, secure, and requires minimal personal information.

Hit reply and let me (or the group) know your thoughts!

Here’s a screenshot below:
Image result for slack screenshots

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Please pass the PocketSword pumpkin.

[Manfred Bergmann]

Hi.

I think, if you plan on putting this to the Apple Store, then you either need a 
new ‚bundle Id‘ which you have control over, or have Nic push it to the store 
under the current ‚bundle Id‘.


Manfred


> Am 12.03.2019 um 08:37 schrieb David Haslam :
> 
> Thanks Michael,
> 
> Surely there’s no need to “rebrand it”?
> What prompted this mention?
> What did you actually mean by ‘rebrand’?
> 
> Was the trial compile done with the latest release of the SWORD API source 
> code?
> cf.  PS 1.4.8 did not support SWORD 1.8 so modules using one of the 3 new 
> v11ns for French Bibles ended up with offsets. 
> 
> Best regards,
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
> On Tue, Mar 12, 2019 at 06:22, Michael Johnson  wrote:
>> Hello, Nic & all.
>> 
>> I downloaded the PocketSword source code, updated it so that it would 
>> compile with the current XCode and run on an iPhone XR simulator, and 
>> started fixing some of its issues. This seemed to me to be preferable to 
>> seeing that program fade away due to not keeping up with the ever-changing 
>> environment. I'm pretty sure I can come up with an update that is helpful.
>> 
>> Nic, I understand that you are busy with other priorities, now, but please 
>> know that many of us greatly appreciate the work you have done in the past 
>> on PocketSword. I don't know how much involvement you would like in the 
>> transition. It can be pretty much as little or as much as you like. If I 
>> just fork the code and rebrand it, then you really don't need to do anything 
>> at all.
>> 
>> Your thoughts?
>> 
>> -- 
>> Aloha,
>> Michael Johnson
>> PO BOX 881143 • PUKALANI HI 96788-1143 • USA
>> mljohnson.org • Phone: +1 808-333-6921 • Skype: kahunapule
>> 
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] PocketSword progress

[Manfred Bergmann]

Hi.

When Nic started developing this I had suggested to collaborate in the SWORD 
backend both used in MacSword/Eloquent and PocketSword.
Unfortunately PocketSword then used its own baked backend with modifications to 
the MacSword code (at the time).

I’m still thinking that there should be collaboration and a common code base.
Eloquent uses the ObjCSword code as in here:
https://github.com/mdbergmann/ObjCSword

I’m not sure about the changes, there might be a lot.
But moving forward it should be considered.



Manfred


> Am 13.03.2019 um 04:03 schrieb Michael Johnson :
> 
> So far, on my copy of PocketSword I have:
> 
>  * Updated to the latest Sword engine.
>  * Switched from downloading indexes to generating them. (The time consumed 
> is not unreasonable for this, now. Apple doesn't support the old, slow 
> hardware that made this seem necessary in the first place.)
> 
> The list of stuff left to do is long, but at the top of the list is trying to 
> correct the problem with the Crosswire Main repository not working. The index 
> generation also needs some UI feedback. (It currently just appears to be 
> frozen while generating the index, which is not very satisfactory.) Once I 
> get those things done, and maybe a couple other tweaks, it might be worth an 
> incremental release...
> 
> -- 
> signature
> 
> Aloha,
> */Michael Johnson/**
> PO BOX 881143 • PUKALANI HI 96788-1143*• USA
> mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
> kahunapule
> 
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] PocketSword progress

[Manfred Bergmann]

> Am 13.03.2019 um 09:46 schrieb Troy A. Griffitts :
> 
> 
> In addition, there are new Swift bindings which work against that Universal 
> binary for both MacOS and iOS. They were done for the Cordova plugin, but 
> most of the code could be used standalone if anyone is interested in writing 
> a Swift UI.
> 
> http://crosswire.org/svn/sword/trunk/bindings/cordova/org.crosswire.sword.cordova.SWORD/src/ios/

That might be a nice option to checkout instead of the Objective-C wrapper 
classes.



Manfred


> 
> 
> 
> On March 13, 2019 12:44:08 AM MST, Manfred Bergmann  
> wrote:
> Hi.
> 
> When Nic started developing this I had suggested to collaborate in the SWORD 
> backend both used in MacSword/Eloquent and PocketSword.
> Unfortunately PocketSword then used its own baked backend with modifications 
> to the MacSword code (at the time).
> 
> I’m still thinking that there should be collaboration and a common code base.
> Eloquent uses the ObjCSword code as in here:
> https://github.com/mdbergmann/ObjCSword
> 
> I’m not sure about the changes, there might be a lot.
> But moving forward it should be considered.
> 
> 
> 
> Manfred
> 
> 
> Am 13.03.2019 um 04:03 schrieb Michael Johnson :
> 
> So far, on my copy of PocketSword I have:
> 
>  * Updated to the latest Sword engine.
>  * Switched from downloading indexes to generating them. (The time consumed 
> is not unreasonable for this, now. Apple doesn't support the old, slow 
> hardware that made this seem necessary in the first place.)
> 
> The list of stuff left to do is long, but at the top of the list is trying to 
> correct the problem with the Crosswire Main repository not working. The index 
> generation also needs some UI feedback. (It currently just appears to be 
> frozen while generating the index, which is not very satisfactory.) Once I 
> get those things done, and maybe a couple other tweaks, it might be worth an 
> incremental release...
> 
> -- 
> signature
> 
> Aloha,
> */Michael Johnson/**
> PO BOX 881143 • PUKALANI HI 96788-1143*• USA
> mljohnson.org <http://mljohnson.org> • Phone: +1 808-333-6921 • Skype: 
> kahunapule
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Happy Easter - Bible download statistics

[Manfred Bergmann]

Hi.

That’s great.
Can we do stats per front end? I’d be interested in that. I believe some front 
ends that use FTP do use a certain login name or so?


Manfred


> Am 21.04.2019 um 10:38 schrieb Peter von Kaehne :
> 
> Happy Easter to all!
> 
> I attach some download statistics which I run yesterday on the old
> server instance. We have shipped from that server alone 1.4 million
> modules last year. These stats do not cover the new server, nor Xiphos
> nor eBible, nor IBT. It would be great if we could do some collective
> accounting at one point.
> 
> There are some interesting things hiding in there.
> 
> Some small Pacific islands must have the whole population downloading
> the text. 2000+ for the Kapingamarangi language.
> 
> Inside Europe apart from English Czech is I think the most downloaded
> language.
> 
> Afghans have downloaded 2.5k Bibles.
> 
> Peter
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] IBT repository - module contents structure

[Manfred Bergmann]

FYI: I had added this feature, to create a default CLucene index, to Eloquent 
to make the index accessible to PocketSword via Module Maintainer mode.
But I do not know to which extend the index works or not works.



Manfred


> Am 28.04.2019 um 15:00 schrieb David Haslam :
> 
> It’s possible, but for unknown causes, the Xiphos produced search index only 
> works in PS for a few modules. 
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
> On Sun, Apr 28, 2019 at 13:12, Johan  wrote:
>> David,
>> 
>> Is it possible to create an index (e.g. in Xiphos) and transfer that (as 
>> part of the other bible and dictionary modules in zipped format) via Module 
>> Maintainer Mode in PocketSword?
>> 
>> Best regards,
>> 
>> Johan Marais
>> 
>> From: David Haslam  
>> Sent: Sunday, 28 April 2019 10:20
>> To: sword-devel mailing list 
>> Subject: [sword-devel] IBT repository - module contents structure
>> 
>>  
>> If you install a Bible module from the IBT repository, the module is 
>> structured such that it also already contains the Lucene search index. 
>> 
>>  
>> Try installing the Chechen module CHE. 
>> 
>>  
>> Thus for PocketSword there is no further need to go to the CrossWire server 
>> to look for a separately maintained unofficially supported installable 
>> search index for each module released. 
>> 
>>  
>> After CHE was installed, the search index existed, even though PS did not 
>> indicate that it had looked for and found a search index from CrossWire. 
>> 
>>  
>> At least that’s what appears to be the case for some IBT modules. But I may 
>> be mistaken. 
>> 
>>  
>> Some other IBT Bible modules are without a built-in search index and the 
>> index is not found at CrossWire either. 
>> 
>>  
>> Might this approach be a useful method to imitate for CrossWire modules?
>> 
>>  
>> Either way, the possibility to harmonise the support for PocketSword search 
>> clearly has more than one potential interim workaround. 
>> 
>>  
>> Best regards,
>> 
>>  
>> David
>> 
>>  
>> Sent from ProtonMail Mobile
>> 
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] MacOS 10.15 and Eloquent ?

[Manfred Bergmann]

Hi.

Eloquent is 64 bit for a few years already. So no problem there.
But It’s not impossible that minor tweaks are necessary once macOS 10.15 is out.



Manfred


> Am 01.06.2019 um 19:30 schrieb David Haslam :
> 
> I’m not a Mac user, but this report caught my attention.
> 
> macOS 10.15 Will Kill 32-Bit Apps: What You Should Do
> https://www.laptopmag.com/articles/macos-10-15-warning-32-bit-apps
> 
> How will this affect Eloquent?
> 
> Best regards,
> 
> David
> 
> Sent from ProtonMail Mobile
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Sword on Mac

[Manfred Bergmann]

Hi Tobias.

You can have a look at the Xcode project here:
https://github.com/mdbergmann/ObjCSword

As a sub-target the Sword library is built as .dylib.



Manfred


> Am 06.06.2019 um 07:56 schrieb Tobias Klein :
> 
> Hi,
> 
> how is Sword build on MacOS? The compilation instructions in the Wiki do not 
> mention MacOS.
> 
> https://wiki.crosswire.org/Tutorial:Compiling_%26_Installing_SWORD
> 
> Are all dependencies available as packages/pre-built binaries, or do the 
> dependencies also need to be built (like on Windows)?
> 
> Any other hints regarding Sword on MacOS?
> 
> Background is that I'm checking what's necessary to provide an Ezra Project 
> build for MacOS. The frontend technology I'm using (Electron) is compatible, 
> so in general it should be possible.
> 
> Best regards,
> Tobias
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] (no subject)

[Manfred Bergmann]

Hi.


> Am 01.12.2019 um 00:52 schrieb Troy A. Griffitts :
> 
> UnlockInfo=Please visit the online store of the German Bible Society to
> purchase an unlock key:  href="https://www.die-bibel.de/shop/bibelausgaben/digitale-bibelausgaben/dvds-und-videos/na28-app-lizenzschluessel-0106";>NA28
> - SWORD Module
> 
> If your frontend doesn't yet support the new UnlockInfo property, please
> consider adding support to help users know how to obtain unlock keys
> when installing locked modules.


Will there be a new tagged SWORD source release where this is in?
I can prepare things using trunk but for a final version I’d rather use a 
tagged release.


Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Chromebooks

[Manfred Bergmann]

Hi.

Here is a list of Chromebooks that support running Android apps.
https://sites.google.com/a/chromium.org/dev/chromium-os/chrome-os-systems-supporting-android-apps

A minor tweak must be done to the Android app to make it appear on the Play 
store on the Chromebook:
https://developer.android.com/topic/arc/index.html


Manfred

> Am 17.03.2020 um 11:48 schrieb Timmy :
> 
> Greetings, I don't know how chrome book runs Android apps, but there's a 
> little info here from some years ago about a user running And Bible on Google 
> Chrome browser. 
> https://github.com/AndBible/and-bible/wiki/Running-And-Bible-in-Chrome
> 
> Blessings 
> Timmy 
> 
> On Tue, Mar 17, 2020, 02:34 Szabó Kristóf Imre  
> wrote:
> Hi,
> 
> I don't own a Chromebook myself, but the concept is there to use web 
> applications wherever possible (the systems have limitied storage by design, 
> if I'm not mistaken). There is technical possibility to install/run Linux 
> applications, but it is not enabled by default.
> 
> Kind regards,
> Kristof
> 
> On Tue, Mar 17, 2020 at 3:51 AM Troy A. Griffitts  
> wrote:
> We just received a 1 star review for Bishop from a Chromebook user.
> 
> I didn't know Chromebook users could run Android applications
> officially.  I had heard it was experimental at one point but didn't
> know it ever reached production.
> 
> Bishop (and I am guessing a ton of other Android apps) aren't geared
> toward devices with keyboards (e.g., we have a grid book and chapter
> selector for easy Bible navigation from a small touch screen; that's not
> how I would want to navigate if I had a keyboard).
> 
> Do we have any apps specifically targeting Chromebooks?  Do they run
> Linux apps?
> 
> May everyone stay COVID-19-free,
> 
> Troy
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] [bt-devel] trolltech / nokia

[Manfred Bergmann]

Yep.

Not sure if I'm a Nokia fan any longer.
Most probably not.

I mean it may be good for the people in Romania but the way they did  
it is far from being good.


Manfred


Am 29.01.2008 um 18:10 schrieb Martin Gruner:

> Yeah. Not sure if this is good.
>
> (Nokia is creating a lot of trouble here by (all of a sudden)  
> shutting down a
> German factory in Bochum to move production to Romaina, despite the  
> fact they
> earned 7 billion Euros last year and production makes only 5% of the  
> total
> costs.)
>
> mg
>
> Am Dienstag, 29. Januar 2008 schrieb Troy A. Griffitts:
>> Surprising news here:
>>
>> http://trolltech.com/company/newsroom/announcements/press.2008-01-28.460571
>> 8236
>>
>> ___
>> bt-devel mailing list
>> [EMAIL PROTECTED]
>> http://www.crosswire.org/mailman/listinfo/bt-devel
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] SWORDWeb / MacOSX

[Manfred Bergmann]

Greg,

Fink has orbit in as installable package if that is of any use.


Manfred



Am 04.02.2008 um 10:25 schrieb Greg Hellings:

> Troy,
>
> I've been working on this, but so far I am stuck with trying to
> compile the orbitcpp.  The latest version of it that I can locate is
> dated back on 2004 and the C++ part compiles fine, but then I keep
> getting errors about missing backend libraries for the idl-compiler.
> I could try to tackle the Java portion, if that would be sufficient,
> but I'd rather try to track down either an updated version of the
> orbitcpp or some sort of patch for Mac.
>
> Is the Java client/server portion sufficient, or does the C++ part
> need to be done as well?
>
> --Greg
>
> On Feb 2, 2008 6:02 PM, Troy A. Griffitts <[EMAIL PROTECTED]>  
> wrote:
>> Dear Greg,
>>
>> Thank you!  In the bindings/corba/orbitcpp directory the targets of  
>> the
>> makefile include a 'server' and 'testclient'.  If you can run the  
>> server
>> successfully, it should output an IOR:x string.  In another  
>> window,
>> if you run the testclient with this string as a parameter, it  
>> should try
>> to contact the server and make a few basic requests.  If this  
>> succeeds,
>> then we should be good to go.
>>
>> If all this succeeds and you get really ambitious, you could try to
>> compile and run the bindings/corba/java directory (the makefiles are
>> pretty much hardcoded so they will require a few path adjustments)  
>> and
>> then see if the java testclient can contact the c++ server.  There  
>> are a
>> few things that might need configuring for this to happen if it  
>> doesn't
>> 'just work'.  Some info can be found on the
>> http://crosswire.org/swordweb page.
>>
>> Let me know how it goes!  Thanks again!
>>
>>-Troy.
>>
>>
>>
>>
>> Greg Hellings wrote:
>>> Troy,
>>>
>>> On Feb 2, 2008 5:41 PM, Troy A. Griffitts <[EMAIL PROTECTED]>  
>>> wrote:
>>>
 I have struggled my way through compiling SWORDWeb binaries for  
 Win32
 and should be releasing a precompiled package shortly.

 At BibleTech:2008 we had a request for a precompiled version for  
 the
 Mac.  Is there anyone who has successfully compiled libsword for  
 the Mac
 who is willing to try compiling the bindings/corba/orbitcpp/  
 folder?

>>>
>>> I'm willing to give this a run for its money (installing ORBit as I
>>> write this), but I have no experience with setting it up, etc.  I've
>>> never used ORBit other than to install it for packages which require
>>> it.  What minimal files would (probably) be necessary, and how do I
>>> test deployment, etc?
>>>
>>> --Greg
>>>
>>>
 This will probably require ORBit and orbitcpp installed first.   
 If you
 can produce a binary, it would be greatly appreciated.

 Thank you for considering.

-Troy.



 ___
 sword-devel mailing list: sword-devel@crosswire.org
 http://www.crosswire.org/mailman/listinfo/sword-devel
 Instructions to unsubscribe/change your settings at above page


>>>
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>>
>>
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Future MacSword

[Manfred Bergmann]

Hi.

Although MacSword is quite old and it would be more than time for  
something new I found that it will still take a good amount of time  
until something usable is there that can replace MacSword.
I'm the only one developing in this area ATM and was quite busy with  
my daily work the last months/weeks, so it hasn't gotten as far as I  
would have liked it.

I have put many hours of work into refactoring the Sword Objective-C  
Backend (coming from MacSword) and in a module installer that is now  
in Eloquent (btw: a new version has been released with some  
enhancements).
My thinking was that until something new is there I would branch  
MacSword and backport the backend and the module installer into  
MacSword. The UI would stay the same and it would be a Leopard only  
application.
IIRC the majority of users that had questions about MacSword actually  
were using Leopard.

Altough the UI of MacSword is hardly usable in iPhone, having  
something Leopard compatible or Leopard only would ease the port to  
iPhone tremendously.

What are your thoughts about this?


Regards,
Manfred



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Future MacSword

[Manfred Bergmann]

Hi Greg.


Am 11.03.2008 um 20:52 schrieb Greg Hellings:

> I've been starting to tackle the iPhone/iPod Touch question this past
> week, and it doesn't look like it would be terribly difficult.  The
> most complicated and tedious portion of the project is getting Sword
> to compile in XCode in a manner which would allow it to build for an
> iPhone app.

It must not necessarily be build in Xcode. And to be honest I wouldn't  
do it.
C/C++ libraries will continue to be C/C++ libraries. What you do on  
Mac is to put a C/C++ library into the Application-Bundle if it is not  
available on the system by default.
MacSword of course has automatic build scripts which create universal  
binaries of the Sword library for the current versions of Mac OSX. For  
iPhone / iPod touch the only thing that needs to be changed is the  
architecture parameter to gcc to build a version for iPhone/iPod touch  
for ARM CPU.
A ARM only build of Sword library with stripping as much as possible  
would not be bigger than 800kByte I guess.

MacSword/Eloquent has a Objective-C++ wrapper to the library which  
altogether could be exported to a Mac like Framework. Currently this  
is not the case but UI si still seperated from Sword backend.

> It seems easiest, to me, if the MacSword UI, etc, were just portions
> of the SVN tree

Backend is, all other stuff is UI basically.

> , in the same way that BibleCS is.  Minimally, it would
> be nice if there was an XCode project included with the Sword API for
> just such reasons.

As said above a Mac like Framework can be created using the backend  
portion of the MacSword application.
But Mac OSX is still Unix and can easily use dylibs which Sword C++  
library is after building on Mac. I wouldn't change that.

> If MacSword was designed to be checked out into a
> subdirectory of the Sword project the way that BibleCS is, then
> perhaps there could be an XCode Project at the head of the sword
> folder which builds the library,
> and a checkout for the MacSword UI
> that built against that library back in the sword folder. (Am I being
> clear here?)

Not sure if I understood you correctly.
MacSword is designed to use a compiled Sword dynamic library dylib  
whereever this library comes from doesn't matter.
I think it can't be more flexible.

> Having such would greatly enhance my ability to build for
> Aspen/iPhone/iPod Touch.  I have the plan for the basic UI on iPhone
> worked out, but I don't yet know how and if apps will have access to
> the file system, etc.  My guess is that modules will have to be
> installed to the root of the App bundle, which also makes sense for
> the behavior of the App in OS X.

I have no idea how the Filesystem on iPhone/iPoid touch looks like.

> Leveraging your work on MacSword would be a wonderful springboard for
> iSwordTouch (or whatever other whimsical name comes up for the
> project) which would cut out most of my guesswork thus far as to
> necessary and superfluous files for a front-end to utilize.

My guess is (I don't have an iPhone), like I said before, that the  
MacSword UI is not really usable on iPhone because of the multi-window  
design. Having one main window would be much better.
I don't have much information about the runtime system on Mac OSX. But  
a strong guess is that it is minimal and could use the Objective-C 2.0  
runtime only using Garbage Collector. Beside that I don't think it is  
a big problem to have something on an iPhone/iPod touch very quickly  
if there are answres to a couple of questions.

> I also
> have access to both Tiger and Leopard simultaneously, so I can biuld
> the system and test on Tiger if you would like to continue supporting
> that at least for the time being.

I would go to a version 1.5 of MacSword which would support Leopard  
and above because a good part of the backend work is done in Objective- 
C 2.0 which is not compatible with Objective-C.
But there still is the current version 1.3.x which is still compatible  
to Panther (Mac OSX 10.3).


Manfred



> On Tue, Mar 11, 2008 at 2:39 PM, Jon Brisbin <[EMAIL PROTECTED]> wrote:
>> I for one am STOKED about an iPhone/iPod Touch Sword app! :)
>>
>> I'm okay with Leopard-only for the time being, particularly as some  
>> of
>> the main apps I'm using these days are Leopard-only...
>>
>> Thanks!
>>
>> Jon Brisbin
>> http://jbrisbin.com
>>
>>
>>
>>
>> On Mar 11, 2008, at 12:37 PM, Manfred Bergmann wrote:
>>
>>> Hi.
>>>
>>> Although MacSword is quite old and it would be more than time for
>>> something new I found that it will still take a good amount of time
>>> until something usable is there that can replace MacSword.
>>> I'm the only one dev

Re: [sword-devel] Future MacSword

[Manfred Bergmann]

Hi DM.

Mac Users should be used to that all of a sudden some software support  
is just canceled.
Just kidding. :)
But still, I think they are used to such things more than Windows or  
Linux or even Java users.
Apple sometimes is very restrictive and makes hard cuts themselfes.

But you are right, having support for the last two major OS releases  
would be good.

Maybe we can have it like this:

- MacSword 1.2.1 for Jaguar, Pather, Sword 1.5.8
This version will not be changed any longer.

- MacSword 1.3.x for Pather, Tiger, Leopard, Sword 1.5.10
Critical bugs will be fixed.
Creating a bundle with default modules.

- MacSword 1.4 for Tiger, Leopard, Sword 1.5.10 and above
Backport of Sword backend changes from Eloquent to MacSword.  
Integration of Module Installer.
This would imply though that Module Installer would need to have the  
Objective-C 2.0 stuff removed.
But after looking into Objective-C 2.0 I think it does not have so  
many enhancements that it justifies abandoning Tiger users.
I think I will look into doing that.


Regards,
Manfred




Am 11.03.2008 um 21:57 schrieb DM Smith:

> Manfred Bergmann wrote:
>> it would be a Leopard only
>> application.
>> IIRC the majority of users that had questions about MacSword actually
>> were using Leopard.
>>
>
> We have thought about which OSes we should support for BibleDesktop.  
> The
> conclusion was to support at least the current and the previous and to
> not actively support earlier versions. We also concluded that we would
> not knowingly prevent earlier platforms from running the latest  
> release
> without great gain.
>
> The way this came about is that we upgraded to Java 5. This was over a
> year after Tiger had been released. I had just gotten a Mac Mini with
> Tiger and was un-aware that Java 5 would never be ported to Panther.
> Within the next few weeks we got reports that it wouldn't run on
> Panther. We then downgraded back to Java 1.4.2.
>
> Our target users include missionaries, pastors, churches, ... with  
> old,
> hand-me-down laptops.
>
> At the time, BD was not close to being feature complete and had some
> nagging bugs. For support reasons, it was not the appropriate time to
> make such a change. I didn't want to be suggesting that a user had to
> pay money (for an OS upgrade) to use our software.
>
> Once we are reasonably feature complete and relatively bug free, we  
> plan
> to do a major development shift to using WebKit (or its equivalent on
> other platforms). This may prevent us from running on older OSes.
>
> If you were to announce a MacSword upgrade, I think that many would  
> want
> to get the upgrade. Especially since your beta is so much better  
> than 1.2.x.
>
> All this is to recommend that Leopard is very recent and Tiger  
> shouldn't
> be abandoned just yet.
>
> -- DM
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Future MacSword

[Manfred Bergmann]

Troy.

Thanks for your comments.

I will work on an official bundle right away. Which are the default  
modules that should be included?

Of course it is necessary to support older systems.
We have support back to Mac OSX Jaguar (10.2) with MacSword 1.2.1.
This is fine. We will keep this and at the same time move forward.


Manfred


Am 11.03.2008 um 20:14 schrieb Troy A. Griffitts:

> Dear Manfred,
>
> I think your ideas are exciting.  My only thoughts (which you've  
> likely
> already considered) are that it would be nice to package an official
> bundle of the beta at sourceforge.  This would allow pre-Leopard users
> to have something usable with our latest modules.  It might be nice to
> also include your module installer in that bundle if it's not too much
> work.  But I don't think making Leopard a requirement moving forward  
> is
> a bad idea, as long as we have some fallback mechanism for less
> fortunate users.  Thanks for all your work.  I realize I haven't given
> any time to assist your work, so my comments here are merely my
> thoughts, for whatever they're worth.
>
>   -Troy.
>
>
>
> Manfred Bergmann wrote:
>> Hi.
>>
>> Although MacSword is quite old and it would be more than time for
>> something new I found that it will still take a good amount of time
>> until something usable is there that can replace MacSword.
>> I'm the only one developing in this area ATM and was quite busy with
>> my daily work the last months/weeks, so it hasn't gotten as far as I
>> would have liked it.
>>
>> I have put many hours of work into refactoring the Sword Objective-C
>> Backend (coming from MacSword) and in a module installer that is now
>> in Eloquent (btw: a new version has been released with some
>> enhancements).
>> My thinking was that until something new is there I would branch
>> MacSword and backport the backend and the module installer into
>> MacSword. The UI would stay the same and it would be a Leopard only
>> application.
>> IIRC the majority of users that had questions about MacSword actually
>> were using Leopard.
>>
>> Altough the UI of MacSword is hardly usable in iPhone, having
>> something Leopard compatible or Leopard only would ease the port to
>> iPhone tremendously.
>>
>> What are your thoughts about this?
>>
>>
>> Regards,
>> Manfred
>>
>>
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Future MacSword

[Manfred Bergmann]

Because I was curious about Objective-C 2.0 which has a couple of  
enhancements (like properties and gargabe collector) and Eloquent is  
completely using it (module installer and Sword backend).
If I backport the module installer and the refactored backend to  
MacSword, it will need the Objective-C 2.0 runtime which is not  
compatible with Tiger.

Even if MacSword (let's say version 1.5) will be Leopard only, older  
version would still be updated with current Sword releases and bug  
fixes.

Manfred


Am 11.03.2008 um 21:27 schrieb David Trotz:

> Curious: Why Leopard only? I am currently running Tiger and won't be
> upgrading for a while and I suspect many are in my shoes as well.  Is
> there some feature of Leopard you are targeting? I currently use
> MacSword (when I am on my mac) and really enjoy it. :-)
> --
> David
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Future MacSword

[Manfred Bergmann]

Hi Greg.


Am 11.03.2008 um 21:42 schrieb Greg Hellings:

> Manfred,
>
> Thanks, that clears up quite a bit of how it works.  More below...
>
> On Tue, Mar 11, 2008 at 3:19 PM, Manfred Bergmann  
> <[EMAIL PROTECTED]> wrote:
>> Hi Greg.
>>
>>
>> Am 11.03.2008 um 20:52 schrieb Greg Hellings:
>>
>>
>>> I've been starting to tackle the iPhone/iPod Touch question this  
>>> past
>>> week, and it doesn't look like it would be terribly difficult.  The
>>> most complicated and tedious portion of the project is getting Sword
>>> to compile in XCode in a manner which would allow it to build for an
>>> iPhone app.
>>
>> It must not necessarily be build in Xcode. And to be honest I  
>> wouldn't
>> do it.
>> C/C++ libraries will continue to be C/C++ libraries. What you do on
>> Mac is to put a C/C++ library into the Application-Bundle if it is  
>> not
>> available on the system by default.
>> MacSword of course has automatic build scripts which create universal
>> binaries of the Sword library for the current versions of Mac OSX.  
>> For
>> iPhone / iPod touch the only thing that needs to be changed is the
>> architecture parameter to gcc to build a version for iPhone/iPod  
>> touch
>> for ARM CPU.
>> A ARM only build of Sword library with stripping as much as possible
>> would not be bigger than 800kByte I guess.
>
> The only supported way to build apps for the iPhone/iPod Touch and to
> test them in the emulator and on the device is to build them with
> XCode.  Thus, the iPhone app will need to be built with the XCode
> application.

Well, there is always a manual way of building Application Bundles and  
I'm pretty sure there is a manual way for the iPhone platform too.
But why do that, Xcode is great and much more convenient.

Btw: Xcode is spelled "Xcode", not "XCode". ;)

> Building the library on the command line shouldn't be
> much of an issue, and including it with the App bundle will also not
> be a problem.  I trust that just passing in the target architecture to
> the configure/build tools for Sword should do the trick?

I think so, yes.

> It still
> would be easier to build it in XCode, so I'll see about both options.

Actually I would say it is not easier. A lot of configuration is  
needed in the target settings in Xcode to make it compile or even  
cross-compile which might be much easier from command line.

>>> , in the same way that BibleCS is.  Minimally, it would
>>> be nice if there was an XCode project included with the Sword API  
>>> for
>>> just such reasons.
>>
>> As said above a Mac like Framework can be created using the backend
>> portion of the MacSword application.
>> But Mac OSX is still Unix and can easily use dylibs which Sword C++
>> library is after building on Mac. I wouldn't change that.
>
> It's probably easiest, for the purpose of the mobile app, to link the
> C/C++ library directly to the application, rather than try to link the
> Sword library into an Objective-C 2.0 wrapper and then wrap that into
> the application.  I only say that because my background is in C/C++
> and I can easier manipulate the code if I use as many of those
> features as possible and as little of the Objective-C as necessary
> (i.e. for only GUI portions).  It also, on the mobile platform, would
> mean fewer layers of abstraction and probably better runtimes.  If I'm
> thinking in the wrong direction, please let me know.

Hmm. Well, in order to create an application which uses Cocoa you  
would need to do some conversation anyway because Cocoa can't deal  
with C++ classes right away. And it uses NSArray, NSDictionary  
collections rather than any C++ templates.
This is what the Objectice-C wrapper does, make it work in Cocoa.
And it is so much more convenient in a Cocoa environment that you  
actually can use the Cocoa/Objective-C classes instead of C++ classes.

>>> If MacSword was designed to be checked out into a
>>> subdirectory of the Sword project the way that BibleCS is, then
>>> perhaps there could be an XCode Project at the head of the sword
>>> folder which builds the library,
>>> and a checkout for the MacSword UI
>>> that built against that library back in the sword folder. (Am I  
>>> being
>>> clear here?)
>>
>> Not sure if I understood you correctly.
>> MacSword is designed to use a compiled Sword dynamic library dylib
>> whereever this library comes from doesn't matter.
>> I think it can't be more flexible.
>
> True, I was just thinking from the build poin

[sword-devel] Someone helping out in french?

[Manfred Bergmann]

Hi.

I'm preparing a MacSword bundle and would need someone who can  
translate a few paragraphs to french.
Anyone?


Manfred



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] crossreference filter

[Manfred Bergmann]

You could have a look at the MacSword sources which contain an  
Objective-C  wrapper to the Sword library.

Somehow I'm thinking that there seem to be many people trying to get  
something going on iPhone.
Maybe the effords should be coordinated.


Regards,
Manfred



Am 15.03.2008 um 03:03 schrieb John Schultz:

> I am doing some initial work with Mac OSX to get a basic Sword based
> program going to have a starting point to try doing a iPhone
> implementation.
>
> I am getting the ESV text with imbedded crossreferences. It appears
> that there is a filter option to remove them, but I am stuck on trying
> to figure this out from the .h files. It looks like a call to
> SWMgr::filterText might work, but I am not sure of the parameter
> requirements.
>
> John Schultz
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Future MacSword

[Manfred Bergmann]

Hi Nathan.

Good to hear from you.
Your name appears on many of the source files in MacSword. :)

Finally I pulled out all the Objective-C 2.0 stuff of the Sword  
wrapper. This way it is more widely useable.
Also I put everything in a framework so there is only one codebase and  
it can be used on different projects.

Unfortunately I don't have access to the website sources and currently  
there is no maintainer.
I don't actually know who the maintainer was. There is quite a need to  
maintain the website because many people are still download the old  
1.2.1 release and then post here to get support because the version  
doesn't work on Leopard and has quite a couple of bugs.

What are you doing then. If I look at your website one could thing you  
are doing the RoR thing.


Regards,
Manfred



Am 17.03.2008 um 03:14 schrieb Nathan Youngman:

>
> Hi,
>
> Thought I'd chime in on the conversation between Manfred and Greg on
> MacSword and the iPhone SDK.
>
> Glad to see MacSword is alive and kicking. The Eloquent wrapper sounds
> like a good step, though the iPhone SDK doesn't include garbage
> collection (pretty much all the other Objective-C 2.0 features are
> intact).
>
> The iPhone SDK does sandbox you into a directory for your application,
> but you could use the networking layer to retrieve and install Sword
> modules. Perhaps another possibility would be to just preload it with
> a few... I'm not sure of the licensing implications, i.e. with ESV,
> God's Word, etc.
>
> I did some work on MacSword back in 2002, long enough ago that I'm not
> sure if I know how to program in C anymore. :-) If whoever is
> maintaining macsword.com could forward [EMAIL PROTECTED] to me, I
> could at least retrieve my password on the Sourceforge project.
> Whether or not I actually am able to help at all is another question
> entirely!
>
> Thanks, Nathan.
>
>
> ---
> Nathan Youngman
> Email: nj at nathany dot com
> Web: http://www.nathany.com
>
>
>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Future MacSword

[Manfred Bergmann]

Hi Nathan.

We don't use Lucene any longer (for quite a while now actually).
Instead Apple's SearchKit is used for indexing/searching.
Maybe there is time to create a Spotlight plugin in the future. But  
more important things need to get done actually.
Do you know if SearchKit is available on iPhone?

Would be good if you could contact Will and ask for that.
I would find it good to also have the website sources version  
controlled actually.


Manfred


Am 17.03.2008 um 17:00 schrieb Nathan Youngman:

> Hi Manfred,
>
> Nice to meet you. :-)
>
> Your wrapper will go a long way towards supporting both Tiger and the
> iPhone SDK, I'm sure. From peering at the source code, I noticed the
> Java
> version of Lucene being used, which won't port to the iPhone either.
>
> Sword uses OSIS and other XML formats internally? Indexing with
> SQLite seems like a good idea to me, but I don't have a good grasp
> of the architecture yet. When I worked for a library automation  
> company
> I learned some basics of making a searchable catalog with a database.
>
> I have been doing RoR for a year or so now, and if we could transfer
> the domain back over to me, I could definitely look at updating or  
> even
> redesigning the web site. I will have to try to get in touch with  
> Will.
>
> - nathan.
>
>
> On 17-Mar-08, at 4:11 AM, Manfred Bergmann wrote:
>
>> Hi Nathan.
>>
>> Good to hear from you.
>> Your name appears on many of the source files in MacSword. :)
>>
>> Finally I pulled out all the Objective-C 2.0 stuff of the Sword
>> wrapper. This way it is more widely useable.
>> Also I put everything in a framework so there is only one codebase  
>> and
>> it can be used on different projects.
>>
>> Unfortunately I don't have access to the website sources and  
>> currently
>> there is no maintainer.
>> I don't actually know who the maintainer was. There is quite a need  
>> to
>> maintain the website because many people are still download the old
>> 1.2.1 release and then post here to get support because the version
>> doesn't work on Leopard and has quite a couple of bugs.
>>
>> What are you doing then. If I look at your website one could thing  
>> you
>> are doing the RoR thing.
>>
>>
>> Regards,
>> Manfred
>
> ---
> Nathan Youngman
> Email: nj at nathany dot com
> Web: http://www.nathany.com
>
>
>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Future MacSword

[Manfred Bergmann]

Guys. :)

Am 17.03.2008 um 17:06 schrieb Greg Hellings:

> Nathan,
>
> On Mon, Mar 17, 2008 at 10:46 AM, Nathan Youngman <[EMAIL PROTECTED] 
> > wrote:
>>
>> Hi Sébastien,
>>
>> While the iPhone only has 128 MB of RAM for running programs, I think
>> the 4-16 GB of storage space should be fine for having multiple  
>> Bibles.
>> Though for simplicity of the interface, it might even be a good idea
>> to scale back to a single text.
>>
>> As far as other languages, it may make sense to release a localized
>> version of the application with the Bible text, rather than having an
>> English UI with any given Bible.
>>
>> I think downloading modules from within the program is certainly
>> possible, but it somewhat complicates the program and perhaps
>> shouldn't be an initial requirement.
>
> The hardest part of that is probably just making sure the sword
> library's wrapper links against the libraries on the iPhone for
> network access.  Actually pulling the files and maintaining them is
> likely to be rather straight-forward.  However, given that there is a
> significant limitation on both the in-memory as well as the on "disk"
> storage, an ability to maintain and delete modules is also a wise
> plan.
>

I'm guessing only, sorry for that.
However the network layer may look like, should be abstracted in a way  
that the developer actually doesn't see a difference from the normal  
Cocoa nerwork stuff.
importing  should be fully enough to get network going.  
Using a different framework than on the full Mac OSX makes no sense to  
me. And after all, the OS on iPhone still is Mac OSX.


Manfred




>>
>> - nathan.
>>
>>
>>
>> On 17-Mar-08, at 4:10 AM, Sebastien Koechlin wrote:
>>
>>> On Sun, Mar 16, 2008 at 07:14:09PM -0700, Nathan Youngman wrote:
 The iPhone SDK does sandbox you into a directory for your
 application,
 but you could use the networking layer to retrieve and install  
 Sword
 modules. Perhaps another possibility would be to just preload it  
 with
 a few... I'm not sure of the licensing implications, i.e. with ESV,
 God's Word, etc.
>>>
>>> This will limit distribution to people using English as language.
>>> Memory is
>>> still limited on the iPhone (and on any flash based memory); so
>>> users must
>>> be able to drop and install modules to suit their needs.
>>>
>>> --
>>> Sébastien Koechlin
>>>
>>>


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] MacSword site

[Manfred Bergmann]

Am 18.03.2008 um 05:03 schrieb Greg Hellings:

> On Mon, Mar 17, 2008 at 10:03 PM, DM Smith <[EMAIL PROTECTED]>  
> wrote:
>>
>>
>>
>> On Mar 17, 2008, at 10:48 PM, Jónatas Ferreira wrote:
>> Hi,
>>
>> I noticed today (and it was talked about here) that the MacSword
>> website still has an old version of MacSword (1.2.1.) while I already
>> have 1.3.1b1 installed. I can't seem to find an up-to-date version on
>> the web. Where should I direct someone that wants to download
>> MacSword? Is there another URL?
>>
>> It's on SourceForge. The MacSword site is dead for all practical  
>> purposes.
>
> Why not have the SF-provided MacSword website be the new main portal
> if there are issues getting ahold of the maintainer of the website?
> Whoever had administrative access over the SF project also has access
> to the macsword.sourceforge.com site.

That's true.
The SF web space would be fully sufficient as the main portal.
And it would be in public hands. There must not be necessarily a  
macsword.com domain, the SF one would be enough IMO.

But I'm not a web developer at least for when it comes to design.
For a start we maybe could use the old website and just copy it over  
there and update it.


Manfred



>
>
> --Greg
>
>>
>> Here is the link:
>> http://sourceforge.net/project/showfiles.php?group_id=73300
>> The bundle is the way to go.
>>
>> In Him,
>> DM
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] MacSword site

[Manfred Bergmann]

Am 18.03.2008 um 08:51 schrieb Nathan Youngman:

>
> we could do that, but it's less then ideal in my mind... not having
> the domain, that is.
>
> i'll wait a bit to hear from Will... maybe you might want to email him
> as well, for emphasis :)

Yep, will do that.

>
>
> the domain could be registered at an account that we all share access
> to, that seems ideal to me.

If this is possible. Would be ideal of course.


Manfred




>
>
> - nathan
>
>
> On 18-Mar-08, at 12:15 AM, Manfred Bergmann wrote:
>
>> That's true.
>> The SF web space would be fully sufficient as the main portal.
>> And it would be in public hands. There must not be necessarily a
>> macsword.com domain, the SF one would be enough IMO.
>>
>> But I'm not a web developer at least for when it comes to design.
>> For a start we maybe could use the old website and just copy it over
>> there and update it.
>>
>>
>> Manfred
>
> ---
> Nathan Youngman
> Email: nj at nathany dot com
> Web: http://www.nathany.com
>
>
>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Future MacSword

[Manfred Bergmann]

Am 17.03.2008 um 17:45 schrieb Nathan Youngman:

>
> Hi Manfred,
>
> Yay, SearchKit! Sounds like a little cleanup is needed in Subversion
> though :-)

You need to look at branches/MacSword-reorg

I did reorganize all source files in a branch some time ago and it  
never made it into the trunk.
So this branch actually is the development trunk now. ;)
A stable version (1.3.1) has been tagged lately which is in tags folder.
This branch will now be further changed, Panther support dropped,  
module installer integrated.

> I'm not sure if SearchKit is on iPhone OS, I don't see why not, but
> never know.
>
> Regarding the networking bit:
>
> "There may be occasions when you need to configure your application
> target so that it links against one framework to run on the iPhone
> simulator and another framework to run on a device. For example, the
> CFNetwork API is a stand-alone framework (CFNetwork.framework) in the
> iPhone SDK for a device but a subframework of the Core Services
> framework (CoreServices.framework) on the iPhone SDK for the iPhone
> simulator."

Ok, but this is not a problem at all.
#ifdef
#else

could simply do the trick.

>
>
>
> I fired off an email to Will... he's not always the best at getting
> back to me, but we'll see.

Indeed.


Manfred


>
>
> On 17-Mar-08, at 9:16 AM, Manfred Bergmann wrote:
>
>> Hi Nathan.
>>
>> We don't use Lucene any longer (for quite a while now actually).
>> Instead Apple's SearchKit is used for indexing/searching.
>> Maybe there is time to create a Spotlight plugin in the future. But
>> more important things need to get done actually.
>> Do you know if SearchKit is available on iPhone?
>>
>> Would be good if you could contact Will and ask for that.
>> I would find it good to also have the website sources version
>> controlled actually.
>>
>>
>> Manfred
>
> ---
> Nathan Youngman
> Email: nj at nathany dot com
> Web: http://www.nathany.com
>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page