id int64 0 5.38k | issuekey stringlengths 4 16 | created stringlengths 19 19 | title stringlengths 5 252 | description stringlengths 1 1.39M | storypoint float64 0 100 |
|---|---|---|---|---|---|
100 | 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/ | 3 |
101 | 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/tst... | 3 |
102 | 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: ... | 3 |
103 | 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"... | 5 |
104 | 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://githu... | 5 |
105 | 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 ... | 5 |
106 | 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} | 3 |
107 | 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] ... | 8 |
108 | 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 ... | 3 |
109 | 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 'd... | 3 |
110 | 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 curren... | 3 |
111 | 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... | 8 |
112 | 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 show... | 3 |
113 | 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 | 2 |
114 | 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.. | 5 |
115 | 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}}. T... | 5 |
116 | 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 ... | 3 |
117 | 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 ou... | 5 |
118 | 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']} ); | 5 |
119 | 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. | 5 |
120 | 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 ... | 8 |
121 | 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. | 3 |
122 | 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 | 3 |
123 | 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. I... | 3 |
124 | 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/p... | 3 |
125 | 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 c... | 2 |
126 | 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 ... | 2 |
127 | 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 m... | 8 |
128 | 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/m... | 3 |
129 | 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. | 5 |
130 | 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} | 5 |
131 | 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. | 3 |
132 | 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 | 1 |
133 | 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 ... | 5 |
134 | 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://g... | 3 |
135 | 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. | 5 |
136 | 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 | 2 |
137 | 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); } ... | 5 |
138 | 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... | 5 |
139 | 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 | 3 |
140 | 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> <... | 5 |
141 | 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 style... | 5 |
142 | 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 colo... | 3 |
143 | 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] ... | 5 |
144 | 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. | 3 |
145 | 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 ... | 3 |
146 | 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. Creat... | 3 |
147 | 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 wil... | 5 |
148 | 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* *a... | 5 |
149 | 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> <TextFiel... | 3 |
150 | 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 re... | 1 |
151 | 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. | 0 |
152 | 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} | 5 |
153 | 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 | 1 |
154 | 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... | 3 |
155 | 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... | 2 |
156 | 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 late... | 5 |
157 | 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. - http... | 5 |
158 | 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> ... | 5 |
159 | 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... | 5 |
160 | 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... | 1 |
161 | 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.... | 3 |
162 | 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 ac... | 8 |
163 | 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... | 1 |
164 | 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(... | 5 |
165 | 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 sho... | 3 |
166 | 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} | 2 |
167 | 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 | 1 |
168 | 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> ... | 3 |
169 | 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/app... | 1 |
170 | 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 relea... | 0 |
171 | 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 ... | 5 |
172 | 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 | 3 |
173 | 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 ski... | 3 |
174 | 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. | 3 |
175 | 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 a... | 5 |
176 | 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. | 3 |
177 | 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... | 3 |
178 | 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="composi... | 3 |
179 | 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:... | 5 |
180 | 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?fo... | 5 |
181 | 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! | 5 |
182 | 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]... | 5 |
183 | 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 {cod... | 5 |
184 | 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="... | 5 |
185 | 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 ... | 8 |
186 | 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 devi... | 5 |
187 | 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}} | 3 |
188 | 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.applicationData... | 5 |
189 | 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 | 3 |
190 | 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 d... | 0 |
191 | 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 ... | 3 |
192 | 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 launch... | 3 |
193 | 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", ... | 8 |
194 | 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=... | 3 |
195 | 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 ... | 1 |
196 | 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 iP... | 3 |
197 | 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 | 0 |
198 | 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}}. | 5 |
199 | 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/5991de44082a492d143612cc2175b7eef30d... | 2 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.