On 26.09.2016 00:25, Peter von Kaehne wrote:
> Libsword needs to be working for all kinds of devices and in a million
> of unanticipated environments. Now and in future.
Give me a break! I doubt there will be much demand in the near future
for BibleTime to run on less than 64-bit CPUs, for example
On Sun, 2016-09-25 at 17:52 -0400, Karl Kleinpaste wrote:
> On 09/25/2016 05:25 PM, Peter von Kaehne wrote:
> > Changes ... need to be slow, reliable and consensual. And the
> > maintainers need to be slow, reliable and acting in consensus, too.
> > Plodders, more than revolutionaries.
> I want to
On 09/25/2016 05:25 PM, Peter von Kaehne wrote:
> Changes ... need to be slow, reliable and consensual. And the
> maintainers need to be slow, reliable and acting in consensus, too.
> Plodders, more than revolutionaries.
I want to see if I've got this straight.
Jaak is being challenged for possib
Libsword needs to be working for all kinds of devices and in a million
of unanticipated environments. Now and in future.
It needs to work for module makers as much as for frontend makeers -
both existing ones and those we have not even thought of yet.
Changes like dropping of utilities (diatheke
On 09/25/2016 03:50 PM, Matěj Cepl wrote:
> the fear that it will kill any upgrades in most Linux distros
There hasn't been a release of the engine in something like 2 years, so
... eh, hardly matters, y'know?
___
sword-devel mailing list: sword-devel@c
On 25.09.2016 22:50, Matěj Cepl wrote:
> On 2016-09-25, 18:54 GMT, Jaak Ristioja wrote:
>> 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++.
>
> Well,
On 2016-09-25, 18:54 GMT, Jaak Ristioja wrote:
> 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++.
Well, aside from the fear that it will kill any upgrade
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
