Custom Reports

[casi]

The idea of a 'central file exchange' or including them directly is far
beyond my current horizon.

What struck me a bit is that the documenation in the gnucash project
does not really invite someone to produce own reports:

1. Scheme came to me rather as a shock, before I could turn it into a
challange (the Wiki was a great help already here)
2. Going through the existing (sophisticated) reports to understand the
API is not too attracting for someone who has to deal with 1.

And when collecting reports from more and more authors, we should also
make sure that report information (the idea of a certain report and it's
constraints) is documented, too.

I see that the Wiki is perfectly perpared for this, it just misses some
flesh to  the bones for people like me, so this is where my current
ambition lies.

There is still a long way to go until I will be happy to present my own
stuff to the public.

But I am very happy to hear that someone else might in fact check my
Wiki-updates and might even prevent it from becoming too error prone.
Yes, please, pitch in!

/Carsten


On Mon, 2012-04-23 at 12:24 -0400, Derek Atkins wrote:
> Shokster <ashok.sinha at gmail.com> writes:
> 
> > I have seen that Wiki page. What I was proposing is some sort of a 'central
> > file exchange' (similar to the Matlab Central File Exchange which I use
> > extensively) hosted anywhere (or on the Wiki) where users can exchange their
> > custom created reports. It's always nice to have a large collection of
> > reports on one site. 
> 
> Historically we've just added reports to the GnuCash sources.  We're
> still happy to do that.  The main issue is that there's really no way to
> regression test, so reports don't get wide amounts of testing, and
> generally people write reports to the stable release, not the
> development code.
> 
> But seriously, if there are reports that don't exist and are generally
> useful then they should get included, not be something that people have
> to find.
> 
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> 
> -derek
>