I like it.
stiller mentions above that "... this approach looses something I really like about Template: solid visual clues to the web-designers about what they must not change..." That's fine, because there are plenty of solutions out there that are geared towards the web designer and programmer being separate. This is a neat solution for those who are doing both ends of the design, as it eliminates the interim templating language step.
Like you, I never had the patience to learn a templating module beyond the simple (but great) HTML::Template. That's not too ideal because for some things that HTML::Template doesn't handle, I end up mixing some HTML into my Perl and outputting that into the template.
Again, I like it, and think it would be a good solution for people who do both the web design and the programming but want to keep their HTML and Perl somewhat separate.
In reply to Re: RFC - Template::Empty
by amarquis
in thread RFC - Template::Empty
by redhotpenguin
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |