Lot's of unnecessary layouts and relayouts while scrolling

I've experienced some choppy tableview scrolling so I looked at the underling objective c code only to discover lot's of inefficient calls inside tiuiview doing unnecessary layouts and over complex things... does anyone working on optimizing and improving the code ??

I think that speed and performance should be a priority instead of features.

I can actually vouch for the developers, that they have spent a ton of hours improving tableview scrolling.

If you see a way to improve it even more, then I suggest that either: 1. You go ahead and do it, and submit a pull request. This is an open-source project, after all 2. At least open up a JIRA ticket outlining the exact changes you'd make.

Contributing to Titanium

I have the highest respect for the effort of building titanium and love the project, this is the reason I started this conversation. todays apps are highly visual rows can be complex not just a title and image (see my app images). making the perceived performance of titanium look bad.

I know it's an open source project, sadly I have only basic objective-c knowledge and the codebase is becoming complex.

I realized the code is not tuned to performance after I defined every rowview with exact pixel dimensions so not lot's of layout calculations need to be made by appcelerator. and then I did a simple logging of things happaning while I scroll, for example I saw lot's (thousands !!) while scrolling to the relayout method of TiViewProxy.m even nothing changed on the view layout. also lot's of calls to TiLayoutQueue also most of the redundant. all those things are killing performance.

in order for appcelerator to strive it must have a performance edge on html5 and I think without focus on performance tuning (like 1.7 release focus on memory leaks) it won't get there.

I did a test on the same complex layout rendered as html and it achieved better scrolling results !!! then appcelerator.