[ALOY-889] iOS: <NavigationGroup> object generates Ti.UI.iPhone.createNavigationGroup, removed in 3.2.0
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Won't Fix |
Resolution Date | 2014-01-20T20:12:09.000+0000 |
Affected Version/s | Alloy 1.3.0 |
Fix Version/s | 2014 Sprint 02 |
Components | n/a |
Labels | qe-3.2.0 |
Reporter | Federico Casali |
Assignee | Tony Lukasavage |
Created | 2013-12-03T01:20:27.000+0000 |
Updated | 2014-01-20T22:27:35.000+0000 |
Description
Problem description
<NavigationGroup id="navgroup" platform="ios,mobileweb">
<Window title="Window 1" id="win1">
</Window>
</NavigationGroup>
is being compiled as:
$.__views.navgroup = Ti.UI.iPhone.createNavigationGroup({
window: $.__views.win1,
id: "navgroup"
});
Titanium.UI.iOS.NavigationWindow is being now used in TiSDK 3.2.0
http://docs.appcelerator.com/titanium/latest/#!/api/Titanium.UI.iPhone-method-createNavigationGroup
Runnable sample app to reproduce available here: https://github.com/appcelerator/alloy/tree/master/test/apps/ui/navgroup
Is it that we should remove
[~ingo] I can remove this now since we've already stated that Alloy 1.3.0 requires TiSDK 3.2.0. It should also be noted that I'll then need to rewrite some test apps to use NavigationWindow instead of NavigationGroup. I think perhaps the right call would be for me to adjust the test apps in order to not use NavigationGroup for 1.3.0 (since they won't impact Alloy's usage), and leave actually pulling
The code generation will be removed in Alloy 1.3.1. The test apps and samples will be changed to use Ti.UI.iOS.NavigationWindow for 1.3.0, as detailed in ALOY-890.
Alloy 1.3.1 will continue to support TiSDK 3.0.0+, so NavigationGroup support will remain.