I think what aki means by "not purely html" is a situation where you have to generate html code from a server-side language .. something like `echo "<div class='left-pane'>content</div>"`. The simple answer is that you dont actually have to and that in fact you should never ever (eeever!). The long answer is to use an mvc pattern or framework. You see an MVC pattern will allow you to write your html layouts/templates kando and then write php or asp or .net logic code without having to even care about a tag. This translates to being able to create different "views" for different browsers or clients while leveraging on the same server side code. Whereas it takes a bit of learning, if you are in this for good then its worth it: both for your street cred, speed of dev and for maintenance balaaz. My advise : if you are in webdev for the long haul then relax - get to fall in love with XHTML and CSS and maybe mvc if you like. They may seem uptight and unyielding at first but in the end you will be glad you made their acquaintance ;-). If you were just "passing-by" - as in you just want sort out some specific problem and move on to other non-web stuff - then by all means, scratch your itch. In Kao we say that you kill a snake with the closest weapon, not the best one. On 11/12/2010, Jonas | Lamu Software <jonas@lamusoftware.com> wrote:
what do you mean by "not purely html"?
This article from 2006 is a good read explaining a div/css based three column layout: http://www.alistapart.com/articles/holygrail/
Keep all css rules in an external style sheet, use classes instead of styling elements individually.
On 12/11/2010 06:24 PM, aki wrote:
@Webmaster, I know this debate about getting serious on the the tables issue but is CSS not purely html? So if you were for eg doing some code in eg php for some function, is the CSS formatting not going to be affected by this? An easier way would be to create the code in a Div tag and place the element. Div tags have very basic properties, how do you control the formatting and correct placement of the elements during run time in a 3 column layout? Applying the Style properties is really not the answer because it does not work, too much time wasted on tweeking where the elements land during runtime. HTML it seems has an uglier side when it come to code outside it scope, yet it cannot offer the same functionality that the code does. So what solution would you recommend for a 3 column layout for code that's not purely html but gets translated to html?
On Sat, Dec 11, 2010 at 6:07 PM, Webmaster wrote:
yes, it is absolutely worth it. Get serious and move on from 1996 tables
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke