search

DataZombies / jQTouch

jQT extensions jqt.activityIndicator, jqt.bars (with numeric badges), jqt.checkGroup & jqt.segmentedControl.Get updates via Twitter http://twitter.com/HeadDZombie. If you find this fork useful please make a donation via PayPal (http://tinyurl.com/2fpmx27). See below for demo links.
MIT License
159 stars 34 forks source link

iScroll algorithm linear complexity? She's sucking mud, Captain... #35

Closed LouMazz closed 13 years ago

LouMazz commented 13 years ago

Running in iOS simulator, all is well with a list of about 175 complex elements. On an iPod, slug city (~5 seconds to respond to tap on a scroll list element). If I make the list 5 elements, joy.

Trying to figure out if the culprit is jQT event detection, iScroll list management, or both.

Clues appreciated before I put on my hip boots and wade into the code.

DataZombies commented 13 years ago

175 complex elements on an iPod? Sounds like you're running out of memory. You might want to just load 50 and have the 51st item a "expose this list item to load more". You could also check out the jQT and iScroll goog groups (http://groups.google.com/group/jqtouch & http://groups.google.com/group/iscroll). Let me know how it turns out, ok? djp

LouMazz commented 13 years ago

Not that complex. The whole DOM might be 20K bytes. In an 8GB iPod. And I'm running out of memory? Though the behavior sure feels that way. Will keep you posted. BTW, jQT events are also not the snappiest with a long list - but, wow, I didn't think 150-200 items qualified as overly long. Silly me...

LouMazz commented 13 years ago

Update: what a difference on an iPhone! iPhone processor RAM: 512K. iPod processor RAM: 256K. Out of memory it is...