Performance (with large number of radios)

[drgullin]

Performance (with large number of radios)

[felixjet]

Maybe you should implement another way to do this, for example, view only the checkboxes from the current view and lets say, 20 rows before and after. For example, if you are viewing rows 120-140 (what fills on screen), let icheck use his magic only in the checkboxes from 100 to 160. The others, just remove() them. Put a on scroll event on the page and invoke new iChecks() as needed.

Or..... paginator!

[drgullin]

2.x version got a huge performance boost, check it out - https://github.com/fronteed/iCheck/tree/2.x-beta

It's memory-safe, binds only a few events and has a quite small number of function calls.
It also cares about reflows/repaints and uses mostly a native functions instead of jQuery's slower alternatives.

I've made some calculations, customization of 1000 inputs takes 0.5s - 1s time.

[genechuah]

We implemented 1.x but now we have 2000+ records that each have an iCheck checkbox. Doing $('.checkbox').iCheck('check') takes forever, possibly up to a full minute. Is v2.x fully backwards-compatible? Is there a way to speed up this operation? Thank you.

[iamsolarplexus]

I ran into this as well but wasn't able to get 2.0 working. So no, I don't believe it's fully backwards-compatible. I'm listening to this script's development feed in the hopes that eventually development will pick up again or there will be a demo of 2.0 somewhere. Haven't had the time to look into it myself.

[mubbashar]

is 2.0 working? i tried to test it but was not able to get it working