Re: [sword-devel] Architecture and issues reporting

2017-02-20 Thread Peter Von Kaehne
> Von: "Jaak Ristioja" > Ideally, the Sword toolset should make it impossible to produce buggy > modules in the first place. I think this is essentially impossible. Not for libsword problems but because the bulk of module problems we encounter nouwadays are not in any form

Re: [sword-devel] Architecture and issues reporting

2017-02-20 Thread Jaak Ristioja
On 19.02.2017 17:28, David Haslam wrote: > 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

Re: [sword-devel] Architecture and issues reporting

2017-02-19 Thread ref...@gmx.net
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

[sword-devel] Architecture and issues reporting

2017-02-19 Thread David Haslam
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