|
you can't be so close minded. vbulletin among many other Web Applications are a perfect example of CSS data being stored in a database.
i've written several web apps which give a user control to modify colors, font sizes, and other CSS attributes. these parameters get stored in a database.
programming my database values to modify the layout inline vs a single dynamic style sheet would be REDICULOUS!! this would be a nightmare to maintain.
your load time argument is seriously flawed also. a dynamic style sheet would be a smaller size to load vs putting style tags in every div you use since there would be a LOT more DHTML to load into the browser.
when was the last time you were worried about a couple of MS for a style sheet to load?? i mean huge bloated dhtml drop downs can get pretty bad sometimes, but if you are just making a little style sheet, the user is not going to notice a difference. ( especially considering my point that you would be loading a lot more html if you coded all style attributes inline )
whether your CSS attributes are in a style sheet or inline, if your page is PHP, then the server call is being made anyway. lol, i keep thinking wtf! as i write this. anyway what about my question .. what do you use PHP/MySQL for?
i would say your argument is completely invalid. take the scope of what he, or anyone else making a dynmic style sheet into context.
the only suggestion you have proposed as an alternative to dynamic style sheets is coding all your style tags inline which i can not believe someone as experienced as yourself would suggest.
__________________
Mike
|