I wasn't ragging on CGI's html methods because they don't
work in some way. I was down on them because separating
content and presentation happens to be a very good bargain.
Writing CGI's html methods to produce desired output is a
bad code factoring.
And it sounds like your company realized the same thing.
Yes, you use CGI's html methods. But you don't code them
up. Instead you autogenerate it from regular HTML. (And
presumably you could take the original, put it through
standard design tools, and then re-autogenerate the CGI
code. If you can't then take the energy to figure out how
to make that doable. You will make up for the
effort in savings on maintainance.)
That works. That addresses the objection squarely.
-
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.
|