To be honest, I think this has little mileage.Too many things can go wrong between module, back and front-end and usually requires a person reasonably aware of the overall architecture to determine where a problem belongs. In the end the frustration described I s one common to anyone running a more
Dear All,
This is to announce that we have just now uploaded AbbottSmithStrongs.
This is is an updated version of AbbottSmithStrongs.
Many thanks to update for the hard work.
yours
The Module Team
P.S.: This email is sent automatically on upload of a new/updated module
_
I don't mean to derail this in any way. I've previously only had experience
with HTML/PHP/SQL, and I'm now learning Python (in order to develop a
SWORD-related Android app)
Would it be beneficial to port the whole project to Python? That seems to
be a widely known and easy to learn language.
Forgi
Assuming the contemplated projects are the digitisation of PD works, I would
rather see the effort devoted to text development than module development.
Text development of any hitherto undigitised work such as a Bible
translation is a demanding task in itself. One has to be particularly
diligent i
Are we any closer to a release of SWORD v1.8 ?
cf. Troy started this thread last October.
As someone without any experience of C++ programming, I sometimes wonder how
many C++ programmers are still active in CrossWire. It seems far, far fewer
than when I first linked up with CrossWire in 2008.
c
Many of the front-end developers get frustrated when users report software or
module issues that are not caused by any fault in the front-end program.
Here in this mailing list, most of us are very familiar with the back-end /
front-end architecture of our Bible software, yet even when relatively
