Using Standard (Valid) HTML Code According to w3.org

[Phil Longstaff]

If this is for trunk, I'd prefer that we *don't* just fix the current scheme 
code.   We really need to decide what we plan to do with reports for 2.6.  We 
have our current scheme reports.  We have a few eguile reports.  We've had a 
suggestion to use laml (http://www.cs.aau.dk/~normark/laml/) to allow us to more 
easily generate reports.  We've had suggestions to replace scheme with python 
for reports.

I don't really have a preference, but I would like to see an updated report 
engine which is 1) common across all reports, 2) allows easy inclusion of CSS, 
3) allows easy inclusion of javascript for things like hiding/expanding 
columns/sections of rows, 4) allows multi-column reports (e.g. balance sheet 
both today and beginning of every year for the past 3 years).

Phil
---------
I used to be a hypochondriac AND a kleptomaniac. So I took something for it.




________________________________
From: John Ralls <jralls at ceridwen.us>
To: Frank H. Ellenberger <f.ellenberger at online.de>
Cc: gnucash-devel at gnucash.org
Sent: Wed, April 13, 2011 9:46:09 AM
Subject: Re: Using Standard (Valid) HTML Code According to w3.org


On Apr 13, 2011, at 5:04 AM, Frank H. Ellenberger wrote:

> Hey John,
> 
> Am Montag, 11. April 2011 um 17:23:17 schrieb John Ralls:
>> We only need the generated HTML to display correctly in the embedded
>> WebKit, which AFAICT it does.
> 
> No, we also offer to export the pages, where they will be rendered by any 
> engine the user has at hand.

Really? Ok.

Joshua, perhaps you could contribute by running reports, checking them against 
the validator, figuring out what's wrong with the HTML, and filing bug reports 
with the details. One of the devs who knows Scheme could then make the necessary 
adjustments.

Regards,
John Ralls

_______________________________________________
gnucash-devel mailing list
gnucash-devel at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel