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
|
|---|---|---|---|---|---|
411 |
TISTUD-1703
|
05/24/2012 19:48:07
|
Titanium Studio: alpha highlight fails for some themes on initial preference change
|
When a block of code is highlighted and the theme preference is changed to certain themes, the highlighting intermittently fails until file reload. This is not a regression. This is only known to affect Windows 7 and Ubuntu 12.04, but not OS X. This is known to affect the following themes: idleFingers iLife 05 Steps to Reproduce: 1. Create a new project, open app.js. 2. Highlight an arbitrary block of code (and keep it highlighted). 3. Go to Preferences > Titanium Studio > Themes. 4. Change the theme to iLife 05 (for example). Click apply. 5. Move the preference window to view app.js. Expected Result: Highlighting alpha should be correctly applied. Actual Result: Highlighting alpha is not working. If the preference is accepted and the file is used, highlighting will be broken until the app is reopened. This is an intermittent issue.
| 8 |
412 |
TISTUD-1704
|
05/24/2012 20:03:32
|
Titanium Studio: App Explorer: Local Filesystem root has no name on Linux
|
On Linux, the Project Explorer Local Filesystem root directory has no name. This does not affect Windows 7 or OS X Snow Leopard. This is not a regression. Steps to Reproduce: 1. Open studio. 2. Navigate to Project Explorer. 3. Navigate to Local Filesystem. 4. Navigate to the root directory. Expected Result: Root directory should have a name. Actual Result: Root directory does not have a name, it is a blank folder. See screenshot.
| 5 |
413 |
TISTUD-1705
|
05/24/2012 20:16:23
|
Titanium Studio: top menu bar receives events on Linux when other menu windows are open
|
Top menu bar receives events on Linux when other menu windows (i.e., Preferences, About, Search) are open. This can result in multiple preference windows being launched. This is not a regression. This does not affect Windows 7 or Snow Leopard. This does not affect Eclipse on Ubuntu. Steps to Reproduce:prav 1. Open studio. 2. Open a menu window (e.g., Preferences, Search). 3. Click on the top menu bar (i.e., File, Edit, etc.). Expected Result: The top menu bar should not receive any click events. Actual Result: The top menu bar can receive events. However, the main editor frame is correctly blocked from receiving events. As a consequence, many info windows can be launched multiple times (i.e., Search, About). However, the main preferences window can only have one instance.
| 8 |
414 |
TISTUD-1706
|
05/25/2012 12:38:18
|
Studio: Project Explorer: "Promote to Project" causes position shift in full screen mode
|
When trying to promote a folder to a project in full screen / maximised mode, Titanium Studio moves when the Promote to Project dialogue box opens. This bug is a regression, this issue does not happen in 2.0.1. Steps to reproduce: 1. Open Titanium Studio in Maximised Mode. 2. In the Project Explorer open the context menu for a folder. 3. Select "Promote to Project". Expected Results: The Dialogue box would open without a change in Titanium Studio's location on the screen. Actual Results: Window containing Titanium Studio goes into windowed mode and shifts up on Windows 7, The screen shifts up while staying full screen for Mac OS 10.7.3, and Ubuntu 11.10 shifts into windowed mode but does not move.
| 5 |
415 |
TISTUD-1707
|
05/25/2012 13:32:13
|
Titanium Studio: module packaging to project with dirty tiapp.xml fails to write module xml tags
|
If a module is packaged to a project with a dirty tiapp.xml (i.e., a module was just deleted using the red X), the module xml tags will not be written to the project tiapp.xml. This is not a regression. There is no log. This is related to TISTUD-1666, but this is a separate edge case. Steps to Reproduce: 1. Create a new project. 2. Create a new module. 3. Package the module to the project. 4. Delete the module from the project using TiApp Editor Overview (click the red X to delete module). This will dirty the tiapp.xml file and remove the module xml tags, but keep the module folder in the project. 5. While the editor is still dirty, package the module again to the project. Expected Result: Module should package and appear in TiAPP Editor Overview, xml tags for the module should exist in the tiapp.xml file. Actual Result: Module packages, but does not appear in the TiAPP Editor Overview. The xml tags are not generated. It is worth noting the module tags will be added if the tiapp.xml file is dirty from other kinds of edits (i.e., changing the app version from 1.0 to 2.0).
| 8 |
416 |
TISTUD-1708
|
05/25/2012 14:52:10
|
Studio: HTML verification does not mark syntax errors
|
I get warning for the DOCTYPE missing but see no syntax errors being marked. This is on a fresh install of Titanium Studio running default settings in a new work space. This is a regression, HTML validation worked in 2.0.1. Steps to reproduce: 1. Create an HTML file with the following: {code} <html xmlns="http://www.w3.org/1999/xhtml" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>HTML</title> <meta name="author" content="qatester" /> <!-- Date: 2012-05-25 --> </head> <body> <a href="http://google.com" src="this shouldn't work" div>Google</a> <xml>this shouldn't be here</xml> <?import namespace="t" implementation="#default#time2"> <p> This tag is correct.</p> </body> </html> {code} Expected results: Validation should return with warning and errors. Actual results: Only the DOCTYPE warning appears.
| 8 |
417 |
TISTUD-1709
|
05/25/2012 16:39:12
|
Studio: HTML verification does not mark a warning for unknown attribute
|
The following code was used in testing and should throw a warning out on the anchor tag's line. Steps to reproduce: 1. Create a HTML file that contains the following: {code} <html xmlns="http://www.w3.org/1999/xhtml" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>HTML</title> <meta name="author" content="qatester" /> <!-- Date: 2012-05-25 --> </head> <body> <a href="http://google.com" src="this shouldn't work" div>Google</a> </body> </html> {code} Expected Result: A warning should appear on the anchor tag's line. Actual Result: The anchor tag's line does not generate any warning.
| 8 |
418 |
TISTUD-1710
|
05/25/2012 17:06:21
|
Dashboard: "Explore" tab has two $$ next to prices of modules
|
The Titanium Studio dashboard shows two dollar signs next to module prices. See attached images.
| 2 |
419 |
TISTUD-1711
|
05/28/2012 03:27:58
|
Titanium Studio: On terminating the launch of Android emulator, an Application Installation Error message box is shown
|
On terminating the launch of Android Emulator while installing an application, a message box is shown for Application Installation Error. This does not occur on 2.0.1. Regression. Steps to Reproduce: 1. Create a new Titanium Mobile project 2. Select the option to run the project on Android Emulator 3. As soon as the emulator launching process starts, but emulator is not yet ready, click on the Terminate button in the console window on the studio (or quit the emulator) 4. Wait for a while Actual: A message box pops up for Application Installation Error with Reason as "Process Exit Value:1". If the emulator gets ready and installation of application has started, then terminating the emulator shows up a message box for Application Installation Error with Reason as "Process Exit Value:143" Refer to the attached screenshot of the message box shown and build log trace Expected: The emulator process should terminate with appropriate message in console and build log but no message box should be shown
| 0 |
420 |
TISTUD-1714
|
05/29/2012 18:51:45
|
Titanium Studio: Preferences menu default size too small to display "Apply" and "Restore Defaults" buttons
|
The Preferences > Titanium Studio > Titanium menu window, by default, is too small to display the "Apply" and "Restore Defaults" buttons. Screenshot attached. Resizing the window will reveal the buttons (and the resize is automatically saved, fixing the problem). This issue did not affect Studio 1.0.9. This is a regression. This does not affect Windows XP. Steps to Reproduce: 1. Delete the meta data for the current workspace (or create a new empty workspace). 2. Restart studio. 3. Go to Preferences > Titanium Studio > Titanium. Expected Result: "Apply" and "Restore Defaults" should be visible. Actual Result: "Apply" and "Restore Defaults" are not visible, window must be resized.
| 3 |
421 |
TISTUD-1717
|
05/30/2012 12:23:25
|
Studio: Command menu does not display in Ubuntu.
|
While testing in Ubuntu 12.04 I noticed that the Command menu does not appear in the Unity desktop (it appears fine in a gnome desktop setup). Something in the interaction with Unity is causing it to not display properly. Steps to reproduce: 1. Open Titanium Studio with Unity as it's desktop (default setting) 2. Try to run a command from the command window. Actual result: The command menu is not present. Expected result: The command menu should be present.
| 13 |
422 |
TISTUD-1719
|
05/30/2012 19:06:30
|
Titanium Studio: Android Run Configuration does not auto-select screen type if none exists
|
In the run configurations settings for an android emulator instance, if the sdk version is changed to one that does not have a screen type that existed in the previously selected sdk, there is only a blank screen type, resulting in invalid settings. It would be expected for studio to automatically select the first available screen type from the list if there is none selected on first sdk change. This is not a regression. Steps to Reproduce: 1. Open Studio. 2. Go to the Run Configurations menu. 3. Create a new android emulator run configuration. 4. Select google api's 2.2. Select a screen type. 5. Select google api's 3.0. Expected Result: A screen type should be selected. Actual Result: The screen type is blank, the run configuration is invalid until the screen type is selected.
| 5 |
423 |
TISTUD-1720
|
05/30/2012 19:29:45
|
run configuration menu should open last used run configuration for the selected project in app explorer
|
When a project is selected in the project explorer, and the project explorer Run Configurations menu is selected, it would be convenient if the Run Configurations menu auto-selected the last used run configuration for that selected project (instead of the last run configuration for all projects). Workflow: 1. Create two projects. 2. Run the first project in emulator. 3. Run the second project in emulator. 3. Select the first project and go to Run Configurations. Expected Result: The last used run configuration for project one should be selected when the run configuration menu is brought up. Actual Result: The project two run configuration will be selected because it was the last used.
| 8 |
424 |
TISTUD-1721
|
05/31/2012 12:31:39
|
setting runtime to rhino then back to v8 results in v8 xml tag in tiapp.xml when it should be default
|
In the TiApp Overview, setting the runtime to rhino, then back to v8 results in an xml tag added to the tiapp.xml when there should be none because v8 is default for 1.8.0.1+ sdks. This is not a regression. Steps to Reproduce: 1. Create a new project using a 1.8.0.1+ sdk (e.g., 2.0.1.GA). 2. Set the runtime to rhino. 3. Set the runtime back to v8. 4. Check the tiapp.xml. Expected Result: There should be no runtime tags at all because v8 is default for newer sdks. Actual Result: There is a v8 tag. This causes a related bug TISTUD-820.
| 3 |
425 |
TISTUD-1723
|
05/31/2012 16:40:43
|
Titanium Accounts "Login" button should be disabled until values are entered for Username and Password
|
Steps: 1. Bring up Titanium Studio->Account preferences 2. Enter a value for username. Keep password empty Expected results: Login button is disabled Actual results: Login button is enabled The Login button should be disabled until values are entered for username and password. This applies to JIRA and NodeJITSU logins
| 5 |
426 |
TISTUD-1724
|
05/31/2012 16:59:07
|
Titanium Studio: sdk updates without prompt if sdk folder is empty
|
If the SDK folder is empty, the SDK will automatically update to the latest when studio first launches. There is no prompt. This is not a regression. This is related to another Lion-specific issue: TISTUD-1529 Steps to Reproduce: 1. Empty the SDK folder. 2. Open studio while online. Expected Result: A prompt appears for an SDK update. Actual Result: No prompt, update occurs automatically.
| 0 |
427 |
TISTUD-1820
|
06/01/2012 00:02:34
|
Creating an app in studio with "HTML-Based" template shows on "my apps" as "HTML Template" regardless of project name, and has the same GUID regardless of user
|
While testing pricing we noted an application appeared on Neha's "my apps" list shortly after she tried to create an HTML-based template project in studio. The GUID or name of the application on "my apps" did not match the studio project Neha created. The name on "my apps" was "HTML Template". Shortly after creation, and while browsing, Neha's "HTML Template" project disappeared from her apps list. Fortunately Chung witnessed this over our shoulders. Natalie was able to reproduce the "HTML template" entry on her account, and I was able to on mine. Although Neha's went missing, we looked at the GUID enough to see similarity with Natalie's GUID. Comparing that to mine, we all have the same GUID. See attached screens for Natalie's production list and my pre-prod list with the new UI. Steps to reproduce: 1) Create a new studio project using "HTML-Based" template 2) Check "my apps" list for "HTML Template" 3) Check GUID Result: GUID will be as seen for others, project will exist and not match name of studio project or GUID. Expected: App entry in "my apps" should have matching name and matching but unique GUID
| 5 |
428 |
TISTUD-1726
|
06/01/2012 08:50:12
|
Error cleaning titanium project when platform SDK has unusual version string
|
I have an app tied to a special SDK version for blackberry, where the folder name is "blackberry_compat_2.0.1.v20120407201726". When the project is cleaned, we throw an error trying to parse the version. {code} !ENTRY org.eclipse.core.resources 4 75 2012-06-01 10:47:31.436 !MESSAGE Errors occurred during the build. !SUBENTRY 1 com.appcelerator.titanium.core 4 75 2012-06-01 10:47:31.436 !MESSAGE Errors running builder 'Titanium Builder' on project 'blackberry_app'. !STACK 0 java.lang.NumberFormatException: For input string: "blackberry_compat_2" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:449) at java.lang.Integer.parseInt(Integer.java:499) at org.osgi.framework.Version.<init>(Version.java:127) at org.osgi.framework.Version.parseVersion(Version.java:225) at com.appcelerator.titanium.core.TitaniumProjectBuilder.clean(TitaniumProjectBuilder.java:72) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:730) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:513) at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:422) at com.aptana.editor.common.preferences.ValidationPreferencePage$ApplyChangesAndBuildJob.run(ValidationPreferencePage.java:130) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 8 |
429 |
TISTUD-1727
|
06/01/2012 16:02:42
|
Titanium Studio blocked for any actions: "The user operation is waiting for background work to complete"
|
Titanium Studio blocked for any actions. Each attempt to import or delete project, or do anything returns a dialog window with message "User Operation is waiting. The user operation is waiting for background work to complete." This problem occurs on 2.0.2 and 2.1.0. Logfile and screenshot are attached.
| 0 |
430 |
TISTUD-1728
|
06/03/2012 19:03:02
|
The module dialog seems to only read modules on startup/restart
|
If you drop a module in Titanium global directory and try and add it using the UI, it won't show up in the list. You must re-start Studio to get it to detect the presence of the new module. We need to re-read each time you launch the dialog
| 5 |
431 |
TISTUD-1730
|
06/04/2012 09:30:51
|
Dashboard: Error:'$H' is undefined
|
When starting Titanium Studio in Windows 7, I am given the following webpage error: Line: 1 Error: '$H' is undefined This is created in the log at about the same time and may be related.: {noformat} !ENTRY com.appcelerator.titanium.core 4 0 2012-06-04 08:22:22.053 !MESSAGE (Build 2.0.2.201205311912) [ERROR] com.appcelerator.titanium.core/debug null !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.core.JVMInfo.hasJavac(JVMInfo.java:265) at com.appcelerator.titanium.core.JVMInfo.hasJavac6432(JVMInfo.java:224) at com.appcelerator.titanium.core.JVMInfo.parseJavaVersion(JVMInfo.java:204) at com.appcelerator.titanium.core.JVMInfo.load(JVMInfo.java:122) at com.appcelerator.titanium.core.JVMInfo.<init>(JVMInfo.java:61) at com.appcelerator.titanium.core.JVMInfo.getInstance(JVMInfo.java:46) at com.appcelerator.titanium.mobile.portal.processor.MobileSDKConfigurationHelper.getVersionInfo(MobileSDKConfigurationHelper.java:141) at com.appcelerator.titanium.mobile.ui.portal.processor.MobileSDKConfigurationProcessor.computeStatus(MobileSDKConfigurationProcessor.java:99) at com.aptana.configurations.processor.AbstractConfigurationProcessor.getStatus(AbstractConfigurationProcessor.java:154) at com.appcelerator.titanium.mobile.ui.portal.actionController.MobileSDKActionController$1.run(MobileSDKActionController.java:124) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {noformat} This is a regression bug, this did not occur in earlier builds of the dashboard (last tested 5/30/2012). Steps to reproduce: 1. Launch Titanium Studio. Expected result: Titanium Studio should start without error. Actual result: Titanium Studio throws the given error and creates the entry in the log file.
| 8 |
432 |
TISTUD-1732
|
06/04/2012 13:48:17
|
Titanium Studio: change default promote project option to titanium mobile
|
When a folder is imported into studio as a "promote to project" option, Web Project is the default setting. It seems like the default option should be "Titanium Mobile Project". Screenshot attached. Import > General > Existing Folder as New Project
| 8 |
433 |
TISTUD-1733
|
06/04/2012 15:17:03
|
Titanium Studio: JIRA Integration: remove priority from bug submission fields
|
In Help > Submit a Ticket, the Priority field needs to be removed.
| 5 |
434 |
TISTUD-1734
|
06/04/2012 16:05:31
|
Titanium Studio: add validation to "promote to project from folder" option for existing projects
|
When a previously existing project is "promoted to project", there is no validation to inform the user a project already exists. Steps to Reproduce: 1. Create a titanium mobile project. 2. Delete the project from the workspace (without removing from disk). 3. Reimport the project using Import > General > Existing Folder as New Project. Expected Result: A notification that the folder has an existing project type. Actual Result: No notification. Existing project info is overwritten.
| 8 |
435 |
TISTUD-1735
|
06/04/2012 17:52:05
|
JavaScript editor is showing a lot more warnings after updating to 2.0.2
|
Steps to reproduce: 1. Import Kitchen Sink sample (or any other sample) from Samples view; 2. Open Preferences > Titanium Studio > Validation > JavaScript and make sure "JSLint Validator" is selected; 3. Click OK and agree to re-build the project if asked. 4. Open Resources/app.js file. Expected result: no validation warning is displayed. Actual result: many validation warnings are shown.
| 8 |
436 |
TISTUD-1737
|
06/05/2012 09:50:44
|
Publish provider wizard does display entire Android platform page
|
Steps: 1. Start the sample publish provider wizard. Publish->Sample Publish Provider->Publish... 2. Select Android and proceed to the platform page Expected results: The entire Android platform page is shown Actual results: The keystore section is cut off, requiring a resize of the wizard
| 5 |
437 |
TISTUD-1738
|
06/05/2012 13:24:16
|
Auto-configure browser list to contain all installed browsers on Mac OSX
|
Description: While attempting to set a browser before running a mobile web preview, I noticed that the list of browsers did not include any specific browsers except firefox. It would be ideal to populate the list of installed browsers rather than have the user populate the list manually. Steps to reproduce: 1) Install Studio 2) Create project with mobile web target 3) Run in browser 4) Select "run configurations" and use the browser selection section Result: Firefox is the only 3rd-party browser listed although I have Chrome, Firefox, and Safari Expected: Firefox not displayed, or all installed browsers displayed Note: The version # of the browser is displayed here as part of the name of the browser.
| 8 |
438 |
TISTUD-1740
|
06/05/2012 17:26:37
|
Titanium Studio: Android Emulator: Not recognized by adb, unable to install to Emulator.
|
When Android emulator deployed, adb fails to recognize the emulator. This is intermittent issue, it effect all emulator versions. This is not an regression it occurred in 2.0.2 Step to reproduce: 1) Create default project. 2) Right Click, Select "Run As", Select "Run Configurations..." 3) Select "Titanium Android Emulator" 4) Select platform Android API: "Google API Android 4.0.3" 5) Apply and Run. Expected Result: adb should recognized the emulator or if this occur then studio should be provide error correction to handle the error properly. Actual Result: adb doesn't recognize the emulator. Studio fails to notified to developer of the failure and App never installed.
| 13 |
439 |
TISTUD-1742
|
06/06/2012 06:30:25
|
Hitting Enter/Return in password field of JIRA login on Submit Ticket dialog doesn't try to log user in
|
It'd be nice to be able to just hit Return/Enter and have it perform "Log In" without needing to click. This does work in the preference page version of the JIRA account login.
| 3 |
440 |
TISTUD-1743
|
06/06/2012 07:01:00
|
Add NodeJS Project wizard to listing in New > menu for Project and App Explorer
|
The NodeJS project wizard is not listed in the "New" submenu like the Web/Ruby/TiMobile/PHP project wizards are.
| 3 |
441 |
TISTUD-1746
|
06/06/2012 12:15:43
|
Titanium Studio: Help > Install Specific Titanium SDK: sdk text field does not have focus when menu first invoked
|
When the Help > Install SDK from URL menu is invoked, the skd text field does not have focus. It did have focus in 2.0.2. This is a usability issue and a regression. Steps to Reproduce: 1. Open Studio. 2. Go to Help > Install Specific Titanium SDK... Expected Result: Menu should pop up and sdk text field should have focus if it is selected. Actual Result: Text field does not have focus if it is selected, user has to manually select the field to paste the URL.
| 3 |
442 |
TISTUD-1752
|
06/07/2012 11:48:19
|
Need BOM (Bill of Materials) for packaged product
|
As part of continued quality control measures, the build and packaging procedure for Titanium releases will now include a BOM verification. This BOM will be generated from the Development environment and will be verified by QE via a fully releasable packaged installation. This procedure was implemented for the 2.0.2 release of SDK package.
| 3 |
443 |
TISTUD-1754
|
06/07/2012 15:05:43
|
Titanium Studio: HTML Editor: invalid closing tag does not generate warning
|
html verification is not working for closing tags. ex: body tags, paragraph tags etc. This is regression as it do work in 2.0.1, there is no log information. Step to reproduce: 1. Create an blank HTML file. 2. Insert the following code: {code} <html> <head> <title> <title> <head> <body> <p> <p> <body> </html> {code} Expected Result: Invalid closing tags should displays the warning icon. Actual Result: No warnings.
| 13 |
444 |
TISTUD-1757
|
06/08/2012 12:55:25
|
Titanium Studio TiApp.xml visual interface does not show common js modules such as the amazon ti.aws
|
Titanium Studio TiApp.xml visual interface does not show common js modules such as the amazon ti.aws Titanium AWS module can be found here: https://github.com/appcelerator-se/aws It is installed sibling to the ti.cloud commonjs module in the /commonJS/ folder After this is installed the tiapp.xml visual editor does not show the ti.aws module as available. it can be manually entered into the tiapp.xml file and works, however the visual interface does not show it PLEASE READ THE FOLLOWING TICKET: there is a bug that is direct conflict with this request: https://jira.appcelerator.org/browse/TISTUD-1318
| 8 |
445 |
TISTUD-1761
|
06/11/2012 16:03:13
|
Titanium Studio: high CPU after removing git-enabled project from workspace
|
When a git-enabled project is imported then deleted (not from disk) from the workspace, the cpu remains abnormally high for a few minutes. CPU: 137% This is not a regression. Attaching stack trace. Steps to Reproduce: 1. Import a git-enabled titanium mobile project. 2. Delete the project (not from disk) from the workspace. 3. Observe CPU usage (i.e., Activity Monitor). Expected Result: CPU should be low (e.g., 1.7%). Actual Result: CPU is high (e.g., 137%) and remains so for a few minutes.
| 8 |
446 |
TISTUD-1767
|
06/12/2012 14:48:53
|
Titanium Studio: Editor: Undo History NPE with Abnormal Workbench Condition error
|
When using Undo History (command + z), a null pointer exception error occurred indicating Abnormal Workbench Condition. I was only able to reproduce this by creating a project, editing app.js, deleting the project from disk, then creating another project with the same name and undoing the edits in the new app.js. Screenshot and log attached. The popup error only occurred once, but the console errors are consistently reproducible. Steps to Reproduce: 1. Create a new titanium project. 2. Make multiple sets of changes to app.js 3. Remove project from disk. 4. Create a new project with identical name. 5.. Undo all the changes to app.js. Expected Result: Changes should undo without error. Actual Results: Occasional NPE error. There did not appear to be any explicit consequences, as I was able to continue undoing/redoing correctly. However, the error logs appear every time an edit is undone.
| 0 |
447 |
TISTUD-1771
|
06/12/2012 23:06:46
|
Add new portal dashboard controller to run browser configuration check
|
Related to TISTUD-1414, a portal controller that: # Runs the browser configuration check on demand # Returns back a list of the currently configured browsers
| 8 |
448 |
TISTUD-1772
|
06/13/2012 09:51:47
|
Add "Install Titanium Module" menu option to Help menu
|
Add a menu option (identical to the original Install Titanium SDK screen) that contains: # A text box for a URL # A browse button allowing a user to navigate to a folder on disk This will then install the specified module into the global SDK folder. A note added to the bottom of the screen informing a user of how to install a module for just a project (by dragging it in) would clarify that behavior.
| 8 |
449 |
TISTUD-1791
|
06/13/2012 21:41:32
|
Allow non-commercial iOS developers to deploy iOS applications
|
I am using Titanium as a university student, by sharing a provisioning portal for my institution. This allows for educational use without paying the $99/year for a full iOS Developer account. The problem I have is that Titanium Studio is too knowledgeable of the commercial iOS developer program web site, and automates a few steps that I need to perform manually. I need to be able to input a developer certificate from the filesystem, as well as a provisioning profile also from the filesystem. The wizards should not prevent me from doing this, even though Titanium's test for me being in the iOS developer program fails (wizard error "Please sign up for the iOS Developer Program"). I can't even get by with editing the Launch Configuration. Any advice would be much appreciated, including dirty tricks like editing Titanium Studio config files, etc.
| 3 |
450 |
TISTUD-1776
|
06/14/2012 12:40:03
|
Titanium Studio: Project Explorer: Python option is not available in the list of "New From Template" under python file
|
"Python" option is not visible under "New From Template" list and after generating the new file from "New> File", "Python" option is not visible under "Commands" after right click inside the generated python file. Step to reproduce. (To generate the python file from template) 1) Click inside the "Project Explorer". 2) Select "New From Template" Actual Result: Python option is not visible. Expected Result: Python option should be visible. Step to reproduce. (After generating the python file from "New File" option.) 1)Right click inside the file. 2) Select the "Commands" option. Actual Result: Python option is not visible. Expected Result: Python option should be visible.
| 8 |
451 |
TISTUD-1778
|
06/14/2012 14:43:36
|
Add Mobile Web project creation section to initial dashboard configuration page
|
Extracted from TISTUD-1459: Additional section added to the initial configuration page. The tickets below were required to implement this feature. * Rename the "Configure" tab to "Get Started" * Confirm the Titanium SDK is downloaded (continuously check the SDKLocator to see if it's configured) * Run the browser configuration check to make sure Mobile Web is available (TISTUD-1414) * Extend current action to provide callback returning the name of the project (APSTUD-4800) * Add button to call new action to run project created in above step (APSTUD-4801), greyed out until a project is created, or there is at least one project in the workspace. * If the user happened to close and reopen the dashboard, the "just created" project might be lost. Pop up a dialog asking the user which project they wish to run. * Make sure wiki documentation is updated to reference the changed tab name of "Get Started" (https://wiki.appcelerator.org/display/guides2/Setting+up+Titanium+Studio) Once a user has successfully gotten off the ground quickly with a mobile web project, we collapse the upper section and expand the lower. This allows them to configure their native platform support and expand into developing iOS, Android, BlackBerry and beyond applications. See https://wiki.appcelerator.org/display/prd/Studio+Dashboard for more information.
| 0 |
452 |
TISTUD-1779
|
06/15/2012 12:17:42
|
Add version information to Windows browser configuration names and refresh version info on demand
|
Related to TISTUD-1414. As discussed, we need to include the version of the browser in question as part of the browser name (see image for example) Ideally, this value would be dynamic, but that appears to be impossible given the current UI. In the case where the user upgrades the browser later, the suggestion is that when the user re-runs the configuration step to auto-search, we replace the version #s of the existing browsers with the newer version.
| 13 |
453 |
TISTUD-1780
|
06/15/2012 13:52:05
|
TiApp.xml incorrectly displays select/enabled deployment targets
|
The enablement of the platform targets is inconsistent Steps: 1. Create a mobile project with just mobile web and SDK >= 2.1.0 2. In the TiApp.xml, enable the android and iphone/ipad targets 3. Change the sdk to < 2.1.0 4. Save the TiApp.xml Results: Checkbox for Android/iphone/ipad are checked but enabled 5. Close the TiApp.xml and reopen it Results Checkbox for Android/iphone/ipad are checked but disabled The checkboxes should be disabled as soon as the SDK is switched (since we can't add/change platforms after the fact in SDK < 2.1)
| 5 |
454 |
TISTUD-1783
|
06/18/2012 18:23:16
|
Titanium Studio: Run Configurations menu not accessible from simplified Studio perspective
|
When the new default simple Studio perspective is used, the Run Configurations menu from the deployment drop-downs is greyed-out. This does not occur on the original Extended Studio perspective. There is no log info. This is a regression in behavior. Steps to Reproduce: 1. Launch Studio. 2. Create a new project. 3. Select the run icon > Run Configurations... Result: Run Configurations is greyed-out and non-functional. Expected Result: Run Configurations should be functional.
| 3 |
455 |
TISTUD-1785
|
06/19/2012 11:13:09
|
When Ti Studio self-applies an update, a directory with several subdirectories remains on the root of the drive
|
When a Ti Studio update is installed (using the built-in update notification), after the update is complete and Ti Studio is restarted, the following file always gets left on the hard drive: {panel}C:\var\hudson\workspace\titanium-standalone-master\builders\com.appcelerator.titanium.standalone.build\eclipse\artifacts.xml{panel} Note that the "var" directory is left at the root of the install drive...adding to the root directory is frowned upon. This file should either be placed in the Ti Studio install directory, or it should be removed at the end of the update installation process.
| 8 |
456 |
TISTUD-1786
|
06/19/2012 12:59:04
|
Last line in JS editor does not have line number when word wrap is enabled
|
h3. Steps to Reproduce 1. Open JS editor 2. Enable line numbers 3. Copy and paste the following: var win = Ti.UI.createWindow({ backgroundColor : 'white' }) var viewImgShow = Titanium.UI.createImageView({ height : '50', bottom : '50' }); view1_foto.addEventListener('click', function(e) { Ti.API.info('click event fired!!'); Titanium.Media.showCamera({ success : function(event) { my_image = event.media; if (event.mediaType == Ti.Media.MEDIA_TYPE_PHOTO) { viewImgShow.image = my_image; viewImgShow.show(); } }, saveToPhotoGallery : true, allowEditing : true, mediaTypes : [Ti.Media.MEDIA_TYPE_VIDEO, Ti.Media.MEDIA_TYPE_PHOTO] }); }); //this does not have a line number h3. Actual Result You will see that the last line does not have a line number. This seems to choke somewhere after line 30. h3. Expected Result The last line in the editor should have a line number
| 13 |
457 |
TISTUD-1788
|
06/19/2012 16:56:45
|
Android SDK wizard fails with the message "NLS missing message: MobileSDKConfigurationProcessor_updatermessage in: com.appcelerator.titanium.mobile.portal.processor.message"
|
When trying to setup Android inside Titanium Studio, the wizard fails showing a window with the following error message: "NLS missing message: MobileSDKConfigurationProcessor_updatermessage in: com.appcelerator.titanium.mobile.portal.processor.message OK" I managed to install the SDK manually, but I get the same error message when I click the UPDATE button. This is a regression from 2.0.2. This does not occur in 2.0.1.
| 3 |
458 |
TISTUD-1790
|
06/20/2012 10:56:58
|
Titanium Studio: Tiapp Editor: Unable to add ti.android.runtime property "v8" value.
|
Unable to add "<property name="ti.android.runtime">v8</property>" after modification is made in "Tiapp.xml" file in windows. Imported edited "Tiapp.xml" file do not have property added, except you do changes from the "Ti.Studio>Tiapp Editor> Overview". Step to reproduce: 1. Create a new TiMob Project 2. Right-click on project and click Delete 3. Click Ok. Do not select Delete project contents on desk 4. Navigate to the newly created project on your system and open the tiapp.xml file 5. Delete the following: <property name="ti.android.runtime">v8</property> 6. Save changes to your tiapp.xml 7. Reopen TiStudio 8. Right-click in the Project Explorer and select Import > Import Existing Titanium Project 9. Click Next 10. Browse for the TiMobile project that has the empty Android Runtime property 11. Check Expected Results 12. Click Finish 13. Expand imported project 14. Open tiapp.xml 15. Click on the tiapp.xml tab 16. Check Expected Results Expected result: Step 11. The following notification should appear http://appcelerator.qe.test.data.s3.amazonaws.com/FeatureTestResources/TiStudioAndroidRuntime/1020_Notification.png Step 16. Verify ti.android.runtime property is added with v8 value i Tiapp.xml Actual result: after modification and get imported the Tiapp.xml file in Ti.Studio, does not add the android property value "V8", unless you make changes from the overview tab in Tiapp Editor.
| 0 |
459 |
TISTUD-1792
|
06/20/2012 13:11:30
|
Titanium Studio: simple perspective not default and can't change back to Studio (extended) if in an old workspace
|
Simple Perspective does not show up and switching to Studio (extended) does not show the toolbar if in an old workspace. Steps to Reproduce: 1. Open Studio. Actual Result: Studio simple perspective is not the default, nor does it exist. The simple perspective is also not available in Window > Open Perspective. Expected Result: Simple perspective is default, exists, and is available in Window > Open Perspective.
| 3 |
460 |
TISTUD-1793
|
06/20/2012 13:19:39
|
Rename "Titanium Mobile [Module] Project" to "Titanium Project" and "Titanium Module Project"
|
In keeping with the removal of Desktop functionality from the core of Studio, we should rename "Titanium Mobile Project" to "Titanium Project" and "Titanium Mobile Module Project" to "Titanium Module Project"
| 13 |
461 |
TISTUD-1795
|
06/20/2012 17:16:40
|
Titanium Studio: Window > Hide Toolbar shows the toolbar instead in new workspace
|
When studio is launched in a new workspace, the simple perspective has a "Window > Hide Toolbar" option, but there is no toolbar. This command will instead show the toolbar. This issue goes away on second launch of studio. Steps to Reproduce: 1. Open Studio in a new workspace. 2. Go to Window > Show Toolbar. Actual Result: Window > Show Toolbar does not exist, it is now called Hide Toolbar. Expected Result: Show Toolbar should exist, Hide Toolbar should not, and Show Toolbar should show the toolbar.
| 3 |
462 |
TISTUD-1796
|
06/21/2012 10:22:27
|
Remove Titanium Desktop Project wizard from being promoted in Simple and Advanced perspectives
|
We need to remove the Titanium Desktop project wizard from the File > New menu, or being "promoted" in any other areas.
| 3 |
463 |
TISTUD-1805
|
06/22/2012 11:38:58
|
Titanium Studio: If Titanium SDK root folder is read-only, Studio will not prompt the user with an error
|
If the root Titanium SDK folder is readonly and latest sdk is not there, Studio will not find an sdk to update when update sdk is called. Step to reproduce: 1. /Users/"Your_home_dir"/Library/Application\ Support/Titanium/mobilesdk/osx 2. Delete the latest version of SDK folder 3. Give "Titanium" folder "read only" permission 4. Open Ti.Studio 5. Select "Help" from menu bar 6. Select "Check for Titanium SDK updates" Actual result: Ti.Studio displaying MSG. "No Ti.SDK update available" Expected result: Documentation web page should load in a browser.
| 5 |
464 |
TISTUD-1809
|
06/22/2012 17:27:13
|
Titanium Studio: Dashboard: remove desktop project from create new project dropdown
|
Dashboard > Develop > Templates > Create New Project still has a dropdown that allows the user to select a desktop project. There should only be one button that only creates a titanium studio project.
| 3 |
465 |
TISTUD-1813
|
06/25/2012 12:50:48
|
Titanium Studio: Run Configuration: new configuration should auto-select current project
|
When a new run configuration is created, it would be helpful if the project were auto-selected based on the project currently in focus (either from the project explorer, or app explorer). Steps to Test: 1. Select a Titanium Mobile project in the project explorer. 2. Go to Run Configurations... 3. Create a new Android Emulator run configuration. Expected Result: The project selected in the project explorer should be the default project in the new configuration. Currently there is no project selected in the new run config, it must be manually selected.
| 8 |
466 |
TISTUD-1817
|
06/25/2012 20:45:23
|
Titanium Studio: Install Titanium Module > Browse while Packaging Module Freezes Studio
|
If the Install Titanium Module... Browse window is open and a module packaging operation completes, studio will freeze. It is not possible to get a stack trace when studio is in this condition. Studio must be force-closed from the Activity Monitor. This is a new fail case, as the Install Module menu is new, and I could not recreate a similar freeze in Studio 2.0.2. Note: I was able to reproduce this every time in OS X, but I could not reproduce at all in Windows 7. Steps to Reproduce: 1. Open Studio. 2. Create a new Android module. 3. Package the module to directory (i.e., /Downloads). 4. While the module is still packaging, go to Help > Install Titanium Module > Install from URL Browse. Actual Result: When the packaging is complete, Studio freezes (screenshot attached). jstack does not work (console logs attached). studio log.txt attached. Expected Result: Studio should not freeze, and the user should be able to continue using it.
| 8 |
467 |
TISTUD-1818
|
06/25/2012 20:58:43
|
Titanium Studio: Upgrade Install Titanium Module to Project to include module in tiapp.xml
|
If a module is installed to project using Help > Install Titanium Module, the module is not added to the tiapp.xml. If a module is packaged to project, it is included in the tiapp.xml. There is no log info. Steps to Reproduce: 1. Create a new Titanium Mobile project. 2. Create a new Titanium Module project. 3. Package the module to a directory (i.e., /Downloads). 4. Go to Help > Install Titanium Module. 5. In Install from URL, select the packaged module zip. 6. In Output, select Project, and select the app project you created. Press OK. Actual Result: Module gets unzipped to project, but the module is not in the tiapp.xml. Expected Result: Module should unzip to project, and a module xml tag should be added to tiapp.xml. The module should be visible in the TiApp Overview.
| 8 |
468 |
TISTUD-1821
|
06/26/2012 14:05:53
|
Titanium Studio: unable to create android module at non-default project location
|
When creating a module in studio, the creation fails with internal error: could not move file. Screenshot and log attached. This only occurs with android modules. However, android modules can be created from the command line. Steps to Reproduce: 1. Go to New > Titanium Mobile Module Project. 2. Type in a project name and module id. 3. Deselect Use Default Location. 4. Browse to a new location (i.e., Desktop/ti). 5. Create the module. Actual Result: Error. Expected Result: New Module.
| 8 |
469 |
TISTUD-1825
|
06/27/2012 13:27:50
|
Add JDK installation to the Titanium Studio installer
|
Based on this: http://nsis.sourceforge.net/Java_Runtime_Environment_Dynamic_Installer Install the JDK as noted from http://titanium-studio.s3.amazonaws.com/jdk/jdk-6u25-windows-i586.exe It can evidently be run silently using the commands here: http://www.oracle.com/technetwork/java/javase/install-windows-189425.html
| 13 |
470 |
TISTUD-1826
|
06/27/2012 17:17:31
|
Android Emulator: terminate button should terminate the emulator
|
Pressing on the terminate button does not terminate the android emulator using V8 & Rhino. This is not a regression,it is reproducible in 2.0.2. Steps to reproduce: Select V8 follow the steps & then select rhino & follow the steps. # Install the latest SDK in the studio. # Create the default app in the titanium studio. # Go to run as>Android Emulator. # Let the emulator sit for 2 min. # Select 'android emulator process' from the studio 'display selected Console' icon. # Press on the terminate button. # Notice that the emulator does not terminate. Have attached the log but could not find anything significant. Actual: The process shows terminated but the emulator does not close. Expected: Pressing on the terminate button should terminate the android emulator.
| 0 |
471 |
TISTUD-1827
|
06/29/2012 10:56:09
|
Detect if node.js is installed, if not, run installer
|
http://nodejs.org/#download # Check to make sure node.js is installed ## For linux, install for Ubuntu, otherwise ask user to install themselves. # If it is, confirm it's within the currently supposed version range. # If not, inform the user to upgrade or install a new version # If it's not installed, download the current package from an appcelerator web site (so we can ship a stable version)
| 40 |
472 |
TISTUD-2002
|
06/29/2012 13:25:31
|
Android: Distribute to Android App Store doesn't give any finalization message
|
When deploying an app to Google Play from Titanium Studio (Publish | Distribute Android App Store), you no longer get a "success" or other finalization message saying that the process is complete. The last line that appears in the Console log is the zipalign command: {panel} "C:\Program Files (x86)\Android\tools\zipalign.exe" -v 4 C:\{MyTitaniumDir}\{MyWorkspaceDir}\{MyAppName}\{MyDistributionLocation}\{MyAppName}.apk C:\{MyTitaniumDir}\{MyWorkspaceDir}\{MyAppName}\{MyDistributionLocation}\{MyAppName}.apkz {panel}
| 5 |
473 |
TISTUD-1828
|
06/29/2012 15:21:30
|
Titanium Studio: intermittent freeze when importing git-enabled project
|
When importing a project with git information, studio freezes intermittently. This is intermittent and difficult to conclusively regression test. Steps to Reproduce: 1. Import KitchenSink from titanium_mobile using Import... > Existing Titanium Project. Actual Result: Studio unresponsive in Activity Monitor, spinning beach ball instead of arrow cursor, Studio not receiving user events. Expected Result: Project should import and git information should display in Project Explorer.
| 8 |
474 |
TISTUD-1831
|
07/02/2012 11:17:11
|
Signup link in Ti Studio login dialog does not work if browser preferences are changed
|
1. Logout of Studio and shut it down and restart 2. You should be presented with the signin screen 3. Click on Signup EXPECTED RESULT: taken to a signup page ACTUAL RESULT: Safari pops up in the background with a "cannot find file". file:///Applications/Titanium%20Studio/TitaniumStudio.app/Contents/MacOS/https:/my.appcelerator.com/auth/signup
| 5 |
475 |
TISTUD-1832
|
07/02/2012 14:59:24
|
Titanium Studio: Preferences > Titanium Studio > Titanium: Titanium SDK Path not correctly re-validated
|
In Preferences > Titanium Studio > Titanium > Titanium SDK Home, if you enter an invalid path (e.g., by removing the last two characters), then add in a valid path (e.g., add the last two characters back), studio will not re-validate the path. There is no log info. This is a regression. This does not occur in Studio 2.1.0. Steps to Reproduce: 1. Open Titanium Studio. 2. Go to Preferences > Titanium Studio > Titanium. 3. Edit the Titanium SDK Home path to make it invalid (i.e., delete the last two characters of text from the path). Studio should display an error. 4. Edit the Titanium SDK Home path to make it valid again (i.e., re-add the last two characters of text from the path). Actual Result: The error remains, the path has not been re-validated. However, the changes can be saved, and the error goes away on preferences menu re-open. Expected Result: The Titanium SDK path should immediately re-validate and the error should go away.
| 5 |
476 |
TISTUD-1833
|
07/02/2012 15:16:00
|
Titanium Studio: Preferences > Titanium Studio > Titanium: Android SDK path can't save if no Android SDKs installed
|
In Preferences > Titanium Studio > Titanium > Android SDK Home, if a fresh Android install is loaded into the path, the preferences cannot be saved. Note: The fresh Android install was just downloaded from http://developer.android.com/sdk/index.html and unzipped, no Android SDKs were installed. There is no log info. This is not a regression. Steps to Reproduce: 1. Download the Android SDK from http://developer.android.com/sdk/index.html. 2. Open Titanium Studio. 3. Go to Preferences > Titanium Studio > Titanium. 4. In Android SDK Home, enter the path to the new Android install. Actual Result: Cannot save the changes to the preferences menu. Expected Result: Can save the changes to the preferences menu. The dashboard config utility should be able use this path to continue the Android SDK installation.
| 8 |
477 |
TISTUD-1834
|
07/02/2012 16:32:26
|
BackingStoreException in the log when creating mobile module project
|
When using File > New > Titanium Mobile Module Project to create an Android module project, I see the following in the log (the project is created successfully): {code} !ENTRY org.eclipse.core.resources 4 4 2012-07-02 15:22:40.110 !MESSAGE Exception occurred while saving project preferences: /tistud1648/.settings/com.aptana.editor.common.prefs. !STACK 1 org.eclipse.core.internal.resources.ResourceException: A resource already exists on disk '/Users/mxia/Documents/workspace/runtime-New_configuration_ts2/tistud1648/.settings'. at org.eclipse.core.internal.resources.Folder.assertCreateRequirements(Folder.java:47) at org.eclipse.core.internal.resources.Folder.create(Folder.java:95) at org.eclipse.core.internal.resources.ProjectPreferences$1.run(ProjectPreferences.java:566) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.core.internal.resources.ProjectPreferences.save(ProjectPreferences.java:590) at org.eclipse.core.internal.preferences.EclipsePreferences.internalFlush(EclipsePreferences.java:440) at org.eclipse.core.internal.resources.ProjectPreferences.flush(ProjectPreferences.java:350) at com.aptana.editor.common.contentassist.UserAgentManager.savePreference(UserAgentManager.java:722) at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.applyPreferenceValues(BasicNewTitaniumProjectWizard.java:487) at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:392) at com.appcelerator.titanium.mobile.ui.module.wizard.NewMobileModuleProjectWizard.finalizeProjectCreation(NewMobileModuleProjectWizard.java:290) at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:349) at com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:252) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 1 org.eclipse.core.resources 4 272 2012-07-02 15:22:40.111 !MESSAGE A resource already exists on disk '/Users/mxia/Documents/workspace/runtime-New_configuration_ts2/tistud1648/.settings'. !ENTRY com.aptana.editor.common 4 0 2012-07-02 15:22:40.189 !MESSAGE (Build 0.0.0.qualifier) [ERROR] Error saving the user-agent preferences. !STACK 0 org.osgi.service.prefs.BackingStoreException: Exception occurred while saving project preferences: /tistud1648/.settings/com.aptana.editor.common.prefs. at org.eclipse.core.internal.resources.ProjectPreferences.save(ProjectPreferences.java:600) at org.eclipse.core.internal.preferences.EclipsePreferences.internalFlush(EclipsePreferences.java:440) at org.eclipse.core.internal.resources.ProjectPreferences.flush(ProjectPreferences.java:350) at com.aptana.editor.common.contentassist.UserAgentManager.savePreference(UserAgentManager.java:722) at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.applyPreferenceValues(BasicNewTitaniumProjectWizard.java:487) at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:392) at com.appcelerator.titanium.mobile.ui.module.wizard.NewMobileModuleProjectWizard.finalizeProjectCreation(NewMobileModuleProjectWizard.java:290) at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:349) at com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:252) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code}
| 8 |
478 |
TISTUD-1835
|
07/02/2012 16:53:56
|
Incorrect items appear under Publish menu the first time right-clicking on a project
|
Steps to reproduce: 1. Open Studio on a workspace with existing projects; 2. right-click on a Titanium mobile project (other types of project shows the behavior too) and select Publish to generate its submenus. Expected result: only the menu items appropriate for the project type will appear. Actual result: the submenus are not filtered, and all items contributed to the Publish menu show up. This only happens the first time the publish menu is generated. The correct menu items will appear when right-clicking again, even without a change in selection.
| 8 |
479 |
TISTUD-1836
|
07/02/2012 18:44:17
|
Titanium Studio: Dashboard: Configuration Wizard: Android SDK: Cancel before download begins freezes process
|
In the Dashboard Configuration Wizard for Android, if the installer is canceled before the Android SDK download begins, the process will freeze. jstack cannot get a stack trace when Studio is in this state, but Studio is useable as the process is running in the background. This is not a regression. This is not intermittent. Steps to Reproduce: 1. Open Titanium Studio. 2. Open Preferences > Titanium Studio > Titanium and delete the Android SDK Home path. 3. Go to the Dashboard > Configure > Android > Install/Upgrade to run the Configuration Wizard. 4. Enter a path to download the Android SDK (e.g., Desktop/TestAndroidSDK) but do not press OK yet. 5. Very quickly (for reliable reproduction), press OK, then Cancel in the previous menu. Actual Result: Process freeze. Expected Result: Cancel the process.
| 8 |
480 |
TISTUD-1840
|
07/05/2012 12:46:00
|
Error while selecting JavaScript Formatter in Preferences
|
1. Open Preferences in Titanium Studio. 2. Select Titanium Stduio->Formatter 3. Select JavaScript and Preview. 4. Error is seen. ( Screenshot attached). 5. After this step, 'preferences' cannot be opened. Screenshot is attached. ( Studio has to be restarted)
| 8 |
481 |
TISTUD-1842
|
07/05/2012 15:31:52
|
Improve prompt when Titanium Module can't be downloaded
|
h3. Steps to replicate # Select *Help > Install Module from URL* # Paste in URL https://developer.appcelerator.com/package/download/12/581/ti.barcode-iphone-1.8.1-android-1.7-2.3.2.zip h3. Expected result Module is behind a redirect. If we can't download, alert the user with the message: "Unable to download module from specified URL. Is the URL valid?" Then re-open the dialog box so they can check and try again. h3. Actual Result Process starts but fails without warning
| 5 |
482 |
TISTUD-1843
|
07/05/2012 15:32:55
|
handle URL redirects in module download/installation
|
h3. Steps to replicate # Select *Help > Install Module from URL* # Paste in URL https://developer.appcelerator.com/package/download/12/581/ti.barcode-iphone-1.8.1-android-1.7-2.3.2.zip h3. Expected result Module downloads. h3. Actual Result Nothing happens.
| 8 |
483 |
TISTUD-1846
|
07/06/2012 14:48:33
|
Titanium Studio: Available Updates: Object Teams Patch for JDT/Core is not applicable to the current configuration and will not be installed
|
When updating Titanium Studio, the JDT plug-in generates warnings. {code} !MESSAGE "Object Teams Patch for JDT/Core" is not applicable to the current configuration and will not be installed. {code} This is not a regression. This issue also occurs in Eclipse Indigo 3.7.2. Steps to Reproduce: 1. Install JDT plugin in Studio: https://wiki.appcelerator.org/display/guides2/Installing+the+Java+Development+Tools 2. Restart Studio. 3. Go to Help > Check for Updates. 4. Install the JDT Patch. Restart Studio. 5. Go to Help > Check for Updates. Actual Result: JDT plugin generates errors. Have to deselect JDT to update regular Studio updates. Expected Result: JDT should be able to install.
| 8 |
484 |
TISTUD-1849
|
07/08/2012 23:50:59
|
Rework Titanium Studio installer
|
https://wiki.appcelerator.org/pages/viewpage.action?pageId=37522780 Currently, Studio involves a three-step installation: # Install Titanium Studio # Install required software (JDK, Node.js, Git) # Configure platforms The first two steps seem clumsy and should be collapsed. This requires the following: # For windows, add JDK, git and Node.js checks and installs to the installer # For Mac, create an installer, and add Node.js check/install. Alternatively, publish Studio as an App Store app (requires OpenJDK: http://intransitione.com/blog/take-java-to-app-store/) # For Linux (Ubuntu), create a proper package with dependencies. For the third step, how can we prompt the user which platforms they wish to develop for, and help them through the configuration? Examples: * Android SDK pre-configuration * Android NDK * BlackBerry (VMWare Fusion, NDK) This should be an extensible model that allows us to plug in new platforms in the future. Ideally, we should also not require it all to be part of some monolithic installer, and some of these things can be downloaded on demand as needed. In 3.2.0, we will add JDK, git, and Node.js to Windows installer, and after the installation, we will prompt user which platforms they would like to setup and guide them through the process.
| 0 |
485 |
TISTUD-1850
|
07/09/2012 00:22:46
|
Replace Android configuration process with reworked version
|
Instead of sending users through the Android UI, we instead download the components directly. https://wiki.appcelerator.org/display/tools/Android+SDK+Installation
| 0 |
486 |
TISTUD-1851
|
07/09/2012 14:14:12
|
Install Alloy package using NPM
|
The determination of whether or not this needs to be run under sudo may not be easy for us to determine. We may need to assume no need for sudo? If we do need to run under sudo we'll need to handle prompting for the sudo password and piping it along to the command. {code} [sudo] npm install -g alloy {code}
| 8 |
487 |
TISTUD-1852
|
07/09/2012 14:18:53
|
Move Template selection to front of project wizards
|
We move project template selection to the first screen in the project wizard (see Xcode for an example here) This allows the user to focus on what they want to create (blank project, game, rss reader, master/detail, etc.). We then ask the user to fill in the name/location/etc later. (Basically swap the first and second page in most project wizards).
| 5 |
488 |
TISTUD-1853
|
07/09/2012 14:21:56
|
Add Alloy project nature icon
|
Need icons for Alloy project nature
| 3 |
489 |
TISTUD-1854
|
07/09/2012 14:22:25
|
Add Alloy project nature
|
Need a new Alloy project nature to tag projects with (and with which we can hang new icons, etc, on)
| 3 |
490 |
TISTUD-1855
|
07/09/2012 14:24:54
|
Creating Alloy projects inside New Titanium Mobile Wizard
|
Creating a new "blank" alloy project is as follows: - Run regular Titanium Mobile project creations (titanium/project.py scripts) - Run 'alloy new path/to/project' to run the alloy generators - Add Alloy project nature (in addition to the titanium mobile nature, web nature) By default, a new Titanium project is an Alloy project Note that an Alloy "template" likely would already have all the generated files, so we shouldn't need to do the script executions (running titanium scripts/alloy binary)
| 8 |
491 |
TISTUD-1856
|
07/09/2012 14:28:29
|
Add blank Alloy project template to project wizard
|
By default, a new Titanium project is an Alloy project. Select the "blank new alloy template" as the default in the titanium mobile project wizard. This creates an alloy project without any template.
| 8 |
492 |
TISTUD-1857
|
07/09/2012 14:32:50
|
Filter Resources folder out from Alloy projects
|
Hide Resources folder - Alloy generates the intermediate files there, most of the app lives in the "app" folder Long-term: - perhaps we root Alloy projects on the "app" folder, and choose an alternate presentation structure like Package Explorer. - What additional folders do we need to hide?
| 5 |
493 |
TISTUD-1858
|
07/09/2012 14:40:57
|
Enable running of Alloy applications
|
This may not require any additional work. We may simply need to run the existing builder.py script as we do with typical Titanium projects. See here for confirmation: https://github.com/appcelerator/alloy
| 8 |
494 |
TISTUD-1859
|
07/09/2012 14:44:49
|
Debugging Alloy applications
|
It's currently unclear if the work needs to mostly be done on the Studio side or the SDK side. In general, we would need a source map to connect the generated source code with the original source code so that users could place breakpoints in the original JS files and have it break appropriately.
| 20 |
495 |
TISTUD-1860
|
07/09/2012 14:45:42
|
Enable packaging of Alloy applications
|
This may not require any additional work. We may simply need to run the existing builder.py script as we do with typical Titanium projects. See here for confirmation: https://github.com/appcelerator/alloy
| 8 |
496 |
TISTUD-1861
|
07/09/2012 14:48:56
|
Associate Alloy XML files with our XML editor
|
Associate XML editor with "*.txml" files
| 2 |
497 |
TISTUD-1862
|
07/09/2012 14:50:07
|
Associate Alloy JSON Style configuration files with our JSON editor
|
What is the alloy JSON style configuration custom file extension we need to associate with? Does our JSOn parser/editor handle the non-standard "expression" syntax?
| 2 |
498 |
TISTUD-1863
|
07/09/2012 14:51:11
|
Associate Alloy JS Makefile (*.JMK files) with our JS editor
|
*.JMK file extension
| 2 |
499 |
TISTUD-1864
|
07/09/2012 17:14:26
|
Alloy Create View Wizard
|
Right-click app/views folder Pop up dialog box asking for view name {{alloy generate view <name>}} Add keyboard shortcut for opening dialog and generating view (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard)
| 8 |
500 |
TISTUD-1865
|
07/09/2012 17:16:00
|
Alloy Create Controller Wizard
|
Right-click app/controllers folder Pop up dialog box asking for controller name {{alloy generate controller <name>}} Add keyboard shortcut for opening dialog and generating controller (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard)
| 8 |
501 |
TISTUD-1866
|
07/09/2012 17:16:54
|
Alloy Create Migration Wizard
|
Right-click app/migrations folder Pop up dialog box asking for migration name {{alloy generate migration <name>}} Add keyboard shortcut for opening dialog and generating migration (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard) This will create a timestamp-ordered migration file for the model specified.
| 8 |
502 |
TISTUD-1867
|
07/09/2012 17:18:08
|
Alloy Create Widget Wizard
|
Right-click app/widgets folder Pop up dialog box asking for widget name {{alloy generate widget <name>}} Add keyboard shortcut for opening dialog and generating widget (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard) This will create a default widget in your projects's app/widgets path.
| 8 |
503 |
TISTUD-1868
|
07/09/2012 17:18:57
|
Alloy Create Model Wizard
|
Right-click app/models folder Pop up dialog box asking for model name, with a small table below for adding new values/types {{alloy generate model <name> [column_name:type, ...]}} For example: {{alloy generate model todo name:string active:boolean}} Add keyboard shortcut for opening dialog and generating widget (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard)
| 13 |
504 |
TISTUD-1870
|
07/09/2012 17:32:10
|
Content assist for $. in JS files
|
As an example: {code} <Window> <Button id="b"></Button> </Window> {code} You would then define a controller named index.js and you could automatically bind events inline in your controller code: {code} $.b.addEventListener("click",function(){ alert("You clicked the button"); }); // "$.index" is the default variable for a top-level container inside the index.xml $.index.open(); {code} So, we would need introspection on the items defined in the XML and display them appropriately in the content assist for the JS files
| 8 |
505 |
TISTUD-1871
|
07/09/2012 17:33:26
|
Content assist for Alloy XML files
|
For Alloy XML files, it is a file with XML tags, i.e.: {code} <View id="a"> <Button id="b">Hello</Button> <Label id="t"></Label> </View> {code} Need XML file containing tag information for Alloy tags. See https://github.com/aptana/studio3/blob/development/plugins/com.aptana.editor.html/metadata/html_metadata.xml
| 20 |
506 |
TISTUD-1872
|
07/09/2012 17:34:41
|
Content assist for Alloy JSON style files
|
The JSON style files specify style information for an app. We can provide CA for the property names, and also possibly common values similar to CSS CA. Need XML file containing CSS style information for the JSON configuration. See https://raw.github.com/aptana/studio3/development/plugins/com.aptana.editor.css/metadata/css_metadata.xml
| 20 |
507 |
TISTUD-1875
|
07/09/2012 18:03:00
|
Create an extension point to support different command-line interfaces
|
We need to be able to support V1 (Python) and V2 (Node.js) of the SDKs directly. # Create an extension point which describes the SDK per version range (< 2.2 is v1, >= 2.2 is v2), and allow contributing commands that are designed to run on a specific CLI. # The extension will return a 'command' to run by asking for a specific command key and passing the SDK version to filter by. A returned command will then be executed and provide progress as it's being executed. # When the CLI has no support for a specific command, a 'no-op' command (or null) can be returned. The extension should also allow querying for a command on a specified CLI version (V1/V2).
| 13 |
508 |
TISTUD-1877
|
07/09/2012 18:13:18
|
Add CLI command support for creating a project
|
Add extensions for the CLI commands that create a Titanium project (mobile / module). h2. Project Creation V1 (Python): {code} /sdk-version/project.py [name] [id] [project-parent-dir] [iphone] [android] [mobileweb] [android.sdk] Environment: DEVELOPER_DIR=[ios.tools] {code} V2 (Node.js): {code} titanium create --platforms=[iphone,ipad,ios,android,blackberry,mobileweb,etc.] [--type=[app]] [--id=string] [--sdk=sdk-version] [--verbose|-v [0-5]] [--template=name] [--[no-]cloud] [--dir=dir] name {code}
| 8 |
509 |
TISTUD-1881
|
07/09/2012 18:21:24
|
Add CLI command support for adding a new platform to an existing project
|
Add an extension for the CLI command that updates the project with new deploy targets. V1 (Python): {code} sdk-version/project.py [name] [id] [project.dir] [platform] -u {code} As it looks like, V2 does not require the *-u* command, and it's suppose to auto-detect the targets in the tiapp.xml, and build the required resources.
| 5 |
510 |
TISTUD-1882
|
07/09/2012 18:22:05
|
iOS: Allow keychain selection
|
Studio needs to be able to support manually selecting a keychain to choose a developer identity from (the list of such keychains is retrieved by {{security list-keychains}}. A keychain is provided to iOS' builder.py by providing it as argv[9] on the command line, after the deploytype. This value should be a full path pointing to the keychain. This ticket is the Studio end of TIMOB-9505.
| 8 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.