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 trouble
;>>>>> your
>>>>>> packages either under src/main/java or src/main/resources and
>>>>>> include them
>>>>>> through header inclusions using a ResourceReference
>>>>>>
>>>>>> Cr
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.
ev
ache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
View this message in context:
http://www.nabble.com/Packa
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 10-Apr-
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? Yo
>>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>
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 differ
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 :
Funny, I was thinkin
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
http://techblog.molindo.at/2008/08/wicket-interf
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 isntan
>
>>
>> --
>> Craig Tataryn
>> site: http://www.basementcoders.com/
>> podcast:http://feeds.feedburner.com/TheBasementCoders
>> irc: ThaDon on freenode #basementcoders, ##wicket, #papernapkin
>> im: craiger...@hotmail.com, skype: crai
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:
for the css
and
for the javascripts
On Thu, Apr 9
for the css
and
for the javascripts
On Thu, Apr 9, 2009 at 11:57 AM, 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. Something like
>
>
>
>
>
>
> Generate just one resource with "javacript1.
I think that I didn't explain it right. What I want is that wicket
concatenate all included javascripts into one file. Something like
Generate just one resource with "javacript1.js", "javacript2.js" and
"javacript3.js" concatenated. The reason for that is to reduce the
number of request
On Thu, Apr 9, 2009 at 9:06 AM, Eduardo Nunes 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 resources, like
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?
Thanks,
Eduardo S. Nunes
-
T
17 matches
Mail list logo
