20. Writing Viewlets¶
A viewlet for the social behavior¶
A viewlet is not a view but a snippet of html and logic that can be put in various places in the site. These places are called viewletmanager
.
- Inspect existing viewlets and their managers by going to http://localhost:8080/Plone/@@manage-viewlets.
- We already customized a viewlet (
collophon.pt
). Now we add a new one. - Viewlets don’t save data (portlets do)
- Viewlets have no user-interface (portlets do)
Exercise 1¶
Register a viewlet ‘number_of_talks’ in the footer that is only visible to admins (the permission you are looking for is cmf.ManagePortal
). Use only a template (no class) to display the number of talks already submitted. Hint: Use Aquisition to get the catalog (You know, you should not do this but there is plenty of code out there that does it...)
Solution
Register the viewlet in browser/configure.zcml
<browser:viewlet
name="number_of_talks"
for="*"
manager="plone.app.layout.viewlets.interfaces.IPortalFooter"
layer="zope.interface.Interface"
template="templates/number_of_talks.pt"
permission="cmf.ManagePortal"
/>
For the for
and layer
-parameters *
is shorthand for zope.interface.Interface
and the same effect as omitting them: The viewlet will be shown for all types of pages and for all Plone sites within your Zope instance.
Add the template browser/templates/number_of_talks.pt
:
<div class="number_of_talks"
tal:define="catalog python:context.portal_catalog;
talks python:len(catalog(portal_type='talk'));">
There are <span tal:replace="talks" /> talks.
</div>
python:context.portal_catalog
will return the catalog through Acquisition. Be carefull if you want to use path-expressions: content/portal_catalog
calls the catalog (and returns all brains). You need to prevent this by using nocall:content/portal_catalog
.
Relying on Acquisition is a bad idea. It would be much better to use the helper view plone_tools
from plone/app/layout/globals/tools.py
to get the catalog.
<div class="number_of_talks"
tal:define="catalog context/@@plone_tools/catalog;
talks python:len(catalog(portal_type='talk'));">
There are <span tal:replace="talks" /> talks.
</div>
context/@@plone_tools/catalog
traverses to the view plone_tools
and calls it’s method catalog
. In python it would look like this:
<div class="number_of_talks"
tal:define="catalog python:context.restrictedTraverse('plone_tools').catalog();
talks python:len(catalog(portal_type='talk'));">
There are <span tal:replace="talks" /> talks.
</div>
It is not a good practice to query the catalog within a template since even simple logic like this should live in Python. But it is very powerful if you are debugging or need a quick and dirty solution.
Exercise 2¶
Register a viewlet ‘days_to_conference’ in the header. Use a class and a template to display the number of days until the conference. You get many bonus-points if you display it in a nice format (think “In 2 days” and “Last Month”) by using an existing javascript or python library.
social-viewlet¶
Let’s add a link to the site that uses the information that we collected using the social-behavior.
We register the viewlet in
browser/configure.zcml
.This registers a viewlet called
social
. It is visible on all content that implements the interfaceISocial
from our behavior. It is also good practice to bind it to the BrowserLayerIPloneconfSiteLayer
of our addon so it only shows up if our addon is actually installed.The viewlet-class
SocialViewlet
is expected in a filebrowser/viewlets.py
.This class does nothing except rendering the associated template (That we have to write yet)
Note
If we used
grok
we would not need to register the viewlets in theconfigure.zcml
but do that in python. We would add a file viewlets.py containing the viewlet-class.This would do the same as the coe above using grok’s paradigm of convention over configuration. In browser views the reference is called view, note that in grok viewlets it is called viewlets (in that case
viewlet/lanyrd_link
).Let’s add the missing template
templates/social_viewlet.pt
.As you can see this is not a valid html document. That is not needed, because we don’t want a complete view here, just a html snippet.
There is a tal define statement, querying for view/lanyrd_link. Like in page templates the template has access to its class.
We have to extend the Social Viewlet now to add the missing attribute:
Why not to access context directly
In this example,
ISocial(self.context)
does return the context directly. It is still good to use this idiom for two reasons:Therefore in this example you could simply write
return self.context.lanyrd
.So far, we