top | item 4763992

(no title)

akdetrick | 13 years ago

The looks like a joy to write, and a nightmare to maintain. I may be old fashioned, but I still see content, style, and behavior as best expressed as separate concerns in source.

discuss

order

vidarh|13 years ago

Not to mention that for any project where you end up getting a designer involved, odds are pretty high that designer will end up handing you plain HTML and CSS.

It's often hard enough to find designers that'll work well with templates that are relatively unobtrusively combined with plain HTML.

Have fun converting back and forth.

lmm|13 years ago

I don't see the use for CSS; it's not powerful enough to express your styling, so you always need some kind of programmatic processor that generates it (whether in javascript or some other language), at which point you might as well have that same program apply styling directly to your elements.

But yeah, I'd rather have strong separation of markup and behaviour. I love the wicket approach to this (your templates are plain html; the only thing you can add to them is identifiers that mark a tag as being replaced by a component; all logic goes in the code), and wish I could find a templating engine for more modern technologies that used the same approach.

talmand|13 years ago

No use for CSS? CSS not powerful enough to express styling? Huh?

You want to get rid of CSS for styling and replace it with something else for styling? Wha?

The processors you speak of output CSS. They do nothing that cannot already be done with CSS, they just make it easier. Plus, when using javascript to apply styles you are still using CSS, you are just applying it in a different way.