Check printing in windows?

[John Layman]

We are touching on a much more fundamental problem here: the lack of defect
triage based on actual usage and criticality.  Indeed, this mail list seems
to be the only thing providing much in the way of a feedback mechanism, but
the feedback doesn't always seem to register.  I think I am paraphrasing
Gerald Weinberg from a book years ago: "In the absence of a feedback loop,
nothing prevents us from inventing our own reality."  That is
word-to-the-wise it would be well for the GnuCash  developers to ponder. 

I brought up the check printing issue because I think it highlights
GnuCash's Achilles heel: the development culture.   Development proceeds
with little sense of who the 'customer' is, what the usage profile might be,
and the unrealistic notion that it's up to users to invent workarounds for
problems or pitch in on the development effort.   GnuCash faces competition
in the cloud (services like Wave Acounting, FreshBooks and the like) and
there is not a chance in the world it will survive that competition if its
developers indulge more in imaginative navel-gazing about features and the
evolution of the code base than in serving the customer base.  As I read
here the explanations for why the printing defect goes unaddressed, I feel
more than a little glum about the accounting software choice I made a couple
of years back.

-----Original Message-----
From: gnucash-user-bounces+john.layman=laymanandlayman.com at gnucash.org
[mailto:gnucash-user-bounces+john.layman=laymanandlayman.com at gnucash.org] On
Behalf Of John Ralls
Sent: Saturday, March 17, 2012 5:44 PM
To: David T.
Cc: gnucash-user at gnucash.org
Subject: Re: Check printing in windows?


On Mar 17, 2012, at 1:14 PM, David T. wrote:

> The point is that Gnucash will continue to be bundled and distributed with
the Windows printing flaw until someone submits a bugfix patch that can be
tested. So Windows users will continue to know about your fixed file (buried
in the user-list archives), and download and install it before they can
print checks under Windows. 
> 
> 
> Wouldn't it just be great if the fixed file were a part of the
application, and Windows users wouldn't have to do all that?
> 

The fundamental problem for the developers is that none of us can replicate
the problem. It doesn't happen for everyone, so we need to know if this
patch in fact fixes the problem for more people than just dniesby.

Regards,
John Ralls


_______________________________________________
gnucash-user mailing list
gnucash-user at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.