On 9/26/01 5:40 PM, "Roy T. Fielding" <[EMAIL PROTECTED]> wrote:
>> My point was that alteration of the model from within the template to me is
>> a violation of MVC but is deemed all right by Jon because it's a 'template
>> engineer' doing this. That's the part I don't buy. Hand those templates
>> you've worked on to a designer and I think you would be pretty much hosed.
>> Some just can't understand and the talented one's don't really feel it's
>> their job to have to deal with any logical constructs.
>
> That would make it pretty difficult to do what I did with Anakia on the
> site transformations. We walk the tree and transform only those elements
> and attributes that need to be transformed, allowing the remainder to
> pass through. If the context is read only, then we would have to copy
> the entire tree in memory first. That would suck.
Velocity used in the context of a tool like Anakia to me is a different
sitution. I was talking strictly in the sense of a webapp where the people
who are dealing with the view have a vague concept of programming at best.
In tools like Torque (and Anakia) a great deal of logic is performed in the
templates and I really like that (I put most of it there), but it is
understood that these templates are a convenient way to alter some logic
without having to recompile. If they are slightly hackish it probably
doesn't matter a great deal. But templates with the same degree complexity
thrown at a designer would probably make them cringe and cause them to throw
sharp objects at programmers passing by.
> ....Roy
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
