BlueBream The Web Component Framework

9.2. Browser Page

9.2.1. Introduction

In the last chapter we have seen how to use resources HTML. The resource HTML will be only available on site-level with the @@ prefix. Where as browser pages are accessed with a single @ just before the page name.

Browser page (or more generically views) are representations for particular objects/components.

If you have a template like this (

Hello, World !

To register a page with the above template for an IFolder interface:


The browser:page directive is used to register browser pages. The name attribute specify the name of page which is used in the URL. The above page can be accessed from this URL: http://localhost:8080/@helloworld.html

9.2.2. View components

While templates display data view components are preparing data. View components convert data to output formats also prepare related data (meta-data). Then, create TAL-friendly object structures (dicts and lists). View components know about: component for which the representation is created (context) and request object holding all output media information (request) Implementation

The organization of the browser code is really up to you and the above examples are just the most basic rules of thumb.

Here is a simple view defined:

from zope.formlib import form
from zope.formlib import DisplayForm
from import IFolder

class HelloWorld(DisplayForm):

    form_fields = form.Fields(IHelloWorld)

    def subFolderIds(self):
        for name, subobj in self.context.items():
            if IFolder.providedBy(subobj):
                yield name

Since methods and attributes of the view component are directly used by the template, they should return simple iterable objects (e.g. lists, tuples, generators) or mappings (e.g. dicts).

9.2.3. Conclusion

This chapter introduced Browser pages.

blog comments powered by Disqus

Table Of Contents

Previous topic

9.1. Browser Resource

Next topic

9.3. Zope Page Templates

This Page