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 complex system - users struggle to point clearly at where a problem stems from.
Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
-------- Original Message --------
Subject: [sword-devel] Architecture and issues reporting
From: David Haslam
To: sword-devel@crosswire.org
CC:
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 new
users begin to understand this, it's still not that simple for them to
distinguish symptoms due to a back-end bug and those due to a front-end bug.
Likewise to judge when a bug is in a module rather than in our software.
I feel that we could do with some worked examples in the developers's wiki
that will aid users in terms of reporting issues.
Please comment and discuss.
If you feel inspired, please start a new wiki page for this very purpose.
Best regards,
David
--
View this message in context: http://sword-dev.350566.n4.nabble.com/Architecture-and-issues-reporting-tp4656697.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
