Enforcing strict model-view separation in template engines Export

@inproceedings{citeulike:1086778, abstract = {The mantra of every experienced web application developer is the same: thou shalt separate business logic from display . Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development. This situation is due mostly to a lack of formal definition of separation and fear that enforcing separation emasculates a template's power. I show that not only is strict separation a worthy design principle, but that we can enforce separation while providing a potent template engine. I demonstrate my StringTemplate engine, used to build jGuru.com and other commercial sites, at work solving some nontrivial generational tasks.My goal is to formalize the study of template engines, thus, providing a common nomenclature, a means of classifying template generational power, and a way to leverage interesting results from formal language theory. I classify three types of restricted templates analogous to Chomsky's type 1..3 grammar classes and formally define separation including the rules that embody separation.Because this paper provides a clear definition of model-view separation, template engine designers may no longer blindly claim enforcement of separation. Moreover, given theoretical arguments and empirical evidence, programmers no longer have an excuse to entangle model and view.}, address = {New York, NY, USA}, author = {Parr, Terence J.}, booktitle = {WWW '04: Proceedings of the 13th international conference on World Wide Web}, citeulike-article-id = {1086778}, citeulike-linkout-0 = {http://portal.acm.org/citation.cfm?id=988703}, citeulike-linkout-1 = {http://dx.doi.org/10.1145/988672.988703}, doi = {10.1145/988672.988703}, isbn = {1-58113-844-X}, keywords = {engines, programming, template, web}, location = {New York, NY, USA}, pages = {224--233}, posted-at = {2007-02-04 10:13:54}, priority = {0}, publisher = {ACM}, title = {Enforcing strict model-view separation in template engines}, url = {http://dx.doi.org/10.1145/988672.988703}, year = {2004} }

TY - CONF ID - citeulike:1086778 L3 - citeulike-article-id:1086778 N2 - The mantra of every experienced web application developer is the same: thou shalt separate business logic from display . Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development. This situation is due mostly to a lack of formal definition of separation and fear that enforcing separation emasculates a template's power. I show that not only is strict separation a worthy design principle, but that we can enforce separation while providing a potent template engine. I demonstrate my StringTemplate engine, used to build jGuru.com and other commercial sites, at work solving some nontrivial generational tasks.My goal is to formalize the study of template engines, thus, providing a common nomenclature, a means of classifying template generational power, and a way to leverage interesting results from formal language theory. I classify three types of restricted templates analogous to Chomsky's type 1..3 grammar classes and formally define separation including the rules that embody separation.Because this paper provides a clear definition of model-view separation, template engine designers may no longer blindly claim enforcement of separation. Moreover, given theoretical arguments and empirical evidence, programmers no longer have an excuse to entangle model and view. CY - New York, NY, USA SN - 1-58113-844-X AD - New York, NY, USA EP - 233 TI - Enforcing strict model-view separation in template engines PB - ACM T2 - WWW '04: Proceedings of the 13th international conference on World Wide Web SP - 224 KW - engines KW - programming KW - template KW - web AU - Parr, Terence PY - 2004/// UR - http://dx.doi.org/10.1145/988672.988703 ER -