https://issues.apache.org/jira/browse/WICKET-4418
there is a link to a benchmark
On Thu, Feb 9, 2012 at 11:13 PM, Johan Compagner jcompag...@gmail.com wrote:
or use the let statement.. but support in all browsers could be a bit
tricky ;)
shouild be javascript 1.7 (thats FF 2.0 from 2006) but
.)
Agree!
Tom Burton
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Wednesday, February 08, 2012 4:25 AM
To: dev@wicket.apache.org
Subject: JS performance optimization in AjaxRequestTarget
Hi,
Do you imagine a use case in which several evaluates
On 8 feb. 2012, at 16:01, Emond Papegaaij emond.papega...@topicus.nl wrote:
In Wicket 6, onDomReady and onLoad scripts are merged into one big script in
the ResourceAggregator. This is to prevent many script tags, all with
$(document).ready(function(){...}) (or the wicket equivalent). This
On Thu, Feb 9, 2012 at 6:16 PM, Frank van Lankvelt f...@a-eskwadraat.nl wrote:
On 8 feb. 2012, at 16:01, Emond Papegaaij emond.papega...@topicus.nl wrote:
In Wicket 6, onDomReady and onLoad scripts are merged into one big script in
the ResourceAggregator. This is to prevent many script tags,
or use the let statement.. but support in all browsers could be a bit
tricky ;)
shouild be javascript 1.7 (thats FF 2.0 from 2006) but i don't think its in
EcmaScript yet (looks like EcmaScript 6 gets it) and most other browsers
follow that and do currently Edition 5.x or something
On Thu, Feb
Hi,
Do you imagine a use case in which several evaluates in
ajax-response should be executed separately (one after another) as
it is now ?
Each evaluate (and priority-evaluate) is executed in an eval() in
wicket-ajax.js. As we all know eval() is slow. As an optimization I
think we can merge all
Hi,
Merging multiple evaluates together will change the scope of some
variables. The variables in the scope of an evaluate block would carry
on in the following evaluate blocks. This could however be mitigated by
wrapping each evaluate block in its own function.
Bertrand
On 08/02/2012 8:24
On Wed, Feb 8, 2012 at 4:33 PM, Bertrand Guay-Paquet
ber...@step.polymtl.ca wrote:
Hi,
Merging multiple evaluates together will change the scope of some variables.
The variables in the scope of an evaluate block would carry on in the
following evaluate blocks. This could however be mitigated
This is very easy to accomplish in 6.0. You only have to delete the code that
keeps the scripts separate when AJAX :). I can fix this, if you want?
Emond
On Wednesday 08 February 2012 16:44:14 Martin Grigorov wrote:
On Wed, Feb 8, 2012 at 4:33 PM, Bertrand Guay-Paquet
ber...@step.polymtl.ca
On Wed, Feb 8, 2012 at 4:50 PM, Emond Papegaaij
emond.papega...@topicus.nl wrote:
This is very easy to accomplish in 6.0. You only have to delete the code that
keeps the scripts separate when AJAX :). I can fix this, if you want?
I think we talk about different things.
I talk about Ajax
In Wicket 6, onDomReady and onLoad scripts are merged into one big script in
the ResourceAggregator. This is to prevent many script tags, all with
$(document).ready(function(){...}) (or the wicket equivalent). This merging is
only done for non-AJAX requests, to preserve the separate evaluates.
On Wed, Feb 8, 2012 at 5:01 PM, Emond Papegaaij
emond.papega...@topicus.nl wrote:
In Wicket 6, onDomReady and onLoad scripts are merged into one big script in
the ResourceAggregator. This is to prevent many script tags, all with
$(document).ready(function(){...}) (or the wicket equivalent).
...@apache.org]
Sent: Wednesday, February 08, 2012 4:25 AM
To: dev@wicket.apache.org
Subject: JS performance optimization in AjaxRequestTarget
Hi,
Do you imagine a use case in which several evaluates in
ajax-response should be executed separately (one after another) as
it is now ?
Each evaluate
13 matches
Mail list logo
