Tapestry 5: Building Web Applications

Prev | Current Page 141 | Next

Alexander Kolesnikov

"Tapestry 5: Building Web Applications"

Simple Components
[ 112 ]
The reversed version of the same logic works for the value property of the
TextField component. If there is no prefix (like t:value="userName"), Tapestry
will be looking for an appropriately named property of the page class, as the default
prefix is prop. However, if for some reason we wanted to treat this value as literal,
we would have to use the literal prefix explicitly.
The If and Checkbox Components
Let's say during registration we want to give the users an opportunity to subscribe to
our newsletter. For this, we are going to add a check box to the registration form, like
the one shown here:
To make the interface slightly more complex, and also to give me an opportunity
to show you yet another component, let's say that as soon as the user clicks on the
check box, the check box should disappear, and a text box for accepting the user's
email should appear instead:
Here is a fragment of the page template that will do the job:

t:value="email"/>

t:value="subscribe"
onclick="this.

Pages:
129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153

Foundation Flex for Designers (page 136) Systems Engineering with SysML/UML: Modeling, Analysis, Design (page 824) Administering Windows Server 2008 Server Core (page 1196)

E-Books for you

Alexander Kolesnikov

"Tapestry 5: Building Web Applications"