in reply to Re: RFC - Template::Empty
in thread RFC - Template::Empty
the display-preparation is simply shifted into Perl, and HTML-generation is reduced to a perfunctory, “empty,” non-task.HTML is empty and a non-task... HTML-generation is not empty at all. How can you call writing methods to manipulate HTML empty?
and what you call a "simple shift" from pull style to push style is proven to create a more powerful templating system: the weakest push-style system is the strongest pull-style...
In a curious way, I think that the approach you are recommending here does “interleave” these two concerns, in an improper way. It is simply the opposite-extreme: the display-preparation is simply shifted into Perl, and HTML-generation is reduced to a perfunctory, “empty,” non-task.What you call the "opposite-extreme" is actually best practice for data processing: processor and processed are completely separated, allowing flexible object-oriented composition.
Processing HTML need be no different than best practice for XML, databases, LDAP and so on .
But I am the person running Wordpress blogs, and drooling over Drupal for all of my personal sites. So while we both agree from a philosophical standpoint on how "WRONG" PHP is, we really both need to shut up and out-deliver. When we have useable web products on par with PHP, then our products can do the talking instead of the idle and empty chatter we are engaging in here.
| I have beheld the tarball of 22.1 on ftp.gnu.org with my own eyes. How can you say that there is no God in the Church of Emacs? -- David Kastrup |
|
| Enforce strict model-view separation in template engines via HTML::Seamstress | The car is in the cdr, not the cdr in the car |
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: all data munging is push style templating
by Rhandom (Curate) on Feb 25, 2008 at 16:49 UTC |