Hi,
On Tue, Jul 3, 2012 at 11:32 PM, sardo mark.willi...@power-oasis.com wrote:
Thanks Martin, that helps. Forgive my naivety, but why do I have the option
of adding CSS via the Java code? Surely it's better to follow convention and
add it into the appropriate .war directory?
If you provide
Martin Grigorov-4 wrote
If you provide components library then you need to distribute the
resources too, not just the classes.
Shared resources is more for delivering dynamically generated content.
A content that is different depending on some external condition
(request parameter, session
UPDATE:
I created a new TestBasePage and a new class that extends TestBasePage. The
markup for TestBasePage has the same head mark up as that in my
application's BasePage class. When I tested the rendered html it still has
two head tags. I then added the wicket:head tag to the child class of
Hi,
If you can reproduce this in a mini application (aka quickstart) then
please attach it to a ticket in our Jira and we will have a look.
On Wed, Jul 4, 2012 at 1:08 PM, sardo mark.willi...@power-oasis.com wrote:
UPDATE:
I created a new TestBasePage and a new class that extends
I have a similar problem:
A css style sheet is added to the app like so:
getSharedResources().add(css_table, new
ContextRelativeResource(css/table.css));
and this css file contains image references like so:
div.tabpanel div.tab-row li {
float: left;
background:
Hi,
Either don't use ContextRelativeResource for the css or use it for all
resources, i.e. the image should be delivered by
ContextRelativeResource too.
With the SharedResources you mount the .css at your own url and
deliver its content. But there is no such code for the images.
I'd remove the
Thanks Martin, that helps. Forgive my naivety, but why do I have the option
of adding CSS via the Java code? Surely it's better to follow convention and
add it into the appropriate .war directory?
...and if I could do the Columbo, Just one more thing, thing. Why am I
getting two head tags in my
Or new ContextImage(...)
Martijn
On Wed, Nov 30, 2011 at 9:09 PM, Martin Grigorov mgrigo...@apache.org wrote:
Try with: new Image(someId, new ContextRelativeResource(images/logout.png))
On Wed, Nov 30, 2011 at 6:40 PM, chris.schaefer cgs.schae...@gmail.com
wrote:
another thing i did not
we are new to wicket,
and currently trying to optimize and performance tune our wicket
application.
using 1.5.3.
we tried to get the caching configuration up and running. red this:
and we have set: /getResourceSettings().setCachingStrategy(strat); /during
application init.
You don't have to. There's a default strategy during development and deployment
that should work in most cases.
Basically you have wicket-examples which are part of the wicket distribution
and
yes we also tested with the default strategy, it does not change anything.
and
yes we reviews the link about caching already.
no we have not found any working example for wicket 1.5. and caching, but
reviewed most of the samples and git sources i think. which example would be
the working one ?
the effects of the caching strategy can been for example on package resources
(e.g. javascript, css, images) …
e.g. start wicket-examples and load the
pub - Localization
page (the page with the different beers :-)
From looking at the html source you see url's like this:
img
thanks for this answer.
in the pub example this seems to work, and we also see the Cache-control
headers.
but we do not need and have language specific resouces (so far).
a. can you tell me how we should change the image construction for our
initialization code which currently looks like this:
another thing i did not mention is,
that in this applicaiton the images and js and css files are stored in the
webapp/images folder and not in the classpath packages !
is it intended / required to store all images within java packages ?
chris
--
View this message in context:
Try with: new Image(someId, new ContextRelativeResource(images/logout.png))
On Wed, Nov 30, 2011 at 6:40 PM, chris.schaefer cgs.schae...@gmail.com wrote:
another thing i did not mention is,
that in this applicaiton the images and js and css files are stored in the
webapp/images folder and
Out of curiosity, why aren't you using ContextImage? That would help with
the contextual path for the logout.png.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Caching-Imagages-CSS-JS-in-Wicket-1-5-3-tp4121068p4121323.html
Sent from the Users forum mailing list
16 matches
Mail list logo
