{ "info": { "author": "Zope Corporation and Contributors", "author_email": "zope3-dev@zope.org", "bugtrack_url": null, "classifiers": [ "Development Status :: 5 - Production/Stable", "Environment :: Web Environment", "Framework :: Zope3", "Intended Audience :: Developers", "License :: OSI Approved :: Zope Public License", "Natural Language :: English", "Operating System :: OS Independent", "Programming Language :: Python", "Topic :: Internet :: WWW/HTTP" ], "description": "This package allows us to separate the registration of the view code and the\nview templates.\n\nWhy is this a good thing?\n\nWhile developing customizable applications that require us to develop multiple\ncustomer UIs for one particular application, we noticed there is a fine but\nclear distinction between skins and layers. Layers contain the logic to\nprepare data for presentation output, namely the view classes. Skins, on the\nother hand contain the resources to generate the UI, for example templates,\nimages and CSS files.\n\nThe problem of the existing infrastructure is that code, template and layer\nare all hardlinked in one zcml configuration directive of the view component\n-- page, content provider, viewlet. This package separates this triplet --\ncode, template, layer -- into two pairs, code/layer and template/skin. No\nadditional components are introduced, since skins and layers are physically\nthe same components.\n\n\n\nDetailed Dcoumentation\n======================\n\n\n============\nViewTemplate\n============\n\nThis package allows us to separate the registration of the view code and the\nview templates.\n\nWhy is this a good thing?\n\nWhile developing customizable applications that require us to develop multiple\ncustomer UIs for one particular application, we noticed there is a fine but\nclear distinction between skins and layers. Layers contain the logic to\nprepare data for presentation output, namely the view classes. Skins, on the\nother hand contain the resources to generate the UI, for example templates,\nimages and CSS files.\n\nThe problem of the existing infrastructure is that code, template and layer\nare all hardlinked in one zcml configuration directive of the view component\n-- page, content provider, viewlet. This package separates this triplet --\ncode, template, layer -- into two pairs, code/layer and template/skin. No\nadditional components are introduced, since skins and layers are physically\nthe same components.\n\nBefore we can setup a view component using this new method, we have to first\ncreate a template ...\n\n >>> import os, tempfile\n >>> temp_dir = tempfile.mkdtemp()\n >>> template = os.path.join(temp_dir, 'demoTemplate.pt')\n >>> open(template, 'w').write('''