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 |
|---|---|---|---|---|---|
0 | ALOY-344 | 10/24/2012 23:41:49 | CLONE - Studio Dashboard: "default" and "Default Project" does not give clear information about Alloy and Project unless description is read. | Steps To Reproduce: 1. On dashboard on studio 3.0, navigate to Develop tab. 2. Notice "default" and "Default Project" & "two-tabbed" and "Tabbed Application" names. Actual: User does not get clear information from names that one is alloy project and another one is Titanium project unless he reads the descripti... | 8 |
1 | ALOY-440 | 12/20/2012 17:21:38 | Ti.UI.Picker has no collection binding | h3. original discussion http://developer.appcelerator.com/question/145992/databinding-on-picker h3. problem Collection binding is not implemented for Ti.UI.Picker as it is for Ti.UI.TableView and other generic Titaniums views (View, Window, ScrollView, etc...). h3. solution Support collection binding o... | 8 |
2 | ALOY-443 | 12/21/2012 13:41:13 | Enable more complex notation in binding | Allow developers to use syntax like the following in collection/model bindings: {code:xml} <Alloy> <Model src="someModel"/> <Window title="{someModel.title} {someModel.subtitle}"/> </Alloy> {code} Basically, instead of assuming the whole property needs to be wrapped in \{\}, allow developers to put a... | 8 |
3 | ALOY-488 | 01/26/2013 22:14:34 | Orphan file cleanup deletes builtins and widget assets | During the compile process Alloy will attempt to remove files from the Resources directory that are no longer present anywhere in the "app" folder. Alloy searches a number of locations in the "app" folder to see if the file is an orphan or not. False negatives should be avoided as they will leave unused files in the pr... | 3 |
4 | ALOY-540 | 03/01/2013 19:25:27 | Resolve suboptimal compression from uglify-js v2 update | The v2 update of uglify-js in Alloy, specifically version 2.2.5, has some suboptimal compressions, which are causing the optimizer.js test spec to fail in certain cases. Specifically the issues are around booleans and cascading of variables in assignments. These issues have been logged with the Uglifyjs2 project in the... | 5 |
5 | ALOY-544 | 03/07/2013 01:14:43 | Ability to define a custom namespace to enable Alloy to generate custom widgets | Alloy should allow the user to specify a custom namespace for each widget in XML which modifies the generated code to use the widgets within the specified namespace. As an example, <Window id="win"> generates Ti.UI.createwindow(). The user should be able to specify <Window ns="mcd" id="win"/>, which Alloy would in t... | 3 |
6 | ALOY-592 | 03/30/2013 18:12:57 | Widget: default new widget platforms do not respect tiapp.xml deployment targets | Widget: default new widget platforms do not respect tiapp.xml deployment targets. Test Steps: 1. Create Alloy project with all deployment targets (including blackberry and tizen). 2. New > Alloy Widget. Test Results: Observe the platforms listed in the widget, only a few targets are present. | 3 |
7 | ALOY-716 | 06/20/2013 23:48:30 | When using view-model binding, whitespace inside curly braces disables binding | h2. problem http://developer.appcelerator.com/question/153856/alloy-update-view-with-fetched-collection h2. expected Both labels in the example below should be data bound, regardless of the superfluous whitespace. {code:xml} <Alloy> <TableView dataCollection="someCollection"> <TableViewRow la... | 13 |
8 | ALOY-1514 | 08/19/2013 11:18:25 | Add a CLI command to extract i18n strings from alloy code and update the strings.xml files (ALSO for XML files) | Now that Alloy 1.2 allows to use L() in XML files, this tool must scan XML files, apart the classic JS and TSS files. I've been tested it and it is not doing it actually. | 1 |
9 | ALOY-1518 | 08/23/2013 19:40:11 | ListView: Custom widget support in templates | Currently there does not seem to be support for adding custom widgets in Listview templates. Please add widget support to ListView. | 13 |
10 | ALOY-829 | 09/18/2013 07:51:11 | Add a shorthand for fetch() adapter | If I get a reference to an ID would be nice to have a shortend like var model = Alloy.createModel("..."); model.fetch({ id: 123 }); instead of have to provide a full sql statement I suggest an implementation approach like this one https://github.com/viezel/napp.alloy.adapter.restsql#extended-sql-interface... | 5 |
11 | ALOY-858 | 10/23/2013 09:36:51 | Alloy: Theme "i18n" and "platform" folders | I would like to be able to theme the {{i18n}} and {{platform}} folders so that for a white-label app I can keep all brand-specific stuff in the theme folder. h1. Use case For example, the i18n strings would include brand-specific texts in multiple languages and the platform folder would include brand-specific Andro... | 8 |
12 | ALOY-859 | 10/23/2013 16:40:04 | Compile failing on OSX Mavericks when targeting Windows Server network drives | h2. update (10/24/2013) A correlation between [~jamesdraper] and [~core13] shows that the likely culprit for this issue is when a network drive sourced from a Windows Server is used as the project folder when building Alloy on OSX Mavericks. h2. original Q&A: http://developer.appcelerator.com/question/158722/... | 13 |
13 | ALOY-932 | 01/21/2014 14:45:54 | Improve error messages when attempting to bind to complex objects | When attempting to bind to a complex object, such as the following, the resulting error messages are not clear and meaningful. {code} <TableView dataCollection="provider"> <TableViewRow id="row" onClick="doViewDetails"> <ImageView id="rowImage" image="{photo.urls.square_75}" /> <Label id="row... | 3 |
14 | ALOY-934 | 01/22/2014 20:09:06 | Change androidView behavior for optionDialog and similar components | We need to change the androidView behavior for optionDialog (and any other components that support an Android-specific view as a child) so that an AndroidView proxy parser is used rather than creating an arbitrary view. Need also to communicate the change, as it deprecates old behavior. Instead of an anroidView b... | 3 |
15 | ALOY-950 | 02/06/2014 00:16:50 | 'localStorage' adapter for Alloy Models should be deprecated and no longer used | h5. Improvement description We should deprecate the usage of the localStorage adapter for Alloy Models. It could create confusion as only supports MobileWeb and Tizen and is outdated by the 'properties' adapter (that supports all platforms). See also http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_Sy... | 3 |
16 | ALOY-952 | 02/07/2014 00:21:45 | Non numeric primary key not escaped during query | I am having a weird issue with alloy model generating an unescaped query, even though it uses prepared statement. To recreate it: 1. Create a model with a non integer primary key. 2. Do a simple model.fetch({id: "your_text_id"}); It will generate a query like so: SELECT * FROM table_name WHERE some_primary_... | 3 |
17 | ALOY-963 | 02/27/2014 01:35:56 | Allow platform specific subfolders in lib and vendor directories | Platform specific folders (iphone,android,etc.) in the app/lib and app/vendor directories were not compiling to Resources correctly. The following pull request will fix this. https://github.com/appcelerator/alloy/pull/337 | 2 |
18 | ALOY-964 | 03/03/2014 15:13:27 | Support AndroidView in addition to View as child of AlertDialog | While the API name is AndroidView, Alloy expects child views of AlertDialog to be created with the View tag. It throws an error that Ti.UI.createAndroidView is not a valid method name if you use AndroidView. While it's okay to support View as a shorthand, we should also support AndroidView as a tag. Reference: http:... | 5 |
19 | ALOY-967 | 03/06/2014 14:53:32 | Support i18n directory in widgets | Customers have requested support for widget specific i18n localization files. This would be useful for fully independent UI widgets. | 3 |
20 | ALOY-977 | 04/01/2014 21:08:56 | Add code comments | Add comments to the alloy scripts, specifically to the compile-related files. Code comment structure should be compatible with the TBD code-doc tool. | 3 |
21 | ALOY-1063 | 04/09/2014 10:03:32 | CLI: `ti clean` should remove/empty `Resources` for Alloy projects | h4. Problem Description With the Alloy compiler trying to become smarter in compiling only those files that are changed, it happens more often that for different reasons the {{Resources}} directory is not up-to-date anymore. For this reason I'd like to see the {{Resources}} folder emptied or removed with {{ti clean}} ... | 3 |
22 | ALOY-1021 | 05/10/2014 19:29:24 | Alloy: Add support for Alloy.CFG and Alloy.Globals in views | As the attached sample app shows, you can not use {{Alloy.CFG.}} and {{Alloy.Globals.}} in Alloy views. In the compiled code, they will end up as strings: {code:javascript} $.__views.__alloyId0 = Ti.UI.createLabel({ top: 50, text: "Alloy.CFG.foo", id: "__alloyId0" }); {code} ... | 3 |
23 | ALOY-1018 | 05/16/2014 18:48:30 | Add defaultNamespace or module attribute to Alloy Tag | Alloy currently has a feature of specifying a module attribute against tags, allowing a custom JS module to be used to create the elements, enabling developers to return modified or different elements. e.g: <Label module="ui'>Foo</Label> It's a very powerful feature and means we can create our custom tags for ... | 5 |
24 | ALOY-1043 | 06/05/2014 20:53:23 | Tooling: add script to compile all test apps and add _generated folders | To improve our testing, we should have _generated folders (containing generated code for each platform) that can be compared to with each run of the {{jake test:all}} script. It should: * Process each project in the test/apps folder tree * Compile the app for each platform, saving the results to _generated/PLAT... | 8 |
25 | ALOY-1044 | 06/06/2014 17:20:26 | Remove the sample widgets | The widgets have been deprecated and should be removed in the next release. They should be handled as follows: * If required for functional test apps or the widget sample apps, either move the required widgets into those apps or implement new simple widgets so as to preserve the goal of the demo apps. * Contact the... | 5 |
26 | ALOY-1089 | 06/24/2014 10:09:58 | Alloy support for Windows toolbar[] attribute | It would be very nice to have direct support for the Window.toolbar[] attribute in Alloy Something like: <Window id="supportWindow" > <toolbar platform="ios"> <Button id="button1" title="First" /> <Button id="button2" title="Second" /> </toolbar> </Window> | 3 |
27 | ALOY-1059 | 06/24/2014 17:39:19 | i18n from app must override i18n from widgets | Given a language string in the app's i18n strings.xml file with the same name as a value in a widget's strings.xml file, the app's string must override that of the widget. To create a test app for this: 1. Copy the ALOY-967 test app 2. Modify the app's i18n/en/strings.xml file to add this new key: {{<string nam... | 5 |
28 | ALOY-1062 | 06/30/2014 11:49:44 | Blackberry: Default Alloy Project shows incorrect app icon for blackberry | Default Alloy Project shows incorrect app icon for blackberry Steps to reproduce: 1)Create any default alloy project and install on device. {color:green}*Expected Result:*{color} Alloy app icon must be displayed on the device. {color:red}*Actual Result:*{color} Instead of Alloy app icon classic app icon is be... | 3 |
29 | ALOY-1064 | 06/30/2014 20:28:17 | ListView parser should remove Templates node after processing the templates | Given a project containing a widget and this in index.xml: {code} <Alloy> <Window> <Widget src="foo"> <ListView> <Templates> <ItemTemplate name="first"> <!-- ... ... ... --> </ItemTemplate> ... | 5 |
30 | ALOY-1067 | 07/02/2014 15:42:20 | Support L() in XML as Label text | For following view, {{L()}} should work if we've set foo equal to some string in i18n. Now it prints out L('foo') instead {code} <Window> <Label>L('foo')</Label> <!-- this print out L('foo') instead of treating it as L() --> </Window> {code} | 3 |
31 | ALOY-1068 | 07/02/2014 15:58:25 | Runtime error if Label's text attribute starts with L() alias in quotes | h6. 1. Use following sample {code} <Alloy> <Window> <Label text="L(foo)" /> </Window> </Alloy> {code} h6. 2. Build and run Results in Alloy runtime error. {code} [ERROR] : Script Error { [ERROR] : backtrace = "#0 () at file:///Users/fmiao/Library/Application%20Support/iPhone%20Simulator/7.1/Appl... | 2 |
32 | ALOY-1096 | 07/03/2014 23:15:03 | Alloy: Update moment.js built-in library to latest version. | The latest version of the moment.js library is v2.7.0, yet Alloy includes an outdated version 2.1.0 as a built in. There are new features and bug fixes on the new version that we could use. As of now, we have to include moment 2.7.0 as a stand-alone lib on our Alloy project for these new features and cannot use th... | 3 |
33 | ALOY-1076 | 07/07/2014 12:38:00 | Studio: Distorted console view for alloy project launch on emulator | Test Steps: This is specific to windows. 1. Create an Alloy Project. 2. Launch it on emulator. Observe the console view. Actual Result: Distorted console view for alloy project launch on emulator is noticed.Please refer attached screenshot. | 5 |
34 | ALOY-1073 | 07/07/2014 18:03:18 | Create a Backbone 1.x compatible sync adapter | To provide for backward compatibility, create a version of the SQL sync adapter that supports Backbone 1.x (current version), leaving the existing adapter for 0.9x compatibility reasons. | 5 |
35 | ALOY-1074 | 07/07/2014 18:06:58 | Enable developers to specify Backbone version in config.json | Enable developers to choose whether to use Backbone 0.9x or 1.x. The default should be 1.x. Support for the older version would be to provide backward compatibility for existing projects that depend on 0.9x behaviors or functionality. | 8 |
36 | ALOY-1075 | 07/07/2014 18:08:38 | Confirm existing adapters support Backbone 1.x | Specifically, check Mads' REST adapter. Provide guidance on updating adapters that don't work. | 3 |
37 | ALOY-1098 | 07/09/2014 10:20:17 | Support actionView property of MenuItem in XML markup | {code} <Menu> <MenuItem> <ActionView> <View backgroundColor="#fff" /> </ActionView> </MenuItem> </Menu> {code} Set actionView of MenuItem using alloy xml markup | 3 |
38 | ALOY-1080 | 07/09/2014 14:49:04 | Compiler fails with misleading message when dataCollection set on ListView rather than ListSection | If the {{dataCollection}} attribute is set on the ListView, as shown below, the Alloy compiler fails with the message that the ItemTemplate must have a name attribute (which it does in the example). {code} <Alloy> <Collection src="mycollection"/> <Window id="win"> <ListView id="thelist" defaultItemTempla... | 3 |
39 | ALOY-1081 | 07/09/2014 15:27:54 | Improve query selection speed through sync adapter optimizations | Community-submitted pull request: https://github.com/appcelerator/alloy/pull/471 Speed improvements for selecting data | 3 |
40 | ALOY-1082 | 07/14/2014 12:53:14 | Allows <Templates> to be children of <Widget> | h2. Description When creating a ListView in a widget, it is not possible to add the templates as children of the widget. h2. Sample The ListView is created as a Widget. XML code: {code} <Alloy> <ListView id="list"> <ListSection> <ListItem image:image="someimage.jpg" label:text="this is some text"/> ... | 3 |
41 | ALOY-1085 | 07/15/2014 15:48:09 | Update Alloy templates | I've prepared a PR with some updates for the Alloy templates: https://github.com/appcelerator/alloy/pull/480 Changes: - Re-Organises platform files copied in by new-command to support the next two: - Moves MarketPlaceArtwork.png to the project root folder to save APK size - Adds iTunesConnect.png to the proj... | 3 |
42 | ALOY-1099 | 07/17/2014 12:29:06 | Alloy: Code Analyzer fails to analyze | Code Analyzer fails to analyze Alloy Project from Studio on Windows system only. But working fine from CLI. 1. Create a default alloy project. 2. Execute the Code Analyzer against Android/Mobileweb platforms. Actual Result - Shows error message. Please refer the attached log file and screen shot for more clarif... | 5 |
43 | ALOY-1118 | 07/18/2014 07:57:23 | Allow theming of tiapp.xml e.g. through Alloy themes | Now Alloy supports theming of {{app/config.json}} and {{i18n}} and {{platforms}} on their way, the last thing to tackle for easily building branded apps of a white label codebase is "theming" {{tiapp.xml}}. This might me the most challenging one, since I guess the CLI already reads some information from {{tiapp.xml}... | 8 |
44 | ALOY-1091 | 07/18/2014 08:15:38 | id property of <Picker> other than 'picker' is treated as a variable | If you use id name except 'picker' to Picker, that id will be handled as variable. h5. view {code:xml} <Alloy> <Picker id="testpicker"/> </Alloy> {code} h5. style {code:css} '#testpicker': { type: Ti.UI.PICKER_TYPE_DATE_AND_TIME } {code} h5. compiled code {code:javascript} $.__views.testpicker ... | 3 |
45 | ALOY-1090 | 07/18/2014 12:05:48 | Views XML: Support spaces in comma-separated lists of targets in the platform attribute | After one hour struggling my mind (since the update from 3.2.3 to 3.3.0) why the same code didn't work, I found a little bug, I suppose its in Alloy 1.4, because changing the SDK from 3.3.0 to 3.2.3 didn't work {code:xml} <Alloy> <Window platform="android, mobileweb" exitOnClose="true"> <Button bottom="5" w... | 3 |
46 | ALOY-1092 | 07/21/2014 02:24:29 | Allow more query options / scope in .tss | The docs state that you have to use Alloy.Globals.* in a .tss query. You can actually use a local function in a controller too, i.e. `"#window[if=myFunc()]"` and that will work too. What won't work however is basing a query off of params passed to the controller instance. It would work, but the Alloy compiler does... | 3 |
47 | ALOY-1093 | 07/21/2014 09:05:11 | Picker: quotes removed from dimension properties with string values during parsing | with alloy 1.4 if i run {{alloy compile --config platform=android}} the code in the tss in the widget {code} Picker[platform=android]":{ left:"10dp", right:"10dp" } {code} is parsed into {code} $.__views.__alloyId7.add($.__views.dateLbl); $.__views.picker = Ti.UI.createPicker({left:10dp,right:10dp,format... | 3 |
48 | ALOY-1094 | 07/21/2014 20:07:26 | Date or time pickers: cannot use Ti.UI.* type constants, must use Titanium.UI.* abbreviations | The following code will generate an error because it uses {{type: Ti.UI.PICKER_TYPE_DATE_AND_TIME}} rather than {{type: Titanium.UI.PICKER_TYPE_DATE_AND_TIME}}. The same is true with any of the date or time type picker type constants. h5. view {code:xml} <Alloy> <Picker id="testpicker"/> </Alloy> {code} h5... | 3 |
49 | ALOY-1097 | 07/22/2014 19:35:20 | Update Popover samples to use contentView in all cases | Adding views to contentView is the preferred technique. Adding views directly to the popover might still work, but our samples should not show that technique. Need to update: * test/apps/ui/popover * test/apps/testing/ALOY-983 | 3 |
50 | ALOY-1108 | 07/25/2014 09:41:28 | Some .svn directories slipped into the GIT repo of Alloy | Dear Alloy guru's, I found some .svn folders in the GIT repo that break an SVN checkout. It's minor I know, but just to let you know. Thanks, Wouter Monkhorst | 2 |
51 | ALOY-1127 | 07/31/2014 09:17:21 | Alloys Data Binding feature does not respect formFactor property | Similar to ALOY-691 the same example fails if using the {{formFactor}} attribute. See following example using Alloy 1.4.1 . It results in a crash. {code:title=views/index.xml} <Alloy> <Collection src="test" /> <Window id="index" platform="ios" formFactor="tablet"> <View id="content" dataCollectio... | 13 |
52 | ALOY-1102 | 07/31/2014 09:29:34 | Module for ListView is not working when using SDK 3.2.3 | h2. Description Following ticket ALOY-1082 I tried to create a module for ListView. While the code (pasted below) works fine using SDK 3.3.0.GA, an error is thrown when building with 3.2.3.GA. h2. Code Code as proposed by [~skypanther] is the following: lib/customlist.js {code} var ListView = function(args)... | 3 |
53 | ALOY-1103 | 07/31/2014 18:49:15 | <headerview formFactor="handheld"> not working and throwing an error | h5. Problem description formFactor='handheld' is not correctly applied if applied to <HeaderView> object. Depending on the target, could either be not visible or crashing the app. h5. Steps to reproduce Use the following sample code: h6. index.xml {code} <Alloy> <Window> <TableView h... | 5 |
54 | ALOY-1104 | 08/01/2014 01:18:55 | Fail build with clear message if controllers/index.js is missing | h6. Problem description Build fails on Android if the 'asset' folder is being deleted from the app project and is also not present in the Resources files folder. h6. Steps to reproduce 1. Create a new Alloy project 2. Delete everything in app folder except "views/index.xml" and "controllers/index.tss". Also dele... | 5 |
55 | ALOY-1105 | 08/01/2014 21:16:57 | Widget assets are not copied to the compiled app | In testing widgets, I've found that widget assets are not copied to the compiled app. Steps to reproduce: 1. Make sure you're using a 1.5.0 branch of Alloy 2. From the repo directory, run {{jake app:run dir=ALOY\-898}} This sample app happens to use the loading widget, which contains a set of graphic assets. 3.... | 5 |
56 | ALOY-1107 | 08/04/2014 04:22:38 | Rollback Theme "i18n" and "platform" folders implementations | Remove changes made to Alloy to implement this feature. A better solution has been proposed to handle this at the platform level and Alloy can then use it to more safely theme these folders. | 2 |
57 | ALOY-1220 | 08/07/2014 04:20:19 | Widgets can not be used in ListView Templates | When leveraging templates in a ListView, the alloy compiler fails when trying to compile an ItemTemplate that contains a Widget tag. | 13 |
58 | ALOY-1112 | 08/08/2014 18:08:01 | Styles TSS: Support spaces in comma-separated lists of targets in the platform attribute | h5. Improvement description See ALOY-1090 Spaces in comma-separated lists of targets in the platform attribute could be supported also in styles .TSS. For example: 1. Create a new project and use the following code: {code} '#index[platform=android, ios]': { backgroundColor: 'yellow', fullscreen: false, ex... | 3 |
59 | ALOY-1113 | 08/08/2014 22:10:35 | Fix case on 'alloy info adapters' command output | "alloy info adapters" command returns the contents of description in the tag name "description". However, "alloy info samples" (or even templates) have the contents in "Description" tag/field. Studio is expecting the same tag for all samples, templates and adapters. I believe the tag name has to be "Description" for al... | 3 |
60 | ALOY-1229 | 08/13/2014 17:47:23 | iOS: ListView filling template incorrectly | The ListView is not filling out incorrectly. The first label "#faultyLabel" should be replace with text and have a backgroundColor="magenta", but what's happening is a new label is appearing behind the next line, with its backgroundColor="magenta" and the text either not displayed or displayed out of view. Create a ... | 5 |
61 | ALOY-1115 | 08/19/2014 22:18:58 | CLI command to create a project from an Alloy test case | In a recent email thread, [~skypanther] had an idea to add an {{alloy}} CLI to create a new Alloy project from a given sample, e.g. {{alloy create_sample basics/simple}}. Moar: bq. ...The samples are actually installed to the developer’s computer...as is a shell/template app. Such a command could merge the two, putt... | 3 |
62 | ALOY-1240 | 08/21/2014 10:15:19 | Date picker type cannot be specified in the TSS | views/index.xml contains: {code} <Picker class="datePicker" id="observation_date_picker" type="Titanium.UI.PICKER_TYPE_DATE"></Picker> {code} styles/index.tss contains: {code} "Picker":{ width:Titanium.UI.FILL, height:Titanium.UI.SIZE, selectionIndicator:"true", useSpinner:"true", } ".datePicker":{ ... | 5 |
63 | ALOY-1116 | 08/22/2014 20:01:45 | sql sync adapter: optimize update method for adding/updating models | Community PR: https://github.com/appcelerator/alloy/pull/518 The proposed change should offer speed improvements but implements no functional changes (in other words, existing code should continue to work). Per the comment on the PR: Consider adding a batch update method that would be faster because it would proc... | 5 |
64 | ALOY-1221 | 08/26/2014 13:52:27 | Support Widgets and Require in ListItem Templates | Currently, it is not possible to use <Widget> or <Require> within a ItemTemplate like this: {code:xml} <Alloy> <ListView id="listview" onItemclick="onItemClick"> <Templates> <ItemTemplate name="default" class="row"> <View class="titles"> <Label bi... | 0 |
65 | ALOY-1121 | 08/26/2014 15:11:11 | Update extract-i18n command to extract strings from XML files in addition to TSS | Community PR https://github.com/appcelerator/alloy/pull/527 Ticket is to test, confirm functionality and applicability. | 3 |
66 | ALOY-1122 | 08/27/2014 22:11:17 | Consistent naming for platform-specific folders | There is a discrepancy in the naming of the folder for iOS-specific resources in the Alloy file structure. For assets and libs, the folder is called "iphone". For controllers, views, and styles, the folder is called "ios". I think we should have one consistent folder name for Alloy. | 3 |
67 | ALOY-1123 | 08/29/2014 18:41:59 | When a new project is created in Appcelerator Studio app.tss should be created | When a new project is created in Appcelerator Studio app.tss should be created since it is not. This is similar to the alloy.js file which is included as an empty file with instructions as to what would go inside app.tss holds global styles | 2 |
68 | ALOY-1125 | 09/02/2014 18:30:42 | Alloy: Button - Click event doesn't trigger | Click event doesn't trigger correctly. After few (~3) clicks the event is not triggered at all. Button basically behave as it was without any event listener. Please look at it ASAP. index.js (only) {code:javascript} var win = Ti.UI.createWindow(); var table = Ti.UI.createTableView(); var row = Ti.UI.creat... | 8 |
69 | ALOY-1124 | 09/02/2014 22:33:14 | When using view-model binding, whitespace outside curly braces for ImageViews crashes the app | h5. Problem description When using view-model binding, putting a whitespace outside curly braces, in the quotes, when using ImageViews, crashes the app h5. Steps to reproduce 1. Grab the sample code for https://jira.appcelerator.org/browse/ALOY-716 : https://github.com/appcelerator/alloy/tree/master/test/apps/test... | 3 |
70 | ALOY-1129 | 09/08/2014 13:23:35 | Delete method shouldn't reset model's id | Community PR https://github.com/appcelerator/alloy/pull/547 "Model's ID should not be deleted (reset) in the adapter. The problem is that after the Sync is done Backbone will trigger destroy which will execute a method called _onModelEvent -> remove ,but model doesn't have an id anymore ,so it won't be deleted from ... | 3 |
71 | ALOY-1130 | 09/08/2014 16:05:39 | "ui/map" sample code error for mobileweb | h5. Problem description Ui/Map module sample is not runnable on MobileWeb for a typo in the code h5. Steps to reproduce 1. Import ui/map sample 2. Run in MobileWeb Result: 'Uncaught reference - ti is not defined at /index.html' The code for MobileWeb is {code} <View id="map" ns="ti.map" method="createView"... | 2 |
72 | ALOY-1131 | 09/08/2014 16:32:04 | ALOY-1028 sample test is not included in master or 1_5_X branch | ALOY-1028 sample test is not icluded in master or 1_5_X branch In present in 1_4_X branch (and works fine with latest 1_5_X). | 2 |
73 | ALOY-1132 | 09/08/2014 19:32:40 | 'testing/ALOY-1058' sample code is using quoted type value | h5. Problem description Sample code for ALOY-1058 is using a value for the type property with quotes, while, setting the type from the TSS, it should be used with no quotes. Not a regression. From the sample code "index.tss", type is defined in this way: {code} "#picker":{ type:"Ti.UI.PICKER_TYPE_DATE" } {c... | 2 |
74 | ALOY-1133 | 09/09/2014 00:32:45 | Alloy 1.5b fails to build a project using Napp Drawer if one of the menus is <Required> ed in. | h4. Expectation Project to build h4. Reality Project doesn't build {code} [INFO] style: "index.tss" [INFO] view: "index.xml" [DEBUG] /usr/local/lib/node_modules/alloy/Alloy/commands/compile/styler.js:582 [DEBUG] var standard = bindingStr.match(/^\s*\'\+(.*)\+\'\s*$/)[1]; [DEBU... | 3 |
75 | ALOY-1134 | 09/09/2014 21:23:04 | Add @3x images and new icon sizes to new-app templates and samples | To support the iPhone 6/6+ screen sizes, we will need to add new icons and launch screen images to our new-app templates and samples. See https://developer.apple.com/library/prerelease/ios/documentation/UserExperience/Conceptual/MobileHIG/IconMatrix.html#//apple_ref/doc/uid/TP40006556-CH27-SW1 for the complete list.... | 3 |
76 | ALOY-1135 | 09/12/2014 12:11:50 | iOS: TextField: Textfield is not visible on window when styles applied in tss file | Textfield not visible on window when styles applied in tss Not a regression. Since issue occurs with 3.3.0.GA also *Steps to reproduce:* 1. Create Alloy Project. Replace the js files with code mentioned below 2. Run the app. index.js: {code} $.win.open(); {code} index.xml: {code} <Alloy> <Window i... | 2 |
77 | ALOY-1137 | 09/13/2014 18:58:49 | Jake: not able to run project from Studio on Genymotion if not manually editing tiapp.xml | h5. Problem description After using Jake to import, setup and run an Alloy project in Appcelerator Studio, is not possible to run it on Genymotion emulators if not manually editing first tiapp.xml. h5. Steps to reproduce 1. Import the Harness project in Appcelerator Studio 2. Import any Alloy project using Jake. ... | 3 |
78 | ALOY-1138 | 09/15/2014 17:12:54 | Error creating a new Widget from Studio if config.json is not present | h5. Problem description If no config.json file is present, creating a new Widget returns an error. h5. Steps 1. Create a new Alloy project 2. Delete config.json file in the root project folder 3. From Appcelerator Studio, left click and create a new Widget Result: a problem occurred creating a new widget. Wi... | 3 |
79 | ALOY-1139 | 09/15/2014 21:46:45 | Investigate options for automated testing | Investigate the use of tiO2 for automated runtime testing to improve our test coverage and improve quality for Alloy development. | 8 |
80 | ALOY-1140 | 09/16/2014 05:11:53 | Windows: The path format for app.js is different from controller files in sourcemap | The sourcemap contains different source location path format for app.js file compared to controller files on Windows platform. The map file for app.js is : {code} "version":3,"file":"Resources/android/app.js","sources":["Resources/android/app.js"] {code} The map file for index.js is : {code} "version":3,"fil... | 8 |
81 | ALOY-1141 | 09/17/2014 17:27:40 | iOS, Jake: Harness project from Studio on iPhone simulators might use wrong Sim version | h5. Problem description Following https://jira.appcelerator.org/browse/ALOY-956, SDK hardcoded version has been removed from tiapp.xml when importing a project in the Harness project. Using iOS 8 simulators and Studio this could lead to running a wrong Simulator version if running the project just after importing i... | 3 |
82 | ALOY-1142 | 09/17/2014 18:20:30 | iOS: ALOY-720 sample: <NavigationGroup> object needs to be changed to <NavigationWindow> | h5. Problem description <NavigationGroup> is no longer supported for iOS. Instead, NavigationWindow object should be used. Sample https://github.com/appcelerator/alloy/tree/master/test/apps/testing/ALOY-720 needs to be updated as still using NavigationGroup and currently failing to run. Ideally, a mobileweb fo... | 2 |
83 | ALOY-1144 | 09/19/2014 11:54:42 | Alloy: createStyle turns proxy objects into JS objects | In Alloy 1.5.0 [{{Alloy.createStyle()}}|https://github.com/appcelerator/alloy/blob/master/Alloy/lib/alloy.js#L233] uses a new utility method [{{deepExtend}}|https://github.com/appcelerator/alloy/blob/master/Alloy/lib/alloy.js#L609] to clone the merged properties. However, because of its implementation a proxy object li... | 3 |
84 | ALOY-1145 | 09/19/2014 15:32:58 | Add ALOY-1144 test case app to master branch | A community pull request for ALOY-1144 was merged to master. It did not include a test app. I added one for the corresponding PR I created to implement the fix in the 1_5_X branch. This ticket is to add that test app to the test/apps/testing folder for the master branch. | 2 |
85 | ALOY-1148 | 09/26/2014 15:17:01 | Update model template code to include Backbone 1.1.2 support code | Per ALOY-1074, if a developer uses Backbone 1.1.2 (rather than the default 0.9.2), he/she must extend the collection definition to account for a breaking change in backbone. Add this to the modelcode.js template file to provide guidance to developers attempting to use this feature. {code} // For Backbone v1.1.2,... | 2 |
86 | ALOY-1152 | 09/26/2014 16:33:38 | Alloy 1.5.0 RC3: Compiler fails on TextArea with child control | Problem: Placing a child control inside a TextArea that is part of a ListView template causes the Alloy compiler to fail with: {quote} [ERROR] Cannot read property 'symbol' of undefined [ERROR] Alloy compiler failed {quote} Test: Build the sample code below. {code:title=index.xml} <Alloy> <Windo... | 5 |
87 | ALOY-1149 | 09/26/2014 23:33:46 | iOS: Gradient array properties are converted into objects | h5. Problem description Gradients contain properties as array, for example the 'color' property. In Alloy, those properties are now converted and passed as objects and an app is crashing if using those properties. The issue seems to be introduced after ALOY-1051 as is not reproducible using Alloy version 1.4.1 (... | 5 |
88 | ALOY-1150 | 09/29/2014 22:16:01 | Release notes: there is no date for the 1.5.0 release | h5. Problem description A date for the 1.5.0 release should be added to the release notes. Alloy CHANGELOG.md in the Github 1.5.0 branch currently says: {code} Release 1.5.0 Full list of Issues that were addressed in Release 1.5.0 [...] Release 1.4.1 (07/28/2014) Below are the fixes included in this release. {... | 1 |
89 | ALOY-1156 | 10/03/2014 16:50:42 | Update readme to prune outdated information | Text in the Getting Started, Additional Notes, Feedback, Contributing, and Contributors sections is perhaps dated. We should confirm that text still applies and prune outdated or extraneous information as needed. Add info on the new --testapp attribute in the Running Sample Test Apps section Update jakelib/readme... | 2 |
90 | ALOY-1163 | 10/07/2014 09:27:14 | Using $.UI.create on a ListView with Custom Data templates causes to hide rows when templates are created programmatically. | h4. Problem Description When using the $.UI.create function for ListViews using custom item templates causes the listitems not to show. h4. Steps to reproduce 1. Create a new mobile project 2. Add this testcase h4. index.xml: {code} <Alloy> <Window id="container" class="container"> </Window> </Alloy> {co... | 5 |
91 | ALOY-1157 | 10/07/2014 17:03:32 | Creating sample app from advanced/android_density doesn't copy resolution-specific image folders | *Steps:* 1. Create a new Alloy app from the advanced/android_density sample {code} titanium create --name=appname --id=com.domain.appname --platforms=all cd appname alloy new . --testapp advanced/android_density {code} Note that the source android_density code includes the following res-* folders each con... | 5 |
92 | ALOY-1241 | 10/08/2014 11:12:31 | Alloy: Widget is loaded - initialized twice | Widget within TableViewSection is initialized twice. index.xml {code:xml} <Alloy> <Window> <TableView> <TableViewSection> <Widget src="abc"/> </TableViewSection> <Widget src="abc"/> </TableView> </Window> </Alloy> {code} widget.xml {code:xml} <Alloy> <TableViewRow title=... | 5 |
93 | ALOY-1158 | 10/08/2014 20:05:55 | Alloy Model/Collection tests need to be updated for supporting also Backbone 1.1.2 | h5. Problem description According to https://jira.appcelerator.org/browse/ALOY-576 we are upgrading Backbone version from 0.9.2 to 1.1.2 Backbone 0.9.2 will still there but will be deprecated in Alloy 1.6.0 - also 1.1.2 is going to break old samples and code, therefore need to be updated. See also docs: https:/... | 3 |
94 | ALOY-1159 | 10/10/2014 14:09:27 | Update underscore library to latest version | Update underscore lib, per PR https://github.com/appcelerator/alloy/pull/578 Need to update both runtime and build-time versions of the lib. | 3 |
95 | ALOY-1160 | 10/10/2014 19:19:55 | Replace splash screens & icons for new projects | We need to replace the draft Alloy icons & splash screens used for new projects prior to the 1.6 release. | 3 |
96 | ALOY-1161 | 10/13/2014 20:39:10 | MobileWeb: using 'backbone 1.1.2' dependency, app crashes on MobileWeb | h5. Problem description Accordingly to https://jira.appcelerator.org/browse/ALOY-1074 Backbone 1.1.2 is now selectable in config. json However, if 1.1.2 is selected, MobileWeb projects are not runnable. h5. Steps to reproduce 1. Create a new Alloy project 2. Edit config.json and add {code} "backbone": "1.1.2"... | 3 |
97 | ALOY-1162 | 10/13/2014 23:42:00 | Backbone 1.1.2 : <model/property> sample returning unexpected data for model attributes | h5. Problem description Using Backbone 1.1.2, sample app included in <model/properties> returns unexpected data values when fetching for stored persistent Model data (using properties adapter). h5. Steps to reproduce Currently working on narrowing down the sample code. However it can be reproduced by getting the a... | 3 |
98 | ALOY-1165 | 10/14/2014 15:05:57 | Compile error when merging backgroundGradient | PR: https://github.com/appcelerator/alloy/pull/588 Review pull request, create test case / sample app to be added to test suite | 3 |
99 | ALOY-1166 | 10/15/2014 15:08:17 | Direction arrow in models/binding_dataFunction test sample not correct on Android | https://github.com/appcelerator/alloy/tree/master/test/apps/models/binding_dataFunction 1. Build and run for Android and iPhone. Results: Direction arrow on Android is center-aligned; on iOS, the arrow is left-aligned. Expected: Arrow position same on both platforms. | 2 |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- 21