Some wisdom(hopefully) from my experience.
Keeping functions that are common to more than one file in a seprate module is a good idea.
What I like to do is to keep all business logic in one file and all display code in another. This gives me a 3 tier model: data, logic, and presentation. While I find this helpful you may not. Use whatever works best in your situation.
You didn't mention it in your post but I would recommend using a templating system, such as HTML::Template. There are several other templating systems available so take a look at a few of them before deciding which one will work best for this project.
Hopefully this will help out a little.
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.