https://pypi.org/project/z3c-viewtemplate/ Recent updates to the Python Package Index for z3c.viewtemplate en https://pypi.org/project/z3c-viewtemplate/0.4.1/ View Templates zope3-dev@zope.org Sun, 12 Dec 2010 16:46:14 GMT https://pypi.org/project/z3c-viewtemplate/0.4.0/ View Templates zope3-dev@zope.org Wed, 05 Nov 2008 15:12:21 GMT https://pypi.org/project/z3c-viewtemplate/0.3.2/ View Templates zope3-dev@zope.org Thu, 01 Nov 2007 20:03:27 GMT https://pypi.org/project/z3c-viewtemplate/0.3.1/ This package allows us to separate the registration of the view code and theview templates.Why is this a good thing?While developing customizable applications that require us to develop multiplecustomer UIs for one particular application, we noticed there is a fine butclear distinction between skins and layers. Layers contain the logic toprepare data for presentation output, namely the view classes. Skins, on theother hand contain the resources to generate the UI, for example templates,images and CSS files.The problem of the existing infrastructure is that code, template and layer are allhardlinked in one zcml configuration directive of the view component -- page,content provider, viewlet. This package separates this triplet -- code, template,layer -- into two pairs, code/layer and template/skin. No additionalcomponents are introduced, since skins and layers are physically the samecomponents. zope3-dev@zope.org Thu, 01 Nov 2007 19:57:02 GMT https://pypi.org/project/z3c-viewtemplate/0.3.0/ This package allows us to separate the registration of the view code and theview templates.Why is this a good thing?While developing customizable applications that require us to develop multiplecustomer UIs for one particular application, we noticed there is a fine butclear distinction between skins and layers. Layers contain the logic toprepare data for presentation output, namely the view classes. Skins, on theother hand contain the resources to generate the UI, for example templates,images and CSS files.The problem of the existing infrastructure is that code, template and layer are allhardlinked in one zcml configuration directive of the view component -- page,content provider, viewlet. This package separates this triplet -- code, template,layer -- into two pairs, code/layer and template/skin. No additionalcomponents are introduced, since skins and layers are physically the samecomponents. zope3-dev@zope.org Thu, 01 Nov 2007 19:55:00 GMT