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.
-
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.
|
