<h3>hello</h3>
… in Seaside you write: html heading level: 3; with: 'hello'.
ouch. <h3>hello</h3>
… in Seaside you write: html heading level: 3; with: 'hello'.
ouch.P.S. We, CLers, had various html-embedding formats battle it out over the years and it seems like CL-WHO won.
(:h3 "Hello)But, I've worked with many a developer who couldn't tell you why divs differ from spans.
Still think of the HTML in the same vein has producing JSON, XML, etc. The CSS is then just the design logic maintained (hopefully!) by the designer.
But there are many advantages to this way of having the html as smalltalk code. You can use the same refactoring tools you use on code to refactor your html. You use the same abstraction and composition mechanisms to structure your html. You use the same control structures for you html than for your code (which are very clear in smalltalk). You can put some html in a method and reuse it in many places, it's also easy for easier to create your own components or tags in seaside than it is in other web component frameworks I have used.
Its like:
html {
h3 { 'hello' }
}
... in Markapl (Perl) or Markaby (Ruby).Much nicer to build (display|markup) logic here than with HTML template methinks.