Re: Wicket6 and big (>100 rows) list with ajaxbehaviour: slow

2012-09-24 Thread obell
Hehe..

Forgot to check different browsers, and to my surprise the only browser with
a significant slowdown is Chrome... :o)

IE8 and Firefox had basically no difference in the timing...

Good idea with the event listener on the table, but I would think that makes
the java-code uglier?
With my workaround (which seems unnecessary now), I use it just like normal,
but instead of adding AjaxFormComponentUpdatingBehavior, I add
AjaxLiteBehavior (custom behavior), and override onEvent in that to handle
the event... With event on table you would have to find out which element
was clicked first (or whatever event you want) and then handle it. Probably
better than my solution, anyway.. :o)


Martin Grigorov-4 wrote
> Hi,
> 
> Which browser do you use ? I guess it is worst with IE.
> 
> In general having a big table with many event listeners (inline or
> not) will lead to slower rendering.
> In our app we also need a table with many rows/columns and we use
> event delegation - there is only one event listener attached at the

>  element and all clicks in the cells are captured by it and
> there we extract the specific data from the event's targetElement.
> This scales much better.
> 
> On Mon, Sep 24, 2012 at 12:30 PM, obell <

> oddgeir@

> > wrote:
>> In Wicket 6 ajax events changed from being inline (
>>
>>
>>
>>
> 
>>
>>
>>
>>
>>
>> I have worked around this, but I would really prefer the official way...
>> Is
>> this being looked at, or is it just unavoidable because of the new way of
>> doing things?
>>
>> On my pc, I get about 3 seconds extra wait-time in wicket 6 vs wicket
>> 1.5.8
>> for a list with 100 rows...
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/Wicket6-and-big-100-rows-list-with-ajaxbehaviour-slow-tp4652281.html
>> Sent from the Users forum mailing list archive at Nabble.com.
>>
>> -
>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>> For additional commands, e-mail: 

> users-help@.apache

>>
> 
> 
> 
> -- 
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket6-and-big-100-rows-list-with-ajaxbehaviour-slow-tp4652281p4652283.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket6 and big (>100 rows) list with ajaxbehaviour: slow

2012-09-24 Thread Martin Grigorov
Hi,

Which browser do you use ? I guess it is worst with IE.

In general having a big table with many event listeners (inline or
not) will lead to slower rendering.
In our app we also need a table with many rows/columns and we use
event delegation - there is only one event listener attached at the
 element and all clicks in the cells are captured by it and
there we extract the specific data from the event's targetElement.
This scales much better.

On Mon, Sep 24, 2012 at 12:30 PM, obell  wrote:
> In Wicket 6 ajax events changed from being inline (
>
>
>
>
>
>
>
>
>
> I have worked around this, but I would really prefer the official way... Is
> this being looked at, or is it just unavoidable because of the new way of
> doing things?
>
> On my pc, I get about 3 seconds extra wait-time in wicket 6 vs wicket 1.5.8
> for a list with 100 rows...
>
>
>
>
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Wicket6-and-big-100-rows-list-with-ajaxbehaviour-slow-tp4652281.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org