[TIMOB-1855] Performance Gains Using TabGroup instead of Window
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-08-16T13:49:35.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 3.0.0 |
Components | iOS |
Labels | ios, iphone, performance, tabgroup, window |
Reporter | Clifton Labrum |
Assignee | Neeraj Gupta |
Created | 2011-04-15T03:04:01.000+0000 |
Updated | 2013-01-15T04:43:40.000+0000 |
Description
Doing a normal window operation in an app like this yields a much slower app (slower as in UI rendering, modals opening and closing, views in a ScrollableView, etc.):
var mainWindow = Titanium.UI.createWindow({ ... });
mainWindow.open();
...than this, which makes the app much faster:
var tabGroup = Titanium.UI.createTabGroup();
var mainWindow = Titanium.UI.createWindow({
navBarHidden:true,
tabBarHidden:true
});
var tab = Titanium.UI.createTab({
window:mainWindow
});
tabGroup.addTab(tab);
tabGroup.open();
Both produce the same visual result, but I see significant performance gains using the invisible tabGroup option.
I have tested this on multiple applications both in the simulator and on a device. This is for iPhone only.
Hopefully this is helpful.
So tabGroup is faster than navigationGroup (since it's in a window) ?
If this is the case, the Titanium people should think about tweaking it, what's the point of using navigationController if tabGroup is a lot faster.
Do you have any numbers on this?
Unable to see a difference using TiSDK 2.2.0v20120816015712. Ticket marked as resolved.
Similar performance noticed while using tabGroup and window Verified On: Studio: 3.0.1.201212181159 SDK: 3.0.0.GA iOS Device: iPhone 3GS(v5.1), iPhone Simulator6.0 XCode: 4.5.2