As the author emeritus of Maypole (Simon Cozens) has said one more than one occasion the templates that are packaged with Maypole are meant for example purposes only and you're not actually supposed to use them (I didn't).

I've been using Maypole for some time now and settled on it after looking at several other web frameworks. Maypole won out for several reasons:

It doesn't try to be everything to everyone. I have built several web applications of varying complexity with different technologies (Siebel, LAM/Perl/PHP, etc.) and have discovered that framework-enabled functionality often gets in the way of properly solving the problems at hand. No number framework developers can forsee and appropriately address all of the problems you're likely to encounter when developing large scale web applications and thus their implementations are often likely to be inaccurate or misused at best. Small frameworks are often best for building small-to-medium sized applications and should seek to provide a basis for implementing a solution but not seek to be the solution.

Secondly, the usefulness of a framework is inversely proportional the level of abstraction. Abstraction is nice but the harder you try to be everything to everyone (see above) the quicker you'll discover that your framework accomplishes little particularly well, with the exception of providing more avenues for half-assed extensions. The phrase "Jack of all trades, master of none" applies particularly well here. Yes, there are several components of Maypole than can be replaced but it works best as it is (i.e. before Simon gave control of it to the hordes).

It is my view that although nicely formatted and well thought out templates are nice, they cannot replace poorly thought-out design. As the templates provided for Maypole are meant to be throw-away examples, I think your thesis as it applies to Maypole is moot and probably for other frameworks as well (although I'm willing to admit that I'm wrong about this assumption). After all, what good is your framework if you have to re-write half of it to suit your needs.

In reply to Re: Maypole: Good code or good templates (Maypole) by Booger
in thread Good code or good templates (Maypole) by zby

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.