I prefer to "isolate" table relations in their own packages using Class::DBI::Lite. ASP4 allows me to keep my presentation-focused logic right there at the "point of effect" while stashing my business logic in output-neutral "Form Handlers". URL Routing (often subject to change) can be declared once within the config and managed by ASP4x::Router - becoming completely transparent to the pages or handlers they route to.
Perl offers multiple ways to get the same thing done - depending on what you are trying to do. I dislike "action at a distance" so I avoid spreading things across too many places to look. I'm sure that in the case of Catalyst after a while a kind of "rhythm" emerges which helps you know where to find out where a particular URI would map to - but you could really trip yourself up if you weren't careful.
-
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.
|