Hey,
> -----Original Message-----
> That's what CSS and the wrapping HTML are for. That's why an HTML
> file which calls on one or more CGIs to render small, simply-
> formatted lists is preferable (unless the server can't cope). In my
> CSS, I can say that any <LI> inside a given <SPAN CLASS="foo">
> appears in a given style. Then all my CGI must print is <LI>item 1
> <LI>item 2 ... The CGI needs to know no style, no formatting,
> nothing but a bare <LI>. It can get more complicated, but not much.
I think you're thinking of a different layer than what Michael is saying:
+--------------+
| Code | Perl
+--------------+
| generates
+--------------+
| Content | (X)HTML
+--------------+
| is styled by
+--------------+
| Presentation | CSS
+--------------+
So, how were you planning on generating the HTML anyway? You can either do
some print() statements, or you can keep the HTML out of your code and use
templates.
The choice is yours -- I just wanted to make sure the code-content
separation is not mislabeled as content-presentation separation.
-Brian
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
