I can tell you some stuff about that right now. CGI.pm is just a quick and dirty module that will save on some typing in your perl script. Emphasis on some. If you're doing anything more than basic html tags it quickly becomes not worth it anymore. Writing tag attributes takes up more time and space than just writing out the html itself. The one thing it's really good for is writing out tables. If you have an array with all your row data you can write something like print Tr( td([EMAIL PROTECTED]) ). That saves a lot of typing. The perldoc has most of the gritty details.
Cascading Style Sheets. Deprecated. I have seen so many bad uses of style sheets it makes me want to cry out in anger. So just don't use them unless there's no other way to do it. They are almost guaranteed to cause compatibility problems. The problem is that some bonehead writes a style sheet that makes a webpage look good on *their* computer. To hell with everybody else who doesn't have the same monitor, resolution, fonts, browser, etc. The one thing they are "good" for is making themes but be careful that it's still ledgible on other machines. I have them turned off in my browser. At 10:50 PM 12/29/03 -0600, Michael D Schleif wrote: >Please, somebody point me to URL's that provide examples and best >practices of using CSS2, CGI.pm and XHTML v1.x. > >-- >Best Regards, -- REMEMBER THE WORLD TRADE CENTER ---=< WTC 911 >=-- "...ne cede males" 00000100 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
