z3c.macro

Archived

This project has been archived by its maintainers, and is no longer receiving any updates.

https://travis-ci.org/zopefoundation/z3c.macro.svg?branch=master

https://coveralls.io/repos/github/zopefoundation/z3c.macro/badge.svg?branch=master

This package provides an adapter and a TALES expression for a more explicit and more flexible macro handling using the adapter registry for macros.

Detailed Documentation

Macro

This package provides a adapter and a TALES expression for a expliciter and flexibler macro handling using the adapter registry for macros.

We start with creating a content object that is used as a view context later:

>>> import zope.interface
>>> import zope.component
>>> from zope.publisher.interfaces.browser import IBrowserView
>>> from zope.publisher.interfaces.browser import IDefaultBrowserLayer
>>> @zope.interface.implementer(zope.interface.Interface)
... class Content(object):
...     pass

>>> content = Content()

We also create a temp dir for sample templates which we define later for testing:

>>> import os, tempfile
>>> temp_dir = tempfile.mkdtemp()

Macro Template

We define a macro template as a adapter providing IMacroTemplate:

>>> path = os.path.join(temp_dir, 'navigation.pt')
>>> with open(path, 'w') as file:
...     _ = file.write('''
... <metal:block define-macro="navigation">
...   <div tal:content="title">---</div>
... </metal:block>
... ''')

Let’s define the macro factory

>>> from z3c.macro import interfaces
>>> from z3c.macro import zcml
>>> navigationMacro = zcml.MacroFactory(path, 'navigation', 'text/html')

and register them as adapter:

>>> zope.component.provideAdapter(
...     navigationMacro,
...     (zope.interface.Interface, IBrowserView, IDefaultBrowserLayer),
...     interfaces.IMacroTemplate,
...     name='navigation')

The TALES macro Expression

The macro expression will look up the name of the macro, call a adapter providing IMacroTemplate and uses them or fills a slot if defined in the macro expression.

Let’s create a page template using the navigation macros:

>>> path = os.path.join(temp_dir, 'first.pt')
>>> with open(path, 'w') as file:
...     _ = file.write('''
... <html>
...   <body>
...     <h1>First Page</h1>
...     <div class="navi">
...       <tal:block define="title string:My Navigation">
...         <metal:block use-macro="macro:navigation" />
...       </tal:block>
...     </div>
...     <div class="content">
...       Content here
...     </div>
...   </body>
... </html>
... ''')

As you can see, we used the macro expression to simply look up a macro called navigation whihc get inserted and replaces the HTML content at this place.

Let’s now create a view using this page template:

>>> from zope.publisher.browser import BrowserView
>>> class simple(BrowserView):
...     def __getitem__(self, name):
...         return self.index.macros[name]
...
...     def __call__(self, **kwargs):
...         return self.index(**kwargs)

>>> from zope.browserpage.viewpagetemplatefile import ViewPageTemplateFile
>>> def SimpleViewClass(path, name=u''):
...     return type(
...         "SimpleViewClass", (simple,),
...         {'index': ViewPageTemplateFile(path), '__name__': name})

>>> FirstPage = SimpleViewClass(path, name='first.html')

>>> zope.component.provideAdapter(
...     FirstPage,
...     (zope.interface.Interface, IDefaultBrowserLayer),
...     zope.interface.Interface,
...     name='first.html')

Finally we look up the view and render it:

>>> from zope.publisher.browser import TestRequest
>>> request = TestRequest()

>>> view = zope.component.getMultiAdapter((content, request),
...                                       name='first.html')
>>> print(view().strip())
<html>
  <body>
    <h1>First Page</h1>
    <div class="navi">
      <div>My Navigation</div>
    </div>
    <div class="content">
      Content here
    </div>
  </body>
</html>

Slot

We can also define a macro slot and fill it with given content:

>>> path = os.path.join(temp_dir, 'addons.pt')
>>> with open(path, 'w') as file:
...     _ = file.write('''
... <metal:block define-macro="addons">
...   Content before header
...   <metal:block define-slot="header">
...     <div>My Header</div>
...   </metal:block>
...   Content after header
... </metal:block>
... ''')

Let’s define the macro factory

>>> addonsMacro = zcml.MacroFactory(path, 'addons', 'text/html')

and register them as adapter:

>>> zope.component.provideAdapter(
...     addonsMacro,
...     (zope.interface.Interface, IBrowserView, IDefaultBrowserLayer),
...     interfaces.IMacroTemplate,
...     name='addons')

Let’s create a page template using the addons macros:

>>> path = os.path.join(temp_dir, 'second.pt')
>>> with open(path, 'w') as file:
...     _ = file.write('''
... <html>
...   <body>
...     <h1>Second Page</h1>
...     <div class="header">
...       <metal:block use-macro="macro:addons">
...         This line get ignored
...         <metal:block fill-slot="header">
...           Header comes from here
...         </metal:block>
...         This line get ignored
...       </metal:block>
...     </div>
...   </body>
... </html>
... ''')

Let’s now create a view using this page template:

>>> SecondPage = SimpleViewClass(path, name='second.html')

