Actually, what I normally do is to generate the report output as an XML file, then run it through XSLT ... or simply let the web browser do that work for me. Simply adopt a consistent structure for the XML data that you intend to report. (Going so far as to define a schema that can be validated is probably a good thing.) Then, set up an XSLT stylesheet that can be used to turn all of them into good-looking output with CSS stylesheets and so forth. It can do a lot of things for you which you therefore don’t have to do in code, and it looks a heck of a lot more professional than “line-printer art.” Using XML also makes the report output in-general more of a resource, that can be used for other things.
(If you want to see just what this technology is capable of, look at this interactive table of the elements which was created in this way ... virtually no programming required.)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||