Robert Graham Merkel <[EMAIL PROTECTED]> writes:
> 1) Report generator, which walks the accounts and generates our
> "report-data". The "report-data" representation is unique
> to this particular report (though, if we're feeling really
> clever, we might specify some guidelines, or even a
> meta-language, to construct this representation). This
> information can then be saved to a file.
>
> 2) Structure generator, which walks the "report-data" representation
> and converts to our "document structure" representation, which
> would look something very like Christopher's proposal. This
> document structure representation is standardised for all reports.
So we're *all* right. Makes me feel all warm and crispy inside :>
Are you comfortable with Robert's summary, Christopher, or do you
think this is going off the deep end?
> This is a real "Swiss-army chainsaw" approach to reporting.
Hey, I'm all in favor of very-loud, gas-spitting, highly-dangerous,
and potentially explosive solutions. If we could just work a
flamethrower in there somehow, I'd be completely satisfied ;>
> Have I missed anything here?
Not that I can tell, I think I agree with basically everything you
said, though the devil's likely to be in the details. Sometimes when
I think I know how I'd ideally *want* things done, when I actually
have to do them, it's turns out to be a lot harder than it looked.
I suspect that some simple trial solutions would be pretty easy to
whip up for text, html, and latex at least. Anyone game?
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
