While I agree with much of this, I think there is a lot of value in logical (not phsyical) separation of the presentation code (templates, XSL, some PDF writing module, etc.) and the domain objects (where the actual logic of the application goes). Keeping them separate doesn't help performance or scalability, but it does help with maintenance, making it much easier to change things later on. Tangling up the SQL with the HTML-generation and the application logic makes it really hard to do general changes, like adding caching to all your database calls.
-
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.
|