Also, every framework is necessarily limited in terms of the number of components
that come pre-packaged with it. Now and again we shall find that the component
we need wasn't created by anyone. Or maybe the existing component just doesn't
fit our needs, or the requirements of our clients. A developer friendly framework
should provide an opportunity to easily extend it by being able to creating custom
components. Tapestry does just this.
In particular, we are going to learn:
What it takes to create a Tapestry 5 component.
How to create a Border component that will contain all the elements
common for all the pages and that will provide an easy way to ensure a
common layout.
How to unleash the power of the Select component by creating a
custom model.
How to create an alternative component for date input that consists of three
Select components.
How to create a universal locale switcher that will automatically adapt to
those locales that are supported by the application.
How to create a custom Tapestry service if the existing services do not
provide the functionality we need.
How to package custom components into a library and make them available
for everyone.
??? ??? ??? ??? ??? ??? ???
Creating Custom Components
[ 196 ]
How to Create a Tapestry 5 Component
In fact, components in Tapestry 5 are very similar to pages.
Pages:
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248