in reply to Re: Re: The scope of templates
in thread I need a title - sucka! :-)

Mine view is that it is not about separation of code and data - but rather about separation of business logic and presentation. This is a valid line of separation. Presentation beside pure visual treats does include some logic and thats why logic is supported by the templating solutions.

Replies are listed 'Best First'.
Re: Re: Re: Re: The scope of templates
by PetaMem (Priest) on Dec 01, 2003 at 14:27 UTC
    Actually I agree with *this*. If there is a justification to export code (not just static content plus some "interpolation") to a templating system, it might be exact for this reason.

    But I have a hard time to see where it would improve maintainability, because then in order to change the presentation layer (template) you have to send your programmers too. (One of the arguments was, that templates don't need programmers. More precisely - the work on (changing) templates.)

    And as for the programmers: I have an *extremely* hard time to see where this code splattering would improve readability.

    Bye
     PetaMem
        All Perl:   MT, NLP, NLU

      It is all about choosing the right tool for the job. The presentation layer is so much different from the business logic layer that it is usefull to have a different language to code it. And with a big and complicated project the cost of introducing a new language will be justified by the big chunk of such coding.