>
> I've never in this situation (building an app from a "finished" HTML
> mockup), but I'll add my two cents anyway.
>
> I don't think the Nevow syntax would be harder, assuming you get XHTML
> from the Web designer, or you can Tidy her work: it's just an XML
> parser away.
>
> I think that strict adherence to standards is the real issue here. I
> would hope that the designer is writing in plain, strict XHTML and
> using CSS for visual look-and-feel. If I had any influence in the
> project, I would mandate it. It wouldn't be hard to adapt the XHTML
> into either PTL or Nevow bracket-expressions. Or you could go the
> external-file route that Donovan described, using Newvow itself (or
> ZPT, or any of the gazillion embedded-logic templating schemes, I
> guess).
>
> If structure can be mostly-frozen early in the project, then you
> shouldn't have too many round-trips: structure is all you need to
> worry about. While you're coding the logic, the designer can tweak the
> CSS in parallel until the cows come home.
>
> If the Web designer isn't writing in structural HTML with CSS... well,
> may God help the programmer (I hope it's not me)! I think you'll get a
> mess no matter what the chosen solution.
>

My two cents are a little off topic, but I just can't hold it :) The
best part of  professional designed website is that it looks great and
(unfortunately) not the validity of HTML/CSS.  I am afraid, as long as
commercial websites will be build, there will be a messy HTML with (for
example) silly transparated gifs instead of CSS "padding", just because
the  client's target group is still using Netscape 4  :-/