HTML table rendering, reports, misc

[Christian Stimming]

-----BEGIN PGP SIGNED MESSAGE-----

Whow, this new account summary report looks indeed impressive with that 
hierarchy enabled. Thanks b.g. for the colspan/rowspan and your changes in 
the report code -- that's how I think Open Source should work. But there 
are still some shortcomings:

* the look of   -- one   seems not to be enough to make the tree 
visible enough. Is there a possibility to specify in a style sheet how 
those #f table-cells should be rendered? With a numeric option on how many 
 's you get?

* the printing look of the report -- those html-anchors <a href... should 
not be visible in the printing view of the report. Actually I'm quite 
surprised and happy that printing works at all. 1. We could add an option 
to style-sheets to surpress rendering of anchors, 2. we could add this 
option to the report parameters, 3. we could generally surpress anchors in 
the printed version.

* SERIOUS BUG! The Query sometimes returns balances for the wrong date. If 
I want my balance for the 12/31/2000, the report will show the balance for 
the 12/30/2000 instead of one day later. Actually (as I checked this out) 
this seems to be always the case. Bill g., Linas, or whoever, did somebody 
misunderstand the Query API? 

Christian

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQCVAwUBOnJy1mXAi+BfhivFAQFdkwP+Iv8ibp7OVUT/CI8rPaRGDKhq9Z0deNnd
I+Q+ZxpGZrOspxgJGoGgywX9dpplk0EnOBTrpFmFcSx9AMk7vak5BaqgUHYX4aeM
YPOK/HVlZCJd35VYCoaKsXJRnCjE6StiC1FrdI5dGIv1Q20eQ5T04yy3zWL5ZN8a
E+OYiLBdibA=
=ThIz
-----END PGP SIGNATURE-----