Custom Reports

[Shokster]

# If the report is adaquately 'commented', then there's no need to have
somebody 'answerable' to it.  Of course, the author can 'comment-in' their
contact if they would like to. 
 
# Also, it should have a short description of what it does, and what the
possiblities are. Schematics (such as flowcharts) work great and could
accompany as a 'jpeg' file. 
 
# There should also be available some pdf example outputs. 
 
I'm not new to programming, I've used plenty of scientific computing. What
is still mystery to me is the structure of a report. Second mystery is the
syntax, but not as much of a hurdle as the first. 
 
You're right Yawar, it would be a lot nicer to have a "'process'
description" as opposed to trying to learn by reverse engineering
built-in-reports. 
 
Do we need a publicly accessible file dump webhost to get the dirty work
started? How do these things work? Or do people work individually and
present only 'fully finished reports' which are then put onto the wiki site? 

--
View this message in context: http://gnucash.1415818.n4.nabble.com/Custom-Reports-tp4577119p4582868.html
Sent from the GnuCash - User mailing list archive at Nabble.com.