This weekend, I released
Excel::Template v0.01 to CPAN. It's a module with the same API as
HTML::Template, but creates Excel spreadsheets (using
jmcnamara's
Spreadsheet::WriteExcel as the renderer). Right now, only a few features are supported, but more are on the way. I wanted to release a basic version so that I could get comments/suggestions quicker.
Features supported:
- Creation of a basic workbook, including multiple named sheets
- Usage of bold formatting
- Variables (both as the var tag and within parameters, like <cell text="$some_var"/>)
- Loops (both within and around the worksheet tag)
Features on the way:
- More formatting (including color, italics, etc)
- Ability to choose how to write the cell (string, URL, number, etc)
- Formulas, including the ability to reference cells already written
- Catching overflow within a sheet (the 65k rows limit)
- Pane freezing
- Anything else Spreadsheet::WriteExcel allows me to do
- Documentation on how to easily write the code for your own nodes. (This is currently supported, just not documented.)
Since this is my first CPAN module, I'd also love to have comments regarding how I did the packaging and POD. (I know I forgot to change the README ... that's first on the list to do.)
I also was at a loss as to how to write the tests. In my rewrite of PDF::Template, I wrote a mockup of pdflib_pl and tested my calls to that module, but there were only some 15 functions used. I'm using more in Spreadsheet::WriteExcel ... can the same method apply? Or, am I missing something really simple?
------
We are the carpenters and bricklayers of the Information Age.
The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6
... strings and arrays will suffice. As they are easily available as native data types in any sane language, ... - blokhead, speaking on evolutionary algorithms
Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.