Great post. I've also had a love/hate relationship with Maypole. The installation was tricky, and its dependence on so many modules with version numbers close to 0.01 by various authors didn't inspire much confidence, but it worked. I also had to add warns all over the place to figure out where things were crashing.

The introductory documentation and articles are all good, but I found that when I started to try to actually adapt and extend Maypole for my needs, there were gaps that could only be filled by reading the code. And then when I tried to deviate a bit from the table/action/id model or add better support for many-to-many relationships things got ugly and I almost had to override entire classes (Class::DBI::AsForm was problematic). But it worked out in the end. My only concern is that it tends to be slow in my poor old hardware.

Using Maypole was definitely a great learning experience. I still use it for the application I developed at that time. When later I had to write a simpler application I found that it was much easier to write it from scratch thanks to the experience I gained. That doesn't mean that I won't use it again, it depends on what I want to do.

In reply to Re: Maypole and I - Tales from the Frontier of a Relationship by itub
in thread Maypole and I - Tales from the Frontier of a Relationship by Corion

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.