comment on

Hey, Thanks for the great review. Having beaten Maypole with a stick myself I appreciate seeing this info out there for new commers. I hated most that non of its documentation even seems to address the problems it has. Of course once you find the problem it is normaly easy to find the answers in the documentation, unfortunatly 90% of my time was spent trying to figure out what the problem was.

On the plus side once I got it working it seems pretty nifty, as it matures and gets some better examples, documentation, and some of the patches integrated with it, it should be an amazing framework. With some effort (read lots and lots of effort) Maypole can even be convinced to run on Apached2 mod_perl 1.99

Thanks for the great review, perhaps you could make some of your Maypole accomplishments available for others to try out.

PS one of my biggest problems turned out to be an error in the TT macro file provided with it. So if you have problems with relative links look there.

___________
Eric Hodges

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

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.


Don't ask to ask, just ask
	PerlMonks