Datasets:

giseldo

/

TAWOS

like 0

ALOY-1167

10/15/2014 17:56:16

Update travis.yml to exit w/non-zero value on errors

GitHub builds are marked as passing even when errors are encountered by Travis. Our test scripts must be exiting with a non-zero value in the case of errors. We should add an {{after_script}} section that exits with 0/non-zero to properly signal build state. http://docs.travis-ci.com/user/build-configuration/

ALOY-1170

10/16/2014 15:11:16

SQL runtime error when running models/listview_binding test app

Steps: 1. Build/run https://github.com/appcelerator/alloy/tree/1_5_X/test/apps/models/binding_listview for Android or iOS Results: On iOS, the following error is generated: {quote} [DEBUG] 2014-10-16 10:02:57.854 binding_listview[31708:445138] [ERROR] A SQLite database error occurred on database '/Users/tstatler/Library/Developer/CoreSimulator/Devices/861898C4-B00A-46FE-B8BF-AF20F274270C/data/Containers/Data/Application/8411B43C-2D41-4140-BD17-9F5275B43166/Library/Private Documents/_alloy_.sql': Error Domain=com.plausiblelabs.pldatabase Code=3 "An error occured parsing the provided SQL statement." UserInfo=0x7c93c470 {com.plausiblelabs.pldatabase.error.vendor.code=1, NSLocalizedDescription=An error occured parsing the provided SQL statement., com.plausiblelabs.pldatabase.error.query.string=INSERT INTO info (title,subtitle,image) VALUES (?,?,?);, com.plausiblelabs.pldatabase.error.vendor.string=table info has no column named title} (SQLite #1: table info has no column named title) (query: 'INSERT INTO info (title,subtitle,image) VALUES (?,?,?);') [ERROR] Script Error { [ERROR] backtrace = "#0 () at file:///Users/tstatler/Library/Developer/CoreSimulator/Devices/861898C4-B00A-46FE-B8BF-AF20F274270C/data/Containers/Bundle/Application/DA7AB9EB-0FAB-4D30-BB29-2E1CD5D26933/binding_listview.app/alloy/models/Info.js:54\n#1 Migrate() at file:///Users/tstatler/Library/Developer/CoreSimulator/Devices/861898C4-B00A-46FE-B8BF-AF20F274270C/data/Containers/Bundle/Application/DA7AB9EB-0FAB-4D30-BB29-2E1CD5D26933/binding_listview.app/alloy/sync/sql.js:245\n#2 () at file:///Users/tstatler/Library/Developer/CoreSimulator/Devices/861898C4-B00A-46FE-B8BF-AF20F274270C/data/Containers/Bundle/Application/DA7AB9EB-0FAB-4D30-BB29-2E1CD5D26933/binding_listview.app/alloy/sync/sql.js:341\n#3 () at file:///Users/tstatler/Library/Developer/CoreSimulator/Devices/861898C4-B00A-46FE-B8BF-AF20F274270C/data/Containers/Bundle/Application/DA7AB9EB-0FAB-4D30-BB29-2E1CD5D26933/binding_listview.app/alloy.js:128\n#4 () at file:///Users/tstatler/Library/Developer/CoreSimulator/Devices/861898C4-B00A-46FE-B8BF-AF20F274270C/data/Containers/Bundle/Application/DA7AB9EB-0FAB-4D30-BB29-2E1CD5D26933/binding_listview.app/alloy/models/Info.js:59"; [ERROR] line = 93; [ERROR] message = "invalid SQL statement"; [ERROR] nativeLocation = "-[TiDatabaseProxy execute:] (TiDatabaseProxy.m:191)"; [ERROR] nativeReason = "Error Domain=com.plausiblelabs.pldatabase Code=3 \"An error occured parsing the provided SQL statement.\" UserInfo=0x7c93c470 {com.plausiblelabs.pldatabase.error.vendor.code=1, NSLocalizedDescription=An error occured parsing the provided SQL statement., com.plausiblelabs.pldatabase.error.query.string=INSERT INTO info (title,subtitle,image) VALUES (?,?,?);, com.plausiblelabs.pldatabase.error.vendor.string=table info has no column named title}"; [ERROR] sourceId = 299232704; [ERROR] sourceURL = "file:///Users/tstatler/Library/Developer/CoreSimulator/Devices/861898C4-B00A-46FE-B8BF-AF20F274270C/data/Containers/Bundle/Application/DA7AB9EB-0FAB-4D30-BB29-2E1CD5D26933/binding_listview.app/alloy/sync/sql.js"; [ERROR] } [ERROR] Script Error Module "alloy/models/Info" failed to leave a valid exports object {quote}

ALOY-1172

10/20/2014 15:18:56

Properties test sample: Collection view doesn't update after adding first item on Android

