> Darko Krizic <[EMAIL PROTECTED]> wrote:
> > ...
> > <table id="results">
> > <tr id="resultheader">
> > <th>Name</th>
> > <th>Count</th>
> > </tr>
> > <tr id="singlerow>
> > <td id="row_name">example name</td>
> > <td id="row_count">example count</td>
> > </tr>
> > </table>
> > ...
> > The problem with many templating systems is the fact that
> they invent a new
> > language like "<td>$variable</td>" which is usually not
> displayable in the
> > Browser so that the designer and the programmer must work tightly.
>
> The designer has to learn 'id="row_name"' in one case, and
> $row_name in
> the other. I'd say that the need to work tightly with the
> programmer is
> pretty much the same: you have to agree on a syntax for gaps that code
> can fill, and on the names of the individual gaps.
There is one big difference in the enhydra approach: The templates are
standard HTML, because the id tag is part of the HTML standard. The designer
can create the whole site and make a dry test, because all links even work.
The tags (with ids) can contain valid values.
...darko
