It's been rumoured that [EMAIL PROTECTED] said:
> My point here is that committing deeply to HTML as the rendering engine may
> not be the smartest answer; being prepared to, at an appropriate juncture,
> "leap" to XML would probably be wise...
This is why I want to split apart the html from the C code;
I don't want html embedded in the c code, because its a
maintainability, enhance-ability mess. I figure, by banishing
the html to its own files, doing the kind of port you talk about
becomes a lot easier. It also allows the themes.org types to
cook up wild color schemes without rudely disrupting the internals
of the report generetor. It makes export-to-gnumeric "trivial".
The trick is how to punch the actual $ amounts and account names into the
html templates; that's where php comes in. Oh, and btw, PHP couldn't care
less if its html, xml, or whatever, as long as the delimiter <? stuff >
is unambigouous.
think "lambda binding values into variables".
--linas
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body
