In case of wro4j, css can be merged no matter where they are located:
Css url rewriting - after css resources are merged, the relative url will
not point any more to a valid location. That is why it is important to
overwrite the url's in the css files after merging. This is the most
powerful
Yes, I see your point... by including jquery with two different sets,
you actually make it worse because it can't be cached anymore.
You're only going to gain a minor advantage if you bundle the whole
possible set (for the whole site) in one download, but I doubt it
would be worth the
Hi,
how about doing this with some kind of precompilation step? You could
manipulate the code with maven or ant befor packing the war having an
task combining all js and css in one.
Just an idea...
Cheers
Bjoern Tietjens
Am 10.04.2009 um 05:31 schrieb Brill Pappin br...@pappin.ca:
I think that this response by Igor to another thread was supposed to be on
this one. Either way, it fits this one.
it is much simpler and more efficient to set proper caching headers.
concatenating resources often does not work because different
components on different pages contribute
The problem with merging css is that the backgrounds will not work anymore
(in case the images are referenced relatively). But there is a solution for
this, check web resource optimizer ( http://code.google.com/p/wro4j/ wro4j
). It performs url rewriting. Also, resources can be located anywhere
You could likely do that fairly easily, but how do you know which ones
are need by which page?
For instance page A may not need all the CSS that page B does.
- Brill Pappin
On 10-Apr-09, at 2:49 AM, Bjoern Tietjens wrote:
Hi,
how about doing this with some kind of precompilation step?
Yah, he's right about the caching... so maybe not work it... however
the solution someone posted was a ... hmm... Just in Time Resource
kind of idea.
which would still optimize for whatever page you were on (instead of
bundling it all up into one giant file).
- Brill Pappin
On
Ahh... forgot about that...
It will only work for CSS files that are in the same directory if you
want to find other resources like images.
Can it be done without doubt but its starting o get more complex than
is likely worth the trouble since as Igor pointed out, the browser
caches them
my point is that the just in time thing will not work
suppose
on page A you use jquery and ext
on page B you use jquery and yui
using this just-in-time composition you will get two resources:
jquery+ext and jquery+yui - so you are trading 3 hits for two hits,
but transferring jquery twice.
On Thu, Apr 9, 2009 at 9:06 AM, Eduardo Nunes esnu...@gmail.com wrote:
Hi,
Is there a way to tell wicket to package all referenced javascripts
together, the same for the css? If there isn't this solution yet, can
anyone tell me where should I look for to implement it?
You can put your
I think that I didn't explain it right. What I want is that wicket
concatenate all included javascripts into one file. Something like
wicket:link
link.. javascript1.js /
link.. javascript2.js /
link.. javascript3.js /
/wicket:link
Generate just one resource with javacript1.js, javacript2.js
link href=... / for the css
and
script language=javascript src=... / for the javascripts
On Thu, Apr 9, 2009 at 11:57 AM, Eduardo Nunes esnu...@gmail.com wrote:
I think that I didn't explain it right. What I want is that wicket
concatenate all included javascripts into one file. Something like
Hi Eduardo!
I remember there was once a discussion here on the mailing list, I think
part of that was
http://techblog.molindo.at/2008/08/wicket-interface-speed-up-merging-resources-for-fewer-http-requests.html
Roman
Eduardo Nunes wrote:
link href=... / for the css
and
script
Take a look to web resource optimizer (wro4j) project, hosted on google code.
It's pretty easy to use:
http://code.google.com/p/wro4j/ wro4j
Alex
Eduardo Nunes wrote:
I think that I didn't explain it right. What I want is that wicket
concatenate all included javascripts into one file.
Funny, I was thinking that same thing...
in one quick app i was writing, I had ~20 header links!
I kept thinking that can't be good :)
although I have not done so yet, I think there must be a way to modify
or create a resource loader that would generate a buffered version of
css (for
Oh nice... exactly what I was thinking... glad I don't have to write it!
- Brill Pappin
On 9-Apr-09, at 1:26 PM, Roman Zechner wrote:
Hi Eduardo!
I remember there was once a discussion here on the mailing list, I
think part of that was
16 matches
Mail list logo
