At 11/30/2006 01:52 AM, Satyam wrote:
And, stepping back, you're perpetuating the embedding of markup
with logic so that it will still take a PHP programmer to modify
the markup of one of your pages. Do you not see the advantage in
separating the two layers?
Yes, I do, and I would recommend using templates or similar tools
to provide for separation of code and markup, but sometimes there
are reasons not to do so, for example, web services.
Please explain why you think web services promote mixing markup with logic.
I didn't say it promotes but it does not require. In web services
there is usually no presentation layer, there is no end user to see
anything at all, then there is no need for a graphics designer
separate from the application programmer. The application consuming
that service might have to display the data, but the service does not.
To reach clarity on this point, let's leave presentation out of
it. I was referring to the separation of presentation from markup
merely to suggest an analagous separation that many of us have
accepted as being helpful to design, development, and
maintenance. What I'm really curious about in this discussion is the
separation of markup from logic.
With respect to separating code and markup, you said "sometimes there
are reasons not to do so, for example, web services." What are some
of those reasons?
Cheers,
Paul
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
