I'm not saying that Maypole is not capable of complex things, but there are quickly diminishing returns once you stack more complexity on Maypole. Maypole gives you a quick start if your application fits well into the Maypole model of things. It makes no sense to use Maypole instead of writing your own framework if you have to either bend your requirements to make them fit to Maypole or if you have to bend Maypole to have it fit your requirements.
And as there already is a good ticketing/tracking solution, I would not waste the time by writing and expanding my own solution but rather use the existing solution.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||