Ah. Nice. I think I get it now.. it's a different approach, but then again,
maybe that's the wicket-way :)
I'll give it a shot and see how it works for me.
Thanks,
Naaman
John Krasnay wrote:
You might consider referencing the image from a Panel, then just using
the panel everywhere. In
Let me make sure I understand: you suggest that I place the img files along
with the html and java files?
But what if I have images that are used in many places in the application?
Do I keep multiple copies of that gif files?
This seems hard to maintain...
Naaman
--
View this message in
https://issues.apache.org/jira/browse/WICKET-390
-igor
On 4/19/07, nlif [EMAIL PROTECTED] wrote:
Let me make sure I understand: you suggest that I place the img files
along
with the html and java files?
But what if I have images that are used in many places in the application?
Do I keep
You might consider referencing the image from a Panel, then just using
the panel everywhere. In that case the image only needs to be kept in
the package that defines the Panel.
If it's something like a logo that appears at the top of every page, you
could also define a base page that renders the
You might consider referencing the image from a Panel, then just using
the panel everywhere. In that case the image only needs to be kept in
the package that defines the Panel.
I find it more lightweight to use a WebComponent with a
replaceComponentTagBody method that just spits out a img
Hi,
I understand that it is the recommendation to place html files in the src
folder, along with the corresponding java files. However, what about images?
Should I place them with the html and java files as well?
I can actually think of good reasons for placing all images in a central
place.
I suppose you can place a src=absolutePathToUrImagesUnderWeb-root and have
the actual resource attached to image component by using a relative path and
following constructors--
Image(java.lang.String id, ResourceReference resourceReference) Or
Image(java.lang.String id, new Model(path))
..But