Steps: 1. Create an Alloy application from the [models/properties|https://github.com/appcelerator/alloy/tree/master/test/apps/models/properties] sample. 2. Build, run on Android. 3. Click Collections tab. 4. Enter text in input and click add/+ buttton. Results: New item doesn't appear in TableView. Expected: Item appears in tableview. Subsequent items added to the collection appear in the TableView, it's just the first one that doesn't. Works as expected on iOS (sim).

ALOY-1173

10/20/2014 20:44:37

Add functionality from alloy-smelter to Alloy

The https://github.com/k0sukey/alloy-smelter offers some nice capabilities that should perhaps be included in Alloy itself. For example, copying/moving/renaming/deleting controllers. Sub-tickets will be needed to implement the individual features. Alternately, alloy-smelter could be wrapped, providing "alloy foo" commands that call to smelter.

ALOY-1174

10/20/2014 20:57:12

Update sync adapters to support promises in addition to callbacks

Per comments at [Hacking alloy to get promises to work|https://github.com/aaronksaunders/tiConnectSampleApp#hacking-of-alloyjs-to-get-promises-to-work], the core model/collection constructors could be modified simply to support using promises in addition to callbacks. As shown in [Aaron's TiConnect sample|https://github.com/aaronksaunders/tiConnectSampleApp/blob/master/app/alloy.js#L22] the change involves returning the results of the sync call. Resolving this cannot break existing apps, so extensive testing should be done on all platforms.

ALOY-1175

10/21/2014 22:09:04

Cannot call methods or access properties on MenuItems declared in markup

DESCRIPTION: Cannot call methods or access properties using the `id` attribute of MenuItems created in XML markup. Related feature ticket: ALOY-1098 REPRODUCTION: Run the Alloy application below. Hit the Expand or Collapse action items or try to expand the action view from the overflow menu. RESULTS: Trying to call a method or accessing a property results in 'Cannot read property of undefined` or `Cannot call method X of undefined`. {noformat} [ERROR] : TiExceptionHandler: (main) [3824,3824] ----- Titanium Javascript Runtime Error ----- [ERROR] : TiExceptionHandler: (main) [0,3824] - In alloy/controllers/index.js:70,28 [ERROR] : TiExceptionHandler: (main) [1,3825] - Message: Uncaught TypeError: Cannot read property 'actionViewExpanded' of undefined [ERROR] : TiExceptionHandler: (main) [0,3825] - Source: Ti.API.info($.item3.actionViewExpanded); [ERROR] : V8Exception: Exception occurred at alloy/controllers/index.js:70: Uncaught TypeError: Cannot read property 'actionViewExpanded' of undefined {noformat} `index.xml` {code} <Alloy> <Window id="win"> <Menu> <MenuItem id="item1" title="Expand" onClick="expand" showAsAction="Titanium.Android.SHOW_AS_ACTION_IF_ROOM" /> <MenuItem id="item2" title="Collapse" onClick="collapse" showAsAction="Titanium.Android.SHOW_AS_ACTION_IF_ROOM" /> <MenuItem id="item3" title="Alt Text" showAsAction="Titanium.Android.SHOW_AS_ACTION_COLLAPSE_ACTION_VIEW" onExpand="report" onCollapse="report"> <ActionView> <View layout="horizontal"> <Button left="0">Search</Button> <TextField right="0" hintText="Type Something"/> </View> </ActionView> </MenuItem> </Menu> </Window> </Alloy> {code} `index.js` {code} $.win.open(); function expand (e) { $.item3.expandActionView(); }; function collapse(e) { $.item3.collapseActionView(); } function report(e) { Ti.API.info(e.type); Ti.API.info($.item3.actionViewExpanded); } {code} Classic Examples: {code} var win = Ti.UI.createWindow(); var item1 = item2 = item3 = null; var actionView = Ti.UI.createView({layout: 'horizontal'}); actionView.add(Ti.UI.createButton({title: 'Search', left: 0})); actionView.add(Ti.UI.createTextField({hintText: 'Type Something', right: '0'})); win.addEventListener("open", function() { win.activity.onCreateOptionsMenu = function(e) { var item, menu; menu = e.menu; menu.clear(); item1 = menu.add({ title : "Collapse", showAsAction: Ti.Android.SHOW_AS_ACTION_ALWAYS }); item1.addEventListener('click', function (e) { item3.collapseActionView(); }); item2 = menu.add({ title : "Expand", showAsAction : Ti.Android.SHOW_AS_ACTION_ALWAYS }); item2.addEventListener('click', function (e) { item3.expandActionView(); }); item3 = menu.add({ title : 'Alt Text', showAsAction : Titanium.Android.SHOW_AS_ACTION_COLLAPSE_ACTION_VIEW, actionView: actionView }); item3.addEventListener('collapse', function(e) { Ti.API.info(item3.actionViewExpanded); }); item3.addEventListener('expand', function(e) { Ti.API.info(item3.actionViewExpanded); }); }; }); win.open(); {code}

ALOY-1177

10/21/2014 23:02:28

Implicitly set ns attribute for SearchView to Ti.UI.Android

When declaring a SearchView element in XML markup, Alloy should assign it the 'Ti.UI.Android' namespace. Alloy is currently doing this for a lot of iOS-specific components. These two items should be equivalent. {code} <SearchView ns="Titanium.UI.Android"/> {code} {code} <SearchView/> {code}

ALOY-1209

11/12/2014 14:01:58

Compile error when a view's attribute contains an escaped quote

The following view: {code:xml} <Alloy> <Window> <Label html="Hello <b>Bold</b> <font color=\"red\">World!</font>" /> </Window> </Alloy> {code} Will result in the following compile error: {code} [INFO] view: "index.xml" [WARN] attribute space is required"html"!! [WARN] @#[line:3,col:3] [ERROR] Error parsing XML file. [ERROR] element parse error: Error: attribute value must after "=" [ERROR] @#[line:3,col:3] [ERROR] Alloy compiler failed {code} I'd expect this to work fine since the {{"}} is escaped?

ALOY-1225

11/24/2014 15:39:25

social.js authorize UI crashes on android

Upon calling the 'authorize' method, the loading view opens and then immediately crashes, resulting in the following error. [INFO] : libc: Fatal signal 11 (SIGSEGV) at 0x00000014 (code=1), thread 2206 (KrollRuntimeThr) The behavior is consistent. However, if I open and close a facebook authorize dialog before opening the twitter authorize dialog, the twitter dialog will usually work. The issue may lie in the "popIn" animation: it appears that the window expands beyond the mobile screen viewport, and will crash at about the time the window should zoom back into the viewport. See the attached video for a demo of the bug. Functionality is fine in iOS v 8.1. Other notes: * Line 514 of the social.js file makes us of the deprecated "Ti.UI.AUTODETECT_NONE" * The default navigation/action bar at the top becomes visible

ALOY-1195

12/02/2014 19:46:55

Alloy Migrations: Template up.down functions do not match documentation

When generating a migration with the Alloy CLI (1.5.1), the generated file has this code: {noformat} migration.up = function(db) { }; migration.down = function(db) { }; {noformat} But documentation uses 'migrator' in place of 'db' for the function parameter. Since the passed-in object itself has a 'db' parameter, the 'migrator' naming helps to avoid potential confusion. migrator.db.execute(...) vs. db.db.execute(...)

ALOY-1202

12/12/2014 15:14:33

Update ti.paint module in HarnessTemplate with a 64-bit compatible version

The HarnessTemplate includes the ti.paint module for use with the test/apps/advanced/native_modules sample. The version included is 32-bit only. Update to a 64-bit version. Incidentally, there is an Android version of this module. The sample app could be updated to work on both iOS and Android (it is iOS-only currently).

ALOY-1206

12/12/2014 22:04:41

Alloy compiler doesn't regenerate controllers if only change is made to the distribution target

When building for a different target environment (development, test or production) conditional code in {{app/alloy.js}} is not updated in {{Resources/\[platform\]/app.js}}. This can cause serious errors when relying on the conditions for particular behaviour in ad-hoc and app store builds. h1. Test case 1. Create a project: {{ti create -t app -p ios -n conditions --id test.conditions -d .}} 2. Make it Alloy: {{cd conditions && alloy new}} 3. Insert the following snippet in both {{app/alloy.js}} and {{app/controllers/index.js}}: {code:javascript} if (ENV_PRODUCTION) console.debug('if (ENV_PRODUCTION)'); if (ENV_TEST) console.debug('if (ENV_TEST)'); if (ENV_DEV) console.debug('if (ENV_DEVELOPMENT)'); {code} 4. Build the production for Simulator: {{ti build -p ios -b}} 5. Confirm that both {{Resources/iphone/app.js}} and {{Resources/iphone/alloy/controllers/index.js}} only have {{console.debug("if (ENV_DEVELOPMENT)");}} which is correct 6. Build for ad-hoc or to device: {{ti build -p ios --target dist-adhoc}} 7. Confirm that {{Resources/iphone/app.js}} still has {{console.debug("if (ENV_DEVELOPMENT)");}} while {{Resources/iphone/alloy/controllers/index.js}} is correctly updated to have {{console.debug("if (ENV_PRODUCTION)");}}

ALOY-1215

12/15/2014 09:32:26

Samples: Alloy RSS Reader sample does not work on iPad

This is not a regression as the issue occurs in SDK 3.4.0.GA as well. Steps to Reproduce: 1. Import the Alloy - RSS Reader sample in studio 2. Run the sample project on iPad device or simulator Actual Result: The app installs and launches successfully but does not show any content. Only waiting spinner is shown continuously. Expected Result; The RSS Reader sample app should show the RSS feeds

ALOY-1205

12/17/2014 16:08:17

Alloy launch image for 667h has the wrong filename

It is named {{Default-Portrait-667h@2x.png}} but should be {{Default-667h@2x.png}} like the classic template has: https://github.com/appcelerator/titanium_mobile/tree/master/iphone/templates/app/default/template/Resources/iphone PR: https://github.com/appcelerator/alloy/pull/637

ALOY-1207

12/18/2014 08:39:10

Alloy: Theme "lib" folder

Although there's no real difference between the Alloy {{assets}} and {{lib}} folder, themes should also support the latter so that to theme a utility module you have in {{app/lib/util.js}} you no longer need to put this in {{app/themes/mine/assets/util.js}}. PR incoming..

ALOY-1210

12/18/2014 09:27:55

Alloy: Add support for DIST in the Project Configuration File

Recently, in Alloy 1.4.0 {{DIST_ADHOC}} and {{DIST_STORE}} were added the options for [conditional code in controllers|http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_Controllers-section-34636384_AlloyControllers-ConditionalCode]. I'd like to also have support the same conditions in {{config.json}}. The use case would be to have different endpoints, keys or other configuration variables for production ad-hoc builds and production store-builds. Example: {code} { "global": {"foo":1}, "env:development": {"foo":2}, "env:test":{"foo":3}, "env:production":{"foo":4}, "os:ios env:production": {"foo":5}, "os:ios env:development": {"foo":6}, "os:ios env:test": {"foo":7}, "os:android":{"foo":8}, "os:mobileweb":{"foo":9}, "os:ios dist:adhoc": {"foo":10}, "os:ios dist:store": {"foo":10}, "dependencies": { "com.foo.widget":"1.0" } } {code}

ALOY-1214

12/22/2014 15:30:09

Button in Inheritance sample app difficult to click on iOS

Steps 1.Build and run https://github.com/appcelerator/alloy/tree/master/test/apps/advanced/inheritance on an iPhone device or simulator. 2. Try to click the baseDialog button. Results: Because the button is partially covered by the status bar it's hard to click, even with a mouse pointer. Expected: Button easy to click with finger or mouse.

ALOY-1232

12/22/2014 21:51:49

--deploy-type ignored on android builds for emulator and device

h4. Problem Description The argument --deploy-type or -D is ignored if the target is android, always generating 'development' for emulator and 'test' for device, even if specified the other way. iOS works fine. I didn't test all the others platforms. h4. Steps to reproduce Since we use these settings to trigger our testing scripts, figured I'd give it a test. Ti.App.deployType seems to work fine here. But your settings from the config.json file do not. added the following to my alloy.js to test faster: {code} console.log('Ti.App.deployType: ', Ti.App.deployType); console.log('Alloy.CFG: ', Alloy.CFG); {code} Results: Genymotion Google Nexus 5 - 5.0.0 - API 21 - 1080x1920 (5.0.0) {code} [INFO] Ti.App.deployType: test [INFO] Alloy.CFG: {"dependencies":{},"TEST_STRING":"TEST ENV"} {code} {code} [INFO] Ti.App.deployType: development [INFO] Alloy.CFG: {"dependencies":{},"TEST_STRING":"TEST ENV"} {code} Genymotion Samsung Galaxy S5 - 4.4.4 - API 19 - 1080x1920 (4.4.4) {code} [INFO] Ti.App.deployType: test [INFO] Alloy.CFG: {"dependencies":{},"TEST_STRING":"TEST ENV"} {code} {code} [INFO] Ti.App.deployType: development [INFO] Alloy.CFG: {"dependencies":{},"TEST_STRING":"TEST ENV"} {code} Device Samsung S4 {code} 12-22 20:32:56.028: I/TiAPI(17077): Ti.App.deployType: development 12-22 20:32:56.028: I/TiAPI(17077): Alloy.CFG: {"dependencies":{},"TEST_STRING":"TEST ENV"} {code} {code} 12-22 20:34:35.465: I/TiAPI(18183): Ti.App.deployType: test 12-22 20:34:35.475: I/TiAPI(18183): Alloy.CFG: {"dependencies":{},"TEST_STRING":"TEST ENV"} {code} h4. Steps to reproduce I used these commands for testing: {code} ti build -p android -D development --device-id ? {code} {code} ti build -p android -D test --device-id ? {code} {code} ti build -p android -D development -T device {code} {code} ti build -p android -D test -T device {code} h4. Extra info Seems like CFG.js doesn't get updated under resources once you switch the deployType flag. Deleting the content of Resources (aka forcing regeneration of CFG.js) will go and use the right config.

ALOY-1285

12/27/2014 00:37:13

TSS conditional statement is ignored by items dynamically generated on runtime

Below is the sample of the TSS condition statement: ".date[if=false]": { backgroundColor: "#f00" } This always gets executed, even if logically it shouldn't be. It happens to elements created on runtime by this code: label = $.UI.create('Label', { text: displayDate, classes: ['date']} );

ALOY-1216

12/29/2014 19:04:23

Speed compilation by enabling selective compiles of specified files

Community PR https://github.com/appcelerator/alloy/pull/625 * PR needs testing to confirm it works as described and introduces no side-effects/regressions * Add unit tests * Open related docs tickets, update ALOY-757 & ALOY-620 as needed.

ALOY-1217

12/30/2014 00:53:24

TextField with proxy property causes compile error as ItemTemplate

h3. index.xml {code:xml} <Alloy> <Window id="settingsWin" title="Settings" class="container" tabBarHidden="true"> <ListView id="listView" defaultItemTemplate="template" allowsSelection="false"> <Templates> <ItemTemplate id="inputTemplate" name="inputTemplate"> <TextField platform="ios" borderStyle="Ti.UI.INPUT_BORDERSTYLE_BEZEL" keyboardToolbarColor="#999" keyboardToolbarHeight="40" top="10" height="35" width="300" value="Focus to see keyboard with toolbar"> <!-- Sets the keyboardToolbar property --> <KeyboardToolbar> <Toolbar> <Items> <Button systemButton="Ti.UI.iPhone.SystemButton.CANCEL" /> <FlexSpace/> <Button systemButton="Ti.UI.iPhone.SystemButton.CAMERA" /> <FlexSpace/> <Button style="Ti.UI.iPhone.SystemButtonStyle.DONE">Send</Button> </Items> </Toolbar> </KeyboardToolbar> </TextField> </ItemTemplate> </Templates> <ListSection headerTitle="Login Id" id="idSection"> <ListItem template="inputTemplate" textfield:value=""/> </ListSection> </ListView> </Window> </Alloy> {code} h3. index.js {code:javascript} $.settingsWin.open(); {code} h3. Console output {code} Titanium Command-Line Interface, CLI version 3.4.1, Titanium SDK version 3.4.1.GA Copyright (c) 2012-2014, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ [DEBUG] : Detecting modules in /Users/ndizazzo/Library/Application Support/Titanium/modules [DEBUG] : Detected android module: com.appcelerator.apm 1.0.10 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/android/com.appcelerator.apm/1.0.10 [DEBUG] : Detected android module: facebook 3.0.2 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/android/facebook/3.0.2 [DEBUG] : Detected android module: facebook 3.0.3 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/android/facebook/3.0.3 [DEBUG] : Detected android module: ti.cloudpush 3.3.0 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/android/ti.cloudpush/3.3.0 [DEBUG] : Detected android module: ti.cloudpush 3.3.4 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/android/ti.cloudpush/3.3.4 [DEBUG] : Detected android module: ti.map 2.1.4 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/android/ti.map/2.1.4 [DEBUG] : Detected android module: ti.map 2.2.2 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/android/ti.map/2.2.2 [DEBUG] : Detected commonjs module: ti.cloud 3.2.3 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/commonjs/ti.cloud/3.2.3 [DEBUG] : Detected commonjs module: ti.cloud 3.2.5 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/commonjs/ti.cloud/3.2.5 [DEBUG] : Detected commonjs module: ti.cloud 3.2.7 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/commonjs/ti.cloud/3.2.7 [DEBUG] : Detected iphone module: com.appcelerator.apm 1.0.10 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/iphone/com.appcelerator.apm/1.0.10 [DEBUG] : Detected iphone module: com.appcelerator.urlSession 1.0.1 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/iphone/com.appcelerator.urlSession/1.0.1 [DEBUG] : Detected iphone module: facebook 3.1.1 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/iphone/facebook/3.1.1 [DEBUG] : Detected iphone module: ti.coremotion 1.0.1 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/iphone/ti.coremotion/1.0.1 [DEBUG] : Detected iphone module: ti.map 2.0.2 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/iphone/ti.map/2.0.2 [DEBUG] : Detected iphone module: ti.map 2.0.4 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/iphone/ti.map/2.0.4 [DEBUG] : Detected iphone module: ti.touchid 1.0 @ /Users/ndizazzo/Library/Application Support/Titanium/modules/iphone/ti.touchid/1.0 [DEBUG] : Detecting plugins in /Users/ndizazzo/dev/Studio_Workspace/TestApplication/plugins [DEBUG] : Detected plugin: ti.alloy @ /Users/ndizazzo/dev/Studio_Workspace/TestApplication/plugins/ti.alloy [DEBUG] : Detecting plugins in /Users/ndizazzo/Library/Application Support/Titanium/plugins [DEBUG] : Detected plugin: com.appcelerator.test @ /Users/ndizazzo/Library/Application Support/Titanium/plugins/com.appcelerator.test [DEBUG] : Looking for Titanium plugin id=ti.alloy version=1.0 [INFO] : Found Titanium plugin id=ti.alloy version=1.0 [DEBUG] : Titanium SDK iOS directory: /Users/ndizazzo/Library/Application Support/Titanium/mobilesdk/osx/3.4.1.GA/iphone [INFO] : Deploy type: development [INFO] : Building for target: simulator [INFO] : Building using iOS SDK: 8.1 [INFO] : Building for iOS Simulator: iPhone 5s [DEBUG] : UDID: xxxx [DEBUG] : Simulator type: iphone [DEBUG] : Simulator version: 8.1 [INFO] : Building for device family: universal [DEBUG] : Setting Xcode target to Debug [DEBUG] : Setting Xcode build OS to iphonesimulator8.1 [DEBUG] : Xcode installation: /Applications/Xcode.app/Contents/Developer [DEBUG] : iOS WWDR certificate: installed [DEBUG] : Building for the following architectures: armv7 armv7s i386 [INFO] : Minimum iOS version: 6.0 [INFO] : Debugging disabled [INFO] : Profiler disabled [INFO] : Forcing rebuild: /Users/ndizazzo/dev/Studio_Workspace/TestApplication/build/iphone/build-manifest.json does not exist [INFO] : Initiating prepare phase [INFO] : Found Alloy app in /Users/ndizazzo/dev/Studio_Workspace/TestApplication/app [INFO] : Executing Alloy compile: /usr/local/bin/node /usr/local/bin/alloy compile /Users/ndizazzo/dev/Studio_Workspace/TestApplication/app --config platform=ios,version=0,simtype=none,devicefamily=universal,deploytype=development,target=simulator --no-colors [DEBUG] : .__ .__ [DEBUG] : _____ | | | | ____ ___.__. [DEBUG] : \__ \ | | | | / _ < | | [DEBUG] : / __ \| |_| |_( <_> )___ | [DEBUG] : (____ /____/____/\____// ____| [DEBUG] : \/ \/ [DEBUG] : Alloy 1.5.1 by Appcelerator. The MVC app framework for Titanium. [DEBUG] : ----- CONFIGURATION ----- [DEBUG] : raw config = "platform=ios,version=0,simtype=none,devicefamily=universal,deploytype=development,target=simulator" [DEBUG] : platform = ios [DEBUG] : version = 0 [DEBUG] : simtype = none [DEBUG] : devicefamily = universal [DEBUG] : deploytype = development [DEBUG] : target = simulator [DEBUG] : project path = /Users/ndizazzo/dev/Studio_Workspace/TestApplication [DEBUG] : app path = /Users/ndizazzo/dev/Studio_Workspace/TestApplication/app [DEBUG] : [DEBUG] : ----- CONFIG.JSON ----- [DEBUG] : dependencies = {} [INFO] : [config.json] regenerating CFG.js from config.json... [DEBUG] : { [DEBUG] : "dependencies": {}, [DEBUG] : "sourcemap": true, [DEBUG] : "autoStyle": false, [DEBUG] : "adapters": [ [DEBUG] : "localStorage", [DEBUG] : "properties", [DEBUG] : "sql" [DEBUG] : ] [DEBUG] : } [DEBUG] : [DEBUG] : ----- CLEANING RESOURCES ----- [DEBUG] : Removing orphaned controllers ... [DEBUG] : Removing orphaned models ... [DEBUG] : Removing orphaned styles ... [DEBUG] : Removing orphaned sync adapters... [DEBUG] : Removing orphaned assets and libs... [DEBUG] : [DEBUG] : ----- BASE RUNTIME FILES ----- [DEBUG] : [INFO] : ----- MVC GENERATION ----- [INFO] : [global style] writing to cache... [INFO] : [index.xml] view processing... [INFO] : style: "index.tss" [INFO] : view: "index.xml" [DEBUG] : /usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract._ItemArray.js:58 [DEBUG] : return state.itemsArray + '.push(' + s.parent.symbol + ');'; [DEBUG] : ^ [ERROR] : : Cannot read property 'symbol' of undefined [DEBUG] : at Object.CU.generateNodeExtended.post (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract._ItemArray.js:58:52) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/base.js:14:17) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/default.js:10:27) [DEBUG] : at parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Ti.UI.Button.js:30:30) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/base.js:11:17) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Ti.UI.Button.js:14:27) [DEBUG] : at Object.exports.generateNode (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:316:48) [DEBUG] : at Object.exports.generateNodeExtended (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:253:17) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract._ItemArray.js:55:16 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract._ItemArray.js:37:4) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/base.js:11:17) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract._ItemArray.js:18:27) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract.Items.js:15:48) [DEBUG] : at Object.exports.generateNode (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:316:48) [DEBUG] : at Object.exports.generateNodeExtended (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:253:17) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract._ItemContainer.js:51:15 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract._ItemContainer.js:31:4) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/base.js:11:17) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract._ItemContainer.js:20:27) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Ti.UI.iOS.Toolbar.js:11:52) [DEBUG] : at Object.exports.generateNode (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:316:48) [DEBUG] : at Object.exports.generateNodeExtended (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:253:17) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/_ProxyProperty.js:43:14 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/_ProxyProperty.js:32:4) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/base.js:11:17) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/_ProxyProperty.js:16:27) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/_ProxyProperty.KeyboardToolbar.js:12:37) [DEBUG] : at Object.exports.generateNode (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:316:48) [DEBUG] : at Object.exports.generateNodeExtended (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:253:17) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Ti.UI.TextField.js:48:14 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Ti.UI.TextField.js:30:4) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/base.js:11:17) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Ti.UI.TextField.js:20:27) [DEBUG] : at Object.exports.generateNode (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:316:48) [DEBUG] : at Object.exports.generateNodeExtended (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:253:17) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract.ItemTemplate.js:64:15 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract.ItemTemplate.js:54:5) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/base.js:11:17) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Alloy.Abstract.ItemTemplate.js:10:27) [DEBUG] : at Object.exports.generateNode (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:316:48) [DEBUG] : at Object.exports.generateNodeExtended (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:253:17) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Ti.UI.ListView.js:131:17 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Ti.UI.ListView.js:122:6 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Ti.UI.ListView.js:48:4) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/base.js:11:17) [DEBUG] : at Object.exports.parse (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/parsers/Ti.UI.ListView.js:29:27) [DEBUG] : at Object.exports.generateNode (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:316:48) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:391:29 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at Object.exports.generateNode (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/compilerUtils.js:386:5) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/index.js:577:28 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at parseAlloyComponent (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/index.js:566:5) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/index.js:258 [DEBUG] : :6 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at /usr/local/lib/node_modules/alloy/Alloy/commands/compile/index.js:247:6 [DEBUG] : at Array.forEach (native) [DEBUG] : at Function._.each._.forEach (/usr/local/lib/node_modules/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] : at module.exports (/usr/local/lib/node_modules/alloy/Alloy/commands/compile/index.js:243:4) [DEBUG] : at Object.<anonymous> (/usr/local/lib/node_modules/alloy/Alloy/alloy.js:103:46) [DEBUG] : at Module._compile (module.js:456:26) [DEBUG] : at Object.Module._extensions..js (module.js:474:10) [DEBUG] : at Module.load (module.js:356:32) [DEBUG] : at Function.Module._load (module.js:312:12) [DEBUG] : at Module.require (module.js:364:17) [DEBUG] : at require (module.js:380:17) [DEBUG] : at Object.<anonymous> (/usr/local/lib/node_modules/alloy/bin/alloy:3:1) [DEBUG] : at Module._compile (module.js:456:26) [DEBUG] : at Object.Module._extensions..js (module.js:474:10) [DEBUG] : at Module.load (module.js:356:32) [DEBUG] : at Function.Module._load (module.js:312:12) [DEBUG] : at Function.Module.runMain (module.js:497:10) [DEBUG] : at startup (node.js:119:16) [DEBUG] : at node.js:906:3 [ERROR] : Alloy compiler failed {code}

ALOY-1219

01/06/2015 08:23:07

ALLOY: prevent parsing of {{ }} in alloy views.

Alloy is currently catching and interpreting {{ }} as an alloy binding when it should only catch { }. This change is needed for https://github.com/dbankier/nano.

ALOY-1222

01/07/2015 18:58:17

Fix failing Travis test `[FAIL] alloy install plugin --> is supported`

Travis builds are failing with {{\[FAIL\] alloy install plugin --> is supported}} Failures are caused by recent changes for ALOY-1173 and ALOY-1207

ALOY-1226

01/13/2015 19:31:28

To Do sample app - validate() fails to prevent invalid (empty) items from being added

The model definition in the test/apps/models/todo app includes a validation check. If a model doesn't pass this check, it should not be added to the database. However, empty items are being added. Per the [Backbone docs|http://backbonejs.org/#Model-validate], you override the validate function with your own code. If a model fails validation, you return any string and save() will be prevented.

ALOY-1228

01/15/2015 14:33:54

Selective compilation can fail with platform-specific controllers and throws Exception incorrectly

Per email from David Bankier, the compilation-optimization technique implemented in [PR625|https://github.com/appcelerator/alloy/pull/625] will fail in certain cases. He suggests the following changes be made to fix these issues: * https://github.com/xavierlacot/alloy/pull/1 * https://github.com/xavierlacot/alloy/pull/2 Investigate and implement, add tests

ALOY-1231

01/20/2015 19:33:57

Mapping sample: add readme, remove map key

Add a readme file to the samples/mapping app that describes the steps that an Android developer would need to follow to run the app (obtain a key, which file to update, etc.) Include a reference to the Guides where the we describe how to obtain a key. Also, update the JMK file to remove the old key (commented out currently). Replace it with something like {{// Paste your key here}}

ALOY-1234

02/02/2015 15:51:49

Annotate Alloy API docs with GitHub URL

To support TIDOC-2058, the following PR adds an {{@editurl}} field to the JSDuck docs for each public class. https://github.com/appcelerator/alloy/pull/659 Ideally, this would be done by a doc build script (like we do for Titanium), but since there are just a few Alloy docs to annotate, this seemed a more direct approach.

ALOY-1237

02/10/2015 11:57:42

Alloy: Remove all event listeners added via view in $.destroy()

Too make it easier for developers to clean up the event listeners they've added via the XML view ({{onClick}} and other attributes), could we make it so that if you add an event listener that way, that it would also be removed in the {{$.destroy()}} method? The developer would still be responsible for calling that method and for removing listeners he added in the controller, but it would align nicely with the current behaviour of the method where it also cleans up a listener added via the view, which is for the {{<Collection>}} or {{<Model}}> tag. For reference: https://github.com/appcelerator/alloy/blob/master/test/apps/basics/markup_events/_generated/ios/alloy/controllers/index.js#L44-L49 Perhaps the {{__defers}} object could be used for this in some way? We could even go as far as extending the Backbone {{$.listenTo()}} method that if its first argument is a proxy, then it would both pass it on to that proxies' {{addEventListener}} method and queue it for removal in {{$.destroy}} at the same time.

ALOY-1238

02/10/2015 17:31:57

Can't re-create index controller after renaming original one

h5. Scenario I want to refactor an existing Alloy app by moving/re-naming the current index.xml/js/tss controller triad to something else, and then create a new index controller. h6. Steps: 1. Create a new Alloy app. 2. Rename views/index.xml, styles/index.tss, and controllers/index.js to views/main.xml, styles/main.tss, and controllers/main.js. 3. Create a new "index" controller: {code} $ alloy generate controller index {code} h6. Results: Actual: {code} [ERROR] Alloy "app" directory has no "controllers/index.js" file at "/Users/tstatler/alloy_test_apps/testing/boo/app/controllers/index.js". {code} Expected: I can create a new index controller w/o error.

ALOY-1239

02/11/2015 15:48:22

Set Node 0.10 as minimum supported version

Update the minimum supported version of Node to 0.10.x. Make sure to check for and update any version checks in the code as well as updating the package.json file.

ALOY-1249

02/18/2015 15:59:35

iOS: Misleading error message when controller file not found

When Alloy can't find a controller on iOS, it gives a message saying that a module (controllerName) for architecture (arm7/arm64) can't be found. very confusing, becuase it sounds like there's a native module problem. {code:title=index.js} Alloy.createController('foo'); {code}

ALOY-1252

02/19/2015 16:45:31

restrictionPath missing in parseAlloyComponent for controller without corresponding view

As reported at https://github.com/dbankier/TiShadow/issues/388#issuecomment-73190579 Alloy optimizes all JS files when using the selective compile feature implemented in ALOY-1216. Community PR to resolve this: https://github.com/appcelerator/alloy/pull/661 Needs verification and testing.

ALOY-1257

03/24/2015 18:15:09

Map DocumentViewer to Ti.UI.iOS instead of deprecated Ti.UI.iPad namespace

The {{DocumentViewer}} tag is currently [mapped|https://github.com/appcelerator/alloy/blob/master/Alloy/common/constants.js#L195] to the {{Ti.UI.iPad}} namespace, while that has been deprecated since Ti SDK 3.0.0 in favour of {{Ti.UI.iOS}}. * PR on master: https://github.com/appcelerator/alloy/pull/673/files

ALOY-1262

04/13/2015 11:03:46

a directory ending with ".js" causes Alloy compiler error

This bug is related to [ALOY-920], which introduced a fix for the specific case of {{should.js}}. When building an Alloy project containg a library directory named with a {{.js}} suffix, the compiler fails: {code} [INFO] ----- OPTIMIZING ----- [INFO] - iphone/vendor/validator.js [ERROR] Error generating AST for "/Users/xavier/titanium/DemoApp/Resources/iphone/vendor/validator.js" [ERROR] EISDIR, illegal operation on a directory [ERROR] Alloy compiler failed {code} The {{getJsFiles()}} Alloy compiler method filters which files have to be optimized, as in https://github.com/appcelerator/alloy/blob/master/Alloy/commands/compile/index.js#L1017 This method fails to exclude items which are directories ending with {{.js}}, and {{uglifyjs.parse()}} then throws an error. A pull request has been submitted at https://github.com/appcelerator/alloy/pull/683

ALOY-1278

05/07/2015 00:05:04

Pass model config to migration functions

It will be nice if sql sync adapter will pass model config to migration functions. It will get access to model columns inside migration for example. {code:javascript} migration.up = function(migrator, config) { migrator.createTable(config); // other migration actions }; {code} Community PR: https://github.com/appcelerator/alloy/pull/684

ALOY-1265

05/12/2015 20:28:41

Update builtin moment.js library to 2.10.6 (or latest)

Moment.js has changed how it handles time zones/UTC. Took me forever to figure out why my calls to {{moment().utcOffset();}} didn't work.

ALOY-1273

05/25/2015 08:32:45

Code documentation contains links to out-dated Titanium docs

The (code) documentation in the Alloy repository contains links to the now out-dated Titanium documentation, where it should be updated to link to the Platform documentation: https://github.com/appcelerator/alloy/search?utf8=%E2%9C%93&q=%22titanium%2Flatest%22

ALOY-1276

05/27/2015 22:25:00

Alloy's deepExtend is broken

Since [this commit|https://github.com/appcelerator/alloy/commit/84c9470d9932a5ad762f8220db79802d91ec4c86], the {{deepExtend()}} method present in Alloy is broken, as deeply merged properties get overwritten three line below. The method should not state: {code} target[name] = deepExtend(deep, clone, copy); } target[name] = copy; {code} but: {code} target[name] = deepExtend(deep, clone, copy); } else { target[name] = copy; } {code} As a consequence, this method is purely useless.

ALOY-1280

06/20/2015 00:15:33

Support CommandBar in XML markup

Windows Phone has a platform-specific feature called the CommandBar, similar to the Android Action Bar or iOS Toolbar. The Titanium.UI.Windows.CommandBar object is assigned an array of buttons and separators to its items property for it to display. For a classic Titanium example, see: https://appcelerator.github.io/appc-docs/latest/#!/api/Titanium.UI.Windows.CommandBar Example of an Alloy view using the CommandBar {noformat} <Alloy> <Window> <CommandBar platform="windows"> <AppBarButton icon="Titanium.UI.Windows.SystemIcon.ADD"/> <!-- Support shorthand notation, that is, omit the namespace --> <AppBarToggleButton icon="LIKEDISLIKE" /> <AppBarSeparator /> </CommandBar> </Window> </Alloy> {noformat}

ALOY-1281

06/22/2015 15:51:55

RSS sample should be removed in favour of Studio version

The RSS sample in the Alloy repository... https://github.com/appcelerator/alloy/tree/master/samples/rss .. should be removed to avoid confusion now Studio has an updated version: https://github.com/appcelerator-developer-relations/Sample.RSS

ALOY-1283

06/25/2015 11:16:10

ActionView views with an ID cannot be found under $ because they are created after merge

ALOY-1175 fixed this issue for IDs set on {{<MenuItem>}} but it is still an issue for views under {{<ActionView>}}. Because they are created after the controller merges {{$.__views}} with {{$}} you cannot access the views via {{$.<id>}}. *index.xml* {code:xml} <Alloy> <Window> <Menu> <MenuItem title="Open" showAsAction="Titanium.Android.SHOW_AS_ACTION_ALWAYS"> <ActionView> <View id="myViewInActionView" backgroundColor="red"> <Button onClick="changeColor">Change Color</Button> </View> </ActionView> </MenuItem> </Menu> </Window> </Alloy> {code} *index.js* {code:javascript} $.index.open(); function changeColor() { $.myViewInActionView.backgroundColor = 'green'; } {code}

ALOY-1287

07/01/2015 09:29:12

Alloy styles compilation does not produce the same results accross successive compilations

In some cases, when the developer overloads in a stylesheets some styles defined in the {{app.tss}} files, the alloy compilation won't produce the same resulting javascript accross successive compilations. Alloy's styler orders style rules to define their priority, but there's a bug with the {{app.tss}} global styles being cached and therefore not correctly being counted by the styler during a compilation phase when {{app.tss}} didn't change. Steps to reproduce: * create a new alloy app, replace its {{app}} folder with the one contained in the attached app.zip file * compile once: {{alloy compile --config platform=ios}}. Check in {{Resources/iphone/alloy/controllers/sum.js}} that the style rules defined in {{app/styles/sum.tss}} are applied correctly * compile again, the generated javascript in the {{Resources}} directory differ. In particular, the {{Resources/iphone/alloy/controllers/sum.js}} does only contain rules from the {{app.tss}} file. A PR is being proposed to fix this problem.

ALOY-1288

07/02/2015 11:45:48

Windows: Label not visible when using default app.tss

The [default app.tss|https://github.com/appcelerator/alloy/blob/master/Alloy/template/app.tss] sets the Window backgroundColor to white for all platforms. on Windows the default color of a label is white, making them invisible when using the default {{app.tss}}. Just like we do for Android, we should set the Label color to black. Note: There might still be issues with other elements that default to white on Windows, like titles in ListViews.

ALOY-1295

07/30/2015 22:46:04

Windows: App crashes when calling fetch() method on a collection bound to a view

REPRODUCTION: Create a new Alloy project and overwrite the files with the versions from the attachment. Run the project in the Windows emulator. RESULTS: The app crashes with the following error: {code} [INFO] Installing and launching the application [INFO] Project built successfully in 20s 802ms [INFO] Connected to app -- Start application log ----------------------------------------------------- [INFO] Disconnected from app -- End application log ------------------------------------------------------- [ERROR] The remote procedure call failed. [ERROR] Error: The remote procedure call failed. at ChildProcess.<anonymous> (C:\ProgramData\Titanium\mobilesdk\win32\5.1.0.v20151026164636\node_modules\windowslib\lib\emulator.js:287:15) at ChildProcess.emit (events.js:110:17) at maybeClose (child_process.js:1008:16) at ChildProcess._handle.onexit (child_process.js:1080:5) {code} OTHER INFO: Comment out the Alloy.Collections.book.fetch() method in the app/controllers/index.js file and the application runs fine.

ALOY-1297

08/12/2015 01:45:30

Cannot use localized strings for AlertDialog ButtonNames in XML

Create a new Alloy project and overwrite the files with the one in the attached ZIP file. Run the project. RESULTS: The dialog displays the localize function and not the value. See attached screenshot. OTHER INFO: Works fine in the TSS.

ALOY-1299

08/17/2015 12:59:06

Cannot build a new project for iOS due to missing appicons

Cannot build to iOS simulator or device. Error shown during build for missing appicons. This is a regression as the issue does not occur on 4.1.0.GA Steps to Reproduce: 1. Create a new titanium project 2. Build it for iOS simulator or device Actual Result: An error is shown {code} [ERROR] No suitable app icon that is at least 180x180, unable to create missing icons: [ERROR] appicon-Small@3x.png - Used for iPhone - required size: 87x87 (29x29 @3x) [ERROR] appicon-Small-40.png - Used for iPad - required size: 40x40 (40x40 @1x) [ERROR] appicon-Small-40@2x.png - Used for iPhone, iPad - required size: 80x80 (40x40 @2x) [ERROR] appicon-Small-40@3x.png - Used for iPhone - required size: 120x120 (40x40 @3x) [ERROR] appicon-76.png - Used for iPad - required size: 76x76 (76x76 @1x) [ERROR] appicon-76@2x.png - Used for iPad - required size: 152x152 (76x76 @2x) [ERROR] An error occurred during build after 8s 152ms ERROR | ti run exited with error code 1 {code} Expected Result: The project should build successfully for iOS

ALOY-1300

08/20/2015 08:54:41

iOS: Assets Catalog inconsistency between Alloy and Classic

Comparing the folders *Assets.xcassets* in the generated build folder between a classic and alloy project, the alloy *AppIcon.appiconset* and *LaunchImage.launchimage* contains inconsistent images, even though the file naming convention is correct. See attached images for comparison. h4. Steps to reproduce 1. Create a ti classic project: ti create 2. enter project folder 3. Create Alloy: alloy new 4. Compile Alloy: alloy compile --config platform=ios 5. Build project: ti build -p ios -I 9.0 h4. Expected result images in assets catalog should be consistent h4. Actual result appicon-60@2x.png and appicon-60@3x.png is different from the rest Default-Landscape-736h@3x.png and Default-667h@2x.png and Default-Portrait-736h@3x.png is different from the rest *Note*: because of this, appc run is seeing the same issue.

ALOY-1627

08/25/2015 23:40:33

Breakpoints not working on alloy apps

Sprint noticed their their break points aren't working on conditions in their alloy apps. I've been able to verify this with my own testing on a fresh application. To clarify (➜ == break point): {code} // This will not pause and the inner block runs ➜ if(true){ console.log("hello Jay!"); } // This will pause if(true){ ➜ console.log("hello Jay!"); } {code} h3. Steps to reproduce 1. Create a new alloy app within Appcelerator Studio 2. Add the above if statement with a breakpoint on the conditoin 3. Run in debugging mode h3. Expected The code pauses on the if statement and doesn't call console.log() h3. Actual The code is ran as if the breakpoint isn't there.

ALOY-1302

09/10/2015 08:21:30

Alloy needs to have a consistent behavior with Ti on App Icons

See related ticket. Currently the behavior in managing the app icons is different. This ticket has to address and make them consistent. With the related ticket, a DefaultIcon.png WILL BE copied into the project's root when {{alloy new}} is run. h4. Test cases APPC CLI : A. Brand new project via Appc. *appc new* *appc run -p ios* B. *appc run -p ios -T dist-adhoc* C. Scenario where DefaultIcon.png (use attached [^DefaultIcon.png] in ticket), and ALL icons described [here|http://docs.appcelerator.com/platform/latest/#!/guide/Icons_and_Splash_Screens] exists, but are different from DefaultIcon.png. (This is the situation when a user decide to IGNORE the DefaultIcon.png and have his very own other icons). *appc run -p ios* D. Scenario where DefaultIcon.png is missing, but ALL icons described [here|http://docs.appcelerator.com/platform/latest/#!/guide/Icons_and_Splash_Screens] exists. (This is the situation when a user updates an existing project to the latest SDK). *appc run -p ios* E. Scenario where DefaultIcon.png is missing, but SOME icons described [here|http://docs.appcelerator.com/platform/latest/#!/guide/Icons_and_Splash_Screens] are missing. (This is the situation when a user updates an existing project with missing icons to the latest SDK). *appc run -p ios* h4. Expected Results: A. Build success. See inside build->iphone->Assets.xcassets and see these files [^defaultContent.png] B. Build success. See inside build->iphone->build->Products->Release-iphoneos->SGIcon.app->Show Package Content, there's the iTunesArtwork.png and iTunesArtwork@2x.png C. Build success. User's icons should be prioritized over the use of DefaultIcon.png. See inside build->iphone->Assets.xcassets and see these files [^withDefaultAndAllIcons.png] D. Build success. See inside build->iphone->Assets.xcassets and see these files [^defaultContent.png] E. Build Fail. See error prompt {code} [ERROR] There are missing app icons [ERROR] You must either create the missing icons below or create an image named "DefaultIcon.png" in the root of your project [ERROR] If the DefaultIcon.png image is present, the build will use it to generate all missing icons [ERROR] It is highly recommended that the DefaultIcon.png be 1024x1024 [ERROR] Unable to create missing icons: [ERROR] Resources/iphone/appicon-Small@3x.png - Used for iPhone - required size: 87x87 [ERROR] Resources/iphone/appicon-Small-40@3x.png - Used for iPhone - required size: 120x120 [ERROR] Resources/iphone/appicon-60@3x.png - Used for iPhone - required size: 180x180 [ERROR] An error occurred during build after 2s 554ms {code} h4. Actual Result: A. Build success. But the content of build->iphone->Assets.xcassets is inconsistent. [^appcdefaultContent.png] In tooling, we have to remove all the existing icons in the Resources folder so that DefaultIcon.png can do it's job.

ALOY-1304

09/16/2015 10:58:18

Alloy: Support Node text for TextField and TextArea

The following sample and attached screenshot shows that {{TextArea}} and {{TextField}} do not support using node text to set the {{value}} property. {code:xml} <Alloy> <Window backgroundColor="white" layout="vertical"> <Label top="20" width="100" backgroundColor="#ccc">Hello</Label> <TextField top="20" width="100" backgroundColor="#ccc">Hello</TextField> <TextArea top="20" width="100" backgroundColor="#ccc">Hello</TextArea> </Window> </Alloy> {code} This is in line with [documentation|http://docs.appcelerator.com/platform/latest/#!/guide/Alloy_XML_Markup-section-35621528_AlloyXMLMarkup-PropertyMapping] so not a bug, but a feature request.

ALOY-1305

09/20/2015 22:07:07

deepclean.js syntax error in line 17: missing semicolon;

Upgraded to Appcelerator Studio 5 and changed the tiapp.xml for the app (I have been in the process of developing for several months now targeted for iOS/iPad) to use Titanium SDK 5.0.0 GA. Experienced the following issue any time I try to build the app (iOS app for iPad 2): deepclean.js regenerates itself and results in a missing semicolon. This is traceable to a syntax error in the GitHub source code https://github.com/appcelerator/alloy/blob/12310dda3b987292ee1bbbbcfdd129af6b6c5cfc/hooks/deepclean.js I have not enough experience with the platform to know how to proceed in resolving this issue.

ALOY-1308

09/25/2015 18:40:12

iTunesArtwork is being copied into Resources/iphone instead of project root

The iTunesArtwork and iTunesArtwork@2x files are being copied from the assets/iphone directory into the Resources/iphone directory when actually they should be copied in to the project root.

ALOY-1313

10/06/2015 17:33:05

Add "bugs" URL to package.json

Adding a URL to the location of where "bugs" are filed makes it easier for developers. {code} "bugs": { "url": "https://jira.appcelerator.org/browse/ALOY" }, {code}

ALOY-1314

10/08/2015 08:42:25

Alloy: Remove alpha channel from DefaultIcon.png

Xcode does not accept app icons with alpha channel in it, please remove the alpha channel for DefaultIcon.png

ALOY-1315

10/08/2015 19:24:31

Update out-of-date Alloy dependencies.

There are a number of out-dated Alloy dependencies, we should update them to the latest stable versions. {quote} "colors" can be updated from 0.6.0-1 to 1.1.2 (Installed: none, Latest: 1.1.2) "pkginfo" can be updated from 0.2.2 to 0.3.0 (Installed: none, Latest: 0.3.0) "commander" can be updated from 0.6.1 to 2.8.1 (Installed: none, Latest: 2.8.1) "wrench" can be updated from 1.3.9 to 1.5.8 (Installed: none, Latest: 1.5.8) "jsonlint" can be updated from 1.5.1 to 1.6.2 (Installed: none, Latest: 1.6.2) "uglify-js" can be updated from 2.4.15 to 2.4.24 (Installed: none, Latest: 2.4.24) "source-map" can be updated from 0.1.9 to 0.5.1 (Installed: none, Latest: 0.5.1) "moment" can be updated from 2.7.0 to 2.10.6 (Installed: none, Latest: 2.10.6) "node.extend" can be updated from 1.0.10 to 1.1.5 (Installed: none, Latest: 1.1.5) {quote}

ALOY-1316

10/09/2015 12:54:36

Support use of $.args.* in any XML attribute or TSS property

We now support using {{$.args}} in XML {{if=$.args.foo}} attributes. However, it would be very useful if you could use it as value of any attribute, as well as value in TSS. The following should then result in a Window containing a label that says _bar_: *index.xml* {code:xml} <Alloy> <Window class="container"> <Require src="foo" foo="bar" /> </Window> </Alloy> {code} *foo.xml* {code:xml} <Alloy> <Label text="$.args.foo" /> </Alloy> {code} Currently this compiles to: {code:javascript} $.__views.foo = Ti.UI.createLabel({ text: "$.args.foo", id: "foo" }); {code} If you try to use {{$.args.foo}} in TSS it will fail to compile with: {code} [ERROR] Expected "Alloy", "L", "Ti", "Titanium", "WPATH", "[", "false", "null", "true", "undefined", "{", comment, end of line, number, string or whitespace but "$" found. {code}

ALOY-1317

10/12/2015 09:08:02

Alloy: Default top-level ID doesn't take if-attribute into account

While ALOY-851 is said to be fixed, the following: {code:xml} <Alloy> <TabGroup if="Alloy.Globals.requiredVersion"> <Require src="list" /> <Require src="apis" /> <Require src="console" /> </TabGroup> <Window if="!Alloy.Globals.requiredVersion"> <Label>This sample requires Titanium 5.1 or later</Label> </Window> </Alloy> {code} still compiles to: {code:javascript} if (Alloy.Globals.requiredVersion) { var __alloyId11 = []; $.__views.__alloyId12 = Alloy.createController("list", { id: "__alloyId12" }); __alloyId11.push($.__views.__alloyId12.getViewEx({ recurse: true })); $.__views.__alloyId14 = Alloy.createController("apis", { id: "__alloyId14" }); __alloyId11.push($.__views.__alloyId14.getViewEx({ recurse: true })); $.__views.__alloyId16 = Alloy.createController("console", { id: "__alloyId16" }); __alloyId11.push($.__views.__alloyId16.getViewEx({ recurse: true })); $.__views.index = Ti.UI.createTabGroup({ tabsBackgroundColor: "white", tabsTintColor: Alloy.CFG.brandPrimary, tabs: __alloyId11, id: "index" }); $.__views.index && $.addTopLevelView($.__views.index); } if (!Alloy.Globals.requiredVersion) { $.__views.__alloyId17 = Ti.UI.createWindow({ backgroundColor: "#fff", barColor: Alloy.CFG.brandPrimary, navTintColor: "#FFF", translucent: false, titleAttributes: { color: "#FFF" }, id: "__alloyId17" }); $.__views.__alloyId17 && $.addTopLevelView($.__views.__alloyId17); $.__views.__alloyId18 = Ti.UI.createLabel({ text: "This sample requires Titanium 5.1 or later", id: "__alloyId18" }); $.__views.__alloyId17.add($.__views.__alloyId18); } {code} which shows that the negative condition does not give the ID "index" to the window, which it should.

ALOY-1318

10/14/2015 17:46:43

DefaultIcon(-platform).png should be theme-able

The new {{/DefaultIcon.png}} which has platform specific versions at {{/DefaultIcon-<platform>.png}} should be theme-able via Alloy. We probably need a similar approach as with {{i18n}} and {{platform}} since we can't overwrite the {{DefaultIcon.png}} in the project root, so we have to do it at build-time. - https://github.com/appcelerator/alloy/pull/662/files#diff-ddbdb7300fa15590afdfee9246ac61fcR327 - https://github.com/appcelerator/alloy/pull/662/files#diff-6487ccfa4909144bbc33134e4d85bdddR159 Kindly pointed out by [~jasonkneen]: https://twitter.com/jasonkneen/status/654326054488834048

ALOY-1319

10/14/2015 22:25:12

Support CardView in XML

Titanium SDK 5.1.0 introduces a new view container for Android called CardView. http://appcelerator.github.io/appc-docs/latest/#!/api/Titanium.UI.Android.CardView We should support it in XML and implicitly set the namespace to Ti.UI.Android. Example XML of sample in API docs: {noformat} <Alloy> <Window> <ScrollView> <CardView ns="Ti.UI.Android"> <Label>A long label...</Label> </CardView> <CardView ns="Ti.UI.Android"> <Label>A long label...</Label> </CardView> <CardView ns="Ti.UI.Android"> <Label>A long label...</Label> </CardView> ... </ScrollView> </Window> </Alloy> {noformat}

ALOY-1320

10/28/2015 12:43:27

Styles not applied when an element uses another namespace

When an Alloy view element uses another namespace styles are no longer applied. When you set {{ns}} to the default {{Ti.UI}} it still works, but any other value will not. *index.xml* {code:xml} <Alloy> <Window> <View /> <View ns="Ti.UI" /> <View ns="Ti.UI.Android" /> </Window> </Alloy> {code} *index.tss* {code} 'View': { backgroundColor: 'red' } {code} *Compiled code* {code:javascript} $.__views.__alloyId0 = Ti.UI.createView({ backgroundColor: "red", id: "__alloyId0" }); $.__views.index.add($.__views.__alloyId0); $.__views.__alloyId1 = Ti.UI.createView({ backgroundColor: "red", id: "__alloyId1" }); $.__views.index.add($.__views.__alloyId1); $.__views.__alloyId2 = Ti.UI.Android.createView({ id: "__alloyId2" }); {code}

ALOY-1321

10/29/2015 01:31:23

iOS: packaged app icons for new projects needs to be updated

Since TI SDK 5.0.0, we support app icons resizing, placing them into assets catalog etc, so we should do a clean up on the app icons to reduce the number of warnings being shown now. 1. All app icons should NOT have alpha channel. 2. Remove unsupported app icons. See current trace when there's no DefaultIcon.png or DefaultIcon-ios.png: {code} [INFO] Creating app icon set [DEBUG] Unsupported app icon Resources/iphone/appicon-176@2x.png, skipping [DEBUG] Unsupported app icon Resources/iphone/appicon-60.png, skipping [WARN] Resources/iphone/appicon-60@2x.png contains an alpha channel and will be flattened against a white background [WARN] Resources/iphone/appicon-60@3x.png contains an alpha channel and will be flattened against a white background [DEBUG] Unsupported app icon Resources/iphone/appicon-72.png, skipping [DEBUG] Unsupported app icon Resources/iphone/appicon-72@2x.png, skipping [WARN] Resources/iphone/appicon-76.png contains an alpha channel and will be flattened against a white background [WARN] Resources/iphone/appicon-Small-40.png contains an alpha channel and will be flattened against a white background [WARN] Resources/iphone/appicon-Small-40@2x.png contains an alpha channel and will be flattened against a white background [DEBUG] Unsupported app icon Resources/iphone/appicon-Small-50.png, skipping [DEBUG] Unsupported app icon Resources/iphone/appicon-Small-50@2x.png, skipping [WARN] Resources/iphone/appicon-Small.png contains an alpha channel and will be flattened against a white background [WARN] Resources/iphone/appicon-Small@2x.png contains an alpha channel and will be flattened against a white background [DEBUG] Unsupported app icon Resources/iphone/appicon@2x.png, skipping {code} *OR* we can just remove all the ios app icons in the assets folder, and only have DefaultIcon.png in the root of the project to avoid confusion.

ALOY-1323

11/01/2015 18:49:35

Alloy: module-tag in Alloy element effects all controller-views

The attached app-folder demonstrates that when you use the {{module}} tag on the {{<Alloy>}} tag of one view, this will be applied to *all* other controller-views as well. 1. Compile the app. 2. Open {{Resources/iphone/controllers/testWindow.js}}. 3. Confirm that it has {{(require("testModule").createWindow || Ti.UI.createWindow)}} for all views as well, while only {{app/views/index.xml}} has has the {{module}} tag. Found by [~falko]

ALOY-1325

11/04/2015 11:51:27

Add PreviewContext element to XML views

Alloy should support the new {{Ti.UI.iOS.createPreviewContext}}. * A PreviewContext can be added to most views via their {{previewContext}} property. * The PreviewContext itself has a {{preview}} property which must be assigned a single View. * The PreviewContext also has an {{actions}} property for one or more actions or action groups. {code:xml} <Alloy> <View> <PreviewContext onPeek="fn1" onPop="fn2" contentHeight="300"> <Preview> <View> <Label>Hello</Label> </View> </Preview> </PreviewContext> <View> <ListView> <PreviewContext onPeek="fn"> <Preview> <View> <Label>Hello</Label> </View> </Preview> <Actions> <Action title="Email" onClick="fn" /> <ActionGroup title="Delete"> <Action title="Confirm" onClick="fn" /> <Action title="Cancel" onClick="fn" /> </ActionGroup> </Actions> </PreviewContext> <ListSection> <ListItem title="Hello" /> </ListSection> </ListView> </Alloy> {code}

ALOY-1331

11/16/2015 23:34:31

Windows: App crashes with 'Cannot find variable: OS_BLACKBERRY

h5.Description When building an Alloy app for Windows Platform the app crashes with the below error The error originates from [this line in alloy.js|https://github.com/appcelerator/alloy/blob/1fb9878e769c6afee6f46516c08b4708830e26a6/Alloy/lib/alloy.js#L486] and removing the OS_BLACKBERRY check allows the app to launch. {code} [ERROR] : Application Error: { [ERROR] : "line": 2, [ERROR] : "column": 10, [ERROR] : "message": "Error while require(/app) Error while require(alloy) Can't find variable: OS_BLACKBERRY", [ERROR] : "native_stack": [ [ERROR] : "JSExportClass<class Titanium::GlobalObject>::CallNamedFunction" [ERROR] : ] [ERROR] : } {code} h5.Steps to reproduce 1. Create an Alloy app using {{appc new}} 2. Build the app to Windows Platform using {{appc run -p windows}} h5.Actual Result App crashes with the below {code} [ERROR] : Application Error: { [ERROR] : "line": 2, [ERROR] : "column": 10, [ERROR] : "message": "Error while require(/app) Error while require(alloy) Can't find variable: OS_BLACKBERRY", [ERROR] : "native_stack": [ [ERROR] : "JSExportClass<class Titanium::GlobalObject>::CallNamedFunction" [ERROR] : ] [ERROR] : } {code} h5.Expected result App should not crash

ALOY-1335

11/27/2015 10:41:20

Use Alloy's deepExtend to handle conditional on-device style inheritance

Alloy selectors provide ways to overload style rules based on switches (formFactor, OS, conditional rules, etc.). Say the TSS is somehow: {code} ... ".title-home": { bottom: 4, }, ".title-home[formFactor=tablet]": { bottom: 8 }, ... {code} The generated code will look like: {code} Alloy.deepExtend(true, o, { bottom: 4 }); Alloy.isTablet && _.extend(o, { bottom: 8 }); {code} If this works fine with most of the properties, this is particularly annoying with font or nested properties. For instance, {code} ".title-home": { font: { fontFamily: "Delius-Regular", fontSize: 11 } }, ".title-home[formFactor=tablet]": { font: { fontSize: 22 } }, {code} will result in the font name being simply ignored on tablets, as {{_.extend()}} is not a deepExtend method. We're lucky, Alloy provides a {{deepExtend()}} implementation which we may want to use. I therefore propose to switch from {{_.extend()}} to Alloy's {{deepExtend}} implementation. This will allow much more efficient ways of integrating complex graphical interfaces, with style inheritances all across the app: {code:xml} <Label class="fonticon icon-row-right icon-arrow-md icon-arrow-right white" /> {code} All styles are merged deeply, and it becomes unnecessary to repeat over and over the font name. I _know_ that this change may break many tests, but I strongly believe that this behavior is the right way styles _should_ work, in the sake for development efficiency.

ALOY-1340

12/14/2015 17:32:48

Alloy selective compilation broken since ALOY-1332

Since [this commit|https://github.com/feons/alloy/commit/25855c1f342eecf6cb6e69dca007d05ebde1771b#diff-ddbdb7300fa15590afdfee9246ac61fcR177], Alloy's selective compilation is broken since the {{Resources}}'s {{alloy.js}} file gets replaced each and every time the alloy compile command is called. Instead, the fix should look if there's a file restriction, and not replace {{alloy.js}} if this restriction does not affect this file. This is particularly problematic when using some compilation watcher (aka. tishadow + grunt-tishadow), which look for changes in the {{Resources}} folder to re-launch the app. With the current change, the app will be refreshed using a template-based {{alloy.js}} file (not a recompiled one).

ALOY-1341

12/16/2015 21:05:23

Add Arabic lang to builtin MomentJS

Community PR: https://github.com/appcelerator/alloy/pull/741 {quote} Arabic Saudi Arabic is the common use from GCC countries, Yemen, Egypt and Sudan. Also using Arabic number ١ ٢ ٣ ٤ ٥ ٦ ٧ ٨ ٩ instead of English {quote}

ALOY-1342

12/16/2015 21:57:46

Sample Todo App TextField text color to black

Community PR: https://github.com/appcelerator/alloy/pull/702

ALOY-1345

01/04/2016 21:20:44

iOS Attributed Strings are not showing

h6.Issue Description Using Attributed String for label in Alloy, it is not showing up in iOS. Where as the same is working properly for Android and in classic. h6.Steps to reproduce //Alloy # Create a new simple project application in alloy # Open the index.xml view # Add the next Label: {code} <Label> <AttributedString class="as"> Appcelerator Titanium rocks! </AttributedString> </Label> {code} # Open the index.tss Style # Add the next style: {code} ".as" : { attributes: [ { type: Ti.UI.ATTRIBUTE_FOREGROUND_COLOR, value: 'red', range: [0, 4] } ] } {code} # Run // Classic (Working project) # Create a new cassic default application project # Open the app.js file # Replace the content with the next code: {code} var win = Ti.UI.createWindow({ backgroundColor: "white" }); var attr = Titanium.UI.createAttributedString({ text: "Appcelerator Rocks" }); // Underlines text attr.addAttribute({ type: Ti.UI.ATTRIBUTE_FOREGROUND_COLOR, value: 'red', range: [0, 4] }); var label = Titanium.UI.createLabel({ left: 20, right: 20, height: Titanium.UI.SIZE, attributedString: attr }); win.add(label); win.open(); {code} # Run

ALOY-1346

01/06/2016 15:54:07

Controller template should no longer declare args variable

Since Alloy 1.6.0 (by ALOY-1092) the compiled controllers [have the following line|https://github.com/appcelerator/alloy/blob/master/Alloy/template/component.js#L20]: {code:javascript} this.args = arguments[0] || {}; // .. var $ = this; {code} Still, our [template for new controllers|https://github.com/appcelerator/alloy/blob/master/Alloy/template/controller.js] has: {code:javascript} var args = arguments[0] || {}; {code} Clearly this is no longer needed. The template can be emptied and the availability of {{$.args}} should be documented. I'll create a separate TIDOC ticket for that.

ALOY-1350

02/04/2016 08:54:16

Warning on compile: moment construction falls back to js Date

Alloy spits out a Moment.js warning on compile and a long stack trace on debug-level: {code} [INFO] [ios.xml] view processing... [INFO] style: "ios.tss" [INFO] view: "ios.xml" [WARN] ing: moment construction falls back to js Date. This is discouraged and will be removed in upcoming major release. Please refer to https://github.com/moment/moment/issues/1407 for more info. [ERROR] [DEBUG] at Function.createFromInputFallback (/Users/fokkezb/dev/forks/alloy/node_modules/moment/moment.js:746:36) [DEBUG] at configFromString (/Users/fokkezb/dev/forks/alloy/node_modules/moment/moment.js:826:32) [DEBUG] at configFromInput (/Users/fokkezb/dev/forks/alloy/node_modules/moment/moment.js:1353:13) [DEBUG] at prepareConfig (/Users/fokkezb/dev/forks/alloy/node_modules/moment/moment.js:1340:13) [DEBUG] at createFromConfig (/Users/fokkezb/dev/forks/alloy/node_modules/moment/moment.js:1307:44) [DEBUG] at createLocalOrUTC (/Users/fokkezb/dev/forks/alloy/node_modules/moment/moment.js:1385:16) [DEBUG] at local__createLocal (/Users/fokkezb/dev/forks/alloy/node_modules/moment/moment.js:1389:16) [DEBUG] at utils_hooks__hooks (/Users/fokkezb/dev/forks/alloy/node_modules/moment/moment.js:16:29) [DEBUG] at Object.exports.createDate (/Users/fokkezb/dev/forks/alloy/Alloy/utils.js:572:26) [DEBUG] at processStyle (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/styler.js:364:17) [DEBUG] at Object.exports.processStyle (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/styler.js:420:2) [DEBUG] at Object.exports.generateStyleParams (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/styler.js:600:20) [DEBUG] at parse (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/parsers/default.js:132:19) [DEBUG] at Object.exports.parse (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/parsers/base.js:11:17) [DEBUG] at Object.exports.parse (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/parsers/default.js:10:27) [DEBUG] at parse (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/parsers/Ti.UI.Picker.js:72:31) [DEBUG] at Object.exports.parse (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/parsers/base.js:11:17) [DEBUG] at Object.exports.parse (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/parsers/Ti.UI.Picker.js:29:27) [DEBUG] at Object.exports.generateNode (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/compilerUtils.js:317:48) [DEBUG] at /Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/compilerUtils.js:401:29 [DEBUG] at Array.forEach (native) [DEBUG] at Function._.each._.forEach (/Users/fokkezb/dev/forks/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] at Object.exports.generateNode (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/compilerUtils.js:392:5) [DEBUG] at /Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/compilerUtils.js:401:29 [DEBUG] at Array.forEach (native) [DEBUG] at Function._.each._.forEach (/Users/fokkezb/dev/forks/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] at Object.exports.generateNode (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/compilerUtils.js:392:5) [DEBUG] at /Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/compilerUtils.js:401:29 [DEBUG] at Array.forEach (native) [DEBUG] at Function._.each._.forEach (/Users/fokkezb/dev/forks/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] at Object.exports.generateNode (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/compilerUtils.js:392:5) [DEBUG] at Object.exports.generateNodeExtended (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/compilerUtils.js:254:17) [DEBUG] at parse (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/parsers/Ti.UI.Tab.js:27:14) [DEBUG] at Object.exports.parse (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/parsers/base.js:11:17) [DEBUG] at Object.exports.parse (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/parsers/Ti.UI.Tab.js:7:27) [DEBUG] at Object.exports.generateNode (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/compilerUtils.js:317:48) [DEBUG] at /Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/index.js:693:28 [DEBUG] at Array.forEach (native) [DEBUG] at Function._.each._.forEach (/Users/fokkezb/dev/forks/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] at parseAlloyComponent (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/index.js:687:5) [DEBUG] at /Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/index.js:304:6 [DEBUG] at Array.forEach (native) [DEBUG] at Function._.each._.forEach (/Users/fokkezb/dev/forks/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] at /Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/index.js:293:6 [DEBUG] at Array.forEach (native) [DEBUG] at Function._.each._.forEach (/Users/fokkezb/dev/forks/alloy/Alloy/lib/alloy/underscore.js:79:11) [DEBUG] at module.exports (/Users/fokkezb/dev/forks/alloy/Alloy/commands/compile/index.js:289:4) [DEBUG] at Object.<anonymous> (/Users/fokkezb/dev/forks/alloy/Alloy/alloy.js:113:46) [DEBUG] at Module._compile (module.js:413:34) [DEBUG] at Object.Module._extensions..js (module.js:422:10) [DEBUG] at Module.load (module.js:357:32) [DEBUG] at Function.Module._load (module.js:314:12) [DEBUG] at Module.require (module.js:367:17) [DEBUG] at require (internal/module.js:16:19) [DEBUG] at Object.<anonymous> (/Users/fokkezb/dev/forks/alloy/bin/alloy:3:1) [DEBUG] at Module._compile (module.js:413:34) [DEBUG] at Object.Module._extensions..js (module.js:422:10) [DEBUG] at Module.load (module.js:357:32) [DEBUG] at Function.Module._load (module.js:314:12) [DEBUG] at Function.Module.runMain (module.js:447:10) [DEBUG] at startup (node.js:139:18) [DEBUG] at node.js:999:3 [INFO] controller: "ios.js" {code} Source (but there's probably more): https://github.com/appcelerator/alloy/blob/master/Alloy/utils.js#L572 PS: We fixed same issue for 360 in APPTS-6100

ALOY-1353

02/04/2016 09:44:35

Annotation doesn't appear in only Alloy Map

I followed this example: http://docs.appcelerator.com/platform/latest/#!/api/Modules.Map-method-createAnnotation but if i create the map with Alloy, the map is ok but the annotation doesn't appear. With this example (no Alloy) all work well: http://docs.appcelerator.com/platform/latest/#!/guide/iOS_Map_Kit i think there are a bug with annotation in Alloy.

ALOY-1352

02/08/2016 16:29:57

Alloy: add support for xhigh on iOS in measurement builtin

{{dpToPX}} and {{pxToDP}} methods of the measurement module should support HD Retina iOS https://github.com/appcelerator/alloy/blob/master/Alloy/builtins/measurement.js

ALOY-1351

02/08/2016 20:16:54

Generating `Resources/alloy.js` from template is not required when selective compile

Community PR: https://github.com/appcelerator/alloy/pull/751 When compiling only app/alloy.js, generating Resources/alloy.js from template is not required. Because Resource/alloy.js is not user's code but builtin code. So when compiling specific controller and alloy.js only, Generate Resource/alloy.js should be skipped. \\ h5. Reproduce steps # delete all file of Resources folder. # run : alloy compile -q ios --config file=app/alloy.js # you can check compiling result on Resource {{Resources/iphone/alloy.js}} is generated from template But {{Resources/iphone/alloy.js}} is not optimized. It has uncompiled CONSTANT such as OS_MOBILEWEB. it makes undefined error on runtime.

ALOY-1356

02/13/2016 16:39:34

Add support for LivePhotoView under Ti.UI.iOS namespace

With TIMOB-19666 resolved for 5.2, the Alloy version shipping with the 5.2 CLI should support defining the {{Ti.UI.iOS.LivePhotoView}} in XML.

ALOY-1357

02/13/2016 18:49:03

Support Ti.UI.iOS.MenuPopup in XML

With TIMOB-5812 resolved for the 5.2.0 SDK, Alloy should support this in XML for the version to be included in Unified CLI 5.2.0. See classic API at: http://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.iOS.MenuPopup The view is not added to any parent and wants a list of strings as items, just like an OptionDialog

ALOY-1358

02/13/2016 18:56:29

Support Ti.UI.iOS.BlurView in XML

With TIMOB-20176 resolved for the 5.4.0 SDK, the Alloy version shipping with CLI 5.4.0 should include support for {{Ti.UI.iOS.BlurView}} in XML. The view must be added to an ImageView.

ALOY-1360

02/22/2016 15:49:23

Allow baseController as attribute of Alloy xml tag

As a developer, I want to add an attribute of "baseController" to the root Alloy xml tag in an Alloy Controller, So that I can define the baseController of a new controller without having to create a .js file. {code:xml} <Alloy baseController="myBaseController"> <Label text="baseControllerTest" /> </Alloy> {code} Added PR: https://github.com/appcelerator/alloy/pull/761

ALOY-1361

02/25/2016 14:50:54

Destroy calling off on variables that may be undefined

If you have an Alloy component that uses databinding and has conditional code defined in the xml, the destroy function is not taking into consideration the fact that the component may be undefined before calling the `off` function. Alloy xml: {code:xml} <TableViewRow id="trainer_row" layout="composite" class="listitem_row" hasChild="true" onClick="$.togglePicker" if="$.args.editmode"> <View height="50" top="0" layout="composite" touchEnabled="false"> <Label text="Trainer" class="listitem_settings_name" touchEnabled="false" /> <Label text="{mymodel.trainer_name}" class="listitem_settings_value_haschild" touchEnabled="false" /> </View> <Picker id="trainer" width="350" height="150" visible="false" onChange="$.onChange" top="40"> <Column dataCollection="trainer"> <Row title="{name}" value="{id}" /> </Column> </Picker> </TableViewRow> {code} Generated code: {code:javascript} if ($.args.editmode) { // ------ only showing relevant code ------ var __alloyId287 = Alloy.Collections["trainer"] || trainer; __alloyId287.on("fetch destroy change add remove reset", __alloyId288); } exports.destroy = function() { __alloyId281.off("fetch destroy change add remove reset", __alloyId282); __alloyId293.off("fetch destroy change add remove reset", __alloyId294); __alloyId314.off("fetch destroy change add remove reset", __alloyId315); __alloyId330.off("fetch destroy change add remove reset", __alloyId331); Alloy.Models.mymodel.off("fetch change destroy", __alloyId346); }; {code} In this case, `__alloyId281` is actually undefined because it was declared and a value assigned inside the conditional if block. This is a pretty serious issue as I believe the error that occurs is stopping the other (existing) `off` functions from being called and causing a memory leak.

ALOY-1368

03/16/2016 12:22:48

Complex data binding for individual model doesn't work with transform() method

The complex data binding introduced by ALOY-443 does not work if the model has a {{transform()}} method: {code:xml} <Alloy> <Model src="user" /> <Window> <Label title="{user.foo}" /> <Label title="the {user.foo}" /> <Label title="{user.foo} - {user.bar}" /> </Window> </Alloy> {code} Compiles to: {code:js} var __alloyId13 = function() { $.__alloyId2.title = _.isFunction(Alloy.Models.user.transform) ? Alloy.Models.user.transform()["foo"] : _.template("<%=user.foo%>", { user: Alloy.Models.user.toJSON() }); $.__alloyId3.title = _.isFunction(Alloy.Models.user.transform) ? Alloy.Models.user.transform()["foo"] : _.template("the <%=user.foo%>", { user: Alloy.Models.user.toJSON() }); $.__alloyId4.title = _.isFunction(Alloy.Models.user.transform) ? Alloy.Models.user.transform()["foo"] : _.template("<%=user.foo%> - <%=user.bar%>", { user: Alloy.Models.user.toJSON() }); }; {code} So, if the model has a {{transform()}} method all three labels will only show the value of the foo attribute. The correct code should be: {code:js} var __alloyId13 = function() { var transformed = _.isFunction(Alloy.Models.user.transform) ? Alloy.Models.user.transform() : Alloy.Models.user.toJSON(); $.__alloyId2.title = _.template("<%=user.foo%>", { user: transformed }); $.__alloyId3.title = _.template("the <%=user.foo%>", { user: transformed }); $.__alloyId4.title = _.template("<%=user.foo%> - <%=user.bar%>", { user: transformed }); }; {code}

ALOY-1474

03/28/2016 08:31:47

Regression: Model data binding no longer works

For ALOY-1369 I changed the interpolation of binding templates: https://github.com/appcelerator/alloy/pull/769/files#diff-a59a2178e486f81366775c39e5393695R571 As found by [~hazemkhaled] this caused a regression in data binding of models without a transform method: https://jira.appcelerator.org/browse/ALOY-1254?focusedCommentId=380741&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-380741 Creating test app and fix.

ALOY-1475

03/28/2016 12:33:57

Alloy compile tests should show diff with known good generated code

Currently when compile tests fail they show: !Screen Shot 2016-03-28 at 13.06.58.png! There's two problems with this: 1. It is showing both the message and the stack trace, last is of no use 2. It is not showing what actually is different I expect it to give: !Screen Shot 2016-03-28 at 13.06.20.png!

ALOY-1476

03/28/2016 12:42:10

Travis does not test against known good generated code because it targets Linux only

While working on ALOY-1474 and local tests I ran into 355 failures to match against known good generated code, while Travis didn't fail at all. After submitting https://github.com/appcelerator/alloy/pull/775 I noticed Travis logs don't mention the tests against the known good generated code at all: {code} [PASS] alloy compile advanced/device_query --> preparing test app [PASS] alloy compile advanced/device_query [android] --> compiles without critical error [PASS] alloy compile advanced/device_query [android] --> leaves no compiler directives in generated code [PASS] alloy compile advanced/device_query [android] --> has no undefined style entries [PASS] alloy compile advanced/device_query [ios] --> compiles without critical error [PASS] alloy compile advanced/device_query [ios] --> leaves no compiler directives in generated code [PASS] alloy compile advanced/device_query [ios] --> has no undefined style entries [PASS] alloy compile advanced/device_query [mobileweb] --> compiles without critical error [PASS] alloy compile advanced/device_query [mobileweb] --> leaves no compiler directives in generated code [PASS] alloy compile advanced/device_query [mobileweb] --> has no undefined style entries {code} while locally it fails: {code} [PASS] alloy compile advanced/device_query --> preparing test app [PASS] alloy compile advanced/device_query [android] --> compiles without critical error [PASS] alloy compile advanced/device_query [android] --> leaves no compiler directives in generated code [PASS] alloy compile advanced/device_query [android] --> has no undefined style entries [PASS] alloy compile advanced/device_query [android] --> generated a alloy/controllers/index.js file [FAIL] alloy compile advanced/device_query [android] --> matches known good generated code for alloy/controllers/index.js [PASS] alloy compile advanced/device_query [ios] --> compiles without critical error [PASS] alloy compile advanced/device_query [ios] --> leaves no compiler directives in generated code [PASS] alloy compile advanced/device_query [ios] --> has no undefined style entries [PASS] alloy compile advanced/device_query [ios] --> generated a alloy/controllers/index.js file [FAIL] alloy compile advanced/device_query [ios] --> matches known good generated code for alloy/controllers/index.js [PASS] alloy compile advanced/device_query [mobileweb] --> compiles without critical error [PASS] alloy compile advanced/device_query [mobileweb] --> leaves no compiler directives in generated code [PASS] alloy compile advanced/device_query [mobileweb] --> has no undefined style entries [PASS] alloy compile advanced/device_query [mobileweb] --> generated a alloy/controllers/index.js file [FAIL] alloy compile advanced/device_query [mobileweb] --> matches known good generated code for alloy/controllers/index.js {code} I also saw this test only runs on darwin: https://github.com/appcelerator/alloy/blob/master/test/specs/compile.js#L173 We don't specify an OS: https://github.com/appcelerator/alloy/blob/master/.travis.yml Which seems to make Travis to only test on Linux: https://travis-ci.org/appcelerator/alloy/builds/118954721 Unfortunately enabling osx on Travis fails: https://travis-ci.org/appcelerator/alloy/jobs/118956715 Because of: https://github.com/travis-ci/travis-ci/issues/2311 Which can be workaround like: https://github.com/travis-ci/travis-ci/issues/2311#issuecomment-171180704 Which I did: https://github.com/appcelerator/alloy/pull/775/files#diff-354f30a63fb0907d4ad57269548329e3L1 And now Travis is failing 355 tests on OSX just like local: https://travis-ci.org/appcelerator/alloy/builds/118959856 I've checked all 355 failures and all were expected because of tests that were not updated for tickets like ALOY-1355, ALOY-1237 and ALOY-1335, so generated new known good code for all.

ALOY-1478

03/29/2016 13:25:26

Data binding fails when binding string or model attribute name has dash, space or quote

Alloy data binding can't handle complex bindings strings or model attributes names that contain a dash, space or quotes. This is in part because of the way it renders the compiled {{\_.template()}} code, but also because of limitations in {{\_.template()}} itself: http://stackoverflow.com/a/15956433/4626813 {code:xml} <Alloy> <Model src="mymodel" /> <Collection src="mymodel" /> <Window> <ScrollView layout="vertical"> <!-- ALL OK --> <Label top="30" text="{mymodel.a}" /> <!-- COMPILE ERROR --> <!-- <Label text="{mymodel.a'b}" /> --> <!-- <Label text="he's {mymodel.a}" /> --> <!-- RUN-TIME ERROR --> <!-- <Label text="{mymodel.a-b}" /> --> <!-- <Label text="{mymodel[a-b]}" /> --> <!-- <Label text="{mymodel.a b}" /> --> <!-- <Label text='{mymodel.a"b}' /> --> <ListView> <ListSection dataCollection="mymodel"> <!-- ALL OK --> <ListItem title="{a}" /> <!-- COMPILE ERROR --> <!-- <ListItem title="{a'b}" /> --> <!-- RUN-TIME ERROR --> <!-- <ListItem title="{a-b}" /> --> <!-- <ListItem title="{[a-b]}" /> --> <!-- <ListItem title="{a b}" /> --> <!-- <ListItem title='{a"b}' /> --> </ListSection> </ListView> </ScrollView> </Window> </Alloy> {code} *index.js* {code:js} var test = { a: 'a', 'a-b': 'a-b', 'a b': 'a b', 'a"b': 'a"b', "a'b": "a'b" }; Alloy.Models.mymodel.set(test); Alloy.Collections.mymodel.reset([test]); $.index.open(); {code} *mymodel.js* {code:js} exports.definition = {}; {code}

ALOY-1479

03/30/2016 14:41:20

Regression: Model instance data binding no longer works

Data binding of local model instances throws an exception in Alloy 1.8.3 and 1.8.4 because of [this line change|https://github.com/appcelerator/alloy/pull/769/files#diff-a59a2178e486f81366775c39e5393695L521] to resolve ALOY-1369. *XML* {code:xml} <Label top="20" text="{$.modelinstance.foo}" /> <Label text="{$.modelinstance.foo} {$.modelinstance.bar}" /> {code} *compiled* {code:js} $.__alloyId4.text = _.template("{$.modelinstance.foo}", { modelinstance: transformed }, { interpolate: /\{([\s\S]+?)\}/g }); $.__alloyId5.text = _.template("{$.modelinstance.foo} {$.modelinstance.bar}", { modelinstance: transformed }, { interpolate: /\{([\s\S]+?)\}/g }); {code}

ALOY-1480

03/31/2016 10:03:15

Bug/Regression: Data binding always returns string values

For ALOY-443 (Alloy 1.5.0) we started to use {{_.template()}} for complex model data binding. With ALOY-1368 and ALOY-1369 we also adopted this method for complex collection data binding. Since {{_.template()}} always returns a string, it doesn't work for binding objects, e.g. an attributedString as the attached test case: {code:xml} <Alloy> <Collection src="source" /> <Window class="container"> <ListView id="List" defaultItemTemplate="test" top="30"> <Templates> <ItemTemplate name="test" height="50"> <View height="Ti.UI.SIZE" layout="vertical"> <Label id="simpleTestLabel" bindId="simpleTestLabel"></Label> <Label id="attributedTestLabel" bindId="attributedTestLabel" top="5"></Label> </View> </ItemTemplate> </Templates> <ListSection dataCollection="source" dataTransform="transform"> <ListItem simpleTestLabel:text="{simple}" attributedTestLabel:attributedString="{attributedString}"></ListItem> </ListSection> </ListView> </Window> </Alloy> {code} h2. Original description Just tested that, using alloy v1.8.2 and v1.8.5 I was unable to set the `attributedString` property via a `ListItem` template. Using alloy 1.7.35 everything is working fine. I attach a simple test project that contains a `ListView` with a template composed by two labels. On the first label I set the `text` property with a simple model string and on the second one i set the `attributedString`. For the first label everything is working correctly (as expected) and for the second one is working only using v1.7.35 of alloy.

ALOY-1486

04/01/2016 20:10:17

iOS, Android: Global styles is not overridden by local styles for orientationModes.

h6. Description If we set orientationModes on window in app.tss file portrait, landscape both and any individual tss file only portrait then portrait mode does not work for individual tss. h6. Steps to reproduce 1. Just create an alloy project. 2. Replace this app.tss and index.tss file, 3. Run this code in device or emulator. 4. Rotate device. 5. It does not stop. h6. actual behaviour If device rotate, the app orientation change. h6. Expected behaviour Since orientation Modes "PORTRAIT" for the index.tss file so it should be always portrait. {code:title=app.tss} "Window": { orientationModes: [Ti.UI.PORTRAIT,Ti.UI.LANDSCAPE_LEFT,Ti.UI.LANDSCAPE_RIGHT], backgroundColor: "red" } {code} {code:title=index.tss} "Window": { orientationModes: [Titanium.UI.PORTRAIT], backgroundColor: "blue" } {code}

ALOY-1492

04/20/2016 19:33:56

Fix no such file or directory when doing "alloy new"

When creating a new alloy project, the creation process should be more careful when platform template folder doesn't not exist. h6. Reproduce Step {{appc new}} titanium app h6. Expected Output The app should be created with no error. h6. Actual Output {{Error: ENOENT: no such file or directory}}

ALOY-1493

04/21/2016 10:54:56

[Alloy] Alloy sql adapter db_file to be function

{code:javascript} // app/models/mytable.js exports.definition = { config: { columns: {}, adapter: { type: "sql", collection_name: "mytable", db_file: function() { var myFile = Titanium.Filesystem.getFile(Titanium.Filesystem.applicationDataDirectory, 'file1.sql'); return myFile.exists() ? myFile.nativePath : Titanium.Filesystem.applicationDataDirectory + 'file2.sql'; }, db_name: "projectsDB", idAttribute: "UserID", remoteBackup: false } } }; {code} https://github.com/appcelerator/alloy/pull/788

ALOY-1494

04/22/2016 17:05:05

iOS: Support Ti.UI.iOS.Stepper in Alloy

https://jira.appcelerator.org/browse/TIMOB-6305 adds support for the new Stepper UI element on iOS. We should include the alloy-change just from the beginning

ALOY-1495

04/25/2016 14:45:54

Support newer versions of Underscore / Lodash

{quote}This is different than ticket ALOY-1168: https://jira.appcelerator.org/browse/ALOY-1168{quote} ALOY-1168 is about replacing the shipped version of underscore. This ticket is about supporting apps where underscore is replaced by the developer. I still think that ALOY-1168 should be implemented and I have developed it in a fork (https://github.com/mobilehero/adamantium/tree/feature/underscore-to-lodash), but I am having issues w/ the tests. Currently, Alloy allows developer to replace the current version of underscore with a different version (or with lodash) by putting the updated underscore.js file in the directory: /app/lib/alloy. However, the issue is that the code that Alloy generates for a controller that uses databinding, references the old version of _.template. There are probably several different ways this could be solved to support both old and new versions of Underscore. One might be to check the version of underscore. I think the function was changed in 1.7.0. Let me know if you think there is a workable solution and I can create a PR and tests for it. Thanks!!

ALOY-1504

04/29/2016 15:13:59

ERROR: Alloy is not defined

I have an Android project integrated with _iamyellow.net_ Push Notification module. Erroneous scenario generated by following steps. 1. App is closed manually in background 2. There is a notification in notification bar for the app 3. App is opened by tapping on the notification. 4. An error with "Alloy is not defined", sourced build/android/assets/alloy.js, is appeared. Please refer screenshot in attachment. 5. App sticks at default screen after receiving error. Please consider this as high priority issue. Regards.

ALOY-1508

06/02/2016 12:26:12

iOS: Localised splash screen is not visible

When I add the splash screen in the "app/i18n/en/" path I am not able to see the splash screen. I get black screen. *Steps to reproduce:* 1. Create an alloy project 2. Place a splash screen image In app/i18n/en/ folder 3. Run the app on simulator *Expected:* Splash screen should be visible when the app launches. *Actual:* A black screen is shown instead of splash screen image. Reference: http://docs.appcelerator.com/platform/latest/#!/guide/Icons_and_Splash_Screens-section-29004897_IconsandSplashScreens-LocalizedSplashScreens

ALOY-1502

06/05/2016 17:42:37

Destroy Model in Alloy doesn't seem to be working

Hi, Trying to delete models using destroy() events seems not working. Steps to reproduce : 1. Create a simple Alloy project. 2.Create a model TestUser.js {code} exports.definition = { config: { columns: { 'id': 'INTEGER PRIMARY KEY AUTOINCREMENT', "firstName": "TEXT", "lastName": "TEXT", "street": "TEXT" }, adapter: { type: "sql", collection_name: "TestModel", idAttribute: 'id' } } }; {code} 3. Copy the following code in index.js {code} var user = Alloy.createModel('TestUser'); user.save({id:1, firstName:'aa', lastName:'bb', street:'cc'},{ success:function() { Ti.API.info('*** user before destroy\n' + JSON.stringify(user,null,2)); alert('*** user before destroy\n' + JSON.stringify(user,null,2)); user.destroy({ success:function() { Ti.API.info('*** user after destroy\n' + JSON.stringify(user,null,2)); alert('*** user after destroy\n' + JSON.stringify(user,null,2)); } }); } }); /* user.fetch(); user.destroy({ success:function() { Ti.API.info('*** user after destroy\n' + JSON.stringify(user,null,2)); alert('*** user after destroy\n' + JSON.stringify(user,null,2)); } }); */ $.index.open(); {code} 4. Run this project Destroy Model in Alloy doesn't seem to be working, because I get same log before and after destroy(); Log {code} [INFO] : *** book before destroy [INFO] : { [INFO] : "title": "aa2", [INFO] : "author": "bb2", [INFO] : "alloy_id": "3da5ac16-aa00-0e52-727d-9ad551f5c850" [INFO] : } [INFO] : *** book after destroy [INFO] : { [INFO] : "title": "aa2", [INFO] : "author": "bb2", [INFO] : "alloy_id": "3da5ac16-aa00-0e52-727d-9ad551f5c850" [INFO] : } {code} Environment {code} Operating System Name = Mac OS X Version = 10.11.5 Architecture = 64bit # CPUs = 4 Memory = 8.0GB Node.js Node.js Version = 4.4.4 npm Version = 2.15.1 Appcelerator CLI Installer = 4.2.6 Core Package = 5.3.0 Titanium CLI CLI Version = 5.0.8 node-appc Version = 0.2.31 Titanium SDK : 5.3.0.GA alloy -v : 1.7.33 {code} Thanks

ALOY-1505

06/17/2016 20:13:21

Add ability to pass cancel attribute to Option element for OptionDialog

{quote}As a developer, I want to be able to mark an option as being the option to use for cancelling an OptionDialog in Alloy XML, So that I can use OptionDialog in view without dependency on controller. {quote} Currently, I can do this: {code:xml} <OptionDialog id="dialog" title="Delete File?" cancel="2" > <Options> <Option>Confirm</Option> <Option platform="ios">Help</Option> <Option>Cancel</Option> </Options> </OptionDialog> {code} However, if an option is not displayed due to conditional code, then the index number will no longer be valid. Proposed new attribute: {code:xml} <OptionDialog id="dialog" title="Delete File?"> <Options> <Option>Confirm</Option> <Option platform="ios">Help</Option> <Option cancel="true">Cancel</Option> </Options> </OptionDialog> {code}

ALOY-1510

07/27/2016 16:55:30

Receiving "<SearchView> is only available in Android" when compiling tableview despite platform="android" attribute being present

h2. Problem We have a number of views with tableviews that use the SearchView component. When compiling for iOS, we receive this warning: {code:none} [WARN] <SearchView> is only available in Android [WARN] To get rid of this warning, add platform="android" to your <SearchView> element {code} However, our SearchView elements already have the platform attribute set to "android". h2. Test case {code:lang=xml|title=index.xml} <Alloy> <Window> <TableView> <SearchBar platform="ios"/> <SearchView ns="Ti.UI.Android" platform="android"/> </TableView> </Window> </Alloy> {code} h2. Logs {code:lang=none|title=console} [INFO] [index.xml] view processing... [INFO] style: "index.tss" [INFO] view: "index.xml" [WARN] <SearchView> is only available in Android [WARN] To get rid of this warning, add platform="android" to your <SearchView> element [INFO] controller: "index.js" [TRACE] - Processing "builtins" module... [TRACE] - Processing "optimizer" module... [TRACE] - Processing "compress" module... [INFO] created: "Resources/iphone/alloy/controllers/index.js" [DEBUG] map: "build/map/Resources/iphone/alloy/controllers/index.js.map" [INFO] created: "Resources/iphone/alloy/styles/index.js" {code} h2. Notes I believe the error is in commands/compile/parsers/Ti.UI.TableView.js:49. It currently reads: {code:javascript} if (node.getAttribute('platform') !== 'android') { {code} I believe it should read: {code:javascript} if (child.getAttribute('platform') !== 'android') { {code}

ALOY-1517

08/04/2016 13:15:55

UI elements are not created properly with formFactor property in style

When I use a conditional style I know the style only applies if the conditions are met. If not, a default style will be applied. For example: *index.xml* {code:xml} <Label>Hello, World</Label> {code} *index.tss* {code:javascript} "Label[platform=ios formFactor=tablet]":{ color: "red" } {code} On iPad the label will be red, but it will render as black on other devices. But this is not the case when I’m styling a NavigationWindow for a specific platform: *index.xml* {code:xml} <Alloy> <NavigationWindow> <Window> <Label>Hello, World</Label> </Window> </NavigationWindow> </Alloy> {code} *index.tss* {code:javascript} "NavigationWindow[platform=ios formFactor=tablet]":{} {code} Launching the app on an iPhone, Alloy don’t create the NavigationWindow: {code:javascript} $.__views.index = Ti.UI.iOS.createNavigationWindow(function() { var o = {}; Alloy.isTablet && Alloy.deepExtend(true, o, { window: $.__views.__alloyId0, id: "index" }); return o; }()); {code} The app crash with the error message: *“Invalid type passed to function”*. Why a style determines if create or not the element? The correct code could be: {code:javascript} $.__views.index = Ti.UI.iOS.createNavigationWindow(function() { var o = {}; Alloy.isTablet && Alloy.deepExtend(true, o, { }); Alloy.deepExtend(true, o, { window: $.__views.__alloyId0, id: "index" }); return o; }()); {code}

ALOY-1512

08/11/2016 18:23:06

Replace Uglify with Babylon

At the moment, Uglify has limited support of ES6 features. https://github.com/mishoo/UglifyJS2/issues/448. Consider moving to using Babylon. https://github.com/babel/babylon

ALOY-1519

09/13/2016 12:17:09

Alloy: Support iOS 10 <RefreshControl> tag in Ti.UI.ScrollView

We introduced the {{Ti.UI.RefreshControl}} usage in the {{Ti.UI.ScrollView}} in TIMOB-23524. It is a new iOS 10 feature we exposed to the proxy. Now we need the Alloy parser-binding to use it in the XML like we already can do with the {{Ti.UI.TableView}} and {{Ti.UI.ListView}}.

ALOY-1528

09/13/2016 17:37:04

getWidgetDirectories does not respect theme config.json

We have multiple themes for our Alloy/Titanium application, and each theme needs to have a different sent of dependencies. However, dependencies set in app/themes/theme_name/config.json are not checked when returning widget directories: https://github.com/appcelerator/alloy/blob/5991de44082a492d143612cc2175b7eef30d36e6/Alloy/utils.js#L286 (For reference, this theme config.json _is_ observed when generating the CFG.js file: https://github.com/appcelerator/alloy/blob/977a2c147e809ccd1c05d197d54828c3e7660150/Alloy/commands/compile/compilerUtils.js#L827)