Thank you, Manfred and Troy. :-)
I'll keep these in mind as I update PocketSword.
On 3/13/19 12:01 AM, Manfred Bergmann wrote:
>
>> 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
> 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
>
Hi Michael,
Good to read of the technical progress. Have you visited our tracker to see
what other issues need fixing.
We were alerted a few months ago to Apple's current requirements for iOS app
providers to have an adequate privacy policy that meets their legal standards
and which (IIRC) is
If anyone cares, there is now a supportes build of a Universal libsword binary
in the SWORD repo that works for MacOS and iOS. It's under the objc bindings
and drew heavily from the setup already in there by Manfred and others (thank
you) This readme at this path in the source is a good place t
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 colla
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 l
