Assets are private to the component's initialization, so this doesn't seem like the right thing for me.
Well designed components will provide defaults for assets but allow them to be overridden. The Palette component does this. ----- Original Message ----- From: "Viktor Szathmary" <[EMAIL PROTECTED]> To: "Tapestry Developer" <[EMAIL PROTECTED]> Sent: Saturday, November 02, 2002 9:54 PM Subject: [Tapestry-developer] overriding assets > hi, > > is there a quick way to override a component's assets? it would seem > natural to me, that just like bindings, you could specify the images, > etc a given component should use... right now the solution seems to be > defining a new component, and copying the jwc file, not very practical. > > best regards, > viktor > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
