These days in Tap5, I think most of us either do:
<img t:type="any" src="prop:imgSource"/>
Or else just:
<img src="${imgSource}"/>
You could:
a) extend "any"
b) Write your own component from scratch
c) Maybe refactor your custom code into a mixin? <img t:type="any"
src="prop:imgSource" t:mixins="myTransparentModelingMixin"/>
Robert
On Aug 23, 2011, at 8/232:03 AM , Ken in Nashua wrote:
>
> Hi All,
>
> There use to be a Image component for tap4...
>
> Is there one for tap5 ? If not is there one that suffices...? I am upgrading
> some tap4 code... my derivative extended the old tap4 Image and did some
> transparent modeling.
>
> I want to extend what exists for tap5 Image capabilities and customize using
> what I previously modeled.
>
> Best Regards and thanks
> kcola...@live.com
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
