Thank you Sam and Marcus for your responses.
Yes, I can do what you suggest. I still think it would be useful to
be able to declare application level components, so every page or
related component could refer to them without manual config..
In one sense, it's useful to create components for
And you could always componentize the part of your page which includes
the icons, allowing you to insert them into a page with a single line,
rather than lots of individual lines. Assuming they are grouped
conveniently, at least. If your component doesn't require lots of
parameters, you could pro
just say
in your html-template. No need for .page or .jwc for this
> -Original Message-
> From: Nick Faiz [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 08, 2006 4:28 AM
> To: Tapestry users
> Subject: configuring common components
>
>
> Hi,
>
> Is there a way to configure common
