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 icons, as we are going to hand the application to a graphic designer down the line, and it will make it very easy for the designer to swap in different images,

Cheers,
NIck

On 08/03/2006, at 6:56 PM, Sam Gendler wrote:

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 probably just drop it into the template itself
rather than bothering with the .page file.

--sam


On 3/7/06, Schulte Marcus <[EMAIL PROTECTED]> wrote:
just say
<img jwcid="@YourComponent" param="ognl: somthing" />
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 components so that they do not
have to be entered within each .jwc or .page spec. file?

For example, my current application has a number of icons, each of
them a component. Each time I want to use a icon I have to define it
anew for each .page or .jwc file.

There must be a better way to do it?


Nick Faiz,
Developer
www.q9software.com



-------------------------------------------------------------------- -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user- [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user- [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Nick Faiz,
Developer
www.q9software.com



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to