Extend html.Image or not to extend ?

[Elad Messing <El...@sphera.com>]

Hi All

	My application is brandable. So each user can change images css,
and create its own look and fill.
	I'm now in the process of building the pages of the application.
Many of the images can be brandable, and their source changes -
according to the logged-in user.
	Instead of piping the "Visit.UserBrandingDir" property in front
of each image path, I was thinking of extending the "html.Image"
component, and play with its "imageURL" variable. 
	Is that a good practice, or an "Overkill" ? 
	How would you suggest to change the image path in the subclass ?
	Can I extend "html.Image" but still use its default .jwc and not
copy-paste it to my own ?

	thanks...

Elad Messing

Sphera Tech. LTD
 
<http://www.sphera.com/demosite/index.htm>



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org