>>> zope.component.provideAdapter(
...     SecondPage,
...     (zope.interface.Interface, IDefaultBrowserLayer),
...     zope.interface.Interface,
...     name='second.html')

Finally we look up the view and render it:

>>> view = zope.component.getMultiAdapter((content, request),
...                                       name='second.html')
>>> print(view().strip())
<html>
  <body>
    <h1>Second Page</h1>
    <div class="header">
<BLANKLINE>
  Content before header
<BLANKLINE>
          Header comes from here
<BLANKLINE>
  Content after header
    </div>
  </body>
</html>

Cleanup

>>> import shutil
>>> shutil.rmtree(temp_dir)

macro directive

A macro directive can be used for register macros. Take a look at the README.txt which explains the macro TALES expression.

>>> import sys
>>> from zope.configuration import xmlconfig
>>> import z3c.template
>>> context = xmlconfig.file('meta.zcml', z3c.macro)

First define a template which defines a macro:

>>> import os, tempfile
>>> temp_dir = tempfile.mkdtemp()
>>> file_path = os.path.join(temp_dir, 'file.pt')
>>> with open(file_path, 'w') as file:
...     _ = file.write('''
... <html>
...   <head>
...     <metal:block define-macro="title">
...        <title>Pagelet skin</title>
...     </metal:block>
...   </head>
...   <body>
...     <div>content</div>
...   </body>
... </html>
... ''')

and register the macro provider within the z3c:macroProvider directive:

>>> context = xmlconfig.string("""
... <configure
...     xmlns:z3c="http://namespaces.zope.org/z3c">
...   <z3c:macro
...       template="%s"
...       name="title"
...       />
... </configure>
... """ % file_path, context=context)

We need a content object…

>>> import zope.interface
>>> @zope.interface.implementer(zope.interface.Interface)
... class Content(object):
...     pass
>>> content = Content()

and we need a view…

>>> import zope.interface
>>> import zope.component
>>> from zope.publisher.browser import BrowserPage
>>> class View(BrowserPage):
...     def __init__(self, context, request):
...         self.context = context
...         self.request = request

and we need a request:

>>> from zope.publisher.browser import TestRequest
>>> request = TestRequest()

Check if we get the macro template:

>>> from z3c.macro import interfaces
>>> view = View(content, request)

>>> macro = zope.component.queryMultiAdapter((content, view, request),
...     interface=interfaces.IMacroTemplate, name='title')

>>> macro is not None
True

>>> import os, tempfile
>>> temp_dir = tempfile.mkdtemp()
>>> test_path = os.path.join(temp_dir, 'test.pt')
>>> with open(test_path, 'w') as file:
...     _ = file.write('''
... <html>
...   <body>
...     <metal:macro use-macro="options/macro" />
...   </body>
... </html>
... ''')

>>> from zope.browserpage.viewpagetemplatefile import BoundPageTemplate
>>> from zope.browserpage.viewpagetemplatefile import ViewPageTemplateFile
>>> template = ViewPageTemplateFile(test_path)
>>> print(BoundPageTemplate(template, view)(macro=macro))
<html>
  <body>
    <title>Pagelet skin</title>
  </body>
</html>

Error Conditions

If the file is not available, the directive fails:

>>> context = xmlconfig.string("""
... <configure
...     xmlns:z3c="http://namespaces.zope.org/z3c">
...   <z3c:macro
...       template="this_file_does_not_exist"
...       name="title"
...       />
... </configure>
... """, context=context)
Traceback (most recent call last):
...
zope.configuration.exceptions.ConfigurationError: ...

CHANGES

2.2.1 (2018-12-05)

Fix list of supported Python versions in Trove classifiers: The currently supported Python versions are 2.7, 3.6, 3.7, PyPy2 and PyPy3.
Flake8 the code.

2.2.0 (2018-11-13)

Removed Python 3.5 support, added Python 3.7.
Fixed up tests.
Fix docstring that caused DeprecationWarning.

2.1.0 (2017-10-17)

Drop support for Python 2.6 and 3.3.
Add support for Python 3.4, 3.5 and 3.6.
Add support for PyPy.

2.0.0 (2015-11-09)

Standardize namespace __init__.

2.0.0a1 (2013-02-25)

Added support for Python 3.3.
Replaced deprecated zope.interface.implements usage with equivalent zope.interface.implementer decorator.
Dropped support for Python 2.4 and 2.5.

1.4.2 (2012-02-15)

Remove hooks to use ViewPageTemplateFile from z3c.pt because this breaks when z3c.pt is available, but z3c.ptcompat is not included. As recommended by notes in 1.4.0 release.

1.4.1 (2011-11-15)

bugfix, missing comma in setup install_requires list

1.4.0 (2011-10-29)

Moved z3c.pt include to extras_require chameleon. This makes the package independent from chameleon and friends and allows to include this dependencies in your own project.
Upgrade to chameleon 2.0 template engine and use the newest z3c.pt and z3c.ptcompat packages adjusted to work with chameleon 2.0.

See the notes from the z3c.ptcompat package:

