This was another way of passing information from one page to another. Now let's
return to how we define components on the pages??”there are a few different ways to
do that too.
Different Ways of Defining Components
So far, we have seen just one approach to defining a component on a page??”by using
an XML element in the Tapestry namespace, like this:
The Foundations of Tapestry
[ 68 ]
However, this simple approach has a downside. If we preview the Start page
template in a web browser, we'll see something similar to this:
.
It is not a problem that the values to be inserted into the page are replaced by
expansions. This is a static preview, after all. What is worse, some components have
simply disappeared. We do not see the link to the Another page, and there is no
text box.
This means that when we are declaring components as shown above, we are losing
the ability to preview the page template in a web browser and to continue editing it
using common HTML editors like Dreamweaver.
This might not be a big deal if you are creating both templates and page classes
on your own and if the design of the page is not too complicated. However, web
applications are often developed by a mixed team where designers work on
templates while developers concentrate on page classes.
Pages:
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99