Lack of documentation is definitely a problem with PDF::Template. The tests that are there show some ideas, but I have to go back to the source to remember how to do stuff.
As for the layout, it's real XML - I use XML::Parser to parse it. The "pseudo" part of it comes from the fact that a childnode has access to the attributes of all its ancestor nodes. This scoping was so that you could specify something in the pdftemplate node (the root), such as H, and have all the children use that as their H. (This feature is actually one part of the performance problem I was speaking of.)
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|