Update z3c.ptcompat implementation to use component-based template engine configuration, plugging directly into the Zope Toolkit framework.

The z3c.ptcompat package no longer provides template classes, or ZCML directives; you should import directly from the ZTK codebase.

Note that the PREFER_Z3C_PT environment option has been rendered obsolete; instead, this is now managed via component configuration.

Also note that the chameleon CHAMELEON_CACHE environment value changed from True/False to a path. Skip this property if you don’t like to use a cache. None or False defined in buildout environment section doesn’t work. At least with chameleon <= 2.5.4

Attention: You need to include the configure.zcml file from z3c.ptcompat for enable the z3c.pt template engine. The configure.zcml will plugin the template engine. Also remove any custom built hooks which will import z3c.ptcompat in your tests or other places.

1.3.0 (2010-07-05)

Tests now require zope.browserpage >= 3.12 instead of zope.app.pagetemplate as the expression type registration has been moved there recently.
No longer using deprecated zope.testing.doctestunit but built-in doctest instead.

1.2.1 (2009-03-07)

Presence of z3c.pt is not sufficient to register macro-utility, chameleon.zpt is required otherwise the factory for the utility is not defined.

1.2.0 (2009-03-07)

Allow use of z3c.pt using z3c.ptcompat compatibility layer.
Change package’s mailing list address to zope-dev at zope.org.

1.1.0 (2007-11-01)

Update package info data.
Add z3c namespace package declaration.

1.0.0 (2007-09-30)

Initial release.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

z3c.macro-2.2.1.tar.gz (16.1 kB view details)

Uploaded Dec 5, 2018 Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

z3c.macro-2.2.1-py2.py3-none-any.whl (20.0 kB view details)

Uploaded Dec 5, 2018 Python 2Python 3

File details

Details for the file z3c.macro-2.2.1.tar.gz.

File metadata

Download URL: z3c.macro-2.2.1.tar.gz
Upload date: Dec 5, 2018
Size: 16.1 kB
Tags: Source
Uploaded using Trusted Publishing? No
Uploaded via: twine/1.10.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.19.7 CPython/2.7.15

File hashes

Hashes for z3c.macro-2.2.1.tar.gz
Algorithm	Hash digest
SHA256	`0caa0fe0e83095f71ae283aeb03ac210d7df50588e9034d07a7bd817eccef989`
MD5	`a53e030917cdb12b4ef6812e4a599724`
BLAKE2b-256	`b911b6c0c81794b427bb1cacb873ed54360f8eabaf78ab2cb4136de69a43f9d3`

See more details on using hashes here.

File details

Details for the file z3c.macro-2.2.1-py2.py3-none-any.whl.

File metadata

Download URL: z3c.macro-2.2.1-py2.py3-none-any.whl
Upload date: Dec 5, 2018
Size: 20.0 kB
Tags: Python 2, Python 3
Uploaded using Trusted Publishing? No
Uploaded via: twine/1.10.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.19.7 CPython/2.7.15

File hashes

Hashes for z3c.macro-2.2.1-py2.py3-none-any.whl
Algorithm	Hash digest
SHA256	`c9c3243e0f73a3061c5c315d6dae6c332aca6868c42c56cd4ff2971a936c0620`
MD5	`494ebee636ced1b680cdd866653690d9`
BLAKE2b-256	`1aaace93a465d30fc2c671444db8e54f821c0289c8e4c906520cc4cd597b463f`

See more details on using hashes here.

Release history Release notifications | RSS feed

3.1 archived

Feb 14, 2025

3.0 archived

Jan 11, 2024

2.3 archived

Dec 16, 2021

This release

2.2.1 archived

Dec 5, 2018

2.2.0 archived

Nov 13, 2018

2.1.0 archived

Oct 17, 2017

2.0.0 archived

Nov 9, 2015

2.0.0a1 archived

Feb 25, 2013

1.4.2 archived

Feb 15, 2012

1.4.1 archived

Nov 15, 2011

1.4.0 archived

Oct 29, 2011

1.3.0 archived

Jul 5, 2010

1.2.1 archived

Mar 7, 2009

1.2.0 archived

Mar 6, 2009

1.1.0 archived

Nov 1, 2007

1.0.0 archived

May 22, 2007

z3c.macro 2.2.1

Detailed Documentation

Macro

Macro Template

The TALES macro Expression

Slot

Cleanup

macro directive

Error Conditions

CHANGES

2.2.1 (2018-12-05)

2.2.0 (2018-11-13)

2.1.0 (2017-10-17)

2.0.0 (2015-11-09)

2.0.0a1 (2013-02-25)

1.4.2 (2012-02-15)

1.4.1 (2011-11-15)

1.4.0 (2011-10-29)

1.3.0 (2010-07-05)

1.2.1 (2009-03-07)

1.2.0 (2009-03-07)

1.1.0 (2007-11-01)

1.0.0 (2007-09-30)

Project links

Key dates

Owner

24 maintainers

Credits

License

Tags

Classifiers

Download files

Source Distribution

Built Distribution

File details

File metadata

File hashes

File details

File metadata

File hashes

Release history Release notifications | RSS feed