I know we said we don't want to touch CSS until post-1.0 but
I've run into the following problem. If you can suggest a workaround I
would be greatful...

        I'm trying to use BufferedDynamicImageResource to generate my
round corner images. The thing is, you can only bind these resources to
Image components, which are classic HTML <img> tags.

        The problem is that my code looks something like this:

<div style=" background-image: url(XXX); background-repeat: no-repeat;
background-position: left top" id="wicket-topLeft">

        where XXX should get replaced with the image filename. Fine, so
I can replace XXX with the appropriate filename, but then I run into a
problem with Wicket's component model. In order to find out the image
filename I must render an Image component. In order to render an Image
component, it must show up within my markup. Since my markup refers to
the image within CSS code, not using an <img> tag, Wicket will complain
that the component is not referenced by the markup. Basically, I cannot
get Wicket to persist the dynamic image to disk and tell me what its
associated filename is so I can dump it back into the CSS code.

        Again, I know you don't want to add full-fledged CSS support
anytime soon, but I've really got to get some sort of workaround
here... A simple but uncomfortable hack would be to get trick Image
into ignoring the fact that it is not in the markup and render itself
anyway. Not ideal but maybe it's the simplest approach... Ideas?

Gili



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to