(TTYConsoleProcess.java:33) com.aptana.console.process.ConsoleProcessFactory.newProcess(ConsoleProcessFactory.java:32) org.eclipse.debug.core.DebugPlugin.newProcess(DebugPlugin.java:750) com.aptana.git.internal.core.launching.GitLaunchDelegate.launch(GitLaunchDelegate.java:66) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696) com.aptana.git.ui.internal.Launcher.launch(Launcher.java:59) com.aptana.git.ui.internal.actions.AbstractSimpleGitCommandHandler$1.run(AbstractSimpleGitCommandHandler.java:81) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code},8,train
TISTUD-1139,Should check and load the existing .project file before setting our required natures/builders when creating or importing a project we support,"Currently in our project creation or import wizards, we always create a new project description using IWorkspace.newProjectDescription() and then set nature ids and builders on it, but there is a possibility that the directory we're creating the project in or importing from already has a .project file. The correct way would be: 1. Check if a .project file exists in the specified directory; 2. Load project description from the .project file using IWorkspace.loadProjectDescription(); 3. Check if the project description already contains the natures and builders that we need and only add the missing ones; 4. If the project description isn't modified because it already includes the natures and builders we need, there will not be a need to call IProject.setDescription(); otherwise, call the method to update the .project file. We should be able to capture most of the steps in an utility method. ",13,train
TISTUD-1152,Add XSD-based Validation for tiapp.xml and timodule.xml editors,"Once we have a XSD for tiapp.xml, we need to validate against it. Doing so requires: * XSD * build participant to wrap calling the XSD ",8,train
TISTUD-1156,Project creation needs to check for app id segments that start with a number,"Android requires that all namespaces in a package not start with a number, but studio only checks the first namespace currently. Example invalid package name: com.test.123",5,train
TISTUD-1158,Multiple instances of the same process showing up in the console view,"# Clone the Kitchen Sink sample into your workspace # Clear all terminated launches in the Studio console # Run the Kitchen Sink sample in the Android emulator Note the duplication of launch processes, in particular, FastDev and the Android Emulator Process",13,train
TISTUD-1162,Research support ScriptDoc'ing of CommonJS Modules,"Research what changes will be needed in the JS inferencing, indexing, and content assist to add support for CommonJS modules to JS content assist",13,train
TISTUD-1163,Make IOS Package/Run on Device launch configuration public,"Refactor the existing wizard page contents so they can be re-used in the Launch configuration tabs. Expose the Launch configurations so they are public. Launch the ""full"" wizard if the launch configuration is initiated for the first time",20,train
TISTUD-1164,Make Android Package launch configuration visible to users,"Refactor the Android wizard page contents so it can be reused in the Launch configuration tab. Add a launch configuration for ""Install on Android Device"", which allows users to specify a android sdk",20,train
TISTUD-1165,Add MobileWeb Distribute operation as a Launch configuration,Refactor the wizard page contents so it can be re-used in a new Mobile Web Launch configuration,20,train
TISTUD-1167,Investigate ability to auto-scroll lock the console,,8,train
TISTUD-1168,Add Common Interface for consolidating UI errors and notifying listeners when status changes,,5,train
TISTUD-1169,Write a document on Ruble localization,"We now allow Rubles to be localized. Add a document to the Wiki covering the following topics (might be two, depending on the amount of content): * How the architecture works * How to externalize strings * How to contribute a new localization The document should have a few short examples to illustrate the concepts.",3,train
TISTUD-1171,Upgrade Run/Debug/Deploy icons,"We have a a few icons (as detailed in the attached document) that need upgrading as they are not in keeping with they rest of the Studio UI. In general, they should be a bit more three-dimensional and colorful. * Run icon * Debug Icon * Distribute/Deploy icon",5,train
TISTUD-1175,JavaScript externalizations are not evident in commands menu,"Please see capture at http://www.screencast.com/t/ZGzGqfaZfq0w. The string externalizations in the JavaScript ruble are not evident in the Commands menu. Furthermore, the list of keys in the en.yml do not match the drop down menu list. Steps to Replicate : 1) Open Titanium Studio 2) Clone the JavaScript ruble and select the development branch 3) Edit the en.yml file, save and cycle Studio Actual Results : The cache.en_US.yml file contains the edited values, however the JavaScript drop down menu has not changed. Expected Results : The commands menu should contain the new values. ",8,train
TISTUD-1179,Titanium Studio: titanium.py create: iphone project imported into studio does not include ipad as a selected target,"When an iphone project is created using 'titanium.py create', and imported into studio, ipad is not selected as a deployment target. This is relevant because projects imported into studio after being created by 'titanium.py create' do not initially contain tiapp.xml deployment target tags. The tags are created on import based on the presence of a respective platform folder (i.e., NewProject/iphone). Because iPad and iPhone use the same folder, they should both be selected as targets when imported to studio for the first time. Steps to Reproduce: 1. Generate a new iphone project using titanium.py create, such as: {code:title=} // dhydeMBPLion:~ dhyde$ /Users/dhyde/Library/Application\ Support/Titanium/mobilesdk/osx/1.8.1/titanium.py create --platform=iphone --type=project --dir=/Users/dhyde/Downloads --name=NewProject --id=com.appcelerator.project // {code} 2. Import the project into studio. 3. Open tiapp.xml and observe the deployment targets. Expected Result: iPhone and iPad should be selected as targets. Actual Result: Only iPhone is selected.",8,train
TISTUD-1180,MobileWeb : Selecting to clean a mobile web project does not remove the contents of the build folder,Steps to reproduce: 1. Create a default Titanium project and be sure to have mobile web selected as a target 2. Run the project as a preview in the browser 3. In Ti Studio select Project > Clean... Actual result: The contents of the build folder persist Expected result: The contents of the build folder are removed,5,train
TISTUD-1182,Create ACS Overview Page,"When a user wishes to learn more about Appcelerator Cloud Services from inside Studio, they are directed to this page here: https://wiki.appcelerator.org/display/tis/Appcelerator+Cloud+Services It needs to be filled with appropriate content. Some of that will be instructions on how to use the functionality, and some of it how to enable it inside Studio. I would imagine this top-level page could be a landing area, and specific sub-pages could be created as necessary.",8,train
TISTUD-1183,"Add ""release notes"" overview to Titanium SDK update dialogs","As in Studio 1.5, we previously prompted for user updates with a custom dialog box containing a browser pointing to a remote URL containing the latest set of release notes, similar to this: http://developer.appcelerator.com/apidoc/mobile/1.8.1/changelog.html, but formatted differently. I've attached a screenshot of how 1Password does it, which seems fine. Ideally, this dialog would _follow_ clicking on the yellow toast (though note the case where we had both a SDK and a Studio simultaneous update--we should handle that gracefully) The SDK and Studio dialogs will be identical, save the URL in the middle. However, we only do the SDK update dialog right now, as we completely control that process.",20,train
TISTUD-1184,"MobileWeb : Remove the ""Beta"" tag from mobile web for Ti Studio 2.0 release","As per Ingo, this ticket is for ensuring the removal of the beta tag in Ti Studio 2.0 There are two main places this needs to occur: 1. In tiapp.xml overview view 2. In the new project wizard",2,train
TISTUD-1185,Only check ACS checkbox if cloud services will actually be added,"In the attached image, I am not using an ACS-compatible SDK version, so the control is greyed out. However, the checkbox is still checked, making me think that it _will_ use cloud services, even though I can't change that option. Instead, in this case, the checkbox should be unchecked.",3,train
TISTUD-1186,"Add Label for ""More Info"" to ACS cloud area","From the demo, Jo ann had asked for the Info (?) link to be brought back even after a user has selected to enable cloud services.",5,train
TISTUD-1187,Move SDK check for cloud services back to 2.0,We moved the SDK check to 1.9 for demo purposes. Revert this back to 2.0 by Titanium Studio GA,1,train
TISTUD-1188,Dashboard : After logging into Ti Studio for the first time an error is presented and dashboard content fails to load until one refreshes the page,"Steps to reproduce: 1. Make sure you are not currently logged in to Ti Studio 2. Login to Ti Studio and wait for the dashboard pane to appear Expected result: The dashboard page loads without error Actual result: An error dialog is presented *see attached screenshots* and dashboard content doesn't load *Note a workaround is to just reload/refresh the page, however if one closes the dashboard the same issue persists*",8,train
TISTUD-1193,"""window"" hover has description twice","# Open a new .JS document # Type ""window"" (no quotes) # Hover over the item. Note it says ""Reference to the current Window. Reference to the current Window.""",5,train
TISTUD-1194,Type names missing from JavaScript hover,"# Create a new Titanium Mobile project # Open up app.js # Hover over a call to ""createWindow"" # Note the incomplete text: ""Create and return an instance of ."" Looking at the JSCA file, the type is denoted by <>: ""description"": ""(Optional) A dictionary object with properties as defined in .
"" Ideally, we pre-process those tags so that we might create a link to the remote type that users can click on. Alternately, we could have the JSCA file generated with a proper enclosing tag (but links might be very difficult)",8,train
TISTUD-1196,Add support for new Xcode 4.3 install location,"It appears Xcode 4.3 has changed the location of developer tools. In particularly, it's packaged as a single application, with the platforms and command-line tools installed underneath. Homebrew has a function that finds the proper path prefix: https://github.com/mxcl/homebrew/blob/master/Library/Homebrew/utils.rb Note...xcode-select no longer seems to be installed by default, so note that we have to have a fallback here * Check /usr/bin/xcode-select -print-path to see if it exists and is an absolute path. if so, use that * Else check if /Developer exists. If so, use that. * Else check if /Applications/Xcode.app/Contents/Developer exists. If so, use that. * Else ask spotlight where Xcode is (mdfind ""kMDItemDisplayName==Xcode&&kMDItemKind==Application). if that succeeds, append /Contents/Developer to that location",5,train
TISTUD-1198,Merge multiple update dialogs into a single dialog,"If there are multiple product updates (i.e. Studio and a SDK), we should pop up a single yellow toast, and a ""release notes"" dialog that allows you to switch between the currently active product release notes. Suggestion is we do something similar to apple...we have a set of checkboxes at the top for all products being updated, and then clicking on a product shows the release notes below",13,train
TISTUD-1199,Use pre-configured web servers to launch Mobile Web preview,"The Mobile Web ""browser preview"" launch configuration uses some separate settings for determining which browser to launch. Instead, we should have a drop down respecting the current browser settings in preferences: * Have a radio button for ""Global settings"" or ""Specific choose:"". * If user selects to specifically choose a different option than the global settings, have a drop down with the following options: ** Internal browser ** System browser ** Browser 1 ** Browser 2 * Have a link to open the preference page for users to manage the settings. If any launch configuration fails because a browser setting has been removed, fall back to an external browser using the system default.",13,train
TISTUD-1200,Exclude derived resources from validation,"# Create a new Mobile Web project # Run a browser preview # Note the litany of errors in /build/mobileweb. All of those are derived resources, and as such, should not show errors.",5,train
TISTUD-1204,Create test plan for tiapp.xml module additions,The new additions to the tiapp.xml need formal testing. We need a test plan.,13,train
TISTUD-1217,"Use ""TestFlight"" logo on relevant dialogs and wizards",Add the TestFlight logo to at least the following screens: # Register existing # Publish wizard,8,train
TISTUD-1218,"Add a ""TestFlight"" description to Register Existing and Publish screens","At the top of the ""Register Existing"" and right below the ""Publish"" screen dropdown, add the following text: ""TestFlight allows developers to publish beta builds of applications to a group of users organized into a team."" This might need to be contributed as part of an extension point or interface.",2,train
TISTUD-1219,"Minor tweaks of ""Publish"" screen and menu","*Menu* # The menu item seems to be writing out the name improperly (see image) *Publish Screen* # Rename the wizard to ""Publish _AppName_ to _TeamAlias_"" # The Manage... button needs to go to the Studio TestFlight preferences # Don't show the error message if there are no registered teams on dialog open. Instead, add a description of ""Choose the platform to which you wish to publish, and the publication target"" # Add a label below the platform choice with ""Platform choice is determined by the platforms this provider supports and the deployment targets for this project."" # Add a label below the dropdown as shown in TISTUD-1218. # Disable the dropdown until is has something to select # If choosing ""Publish..."", auto-select the first item in the list if there is one",8,train
TISTUD-1221,OpenShift: surface the root cause to the error dialog when creating an application failed,"Currently, when creating an OpenShift application failed, the project creation wizard will show an error dialog as attached, but it doesn't contain the actual root cause that made the creation fail. User would have to go to Help > Titanium Studio > View Log File... to see the full response. We should change the behavior to surface the cause in the details section of the error dialog.",5,train
TISTUD-1222,Parameter content assist showing HTML tags,"# Create a new Titanium Mobile project # Open the app.js file, if it is not open already # Type the following on an empty line in that file: Ti.UI.createWindow( # If you do not get context information after typing the open parenthesis, type ctrl-shift-space h3. Expected behavior: No tags should appear in the parameter description and types indicated via < and > should appear in the text with the brackets stripped. h3. Actual behavior: The tag appears in the description.",5,train
TISTUD-1223,OpenShift: creating an OpenShift PHP project failed,"Followed the steps at https://wiki.appcelerator.org/display/tis/OpenShift+Deployment to create an OpenShift PHP project, and when the wizard finishes, an error is generated as shown in the attached screenshot. Then when checking Help > Titanium Studio > Run Diagnostic Log..., I do see the new OpenShift app, so it looks like it's a problem with cloning the repo.",5,train
TISTUD-1224,Add ACS module XML to tiapp.xml when cloud-enabling a project,"Both when creating a new project with cloud enablement, and upgrading an existing one, we need to add the ID for the cloud module into the tiapp.xml The module id is ""ti.cloud""",5,train
TISTUD-1226,Create test plan for TestFlight integration,A test plan needs to be created for TestFlight integration.,13,train
TISTUD-1227,Incorrect JSCA file selected for content assist when creating new Titanium Mobile project,"1. Create new Titanium Mobile Project 2. Choose an SDK, but _not_ the latest one (i.e. choose 1.8.1 when 1.9 is installed) 3. See 1.8.1 selected in the tiapp.xml, but right-click on the project > build path, and notice the latest JSCA file (i.e. 1.9) is selected",8,train
TISTUD-1229,"""Mobile Web"" action icons should use HTML5 icon, not the ""server"" one","The icons in ""preview"" and ""package"" should be the HTML5 icon used for content assist, not the server icon",3,train
TISTUD-1230,Update project-specific run/debug/package menus with favorites and recent history,"Similar to the global run/debug menus, add run/debug/package history to bottom of App Explorer and Project Explorer menus (perhaps show favorites, then separator, then last five, per project) * Run ** Emulator/Simulator options ** -------------------------- ** Device options ** -------------------------- ** Favorite configuration 1 ** -------------------------- ** Recent configuration 1 ** Recent configuration 2",20,train
TISTUD-1231,Add MobileWeb platform to SDK dashboard configuration screen,"# Add a new platform to the dashboard (add an icon with and without a questionmark) # Mobile web will show a question mark on first launch, or first time it appears # Clicking on the question mark will show the information in the following panels (based on # There will be a link which opens Preferences > General > Web Browser, and another link which opens https://wiki.appcelerator.org/display/tis/Mobile+Web+Support {panel} Mobile Web previewing works best in modern HTML 5-compliant browsers. We recommend you configure your Studio browsers before working on mobile web projects: 1) Click [here] to open browser preferences. 2) Add one or more entries for . Alternately, if your default system browser meets one these requirements, you can leave the preference alone. 3) Save and close the preference. {panel} Text to replace for **: * OS X: Safari 5+, Chrome 10+, or Firefox 10+ * Windows: Chrome 10+, Firefox 10+, or IE 10 * Linux: Chrome 10+ or Firefox 10+ ",20,train
TISTUD-1236,Show text hovers on variable/identifiers in declaration statements,When hovering over the name of the identifier/variable in an assignment/declaration we don't get hovers as we do when hovering over the exact same variable in a reference.,3,train
TISTUD-1237,Text hovers not showing on rhs of variable assignments,"If we hover over the rhs of an assignment where it is a function call, we don't get hovers for the method we're invoking.",5,train
TISTUD-1257,Kitchen Sink : Importing Kitchen Sink from the samples area sometimes produces an error and doesn't allow the sample to be imported,"Steps to reproduce: 1. Launch Studio 2. Ensure you do not have Kitchen Sink as a project in Studio or your workspace 3. Import Kitchen Sink from the Studio samples Actual result: An error dialog is displayed and Kitchen Sink is not imported Expected result: Kitchen Sink is imported without error *Note since this error does not occur every time I was unable to capture the error dialog, but I attached the log*",8,train
TISTUD-1259,Studio installer for Windows: Install screen has rendering and refresh issues during install,"Description: While testing the installer for Windows, we noted that the border around the detail field, and the border around the progress bar were not initially drawn. When another window is placed over the installer window and then closed, the borders appear. Please see screenshots for more information Steps to reproduce: 1) If studio is installed, uninstall it 2) Download the installer from my.appcelerator.com 3) Run the installer and examine the window 4) Open the detail view 5) PLace a window over the installer window and then close it Results: The borders around the detail field and the progress bar are not drawn, placing a window over the installer window then closing it causes them to appear. Expected: No rendering issues on the installation window. Note: We also saw text overwriting itself in the detail field on one out of three attempts, but have been unable to reproduce it thus far.Image ""badRefresh"" shows this behavior.",5,train
TISTUD-1260,Titanium Studio: MobileWeb: Preferences need MobileWeb default run configuration menu,"The Titanium preferences menu needs a default run configurations sub-menu for MobileWeb. Android has a default run configuration menu. Parity issue and basic functionality. The MobileWeb sub-menu (default browser, etc.) would be in the preferences menu below the Android default configuration settings. Screenshots attached. ",8,train
TISTUD-1261,Snippets view color scheme on Windows is not consistent with other views,Currently the color scheme for the snippets view on Windows (tested on XP specifically) is not consistent with the other Studio views. See attached screenshots Background colors need updating Disabled tag buttons are not painted properly Hover over the tag buttons has an outline Snippet popup toolbar bg color has incorrect border colors,13,train
TISTUD-1266,TiStudio: Projects - Cannot import a project when project is copied from a GitHub repository folder,Steps to reproduce: 1. Import a project from a GitHub repository folder 2. Delete project from Studio; do not select *Delete project contents on disk* 3. Copy project from GitHub repository folder into workspace folder 4. Import project from workspace Actual: Get a *Invalid project description* error. See attachment. Expected: Should be able to import copied projects Note: No logs were generated.,8,train
TISTUD-1268,Titanium Studio: Content Assist: assist menu intermittently fails to close at all,"In addition to being persistent as a stand-alone window when focused (related issue), the content assist menu intermittently fails to close at all until studio closes. Pressing escape, clicking away, etc. do not close the content assist menu. Steps to Reproduce: 1. Create a default project. 2. Open content assist within the app.js editor. 3. Click the content assist menu to give it focus. 4. Close the content assist menu (e.g., 'escape', click away, etc.). Expected Result: Content Assist menu should close. Actual Result: Content Assist menu intermittently does not close at all until studio is closed.",8,train
TISTUD-1269,Titanium Studio: Content Assist: content assist results in no proposals if code file contains syntax error warnings,"If a code file contains syntax error warnings, and content assist is called, no proposals will be generated. This interferes with development. Steps to Reproduce: 1. Create a new project. 2. Insert the following code: {code:title=app.js} switch() { case Ti. } {code} 3. Move the cursor to the right of ""Ti."". 4. Active content assist (cntrl + space). Expected Result: Content Assist should be invoked with proposals. Actual Result: No proposals.",8,train
TISTUD-1271,iOS: Xcode 4.3 - Dashboard link to install Xcode fails,"Description: While testing the Xcode 4.3 capabilities, I started with a clean system and installed studio. On the dashboard an option is given to install Xcode. When clicking on this link, the Appstore opens, but reports a failure. See attached image for details. Steps to reproduce: 1) Install Studio 1.0.9 2) Launch studio and on the dashboard, select ""let's get started"" 3) Select the iOS SDK button and the install link Result: The Mac app store opens but the request fails Expected: The Mac app store opens to a supported Xcode version page",8,train
TISTUD-1272,"iOS: Xcode 4.3 - Dashboard tooltip for iOS SDK, showing supported Xcode versions, needs to be updated","Description: While testing Xcode 4.3, and prior to setting the Xcode-select to point to the correct location, the iOS SDK icon in the dashboard shows setup is needed. When hovering over the icon, a tooltip appears. WHile mostly accurate, some details need updating. Specifically, Xcode 3.2.6 is not supported but is mentioned on the tooltip. Another is the mention of Xcode 4.0+. Currently we do not fully support 4.3, so based on the schedule for this, it can remain as-is or must be limited to pre-4.3 versions. Steps to reproduce: 1) Install and launch studio 2) Open the dashboard and navigate to the sdk setup page 3) Hover over the iOS SDK button Result: The tooltip comes up and has some inconsistencies Expected: The tooltip accurately describes the supported Xcode versions required ",8,train
TISTUD-1273,TiStudio: Console - Console view does not refresh properly when installing or running app on emulator/simulator,Steps to reproduce: 1. Create the default TiMob project 2. Install project to device or run project in simulator/emulator Actual: Console view does not refresh properly. See attachments Expected: Console view should refresh properly.,5,train
TISTUD-1275,JS documentation hover displays a huge header,"# Import the Kitchen Sink project into the workspace (set the Titanium Mobile and the Web Natures in case they are missing after the import). # Open android_menues.js, for example, and hover over the 'tableview' keyword. A documentation hover appears. However, a huge file locations header appears on the top. ",5,train
TISTUD-1276,Studio: Configuration utility maximum for support iOS SDK must be updated,"Description: Currently the configuration utility performs a check of iOS platforms to see if 4.2-5.1 is available. From what I've been told this is non-exclusive, meaning 4.2-5.0 would be shown to satisfy this check, but with 5.1 coming out, the upper bound needs to be corrected. 1) Evaluate the logic here: http://preview.appcelerator.com/dashboard/sdk_info.json 2) Note the iOS platform check as including >= 4.2 and < 5.1 Result: Only iOS SDKs 4.2-5.0.1 would meet with success Expected: Logic evaluates based on target supported iOS SDKs (i.e. [4.2, 5.2))",5,train
TISTUD-1277,The error from generating mobile web app should be surfaced to the user,"When I created a Titanium mobile web project and ran ""Mobile Web Preview in Browser"", the process failed, and I see an error status dialog saying ""Unable to generate Mobile Web App"", but there is no additional details on what caused the issue; checking the log shows nothing either. When I step through to debug, it shows that the script returns the following: {code} Status ERROR: com.appcelerator.titanium.core code=0 ERROR: Unabled to import module ""Image"" Run `sudo easy_install pil` to install the 'Image' module or download from http://www.pythonware.com/products/pil/ null {code} We should surface the cause in the dialog so that user could diagnose and correct the problem. ",5,train
TISTUD-1278,Studio: Studio requires restart if open during Xcode install even though configuration utility reports correctly configured for iOS,"Description: While testing Xcode 4.3, I had an existing Studio install that could no longer detect the iOS SDK. The workaround for this was when I changed workspace to a new empty workspace. This fixed the problem. Please note, I did check the Xcode-select -print-path which showed the correct location. I tried it again anyhow. It was only when I quit Studio and relaunched, selecting a blank folder for my new workspace that the iOS SDK was recognized. Steps to reproduce: 1) Install Xcode 4.3 on a system with no Xcode install (delete 4.2 prior to 4.3 install) but with an existing Studio installation 2) Ensure that you have some projects that exist in the Studio workspace 3) Launch Studio and check the dashboard to ensure it reports your setup is incorrect (since Xcode 4.3 is not in the /Developer folder) 4) Use ""xcode-select -switch"" to set the location of your Xcode install to ""/Applications/Xcode.app/Contents/Developer"" this should fix your installation 5) Check that the Dashboard now reports iOS is configured correctly 6) Try to create a new project with iOS targets Result: iOS can't be selected, but Dashboard shows iOS SDK correctly configured You must restart Studio for the ability to create iOS projects Expected: Dashboard and Studio both able to verify configuration is correct without restart (or with appropriate messaging) ",8,train
TISTUD-1280,Studio: TiApp editor module section - Platform icons could use some improvement,"Description: The QE team like the new TiApp editor features. The icons however seem to have some room for improvement. There are two main areas for evaluation: 1) The iOS icons seem to generate confusion for two reasons: First, the Apple icon is cropped to the point that it is difficult to recognize it as an apple. Second, the three letters used to signify iPad and iPhone are difficult to decipher: ""iPa"" and ""iPh"". 2) While most OSes have the header in white, Linux is grey, making the Android icon difficult to make out as the contrast is too low. An additional concern may be the sourcing of the icons Steps to reproduce: 1) Install Studio 2.0 on any system (linux for Android icon contrast evaluation) 2) Create a new project 3) Edit the TiApp.xml 4) Note the Module section in the editor overview Result: Icons less than ideal Expected: Icons are beautiful",5,train
TISTUD-1281,Research what is causing errors to be generated in JS when semicolons are not used to end statements,We need to determine what is generating the parse errors in JS. Turning off the all validation and forcing a clean build does not remove the errors and associated markers,8,train
TISTUD-1282,Do not show JS parse errors when optional semicolons are excluded,"When we made the change to build participants, we lost the ability to turn on/off parse errors. We should treat those ""validators"" the same as other validators. This should be applied to HTML, CSS, and JS. However, the JS validator should not generate errors when optional semicolons are excluded. Beaver reports a syntax error before trying to recover from the error. We should add a case where errors are not added (or they are deleted) if we're able to fix the parse by adding the optional semicolon to the parse stream.",13,train
TISTUD-1283,OpenShift: should surface the root error when failed to deploy existing project to OpenShift,"We are surfacing the error in the status dialog for creating new OpenShift project, but not for deploying existing ones. ",5,train
TISTUD-1284,"Distribute - Google has announced that the Android Marketplace will be renamed as ""Google Play"", which may warrant an update to the language used in the distribute menu of Titanium Studio","Google changing their Android Marketplace to be named ""Google Play"" warrants a discussion about updating the language used in future versions of Titanium Studio to be inline with this change. This is a link to the official announcement from Google http://googleblog.blogspot.com/2012/03/introducing-google-play-all-your.html",3,train
TISTUD-1285,Titanium Studio: 2.0.0: Dashboard: Samples: samples do not populate from staged dashboard url,"Samples do not populate when beta dashboard is loaded from studio 2.0.0. Steps to Reproduce: 1. Edit TitaniumStudio.ini (2.0.0) file (OS X: TitaniumStudio > Show Package Contents). Add two lines: -Dtitanium.dashboardUrl=http://preview.appcelerator.com/dashboard/index.php -Dtitanium.sdkRequirementsUrl=http://preview.appcelerator.com/dashboard/sdk_info.json 2. Restart Studio 2.0.0, load dashboard, click 'Develop' tab. Expected Result: Samples should populate. Actual Result: Samples section is blank. Screenshot attached.",5,train
TISTUD-1286,"MobileWeb: ""File /index.html not found"" error when loading into browser","When I run ""Mobile Web Preview in Browser"" from TiStudio and the app opens in FireFox, I get a white screen that says: **File /index.html not found** and nothing else. If I then reload the page with the very same URL, everything works fine. But almost everytime I launch from the button with TiStudio, I get the above error. This is the case with all apps I attempt to build for mobile web. ",5,train
TISTUD-1287,Titanium Studio: Content Assist: no Titanium SDK proposals are generated,Content Assist fails to generate Titanium SDK proposals. Regression. Steps to Reproduce: 1. Open studio 2.0. 2. Edit app.js. Type 'Ti.'. Look at Content Assist suggestions (cntrl + space to force CA window). Expected Result: Titanium SDK proposals should appear. Actual Result: No proposals.,8,train
TISTUD-1292,Clarify wording on iOS configuration screen,"The current iOS dashboard configuration screen is a confusing regarding min/max versions of SDKs. So lets display which iOS versions are compatible with this and below that have a link that points to here : https://wiki.appcelerator.org/display/guides/Titanium+Compatibility+Matrix#TitaniumCompatibilityMatrix-iOSSDK%2FTargetiOSPlatform. Regarding the actual text, here is a proposal: An iOS SDK is missing. Titanium supports the following range of iOS versions: Min iOS version: ... Max iOS version: ... Algorithm to calculate this: if inclusive '[', leave the versions as is. if exclusive '(', subtract .1 from the last position, and add .X to the end, i.e. 5.2) => 5.1.X. 5.1.0) => 5.0.9.X (We can ignore the exclusive lower bound case at the moment: https://mail.osgi.org/pipermail/osgi-dev/2008-July/001330.html...It's unlikely we'll need it) Button ('install or update iOS SDK"") Note: If you intend to develop mobile applications using an earlier version of the Titanium Mobile SDK , please consult the Titanium Compatibility Matrix. (this is the link shown above)",8,train
TISTUD-1294,"App Id causing ""[ERROR] Error generating R.java from manifest""","Same issues as referenced in [TIDEV-115|https://jira.appcelerator.org/browse/TIDEV-115] If you specify an app id as simply a single word, as opposed to a reverse domain format, you get an error when building for android (but not ios): {code} [ERROR] Error generating R.java from manifest {code} It's a very cryptic error and really hard to track down. If this type of app id is illegal for Android, the user needs to be notified by Titanium Studio that this is the case. Also, in case a user manually changes the app id and runs into the above error, it would be a lot more useful if the error message actually indicated that the app id was the problem. It's near impossible to figure out that the app id is the issue from that error message alone.",3,train
TISTUD-1295,Convert wiki.appcelerator.org URLs inside Studio into redirects off studio.appcelerator.com,"There are approximately 22 links inside Studio that need to be redirectable, since the exact endpoint is not known at this time. Instead, let's create a PHP page off of studio.appcelerator.com to redirect to the current location, and then we can change it as necessary.",8,train
TISTUD-1296,Add an Android NDK path field in the Titanium Preferences,"Add a preference key, and a field editor, for the Andriod NDK path into the Android group at the Titanium preference page. ",8,train
TISTUD-1297,Titanium MobileWeb when previewed against an internal browser shows empty content,"[This one happens on Windows] Create a mobile-web project (with Titanium SDK 2.0). Right click to run the 'Titanium Mobile Web Previewer'. An internal browser is opened, but the page is blank. Right-clicking and viewing the source shows lot of code there, so we have the content, yet it's not rendering. Selecting the launch (via the Run configurations) and editing it to run on external browser works fine.",8,train
TISTUD-1299,"Extra space in ""Import Existing Titanium Project"" error message","This is very minor, but I noticed that the warning message in the Import Existing Titanium Project dialog appears to have an extra space (see attached).",1,train
TISTUD-1301,Update Studio Dashboard to adjust to packaging changes for 2.0 launch ,"The available packages in 2.0 will change names and pricing of those will be on a per-app basis. Hence a paid subscriber might have more than one package, so we can no longer display the user's plan level on the dashboard. Instead we should just display the following: * a link labeled ""My Apps"" pointing to the site where the user's can view his Apps * a link labeled ""My Account"" pointing to the user's account",5,train
TISTUD-1304,Add DEVELOPER_DIR to environment variables when launching iOS scripts,"Any time we interact with an iOS script, we need to set the DEVELOPER_DIR environment variable equal to the current Xcode location (i.e. what you would normally get from xcode-select -print-path)",8,train
TISTUD-1306,Add support for the @module sdoc tag,"Following JSDoc as a guide, we need to add support for an @module tag. The syntax would be: {code} /** * @module {dir1/dir2/myModuleName} */ {code} This will require us to: # Add support for @module and its parameters to the SDoc parser # Add a module element to the SDoc model # Possibly store a reference of the module name to the document defining it in the JS index",13,train
TISTUD-1307,Create sample documentation of an SDoc'ed CommonJS module,"Using the sample snippets in the Epic containing this ticket, we will need to create documentation that shows that code being scriptdoc'ed for use as a module. We need to update the wiki pages here: * https://wiki.appcelerator.org/display/guides2/ScriptDoc+%28SDOC%29+2.0+Specification * https://wiki.appcelerator.org/display/guides2/Documenting+Your+Code+Using+ScriptDoc * https://wiki.appcelerator.org/display/guides2/ScriptDoc+tag+quick+reference ",13,train
TISTUD-1308,Only show content assist from the current JS file and JS files it has required,"Our current JS CA implementation queries the index file for the entire project. This means that we show content assist for all JS files in a project when bringing up CA in a JS file. We now detect ""require"" invocations and store the required module name in the index. We also have the ability to filter index query results by a list of documents. Using these two items together, we should be able to filter JS CA by required files only. Note, that we may not want this as a default behavior for web projects. So, for the time being, we should implement this for the TiMobile nature only.",20,train
TISTUD-1309,Change Studio to reference new platform -clean option,"Once TIMOB-7652 is complete, we'll need to switch to using that mechanism over the current one. Note, this only will work on SDKs above 2.0.1+, so if the SDK is less than that version, we need to use the old system for now.",8,train
TISTUD-1310,Treat CommonJS modules specially when showing JS CA in a file that includes it,"CommonJS modules make use of a ""module"" object that has an ""exports"" property. Also, there is an ""exports"" global that can be used similarly to ""module.exports"". There are rules in how these two items influence one another as is covered in http://www.hacksparrow.com/node-js-exports-vs-module-exports.html. So, whenever we include CA from a ""require""d module, we need to grab properties from the ""module.exports/exports"" type instead of grabbing items from its global scope.",13,train
TISTUD-1312,TiStudio: Mobile Web - index.html file is not generated when packaging for Mobile Web,"Steps to reproduce: 1. Package default Titanium project for Mobile Web 2. Select ""Create a new project for the Mobile Web app"" 3. Open newly created Mobile Web project Actual: index.html does not appear in the packaged mobile web. See attachment for log. Expected: The packaged mobile web should contain the index.html in order to preview the app. Note: If ti.cloud module exists in the TiApp Editor, remove it from the project.",5,train
TISTUD-1313,Comments are removed when formatting JS code,"Format the following code: {code} function uploadImage() { if(Titanium.Platform.name == 'android') { req.send({ 'aToken' : Titanium.Locale.getString('app_token_only'), 'uToken' : Titanium.App.Properties.getString('uToken'), 'fileType' : '2'}) // Only Change, Added single quote for Android 'fileObject' : blob }); } else { req.send({ 'aToken' : Titanium.Locale.getString('app_token_only'), 'uToken' : Titanium.App.Properties.getString('uToken'), 'fileType' : 2}) // Only Change, No change needed for IPhone 'fileObject' : blob }); } } {code} Expected result: Code formats with all the comments included Actual results: The '// Only Change' comments are removed during the formatting process.",5,train
TISTUD-1314,"Titanium Studio: TiApp Editor: Build Properties: Titanium SDK: if no sdk's exist, sdk list not cleared","If all SDKs are removed from the SDK folder, they remain in the TiApp Editor SDK list. Note: They are later correctly removed when the tiapp.xml file is reloaded. The tiapp.xml SDK version remains as the last available version (expected). Steps to Reproduce: 1. Create a new project. 2. Remove all SDK's from the SDK folder (i.e., Application Support/Titanium/mobilesdk/osx/2.0.0.v20120312104735). Expected Result: TiApp Editor SDK list should be cleared and the tiapp.xml SDK version should be the last available version. Actual Result: The TiApp Editor SDK list is full, and any selected versions do not change the tiapp.xml (because they do not exist). However, the list is properly cleared on tiapp.xml reload.",3,train
TISTUD-1315,"Titanium Studio: TiApp Editor: Build Properties: Titanium SDK: if sdk field is set after being blank, tiapp.xml not updated","In the TiApp Editor, if another SDK is selected in the TiApp Editor SDK field when the field was previously blank (linked issue), the respective tiapp.xml is not updated, resulting in an invalid configuration. Steps to Reproduce: 1. Create new project. 2. Remove current SDK from SDK folder (i.e., Application Support/Titanium/mobilesdk/osx/2.0.0.v20120312104735). The TiApp Editor SDK field should be blank. 3. Select another available SDK from the TiApp Editor SDK list. 4. View the tiapp.xml. Expected Result: The SDK version in the tiapp.xml should reflect the version selected in the TiApp Editor SDK drop-down list. Actual Result: The SDK version in the tiapp.xml is whatever was last set, resulting in an invalid configuration. Note: The tiapp.xml SDK version is correctly updated if the tiapp.xml file is reloaded.",2,train
TISTUD-1316,"Titanium Studio: TiApp Editor: Build Properties: Titanium SDK: if current sdk removed from filesystem, tiapp not updated","When an SDK folder (i.e., Application Support/Titanium/mobilesdk/osx/2.0.0.v20120312104735) is removed from the filesystem (moved or deleted), the TiApp Editor SDK field for any open projects is set to nothing, and the tiapp.xml remains as the deleted SDK version. It is expected that the SDK field in the TiApp Editor would immediately be updated to the latest SDK, as well as the tiapp.xml. This expectation is reinforced by the fact that when the tiapp.xml file is re-opened in Studio, the TiApp Editor SDK field is set to the latest existing version of the SDK, and the tiapp.xml is updated to the latest SDK. Note: As a related consequence (linked issue), when another SDK is selected in the TiApp Editor SDK field (when the field was previously blank), the respective tiapp.xml is not updated, resulting in an invalid configuration. Note: As an edge case (linked issue), if all SDKs are removed from the SDK folder, they remain in the TiApp Editor SDK list, but they are later correctly removed when the tiapp.xml file is reloaded. The tiapp.xml SDK version remains as the last available version (expected). Steps to Reproduce: 1. Create a new project. 2. Move the selected SDK version folder from it's directory to another location. Expected Result: The TiApp Editor SDK should immediately update to the highest available SDK version, and the tiapp.xml should be updated. This would occur anyway if the tiapp.xml file were re-opened in Studio. Actual Result: The TiApp Editor SDK field is blank, the tiapp.xml SDK version remains as the one removed.",5,train
TISTUD-1318,Filter out CommonJS modules from the tiapp.xml editor screen,We have implemented ACS module as a CommonJS module and bundled it with the Mobile SDK. We are not officially supporting CommonJS modules (yet) and we have added this support to Mobile SDK just for ACS module. Please filter out CommonJS modules from Studio UI and other tools.,8,train
TISTUD-1320,Tabbed Template is giving a runtime error on Android ,Steps To Reproduce: 1. Create a new TiMob project with the Tabbed Template 2. Run on Device/Emulator 3. Click on Open New Window Actual: Runtime Error (See attachment) Expected: To open a new window,3,train
TISTUD-1322,Confim links as part of Studio 2.0 release.,"Before release, we need to confirm the links listed on TISTUD-1295 are still correct.",5,train
TISTUD-1323,Studio: Collapsing Javascript outline node crashes Ti Studio.,"While testing APSTUD-4178, I had Studio crash while trying to collapse a node on a Javascript outline. Nothing is reported to the log file but Lion generates the attached crash report. Steps to reproduce: 1. Open TIStudio. 2. Open the js.js file. 3. Open the html.html file. 4. Use the outline windows to expand all on the Javascript file. 5. Close the iadt function in the Javascript file. 6. Use the outline window to expand all on the HTML file. 7. Close the iadt function in the HTML file. Actual Results: Collapsing one of the two functions will cause the program to hang and then crash. Expected Results: Both outlines should collapse the function and the program should respond normally. ",13,train
TISTUD-1325,Update dashboard to remove warning about Xcode 4.3,"Currently, we warn users about _not_ installing Xcode 4.3. Once that support is in, we'll need to remove that warning: {code} Note:
Xcode 4.3 (the most recent version which is downloadable in the Mac App Store) is not yet supported by Titanium Studio or the Mobile SDK.
Lion and Snow Leopard:
- Visit developer.apple.com/downloads
- Search for Xcode 4.2
- Download and install Xcode 4.2 for your OS version:
Once finished, return here.
{code} new text: {code} Lion:
- Click the ""Install"" button, or open the Mac App Store application
- Search for Xcode
- Download and install Xcode 4.2
Snow Leopard:
- Visit developer.apple.com/downloads (paid account required)
- Search for Xcode 4.2
- Download and install Xcode 4.2
Once finished, return here.
{code} We also need to update the sdk_info links for the Xcode download to http://itunes.apple.com/us/app/xcode/id497799835?ls=1&mt=12",5,train
TISTUD-1327,Add Titanium platform support info in CA for Titanium namespaces,"I invoked CA on ""Titanium."" using Titanium 1.8.2. The results for what show up as supported platforms is pretty spotty. Most just show none. A few functions show Android, ipad and iphone. The ""sub-classes' (i.e. API, Buffer) show none. Android doesn't show as only available on Android.",13,train
TISTUD-1329,Auto-detect and set up CA platform filters for Titanium projects,We should set up the CA platform list on Titanium mobile projects based on the deployment targets specified in the tiapp.xml itself.,8,train
TISTUD-1330,"Default the CA user-agent list to Android, iPhone, iPad and Mobileweb for Titanium Mobile nature","By default, the Titanium platforms are not set up as the default to show for Titanium Mobile project nature projects.",8,train
TISTUD-1332,MobileWeb launches are never removed from the Debug view,"Launch a MobileWeb preview in a browser. A launch is added to the Debug view, and it's there to stay. The only way to remove it is to click it and hit 'delete'.",5,train
TISTUD-1333,Seeing error on unrecognized type name with JSMetadata,"When running Titanium Studio 2.0.0.201203121914, I saw many entries of the following in the log: {code} !ENTRY com.aptana.editor.js 4 0 2012-03-13 16:57:37.690 !MESSAGE (Build 3.0.3.1331566826) [ERROR] Unrecognized type name in JSCAHandler#createType: JSMetadata {code} ",2,train
TISTUD-1334,An empty version in the modules section of the tiapp.xml prevents the TiApp editor from being opened ,1. Have a module directive in the tiapp.xml without a 'version=...' attribute. 2. Open the TiApp editor Result: A null pointer exception prevents it from getting opened. ,3,train
TISTUD-1335,Content Assist: JavaScript class objects generate non-static proposals,"JavaScript objects such as Array, Boolean, Date, Number, and RegExp generate Content Assist proposals that are not static methods. The methods are generated correctly in Eclipse. Screenshot attached. For instance, String.charCodeAt is proposed when it is an instance method, and will not work on the String object. Steps to Reproduce: 1. Create a new project. 2. In app.js, type a JavaScript class object followed by a dot, activate Content Assist. Expected Result: Static methods and/or methods that work should be proposed. Actual Result: Instance methods are proposed (which will not work), along with many other generic properties which are questionable.",8,train
TISTUD-1336,Content Assist: String.fromCharCode: no proposal generated,"Using Content Assist, 'String.' does not propose the method 'fromCharCode' (though it does work when run). However, the method is proposed in Eclipse. The method is also erroneously proposed in string instances (and the method does not work, as expected) (linked issue). Steps to Reproduce: 1. Create a new project. 2. In app.js, type String. and activate Content Assist. Expected Result: String.fromCharCode should be proposed. Actual Result: Method is not proposed.",5,train
TISTUD-1337,Content Assist: string instance.fromCharCode: static proposal erroneously generated,"When a String instance invokes Content Assist, 'fromCharCode' is proposed when it is a static method and will not work on an instance. Steps to Reproduce: 1. Create a new project. 2. Type: {code:title=app.js} // var x = ""xxx"".; // {code} 3. Place the cursor after the dot and activate Content Assist. Expected Result: ""xxx"".fromCharCode should not be proposed. Actual Result: fromCharCode is proposed, though it will not work, and is a static String method.",5,train
TISTUD-1338,Content Assist: string instance.charCodeAt: proposal missing,"String instance method: charCodeAt not proposed in Content Assist, though it works at runtime. Steps to Reproduce: 1. Create a new project, type: {code:title=app.js} // var x = ""xxx"".; // {code} 2. Activate Content Assist after the string instance to generate proposals for ""xxx"".-> Expected Result: charCodeAt should be proposed. Actual Result: charCodeAt not proposed, but does run correctly.",5,train
TISTUD-1339,Tititanium Studio: Mobile Web module support,"Titantium Studio needs to support creating and compiling Mobile Web modules. Creating a new Mobile Web module is identical to iphone and android, except you specify --platform=mobileweb and you don't need to specific the androidsdk. {code} python /Library/Application\ Support/Titanium/mobilesdk/osx/2.0.0/titanium.py create --platform=mobileweb --type=module --dir=. --name=mymodule --id=mymodule {code} Inside the generated module directory is the {{build.py}}. Simply run that and it'll generate a {{mymodule-mobileweb-0.1.zip}} file. During compilation, it will create a {{build}} directory. This directory can be nuked when doing a clean. Mobile Web module configuration is set in the timodule.xml (similar to Android). We are still nailing down the various settings that will be available in the timodule.xml. ",8,train
TISTUD-1341,"Studio: SDK Update release note view has no ""back"" capability ","Description: While testing the new feature that provides users with a view of the release notes, I clicked a link which opened JIRA in the same view. There was no option to return to the release notes, so I was forced to close the view. Steps to reproduce: 1) Install the latest Studio 2.0 version 2) Remove SDK version 1.8.2 if you have it installed (and any later versions) from your Titanium folder 3) Launch Studio and click the yellow ""updates available"" box or use the help>Check for titanium SDK updates option 4) When the ""Titanium SDK Upgrade Available"" window appears, click one of the JIRA ticket links Result: JIRA displayed, with no way to return to release notes Expected: Link opens in new window or method of navigation available",3,train
TISTUD-1342,"Studio: SDK Update release note view link for ""Titanium mobile reference documentation for 1.8.2"" fails with error","Description: While testing the new feature that provides users with a view of the release notes, I clicked the link for ""Titanium mobile reference documentation for 1.8.2"". This failed with an error. Steps to reproduce: 1) Install the latest Studio 2.0 version 2) Remove SDK version 1.8.2 if you have it installed (and any later versions) from your Titanium folder 3) Launch Studio and click the yellow ""updates available"" box or use the help>Check for titanium SDK updates option 4) When the ""Titanium SDK Upgrade Available"" window appears, click the ""Titanium mobile reference documentation for 1.8.2"" link Result: Failure with an error, see attached image Expected: Link opens",3,train
TISTUD-1343,Studio: SDK Update release note view will not come up if dismissed and then help>Check for titanium sdk updates option is used,"Description: While testing the new feature that provides users with a view of the release notes, I clicked a link which opened JIRA in the same view. There was no option to return to the release notes, so I was forced to close the view. Steps to reproduce: 1) Install the latest Studio 2.0 version 2) Remove SDK version 1.8.2 if you have it installed (and any later versions) from your Titanium folder 3) Launch Studio and click the yellow ""updates available"" box 4) When the ""Titanium SDK Upgrade Available"" window appears, select ""remind me later"" 5) Use the help>Check for titanium SDK updates option Result: SDK install begin with no preview of the release notes Expected: Release notes view always presented when installing SDK update",5,train
TISTUD-1345,Remove 2.1 as Android SDKs requirement for Android development,"Description: On one of our newer installations of Studio, the Android SDK is properly configured to support 1.8.0+ SDKs. The Dashboard configuration page shows an incorrectly configured Android SDK. In comparing the listed text to the actual configuration: {code} Android configuration details. One or more pieces are missing from the Android SDK. It may be that the Android SDK is already installed and Titanium Studio cannot locate the directory, or it may be that some additional components need to be installed. Items required: An Android SDK is missing. Titanium requires Android platforms 2.1.* and 2.2.* Add-Ons Google APIs 7, Google APIs 8 {code} We were missing the 2.1 SDK. The result is that imported samples could be run as expected in the emulator, but no project could have the deployment target set during creation of afterward. The tooltip text lists similar requirements, see attached image. Steps to reproduce: 1) Configure a system with ANY supported SDK 1.8.0+ Android SDK (Android 2.2 - 4.0) 2) Launch Studio, add the Android SDK path in the studio preferences 3) On the dashboard, check the configuration utility's report on the usability of the Android SDK Result: If you don't have both 2.1 and 2.2 SDKs, the configuration is determined to be incorrect Expected: Only 2.2 is installed (and required) by default",5,train
TISTUD-1346,Studio: Edit this bundle from Commands/Titanium Mobile gives an Error,"Edit this bundle from Commands/Titanium Mobile gives an Error ""Grabbing bundle Titanium Mobile..has encountered a problem Git Clone failed. screen shot is attached log file is attached Steps to reproduce : 1: click on Commands 2: Click on Titanium Mobile 3: Click on Edit the bundle Actual result : Error Message Grabbing bundle Titanium Mobile ..has encountered a problem Expected results : should be able to Edit the bundle ",3,train
TISTUD-1347,Titanium Studio: Clean fails when iPhone Simulator is still running,When doing a clean on a mac when the iPhone simulator is running causes this: {code} !ENTRY org.eclipse.core.resources 4 566 2012-03-14 17:52:23.632 !MESSAGE Errors occurred during the build. !SUBENTRY 1 com.appcelerator.titanium.core 4 75 2012-03-14 17:52:23.632 !MESSAGE Errors running builder 'Titanium Builder' on project 'timob-5698-maps'. !STACK 1 org.eclipse.core.internal.resources.ResourceException: A resource already exists on disk '/Volumes/ultima/projects/titanium/timob-5698-maps/build'. org.eclipse.core.internal.resources.Folder.assertCreateRequirements(Folder.java:47) org.eclipse.core.internal.resources.Folder.create(Folder.java:95) org.eclipse.core.internal.resources.Folder.create(Folder.java:125) com.appcelerator.titanium.core.TitaniumProjectBuilder.clean(TitaniumProjectBuilder.java:51) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:730) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:394) org.eclipse.core.internal.resources.Project$1.run(Project.java:618) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597) org.eclipse.core.internal.resources.Project.build(Project.java:114) org.eclipse.ui.internal.ide.dialogs.CleanDialog.doClean(CleanDialog.java:310) org.eclipse.ui.internal.ide.dialogs.CleanDialog$1.runInWorkspace(CleanDialog.java:151) org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 2 org.eclipse.core.resources 4 272 2012-03-14 17:52:23.632 !MESSAGE A resource already exists on disk '/Volumes/ultima/projects/titanium/timob-5698-maps/build'. !SUBENTRY 1 org.eclipse.core.resources 4 272 2012-03-14 17:52:23.632 !MESSAGE A resource already exists on disk '/Volumes/ultima/projects/titanium/timob-5698-maps/build'. {code},5,train
TISTUD-1348,Studio: Cannot open tiapp.xml from FTP source.,"Trying to open the Tiapp.xml from an FTP server returns this error: {noformat} ""Could not open the editor: Expected a tiapp.xml path and got '/var/folders/yl/gg2bc1h9767cchr1wrmrhkjr0000gp/T/aptanavfs706594519621445678tiapp.xml' {noformat} This caused the attached logfile to be generated in the Titanium log. Steps to reproduce: 1. Create a Titainum Mobile project. 2. Upload the Mobile project to an FTP server. 3. Attempt to open the tiapp.xml Actual result: An editor opens showing the above error. Expected result: You should be able to open the tiapp.xml, but it will be treated as an ""external"" tiapp.xml, so some editing options are disabled.",5,train
TISTUD-1350,Read Titanium Mobile SDK dependencies file to determine which Android SDKs need to be installed,"Since 1.8.0.1, the android platform now has a dependency file that shows which Android platform versions need to be installed: {code} $ cat mobilesdk/osx/2.0.0/android/dependency.json { ""min_api_level"": ""8"", ""dependencies"": { ""accelerometer"":[], ""analytics"":[], ""android"":[], ""app"":[], ""calendar"":[""android""], ""contacts"":[], ""database"":[], ""facebook"":[], ""filesystem"":[], ""gesture"":[""ui""], ""geolocation"":[], ""locale"":[], ""map"":[], ""media"":[""filesystem""], ""network"":[""xml""], ""platform"":[], ""ui"":[""filesystem"",""media""], ""utils"":[], ""xml"":[] }, ""required"": [""analytics"",""android"",""app"",""ui"",""locale""], ""libraries"": { ""android"":[""jaxen-1.1.1.jar"",""ti-commons-codec-1.3.jar"",""kroll-common.jar"",""titanium.jar""], ""xml"":[""jaxen-1.1.1.jar""], ""ui"":[""android-support-v4.jar""], ""network"":[""thirdparty.jar""] }, ""runtimes"": { ""v8"":[""kroll-v8.jar""], ""rhino"":[""kroll-rhino.jar"",""js.jar""], ""defaultRuntime"":""v8"" } } {code} Suggest we use this alongside the requirements in the sdk_info.json. The sdk_info suggests a default set of SDKs we encourage all users to install, and we use the dependencies file to confirm we aren't missing something.",13,train
TISTUD-1351,Update Titanium Studio Run/Debug/Publish wizard/dialog banners,The wizard banners should be consistent with the action icons * Run on iOS Device Wizard * iOS Distribution Wizard * Android Distribution Wizard * Mobile Web packaging Wizard See attached request document,5,train
TISTUD-1352,Studio: Insert line below current returned divide by zero error.,"While testing APSTUD-3553 I went to edit an file that I had opened from the FTP server. When I tried to add a second line, the machine hung and gave me a / by zero error and told me to check the log. Attached is the photo of the error and below is the event from the log. {noformat} !ENTRY org.eclipse.ui 4 4 2012-03-14 13:15:36.553 !MESSAGE ""Insert Line Below Current Line"" did not complete normally. Please see the log for more information. !ENTRY org.eclipse.ui 4 0 2012-03-14 13:15:36.554 !MESSAGE / by zero !STACK 0 java.lang.ArithmeticException: / by zero com.aptana.editor.php.internal.ui.editor.formatting.AbstractPHPAutoEditStrategy.getIndentationString(AbstractPHPAutoEditStrategy.java:690) com.aptana.editor.php.internal.ui.editor.formatting.AbstractPHPAutoEditStrategy.getIndentationAtOffset(AbstractPHPAutoEditStrategy.java:607) com.aptana.editor.php.internal.ui.editor.formatting.PHPAutoIndentStrategy.customizeCloseCurly(PHPAutoIndentStrategy.java:405) com.aptana.editor.php.internal.ui.editor.formatting.PHPAutoIndentStrategy.innerCustomizeDocumentCommand(PHPAutoIndentStrategy.java:194) com.aptana.editor.php.internal.ui.editor.formatting.PHPAutoIndentStrategy.customizeDocumentCommand(PHPAutoIndentStrategy.java:58) org.eclipse.jface.text.TextViewer.customizeDocumentCommand(TextViewer.java:3745) org.eclipse.jface.text.TextViewer.handleVerifyEvent(TextViewer.java:3782) org.eclipse.jface.text.source.projection.ProjectionViewer.handleVerifyEvent(ProjectionViewer.java:1277) org.eclipse.jface.text.TextViewer$TextVerifyListener.verifyText(TextViewer.java:435) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:265) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1061) org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7148) org.eclipse.swt.custom.StyledText.replaceTextRange(StyledText.java:7762) org.eclipse.ui.texteditor.InsertLineAction.run(InsertLineAction.java:144) org.eclipse.jface.action.Action.runWithEvent(Action.java:498) org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.filterEvent(Display.java:1531) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1257) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) org.eclipse.swt.widgets.Control.traverse(Control.java:4858) org.eclipse.swt.widgets.Control.translateTraversal(Control.java:4836) org.eclipse.swt.widgets.Composite.translateTraversal(Composite.java:1542) org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3016) org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:734) org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1743) org.eclipse.swt.widgets.Control.windowProc(Control.java:5016) org.eclipse.swt.widgets.Display.windowProc(Display.java:4408) org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8422) org.eclipse.swt.widgets.Display.eventProc(Display.java:1245) org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2276) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:616) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) {noformat}",5,train
TISTUD-1353,iOS: Clean needs to call `xcodebuild clean` to remove stale files,The {{Project->Clean}} command in Studio needs to call out to {{xcodebuild}} when cleaning iOS targets in order to ensure that stale information is removed. The exact command that needs to be performed is: {code} xcodebuild -project $\{PROJECT_DIR\}/build/iphone/$\{PROJECT_NAME\}.xcodeproj -sdk iphoneos -alltargets clean xcodebuild -project $\{PROJECT_DIR\}/build/iphone/$\{PROJECT_NAME\}.xcodeproj -sdk iphonesimulator -alltargets clean {code} We need to call this _before_ deleting the iPhone folder. This bug is the Studio version of TIMOB-8025. Please get cbarber to test and resolve that ticket when complete.,5,train
TISTUD-1354,Newly created apps are not appearing on the Apps page.,"New apps are not appearing on the https://my.appcelerator.com/apps/ page. I'm currently using Titanium Studio, build: 2.0.0.201203152033. The account I've discovered this on is phillis@shastaqa.com and the app guid of one of the missing apps is 75629f0e-def5-45f3-b8be-92b840eec93d (CFish4). I've checked the admin system and the app is not associated with the account.",3,train
TISTUD-1357,app-track called thousands of times (started today),"We're getting thousands of repeated calls to app-track from Titanium Studion 2.0 and Aptana 3.1. This started today, and his happening sporadically (once an hour or so) so it maybe a newly introduced bug. Looking at our logs, it looks like repeated calls for portal.samples.getSamples. Below is one mid that made the same call over 6000 times in the last hour. % grep e5254afa-f674-ea48-e1c7-69b86c6a62be des* | grep getSamples | wc -l 6831 {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""17ef49c6-52ea-f56a-4248-603f-ae0ad370"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""45e6f73a-9238-30aa-2bdf-60a7-931fd787"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""08597ce2-defe-5631-5671-1ac2-d5a2cd79"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""fba34374-83b6-6e1c-4f06-3011-d2551211"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""e1261085-61ce-b302-5cfe-f846-94c0a68a"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""f47c30f9-37b7-eeaa-090a-3fc0-c71047cf"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""a0e66d11-60d8-fb5a-315f-33cc-84a9bdc3"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""91ede117-b2fb-35a6-77b6-6ec3-40dc5580"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""fe19d99e-542e-5d26-5ca0-5dbc-d49bc060"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""06dca5b8-9a0e-e606-780f-73a9-46a27b71"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""fb019521-7af3-43f5-84b6-e5f6-a4ae2e8e"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""218e2fcb-3ca4-a4ab-d5b0-c9c9-5ee494a5"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540"",""ip"":""10.0.1.3"",""id"":""1fa0b6bb-d023-34c0-f6b7-2b5d-c8a7ba93"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} {""event"":""portal.samples.getSamples"",""type"":""portal"",""sid"":""69d66b6f3be7ca8bde1f1567ed63f4368e67846c"",""guid"":""9f5c585e-b9e6-40b4-8ae9-c9d75cf32884"",""mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be"",""app_id"":""com.appcelerator.titanium_developer_2"",""app_name"":""Titanium Studio"",""app_version"":""2.0.0.1327441212"",""mac_addr"":""00:23:32:de:0f:a8"",""platform"":""osx"",""version"":""1.1.0"",""os"":""Mac OS X"",""ostype"":""32bit"",""osver"":""10.7.3"",""osarch"":""i386"",""oscpu"":""2"",""un"":""gw2001jp@gmail.com"",""ver"":""2"",""tz"":""-540""^C,""ip"":""10.0.1.3"",""id"":""aad3e846-8987-7f6d-a81b-6d8d-70914595"",""server_ts"":""2012-03-19T10:21:34-07:00"",""server_mid"":""e5254afa-f674-ea48-e1c7-69b86c6a62be""} ",8,train
TISTUD-1358,iOS Preference page should utilize vertical scroll bars on tables,"If you have a long list of certificates or provisioning profiles, the preference dialog gets very tall. We need to specify a standard height for the table so the vertical scroll bars are utilized",3,train
TISTUD-1363,"Application ""null"" has been packaged message when starting a server","Stumbled into this one when validating APSTUD-3664. # Create a new Server. # Insert the start and stop commands into the server-dialog. In my case, I tried that with both xampp commands, and with apache commands (same result). # Start the server from the Servers view. A message appears and inform you that the server is running, and press any key to continue. Press a key... # A message dialog appears and notify something about packaging. # The servers view displays the server as stopped, while it's still running. # When staring the server again, you get a message that says that the server is running, and press any key to continue. Do that, and you get the packaging dialog again. ",5,train
TISTUD-1365,"""Source not found"" while iOS debugging ","Steps to reproduce: # Create a new Titanium Mobile project # Put a breakpoint on one of the ""var"" declarations in app.js # Launch the iOS simulator # When debugging stops on the breakpoint, note the error as shown in the screenshot",8,train
TISTUD-1366,Only check apiversion tag in manifest for Android modules,"iPhone modules are displayed as not supported when the Titanium SDK version is set to version 1.8.0.1 or newer. This appears to be due to the fact that the manifest file for iPhone modules currently do not include the 'apiversion: 2' entry. The 'apiversion' entry was added for Android modules in Titanium SDK version 1.8.0.1 to indicate that the internal module API had changed. This change only impacted Android modules and it should be checked for Android modules because older versions of Android modules will not work with Titanium SDK version 1.8.0.1 or newer (and vice-versa). This is not the case for iPhone modules (currently). The check for the 'apiversion' tag should ONLY be done for Android modules. It should be ignored for iPhone modules. To test: # Create a new Titanium Mobile project # Open up tiapp.xml and add a module to the project using the modules panel (I used ti.greystripe). Note the module appears active # Edit the module manifest file to raise the apiversion to something like ""3"" in the iOS and Android (current maximum version is 2 for 1.8/2.0) # Save tapp.xml and restart Studio. Note that the module now appears greyed out, but should be available for iOS ",5,train
TISTUD-1367,"Studio: Clean single project does not clean, does not log any errors when Mobile Web folder is empty","Description: While testing, we tried to clean a project using the single project clean option. Nothing happened, both the Android and iPhone folder contents were untouched. Nothing was logged even when I included the debug single component setting. Only when I previewed in browser for mobile web, and then cleaned did the project actually clean Steps to reproduce: 1) Create a project with studio using all deployment targets 2) Build the project for iOS and Android to get some content in the build folders 3) Choose Project > Clean and select only the project you created 4) Check the contents of the build folders Result: The contents of the build folders remain - no clean occurred Expected: The project build folders are emptied Note: I was able to clean only after launching a mobile web preview in Browser. Then the clean functioned as expected.",8,train
TISTUD-1368,Studio: Kitchen Sink Nook not available in samples,"Description: The sample Kitchen Sink Nook is not available on Linux systems. Steps to reproduce: 1) Install Titanium Studio, build: 2.0.0.v20120320000301 on a linux system 2) Navigate to the samples Result: Kitchen Sink Nook is not available Expected: The sample for Kitchen Sink Nook should be available on Linux",3,train
TISTUD-1369,Studio: Titanium Studio Samples: Incorrect message shown at top of the New sample project window while importing the sample,"Description: While importing a sample application, an incorrect message is shown at the top of New Sample Project pop up window that Files already exist in your destination directory. They will be deleted if you continue. Steps to Reproduce: 1. Open Titanium Studio 2. Use a workspace that does not have the folder for the sample to be imported 3. Go to samples section/dashboard, select a sample and import sample as project 4. A pop window for New Sample Project opens up Actual: A message is shown at the top as ""Files already exist in your destination directory. They will be deleted if you continue."" Expected: The message should not be shown as there does not already exist files for the sample being imported ",5,train
TISTUD-1370,"Remove extraneous ""No file system is defined for scheme: git"" messages",# Create a new rubbly file with a link like git:// in it (could be a github repo URL) # Hold down the Ctrl key and hover over the link # See the item below in the log file Suggest just not writing out the message for protocols we don't understand or handle. {code} (Build 3.0.3.qualifier) [ERROR] No file system is defined for scheme: git org.eclipse.core.runtime.CoreException: No file system is defined for scheme: git org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55) org.eclipse.core.internal.filesystem.Policy.error(Policy.java:50) org.eclipse.core.internal.filesystem.InternalFileSystemCore.getFileSystem(InternalFileSystemCore.java:65) org.eclipse.core.filesystem.EFS.getFileSystem(EFS.java:430) com.aptana.editor.common.resolver.URIResolver.getFileStore(URIResolver.java:76) com.aptana.editor.common.resolver.URIResolver.resolveURI(URIResolver.java:119) com.aptana.editor.common.text.hyperlink.HyperlinkDetector.detectHyperlinks(HyperlinkDetector.java:81) org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:286) org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:258) org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:462) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:211) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4125) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3971) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3610) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.aptana.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code},3,train
TISTUD-1373,ModulesTable - Replace the iPhone and iPad columns with a single iOS column,The Modules table in the TiApp editor should not display two platforms for iPhone and iPad. It should only display one column for iOS.,8,train
TISTUD-1376,Titanium Studio: Samples: RSS Reader and Geocoder: reimported projects rename and disappear on second install,"When RSS Reader or Geocoder are installed from the dashboard/samples pane, deleted (without filesystem removal), and reimported into studio, the projects import with a different project name: Sample.Mapping and Sample.RSS instead of Geocoder and RSS Reader. If the user attempts to reinstall the sample from the dashboard/samples pane, there will be a fatal git dialog box and the project will disappear from the filesystem. Steps to Reproduce: 1. Install RSS Reader or Geocoder from the samples pane or dashboard links. 2. Delete project from workspace without removing it from the filesystem. 3. Re-import project back into studio from workspace. Expected Result: Project should have same name as before. Actual Result: Project has different name. 4. Install the project again from the samples pane or dashboard links. 5. Press ok, accept the install. Expected Result: Project should be overwritten and a new version of the sample should take its place. Actual Result: Git warning dialog, followed by automatic deletion of project from the OS.",8,train
TISTUD-1377,Unable to locate module ti.cloud when launching Mobile Web application,"Summary: When a single window template application is selected to be run on Mobile Web Preview on Browser and Mobile Web Preview on Emulator, an error is shown Steps to Reproduce: 1. Create a new app, with template as Single Windows 2. Click on the run button and select the option for Mobile Web Preview on Browser or Mobile Web Preview on Emulator An error is shown Unable to generate Mobile Web App. Error: [INFO] Titanium Mobile Web Compiler v2.0.0.v20120320000301 [INFO] Compiling Mobile Web project ""SingleWindow"" [development] [INFO] Copying /Library/Application Support/Titanium/mobilesdk/osx/2.0.0.v20120320000301/mobileweb/themes... [INFO] Copying /Users/ingo/Documents/Aptana Studio 3 Workspace/SingleWindow/Resources... [INFO] Copying /Users/ingo/Documents/Aptana Studio 3 Workspace/SingleWindow/Resources/mobileweb... [INFO] Copying /Library/Application Support/Titanium/mobilesdk/osx/2.0.0.v20120320000301/mobileweb/titanium... [INFO] Scanning project for dependencies... [INFO] Searching for all required modules... [INFO] Locating Ti+ modules... [ERROR] Unable to find Ti+ module ""ti.cloud"", v2.0 It appears that the platform=""commonjs"" is being left off the module definition, which then causes this issue.",5,train
TISTUD-1378,Add iOS Ad Hoc package launch configuration that produces an ipa/app,"Currently, production builds of iOS targeted projects produce an archived XCode project. For ad hoc distribution, users are expected to take the generated ipa/app and distribute it accordingly, so they would have to go into XCode to generate the output. To simplify the distribution process and reduce the need for users to mess with XCode, we should provide a separate Ad Hoc distribution launch configuration and wizard The Ad hoc distribution process with be similar to the app store distribution with the following differences: -Only ad hoc distribution certificates/profiles are displayed -Specify either app or ipa output -Specify a location for the output ",8,train
TISTUD-1380,Studio: Tiapp.xml editor gets out of sync and warns of changes in filesystem.,"Description: WHile testing, Natalie noticed that her changes to Tiapp (for the SDK version) were not being reflected, and subsequent builds were still using the previous SDK setting. We investigated, and noted that manipulating the pop-up for the SDK version would warn that the file had changed on the file system,and did she want to sync. With Shalom running us through some tests we determined a few things, most disconcerting is the fact that the Tiapp XML view had a different SDK listed than showed in the Overview. This explained the issue with building with the wrong SDK. We still are investigating why the TiApp.xml is showing as out of sync from the file system perspective. Steps to reproduce: 1) Install and run Studio 2) Create a project and build for device 3) Open TiApp.xml editor and change SDK then save 4) Continue to change SDK and save until you get warned about file system sync Result: After a few moments you should see the sync warning. You may also notice if you examine the XML that the SDK setting is not matching. Expected: No sync warnings simply manipulating the tiapp. No SDK setting mismatch.",8,train
TISTUD-1381,Unable to preview mobile web application when launching preview of index.html page,"Steps to reproduce: 1. Create a Single Window project from template wizard 2. Select the application in Project Explorer 3. Choose Publish > Package - Mobile Web 4. Select ""Create a new Project"" and give the project a unique name 5. Complete the wizard 6. Find the new project in the workspace 7. Double-click on the index.html file to open up the main page 8. Click on the preview button in the header Actual: The app is stuck at the splash screen Expected: The mobile web app should work like a regular Single Window app on the phone. Note: The default TiMob project packaged for mobile web works as expected i.e. it does not get stuck at the splash screen. I believe the issue here is that we are launching the preview for the mobile web application from a file URL, and evidently it does not work that way. It is probably easier to extend Studio than to fix this behavior in Mobile Web. Suggested fix: * When creating a new project as part of the mobile web packaging wizard, create a new default server for use in preview and associate it with that project.",8,train
TISTUD-1382,Titanium Studio: Samples: samples pane and samples dashboard links intermittently disappear,"When using studio, the samples pane and samples dashboard links intermittently disappear. They exist on launch, disappear once in a while, then re-appear on studio restart. Has occurred twice in a few hours. Studio log attached. Steps to Reproduce: 1. Start studio. 2. Use studio for hours. Expected Result: Samples pane should contain samples, dashboard samples links should exist. Actual Result: Once in a while, the samples disappear.",3,train
TISTUD-1383,Widget is disposed related to SamplesView.run(),Noticed this in a log file. Add reproduction steps if you can figure them out {code} !ENTRY org.eclipse.jface 4 0 2012-03-16 10:59:55.337 !MESSAGE Unhandled event loop exception during blocked modal context. !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed) org.eclipse.swt.SWT.error(SWT.java:4282) org.eclipse.swt.SWT.error(SWT.java:4197) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:275) com.appcelerator.titanium.rcp.IDEWorkbenchAdvisor.disconnectFromWorkspace(IDEWorkbenchAdvisor.java:499) com.appcelerator.titanium.rcp.IDEWorkbenchAdvisor.postShutdown(IDEWorkbenchAdvisor.java:407) org.eclipse.ui.internal.Workbench.shutdown(Workbench.java:3023) org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1118) org.eclipse.ui.internal.Workbench.access$15(Workbench.java:1035) org.eclipse.ui.internal.Workbench$25.run(Workbench.java:1279) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.internal.Workbench.close(Workbench.java:1277) org.eclipse.ui.internal.Workbench.close(Workbench.java:1249) com.appcelerator.titanium.core.TitaniumUserManager.signOut(TitaniumUserManager.java:172) com.appcelerator.titanium.ui.internal.TitaniumHomeControlContribution.signOut(TitaniumHomeControlContribution.java:110) com.appcelerator.titanium.ui.internal.TitaniumHomeControlContribution.access$2(TitaniumHomeControlContribution.java:104) com.appcelerator.titanium.ui.internal.TitaniumHomeControlContribution$2.widgetSelected(TitaniumHomeControlContribution.java:86) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1094) org.eclipse.swt.widgets.Link.wmNotifyChild(Link.java:1071) org.eclipse.swt.widgets.Control.wmNotify(Control.java:5534) org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:1896) org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:5086) org.eclipse.swt.widgets.Control.windowProc(Control.java:4584) org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2425) org.eclipse.swt.widgets.Link.callWindowProc(Link.java:172) org.eclipse.swt.widgets.Widget.wmLButtonUp(Widget.java:2057) org.eclipse.swt.widgets.Control.WM_LBUTTONUP(Control.java:4912) org.eclipse.swt.widgets.Link.WM_LBUTTONUP(Link.java:909) org.eclipse.swt.widgets.Control.windowProc(Control.java:4565) org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2531) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) Caused by: org.eclipse.swt.SWTException: Widget is disposed org.eclipse.swt.SWT.error(SWT.java:4282) org.eclipse.swt.SWT.error(SWT.java:4197) org.eclipse.swt.SWT.error(SWT.java:4168) org.eclipse.swt.widgets.Widget.error(Widget.java:468) org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340) org.eclipse.swt.widgets.Tree.getSelection(Tree.java:3402) org.eclipse.jface.viewers.TreeViewer.getSelection(TreeViewer.java:256) org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:344) org.eclipse.jface.viewers.AbstractTreeViewer.setSelectionToWidget(AbstractTreeViewer.java:2521) org.eclipse.jface.viewers.AbstractTreeViewer.setSelectionToWidget(AbstractTreeViewer.java:2944) org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1450) org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403) org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1506) org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:537) org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1465) com.aptana.samples.ui.views.SamplesView$1$1.run(SamplesView.java:63) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 61 more {code},2,train
TISTUD-1384,"Clicking ""Publish"" multiple times when package application for distribution on Mobile Web results in an error","Summary: When an application is selected to be packaged for distribution on Mobile Web, an error is shown Steps to Reproduce: 1. Create a new project 2. Click on the Publish button and select the option for Package Mobile Web 3. In the pop up window, select the third option for Create a new project for the new mobile web app 4. Put in a project name and click on Publish (do it at least 2x quickly) A packaging error is shown with the message ""Failed to package project"" ",8,train
TISTUD-1392,Unable to package mobile web to a project with a space in the name,"# Create a new project # Click on the Publish button and select the option for Package Mobile Web # In the pop up window, select the third option for Create a new project for the new mobile web app # Put in a project name with a space (I used ""test 4"" and click on Publish It appears to work, but ultimately fails, as shown in attached screenshot See this in details view: {code} Creation Problems Invalid project description. OK /Users/ingo/Documents/Titanium Studio Workspace 3/test overlaps the location of another project: 'test ' {code}",5,train
TISTUD-1393,Launching a mobile web preview resets the default web server root,"# Create a new Mobile Web project # Launch it in the browser preview # Package it into a new project # Press the Firefox - Internal Server Run configuration # Get ""Launch URL is not defined"" as a popup error Looking into the code, it appears that the currently running internal server now has a project root under /build/mobileweb for the last project, for the URL mapping fails.",13,train
TISTUD-1395,Running package operations (on multiple platforms) on the same project multiple times causes errors,"Since package operations are now public launch configurations, you can run multiple configurations in quick succession. This will cause errors since the package operations operate on the build directory. We should queue up the launch configurations so they are sequential, scheduling launches based on the project. Steps: 1. Create a mobile project with iOS, Android and mobile web deployment targets 2. Perform project package for iOS 3. Perform project package for android 4. Perform project package for mobile web 5. From the run shortcut, re-run 2/3/4 operations multiple times Expected: Each package operation completes successfully Actual: Error occurs",8,train
TISTUD-1396,Auto-select API version of Android SDK if available,"When the Android SDK is installed, auto-select (in Preferences > Titanium > Default Android SDK) the ""Google APIs..."" version of the correct Android SDK version for the installed Titanium SDK version. This will make it easier for new users installing Titanium for the first time, who are unaware of the difference between the standard and enhanced Android SDK versions. Note that this request may be somewhat related to TISTUD-1350 when implemented.",5,train
TISTUD-1401,Add Xcode Version Manager,"Currently, if a user has both Xcode 4.2 and Xcode 4.3 installed, they would have to manually execute xcode-select to switch the Xcode version used for iOS operations. I propose we do the following -Update the Titanium preferences for IOS SDK home to be a combo box -The combo box contains a list of detected Xcode locations -Upon applying the changes, we call the sudo xcode-select -switch command ",13,train
TISTUD-1402,ACS keys cut off when generated in TiApp Editor,"When enabling the ACS on Windows, the ACS labels at the TiApp cloud section get cut off from the bottom. (see screenshot) It's visible only when enabling ACS. When re-opening the TiApp editor, it looks fine.",3,train
TISTUD-1404,Add description to iOS SDK location to describe how to run with different Xcode versions,"For Xcode4.3, the xcode-select command must be run to ensure properly function of the iOS platform scripts. Running the command can be foreign and difficult for some users. We should display a informative description and link on how to run xcode-select. There should be a linked wiki/doc page that describes in further detail on how to run the command. The description should be included in the iOS section of the Titanium preferences. It should state: ""If the desired Xcode installation is not displayed, you will need to run ""sudo xcode-select "" to target a specific installation. More details""",8,train
TISTUD-1407,Add platform attribute to module element(s),"When a module that supports only a single platform is added to a project using the new modules table, the module element is added to tiapp.xml but it is missing the platform tag. Steps to reproduce: 1. Create a new mobile application project -- use defaults of all application target types 2. Click on the button to add a new module (+) 3. Select a module that is only available on one platform (e.g. ti.push) 4. Save the project 5. Attempt to run the application in the iPhone simulator 6. Build should fail with an error indicating that the ti.push module is missing Without the 'platform' tag on the module entry, the build script will attempt to locate the module for all application targets. The module element needs to include the 'platform' tag so that the module is only searched for when building for that target. For example, 'platform=""android""'. Also, without the 'platform' tag the module displays in the Modules table with its version number available on all platforms -- which is incorrect since it is only available on the single platform. ",8,train
TISTUD-1508,Console view doesn't use background color when already open and a new process is launched,"See screencast at: http://dl.dropbox.com/u/11524266/tistudio.mov He has the console open with some prior output from a previous run of an app (properly colored), then he launches a new run from the App Explorer, a new console page is added that has the theme fg colors, but stays with a white bg. When he clicks on the console to focus it, it gets the black bg applied.",8,train
TISTUD-1410,Add URL bar to integrated mobileweb preview,"The integrated web preview in TiStudio does not expose the local URL to which the preview pane is connected. You can see it in the title bar of TiStudio itself, but its not copyable. It would be helpful to have the URL bar shown above mobileweb preview panes. ",3,train
TISTUD-1412,Add ability to read packaged rubles from the Titanium SDK directory,"As we move towards having per-SDK-version samples and templates, it makes sense that those items would be contributed from the platform itself. Propose a file structure like: /Application/Library Support/titanium/mobilesdk///studio or we could put them in modules: /Application/Library Support/titanium/modules/studio/ Studio would need to inspect the SDK directory and read from a crafted set of directories for Rubles in specific locations.",13,train
TISTUD-1414,Auto-configure browser list to contain all installed browsers on Windows,"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 ",20,train
TISTUD-1415,Update Studio to ship with Android tools r17 by default,"Update the sdk_info file to point to the newest r17 version of the tools. To test, remove your Android folder and start the configuration process on Window, Linux and mac. It should install r17 of the tooling.",3,train
TISTUD-1416,Titanium Mobile Module project wizard overwrites default manifest content,"Close to a blocker, but you can get around it # Create a new mobile module project for iOS. Fill in any default values # Go through the wizard # Attempt to package the project. You will get an error of ""missing required manifest key 'name'"" Inspecting the manifest file, you should have something like: {code} # # this is your module manifest and used by Titanium # during compilation, packaging, distribution, etc. # version: 0.1 apiversion: 2 description: My module author: Your Name license: Specify your license copyright: Copyright (c) 2012 by Your Company # these should not be edited name: testmodule4 moduleid: asdasd.asdas guid: 60a2774b-54c6-47d2-9889-d38698d3c0d3 platform: iphone minsdk: 2.0.0.v20120322190311 {code} but instead, you get: {code} #appname: testModule #publisher: ingo #url: #image: appicon.png #appid: com.test #desc: undefined #type: module #guid: e292c47a-1210-46e9-9721-4444553793dd {code} We need to preserve the contents of the manifest file and only change elements as necessary. BasicNewTitaniumProject.generateInitialManifest() is not useful in the context of module generation. It may also cause problems with other templates too, as it seems we are completely overwriting the original manifest. We should append/modify as necessary. ",8,train
TISTUD-1417,Convert release notes to use new URL,"Once the release notes are in the new location, we may need to update the code that parses them, and modify the redirect off of studio.appcelerator.com. See TitaniumSDKReleaseNotesDialog.",5,train
TISTUD-1419,"""Installed JREs"" page missing","# Create a new Android Mobile Module project # It should create the project, but have the warning ""Unbound classpath container: 'Default System Library' in project 'testAndroid'"" # Attempting to fix that, it seems you should edit your Installed JREs preference page. However, the Standalone version of Studio doesn't have it, unlike the version of Eclipse (see screenshots). # Attempting to install the JDT tools via the notes on this page (though substituting Indigo as a version) does not appear to work as you get conflicting dependency errors. It seems we either need to remove the JDT items, or we're not fully shipping the full set. Suggested fixes: * Do not ship optional components (i.e. JDT) * Remove the django templates from Pydev, and allow users to install them optionally.",13,train
TISTUD-1420,Open-source Titanium Desktop Studio integration,"We'd like to make it easier for users to extend and contribute to the Titanium Desktop (TIDe) project. # Refactor the current Titanium Desktop plugin(s) into a new repo ## We can remove references in the *.update plugin, since the update process will likely be much different in the future ## Do we need to create the concept of a Titanium type (i.e. desktop, mobile, ?) that would contribute a few things into the system # Add a feature enabling users to install the plugin separately on top of Studio # Create a hudson build to build this plugin and push it to a deployment site # Change the license of the plugin to Apache 2 See attached image for dependencies.",20,train
TISTUD-1421,Titanium Studio: MobileWeb: Preview in Emulator conditionally fails with: Launch url is not defined,"When deploying a second mobile web project to preview in emulator browser, studio fails with error: Launch url is not defined. Studio log identical to dialog box screenshot. Found in Windows 7, but not Snow Leopard. Steps to Reproduce: 1. Create two projects. 2. Preview first project in emulator browser. 3. Preview second project in emulator browser. Expected Result: Second project should deploy. Actual Result: Deployment fails in studio. Note: Relaunching the first project works as expected. ",8,train
TISTUD-1422,Titanium Studio: MobileWeb: cannot re-deploy app in Firefox on OSX,"When re-deploying a mobile web app to firefox, the app is launched in a new window, instead of a new tab. Firefox on Snow Leopard can only have one instance, so the deployment fails and the new window is closed. MobileWeb Firefox preview should be deployed to a new tab. Does not occur on Windows 7 (app is opened in new tab). Steps to Reproduce: 1. Create project. 2. Preview in browser to firefox. 3. Preview again in browser to firefox. Expected Result: App should open in new tab. Actual Result: App opens in new window, which is automatically closed due to firefox single instance policy on Snow Leopard.",8,train
TISTUD-1426,Remove option to launch Mobile Web Preview in internal browser,"The studio internal browser may not fire touch events to mobile web apps. Steps to Reproduce: 1. Create default app. 2. Preview in internal browser. 3. Click on buttons. Expected Result: The app should respond to click events. Actual Result: No response. Works on the other external browsers. It apparently sometimes works on some machines and not on others. Based on feedback, it appears there is some conflict between Mobile Web and the internal browser. Thus, the best option is to remove the ability to use the internal browser.",5,train
TISTUD-1424,Titanium Studio: MobileWeb: Packaging: allow packaging to non-existent directory,"When packaging to a non-existent directory, an error is presented and the user cannot package. Steps to Reproduce: 1. Create a new project. 2. Package for mobile web. 3. Create a path using a new sub-directory hand-typed. Expected Result: Should be able to package app and new directory is created. Actual Result: Warning prevents app from packaging. Suggested solution: * Create directory * Don't show warning * Pop up error if issue creating dir",5,train
TISTUD-1428,Studio preferences > titanium General - an error is shown if desktop sdk is not installed (may no longer be appropriate and cause unnecessary alarm),"h2. Problem # Do not have the desktop sdk installed # Titanium studio menu item > preferences > titanium studio > titanium # check the window for errors {noformat} An error was detected with the SDKs configuration. Reason: [Titanium SDK Home] Could not locate a Titanium Desktop SDK at the given path {noformat} Note that Ti Desktop is no longer officially supported, so this validation should be removed, or result in a warning rather than error. results: https://skitch.com/thomashue/8ch87/preferences. the user is shown an error. Being that we have put the desktop out to pasture, it might cause unnecessary alarm to user h2. Workaround Install Desktop SDK from [Continuous Builds|https://wiki.appcelerator.org/display/guides/Installing+Titanium+SDK+Continuous+Builds] site",3,train
TISTUD-1431,Studio: Launching debugger successfully produces unexpected log entries.,Description: After a debugger session launch I noted that the log contained an entry repeated many times that was unexpected. This occurs when the debugger launch is working as expected and in cases where the debugger fails to connect. The log from a good debugger launch: {code:title=.log} !ENTRY com.aptana.js.debug.core 1 0 2012-03-26 13:55:51.772 !MESSAGE Extension version: 3.0.0.1329178773; protocol v1 !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:54.394 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:55.395 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:56.397 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:57.398 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:58.400 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:59.401 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:00.403 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:01.405 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:02.406 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:03.407 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:04.408 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:05.410 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:06.411 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:07.412 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:08.413 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:09.414 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:10.416 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:11.417 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:12.418 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:13.420 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:14.421 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:15.423 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:16.424 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:17.425 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:18.427 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read ti...,8,train
TISTUD-1432,Titanium Studio: Preferences: Titanium: cannot save Titanium SDK home path,"When editing the titanium sdk home path, cannot save changes. The workaround is to click 'restore defaults', make the changes, then save. Steps to Reproduce: 1. Copy Application Support/Titanium (the sdk super-folder) to another location. 2. In studio, preferences, change the titanium sdk home to this new location. Expected Result: Should be able to save changes. Actual Result: Cannot save changes. Must restore defaults, then edit and save changes.",5,train
TISTUD-1435,Android module projects should have better validation for name and id,"When creating a mobile module project, we should be more strict about the name validation and the module-id validation. * Names should not contain any hyphens (and other special characters that can 'kill' the generated JavaScript example, or the packaging). Suggest we use the javascript identifier rules here. * module-id should follow the Java conventions for package names (just like we do with Android).",8,train
TISTUD-1436,Packaging of Android module fails to copy built module to destination,"# Create a new Android mobile module project # Attempt to package it for a project or a folder on disk (it probably also fails for the Titanium SDK) # It appears to work, but fails to copy the file to the destination, with the following error: {code} (Build 1.0.0.qualifier) [ERROR] Could not move: /Users/ingo/Documents/Aptana_Studio_3_Workspace/asdasd/dist/app.bapp-android-0.1.zip. org.eclipse.core.runtime.CoreException: Could not move: /Users/ingo/Documents/Aptana_Studio_3_Workspace/asdasd/dist/app.bapp-android-0.1.zip. org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55) org.eclipse.core.filesystem.provider.FileStore.move(FileStore.java:415) org.eclipse.core.internal.filesystem.local.LocalFile.move(LocalFile.java:352) com.appcelerator.titanium.mobile.module.launching.ModulePackagerUtil.processModule(ModulePackagerUtil.java:75) com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate$1.run(AndroidModulePackageLaunchConfigurationDelegate.java:104) java.lang.Thread.run(Thread.java:680) Caused by: org.eclipse.core.runtime.CoreException: Could not write file: /Users/ingo/Documents/Aptana_Studio_3_Workspace/testMobile/dist/app.bapp-android-0.1.zip. org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55) org.eclipse.core.internal.filesystem.local.LocalFile.openOutputStream(LocalFile.java:391) org.eclipse.core.filesystem.provider.FileStore.copyFile(FileStore.java:221) org.eclipse.core.filesystem.provider.FileStore.copy(FileStore.java:143) org.eclipse.core.internal.filesystem.local.LocalFile.copy(LocalFile.java:111) org.eclipse.core.filesystem.provider.FileStore.move(FileStore.java:410) ... 4 more Caused by: java.io.FileNotFoundException: /Users/ingo/Documents/Aptana_Studio_3_Workspace/testMobile/dist/app.bapp-android-0.1.zip (No such file or directory) java.io.FileOutputStream.open(Native Method) java.io.FileOutputStream.(FileOutputStream.java:194) org.eclipse.core.internal.filesystem.local.LocalFile.openOutputStream(LocalFile.java:382) ... 8 more {code} The issue appears to be the fact it's copying it from inside /dest, but that it attempts to copy it into a /dest subfolder as well, which doesn't exist.",5,train
TISTUD-1442,Prevent an Android Mobile Module project creation when JDT is not installed,"Android mobile-module project should not be created unless the JDT plugins (feature) are installed. Right now, a created project on an environment without JDT is not usable.",5,train
TISTUD-1443,Studio: Build Participation: Windows does not update content assist for new class methods in Javascript,Failed test case BP1009. Javascript: New class methods do not appear in content assist before saving. Steps to reproduce: 1. Define a class. 2. Add a method to the class definition. 3. Create a new instance of the variable. 4. On a new line type the name of the instance identifier with the member selection operator. Expected result: The declared class method will appear in the content assist list. Actual result: The new method does not show up in content assist.,5,train
TISTUD-1445,"Project fails to build, launch emulator with Android R17 tools & Ti2.0","h5. Actual Behavior All projects fail to build to the emulator under the environment listed above. I get the error shown in the attached screen. Eventually, I get the message that the build script has timed out waiting for the emulator to launch -- restarting ADB has no effect. Via twitter, some have suggested that you need to disable FastDev with the R17 tools & Titanium. You can see from the attached screen that I tried that. But it had no effect. Neither did specifying an older Android tool level. h5. Work around I can reset the project to use the Titanium 1.8.2 SDK. The project will build & the emulator will launch as expected. Then, I can rebuild the project using any of the 2.0x CI builds I have on my system and they'll all work just fine. h5. Expected behavior I can build with Ti2.0 and the R17 tools without implementing the Work around. ",8,train
TISTUD-1447,Run preference page platform loading using a job,"Currently when the preference page is opened, it takes some time for the dialog to appear, resulting in a wait cursor to appear. This is very confusing for users. The proposed solution is: -When the preference page is opened, run the loading of platform information in a background job -While the platform information is loaded, the corresponding platform UI is disabled and the value of ""Loading..."" is displayed. We should do this for the two main platforms, iOS and Android, since they require the most processing time.",13,train
TISTUD-1450,Studio: Updated modules delivered via CI builds are not replacing existing modules if they share the same name,"While evaluating ACS features, we encountered an Android issue that was supposed to have been fixed in the latest ti.cloud module. Upon further investigation we determined that the module was in fact included with the latest CI build. We conducted a few experiments and determined that although the module was updated, the name was the same so during the unzipping process, the module was not replacing the existing older module. Steps to reproduce: 1) Delete your existing common JS module folder from the Titanium folder 2) install a CI build from 3/24 or before 3) Check the contents of the module folder 4) install a CI build from 3/27 or later 5) Check the contents of the module folder Results: The ti.cloud module is the older broken module, not the newer fixed module Expected: The module is overwritten by the newer module with the same name. Note: There is no relevant content in the log",8,train
TISTUD-1452,Simplify initial Studio UI and perspective,"An exercise in simplifying the new user experience: * Rename Web perspective to ""Studio (extended)"" * Create new ""Studio"" perspective ** remove top level toolbar ** add keyboard shortcuts commands for ""occurrences"", ""block selection"", ""show whitespace characters"" ** remove samples view ** remove outline view ** remove snippets view ** remove servers, problems, terminal, console view ** keep console view hidden unless an error comes up",13,train
TISTUD-1456,Add default UI configuration options to dashboard ,"* Remove Welcome page * Replace with accordion. Initially open a section to configure TISTUD-1456 ** Light/dark theme ** Simple/advanced perspective ** See APSTUD-4798 and APSTUD-4799 for actions to call The bottom half of the accordion is similar to what we have currently If we reduce or remove the top toolbar, we may wish to surface some common initial configuration options to the first tab of the dashboard--something equivalent to an initial questionnaire. It could be perhaps in some normally ""hidden"" area for ""advanced configuration"" if we determine it's useful but is confusing on first run.",20,train
TISTUD-1464,Inform users they need to switch to a workspace without spaces if doing Android Module development,"When using the Android NDK, if you have spaces in your path (i.e. /Users/username/Documents/Titanium Studio Workspace), Studio will fail to be able to build an Android module project. Suggest putting up a warning when creating a mobile module project warning users about the issue and informing them how to solve it (direct them to the wiki page on how to move/switch their workspace: http://docs.appcelerator.com/titanium/2.0/index.html#!/guide/Switching_your_Workspace).",5,train
TISTUD-1466,Use built-in ANT when packaging Android modules,"# Created a new Android mobile module project # Attempt to package the project # Run into this error: {code} Caused by: java.lang.NullPointerException com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate.launch(AndroidModulePackageLaunchConfigurationDelegate.java:83) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1023) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Root exception: java.lang.NullPointerException com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate.launch(AndroidModulePackageLaunchConfigurationDelegate.java:83) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1023) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code} snippet of code: final Process osProcess = ProcessUtil.run(antPath.toOSString(), project.getLocation()); It appears it can't find ANT. We package ANT as part of Studio, so we should instead use the built-in ANT rather than calling it on the command line. Workaround: Right-click on build.xml. Click *Run As* > *Ant Build* (the first option)",5,train
TISTUD-1468,Add Titanium Project GUID to ACS application creation call,"When creating an application in ACS, we need to pass the GUID along with the call. The format will be: ti_guid=, passed to the create.json call.",3,train
TISTUD-1469,Studio: HTML Template selection does not load correctly.,After first loading Titanium Studio the template selection for the New from template > HTML has the wrong selection (see screen shot). If I load a template for HTML this fixes the template selection found in the menu. Steps to reproduce: 1. Open Titanium Studio. 2. Click File > New From Template > HTML Expected results: Should see a list of all available templates for HTML files. Actual results: Only a strange entry and the HTML 5 template appear.,8,train
TISTUD-1474,"Titanium Studio: Installer - On Windows 7, when installing Titanium Studio, the License Agreement has a bad refresh screen",Steps to reproduce: 1. Get Titanium Studio 2.0.0 installer for Windows 2. Hit next until you see the License Agreement screen Actual: The License Agreement has a bad refresh screen. See attachment Expected: Should be able to see the License Agreement. Note: Does not occur with the Titanium Studio 1.0.9 installer.,5,train
TISTUD-1476,NPE in TitaniumUpdateStartup.run(),"Found in my log file. To replicate (my be intermittent), try shutting down Studio right in the middle of the ""log in"" process {code} !ENTRY org.eclipse.core.jobs 4 2 2012-03-31 07:44:07.268 !MESSAGE An internal error occurred during: ""Checking for new Titanium SDK Updates..."". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.update.TitaniumUpdateStartup$1.run(TitaniumUpdateStartup.java:79) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}",3,train
TISTUD-1477,Make Titanium SDK release-notes grabbing more robust,"If the current set of release notes is from a full HTML page that _does not_ contain a , the release noes will launch in a new browser window. # Allow for override of TitaniumSDKReleaseNotesDialog.RELEASE_NOTES_URL as a command-line option to make testing this easier. # First try to grab apidiv. # Then try to grab interior of body node, or if no body node, then whole content. If either work then replace release_notes template with new content. # If all else fails, use whole content and don't use the template. Notes: * Be careful of nulls * Anchor links didn't appear to work (might need to be munged?) ",8,train
TISTUD-1479,Allow selecting a non-existing directory as the Titanium SDK directory,"When a user selects a Titanium SDK path in the preference page, we don't allow a path that has no Titanium SDK in it. A better behavior would be: # Allow an arbitrary directory selection. # Prompt the user that the Titanium SDK will be downloaded into the new location (in case it's missing an SDK). # In case a directory creation is needed, we'll do that *before* the preference dialog is closed (on apply/ok). This will clear any permission issues with the selected path before the SDK is downloaded. # If everything is OK with the new location, start the SDK update process into the new path. ",8,train
TISTUD-1481,Studio: Install site will not allow for software to be installed.,"When trying to install the TestFlight software plugin following the steps below I found that I can not proceed to the licence page in the installation. Steps to reproduce: 1. From the Help menu, select Install New Software... to open an Install pop-up window. 2. In the Work with: text box of the Install window, type the URL http://ec2-50-16-19-245.compute-1.amazonaws.com/appcelerator/studio/testflight/update/release/ for the update site, and hit the Enter key. 3. In the populated table below, check the box next to the name of the plug-in, and click the Next button. 4. Click the Next button to go to the license page. Expected result: The licence page is displayed and the installation can be completed. Actual result: The next button does not become active and there is no way to continue to the next part of the installation. ",5,train
TISTUD-1488,ACS Keys not copy-able,"I enabled ACS for one of my apps using early access 2.0 Studio, and it shows the production and development keys, but you can't copy it, if we need to use HTTP access or test using other software - we would have to manually type this out, or go to the ACS website, can the keys in Studio be copy-able?",5,train
TISTUD-1482,NPE in Log when Studio is shutdown,"Found in my log file. To replicate (my be intermittent): 1. Start up Studio 2. Open the Progress View 3. Restart Studio 4. When Studio is started, take note of the items in the Progress view 5. When there are items running int he progress view, close Studio I repeated this 4 times, with different tasks in the progress view running, and saw the NPE twice !MESSAGE Errors running builder 'Studio Unified Builder' on project 'testMe'. !STACK 0 java.lang.NullPointerException com.aptana.core.build.UnifiedBuilder.getIndexManager(UnifiedBuilder.java:367) com.aptana.core.build.UnifiedBuilder.filterFiles(UnifiedBuilder.java:471) com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:400) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:302) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:148) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) ",3,train
TISTUD-1485,Update sites for Openshift/TestFlight should not contain both plugin and feature node,"When we install from an update site using the result from the TestFlight and Openshift builds, the categorized nodes are the plugin and the feature nodes. Typically it should just contain the Feature install, which would pull in the plugin as part of it. In this case, if we check just the feature and not the plugin, the install is an invalid one, resulting in an invalid install. ",8,train
TISTUD-1489,"Update IPublishType.publish() method to explicitly pass in PlatformType, output location and publish target","For clarity, we should pass in the parameters we know about explicitly - Publish target, platform type, and output location. ",5,train
TISTUD-1490,Titanium Studio: SDK: updating to readonly sdk folder gives no such directory error,"When updating SDK to an SDK folder with readonly access, a directory not found error is presented (instead of invalid permissions). Steps to Reproduce: 1. Change the permissions of the Titanium SDK folder to readonly (e.g., folder right click -> properties -> permissions, etc.). 2. Update the SDK to a different version. Update Option 1: Go to http://builds.appcelerator.com.s3.amazonaws.com/index.html, copy an SDK location. Go to Studio: Help -> Install Titanium SDK From URL, paste the link, update. Update Option 2: Remove the last live version of the SDK from the SDK folder. Go to Studio: Help -> Check For Titanium SDK Updates. Expected Result: There should be an error indicating the SDK folder does not have write permissions. Actual Result: Directory not found error.",5,train
TISTUD-1494,Building for iOS device in Studio 2.0 against SDK 2.0.0GA (Ad-Hoc certs and PUSH issues),"when I build for an iOS Device Xcode bounces in the dock for nearly a minute before it will unlock beachball and allow me to make a selection, it happens once before the first window shows and then once again before build. If I select Manage option - this whole Xcode bouncing in the dock repeatedly (like its loading and quitting again and again) happens ... its very slow. Compared to 1.x Studio which is much faster. The preselected provisioning profiles is not clear, and somehow I managed to build against an ad-hoc certificate, i did not consciously choose this) but it caused my Push Notification Process to throw up errors. I tried 2 possible certs that were available to me and both times it must have used an ad-hoc certificate. I went back to 1.x and rebuilt it. I preferred the ability to remove and add certificates manually at this stage. Always avoided confusion for me. ",8,train
TISTUD-1496,Trailing semicolon after curly brace in conditional causes error in JS formatting,"Steps to reproduce: 1. Create a new .js file in a project 2. Copy the following code and paste it into the .js file {code} if ( i == _i) {} else {}; {code} 3. Press command+shift+f on mac to format the pasted code Actual result: The following error is generated in the log file: !ENTRY com.aptana.formatter.epl 4 0 2012-04-05 11:14:39.664 !MESSAGE (Build 3.0.0.1332346356) [ERROR] com.aptana.formatter.epl/debug Error while formatting the code in your editor. Please submit a bug report through Studio's support and include the relevant code which triggered this error. Expected result: The code is formatted correctly. It appears to be that last trailing semicolon. Delete that, and it works.",5,train
TISTUD-1497,"Studio displays iOS ad hoc provisioning profiles as ""development"" when it should be ""distribution""","Studio displays Ad hoc provisioning profiles incorrectly as ""development"". This causes confusion in the following areas: -Preferences displays the displays the type incorrectly -The iOS distribution wizard displays Apple iTunes, Ad hoc, and development profiles (should only display Apple iTunes and Ad hoc profiles) -The iOS Run on device wizard displays Apple iTunes, Ad hoc, and development profiles (should only display development profiles) Special attention must be made to the way we cache provisioning profiles, since a fix to the SDK will not update the ""type"" of the cached provisioning profiles. We have to trigger a flush of the cache if there is a presence of SDK 2.2.0, where previously there wasn't. This is blocked by an SDK bug",8,train
TISTUD-1503,Fix padding on release notes dialog,"The current release notes template is very specific about what content it expects to style. However, this can lead to release notes not having any padding around the edge of the content. Recommend adjusting the styling slightly to accommodate.",3,train
TISTUD-1506,Titanium Studio: Configuration: Preferences > Titanium Studio > Titanium freezes studio,"Navigating to Preferences > Titanium Studio > Titanium freezes studio. This does not occur in the last studio build. Regression. Steps to Reproduce: 1. Open Studio. 2. Navigate to Preferences > Titanium Studio > Titanium. Expected Result: Titanium Preferences should open. Actual Result: Studio freezes, need to force-close.",8,train
TISTUD-1507,Error opening the Titanium preferences when the Desktop SDK is incomplete,"An attached log to TISTUD-1506 revealed this problem. {code} !ENTRY org.eclipse.jface 4 2 2012-04-10 12:55:28.904\ !MESSAGE Problems occurred when invoking code from plug-in: ""org.eclipse.jface"".\ !STACK 0\ java.lang.NullPointerException\ com.appcelerator.titanium.desktop.DesktopSDKEntity.setModules(DesktopSDKEntity.java:54)\ com.appcelerator.titanium.desktop.DesktopSDKEntity.
(DesktopSDKEntity.java:39)\ com.appcelerator.titanium.desktop.TitaniumDesktopSDKLocator.initialize(TitaniumDesktopSDKLocator.java:169)\ com.appcelerator.titanium.desktop.TitaniumDesktopSDKLocator.(TitaniumDesktopSDKLocator.java:52)\ com.appcelerator.titanium.ui.preferences.TitaniumSDKDirectoryFieldEditor.doCheckState(TitaniumSDKDirectoryFieldEditor.java:94)\ org.eclipse.jface.preference.StringFieldEditor.checkState(StringFieldEditor.java:193)\ org.eclipse.jface.preference.StringFieldEditor.refreshValidState(StringFieldEditor.java:409)\ org.eclipse.jface.preference.FieldEditor.load(FieldEditor.java:501)\ org.eclipse.jface.preference.FieldEditorPreferencePage.initialize(FieldEditorPreferencePage.java:307)\ org.eclipse.jface.preference.FieldEditorPreferencePage.createContents(FieldEditorPreferencePage.java:233)\ org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232)\ org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501)\ org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258)\ org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)\ org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)\ org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)\ org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252)\ org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:674)\ org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708)\ org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)\ org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704)\ org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:888)\ org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)\ org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)\ org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)\ org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:886)\ org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1226)\ org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1251)\ org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:262)\ org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:256)\ org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:433)\ org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)\ org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)\ org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938)\ org.eclipse.swt.widgets.Display.observerProc(Display.java:3525)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879)\ org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220)\ org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1092)\ org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2052)\ org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1084)\ org.eclipse.swt.widgets.Control.mouseDown(Control.java:2528)\ org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2007)\ org.eclipse.swt.widgets.Display.windowProc(Display.java:5471)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220)\ org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095)\ org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253)\ org.eclipse.swt.widgets.Display.windowProc(Display.java:5535)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989)\ org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)\ org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)\ org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3610)\ org.eclipse.jface.window.Window.runEventLoop(Window.java:825)\ org.eclipse.jface.window.Window.open(Window.java:801)\ org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215)\ org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54)\ org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)\ org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)\ org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:178)\ org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runCommand(CocoaUIEnhancer.java:393)\ org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:535)\ org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:520)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879)\ org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)\ org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94)\ org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3607)\ org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)\ org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)\ org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)\ org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)\ org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)\ org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)\ org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)\ com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125)\ org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)\ org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)\ org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)\ org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)\ org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)\ sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\ sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)\ sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)\ java.lang.reflect.Method.invoke(Method.java:597)\ org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)\ org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)\ org.eclipse.equinox.launcher.Main.run(Main.java:1410)\ {code} ",3,train
TISTUD-1510,Run iOS preference page loading in the background,See parent,8,train
TISTUD-1511,Run Android preference page loading in the background,,8,train
TISTUD-1513,"TiStudio: Mobile Projects - When creating mobile projects offline, two projects with same guid will sporadically be created in my.appcelerator.com/apps site","Steps to reproduce: 1. Launch Studio with internet connection disabled 2. Create a TiMobile project 3. Relaunch Studio with internet connection enabled 4. Check https://my.appcelerator.com/apps *May need to repeat steps 1 - 4 a couple of times* Actual: Two projects with the same guid are created in my.appcelerator.com/apps site. See attachments. Expected: One project should be created at my.appcelerator.com/apps site *Note:* * Bug not reproducible on Titanium Studio, build: 2.0.0 and 1.0.9 * Bug not reproducible on Windows 7 machine * Bug not reproducible when working from home",8,train
TISTUD-1514,"TiStud: Workspace - When switching workspaces from within TiStudio, TiStudio will not launch",Steps to reproduce: 1. Launch TiStudio 2. Go to File > Switch Workspace 3. Select a different workspace Actual: TiStudio will stay stuck at the log in/splash screen. See attachments. Expected: Should be able to launch TiStudio after switching to different workspace Note: Bug does *not* occur on Windows 7 and Lion (10.7.3),13,train
TISTUD-1515,Blocker: Android : Templates : SingleWindow - After creating an Android only single window template a null pointer exception occurred when launching to the emulator,"Steps to reproduce: 1. Create a Android only single window application 2. Launch on the Emulator Actual result: A null pointer error occurs *Note* This occurred consistently, then I cleared out my avds and sdcards and the issue went away Here is the output to the log {code} !ENTRY org.eclipse.core.jobs 4 2 2012-04-11 16:45:17.583 !MESSAGE An internal error occurred during: ""Launching Titanium Android Emulator - singleAnd"". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.mobile.launching.FastDevLaunchConfigurationDelegate$1.terminate(FastDevLaunchConfigurationDelegate.java:56) org.eclipse.debug.core.Launch.terminate(Launch.java:252) com.appcelerator.titanium.core.launching.AbstractSharedProcessLaunch.findOrLaunch(AbstractSharedProcessLaunch.java:170) com.appcelerator.titanium.core.launching.AbstractSharedProcessLaunch.launch(AbstractSharedProcessLaunch.java:92) com.appcelerator.titanium.mobile.android.launching.AndroidSimulatorLaunchConfigurationDelegate.launch(AndroidSimulatorLaunchConfigurationDelegate.java:182) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} *Screenshot attached* Expected result: The app is launched to the simulator ",5,train
TISTUD-1516,Titanium Studio RCP contains JDT plugins,I was trying to verify TISTUD-1442 and found out that I do have JDT plugins in my standalone by default. This is almost a clone of APSTUD-1378 (but this is for Titanium standalone).,13,train
TISTUD-1517,ClassCastException when opening the index.html of a packaged mobile web project,"Running from a dev workspace with latest code in the release branch: 1. Created a Titanium Mobile project with Mobile Web selected as one of the deployment targets; 2. Run Publish > Package Mobile Web and select to create a new project for the Mobile Web app; 3. Open the index.html file from the packaged mobile web project. Actual result: the following exception is generated in the console: {code} Exception in thread ""com.aptana.editor.common.text.reconciler.CommonReconciler"" java.lang.ClassCastException: com.aptana.editor.js.parsing.ast.JSAssignmentNode cannot be cast to com.aptana.editor.html.parsing.ast.HTMLElementNode com.aptana.editor.html.validator.HTMLTidyValidator.handleNode(HTMLTidyValidator.java:400) com.aptana.editor.html.validator.HTMLTidyValidator.access$0(HTMLTidyValidator.java:394) com.aptana.editor.html.validator.HTMLTidyValidator$1.include(HTMLTidyValidator.java:386) com.aptana.editor.html.validator.HTMLTidyValidator$1.include(HTMLTidyValidator.java:1) com.aptana.parsing.util.ParseUtil.treeApply(ParseUtil.java:155) com.aptana.parsing.util.ParseUtil.treeApply(ParseUtil.java:121) com.aptana.editor.html.validator.HTMLTidyValidator.validateAST(HTMLTidyValidator.java:382) com.aptana.editor.html.validator.HTMLTidyValidator.buildFile(HTMLTidyValidator.java:164) com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.runParticipants(CommonReconcilingStrategy.java:277) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:238) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:205) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.initialReconcile(CommonReconcilingStrategy.java:137) com.aptana.editor.common.text.reconciler.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:113) com.aptana.editor.common.text.reconciler.CommonReconciler.initialProcess(CommonReconciler.java:188) org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173) {code} Expected result: no exception occurs. ",3,train
TISTUD-1518,"TiStudio: Dashboard - Drop down does not refresh properly when trying to ""Create new project"" template","Steps to reproduce: 1. Launch TiStudio 2. In Dashboard, go to Develop tab 3. Under Templates, find *Create new project* 4. Hover above drop down Actual: Drop down does not appear. Need to move mouse down to refresh properly. See no_drop_down.png Expected: Drop down should immediately display *Desktop* and *Mobile*. See drop_down.png Notes: Bug does *not* appear on Lion (10.7.3) and Windows 7",8,train
TISTUD-1522,Android and iOS module packagers have launch configuration types but no tab group defined,"When opening ""Run Configuration..."" dialog, we see Android Module Packager and iOS Module Packager in the list, but double-clicking on them causes an error showing there is no corresponding tab group defined. ",13,train
TISTUD-1523,Fail Jenkins build if Studio contains JDT plugins,"As a way of keeping ourselves from accidentally releasing JDT into the wild as part of Studio, we need to fail the Aptana Studio and Titanium Studio builds if either the plugin or standalone versions come packaged with the JDT plugins. This prevents half-baked JDT installs which hen keep a user from later installing the whole JDT proper for module development.",8,train
TISTUD-1525,Unable to click on anchor links in release notes,"# Delete SDK 2.0.1.GA. # Prompt for SDK updates # When the release notes pop up, click on an anchor # View the log file. You'll see a set of errors like: {code} !ENTRY com.aptana.ui 4 0 2012-04-16 23:23:49.344 !MESSAGE (Build 3.0.3.1331579821) [ERROR] unknown protocol: about !STACK 0 java.net.MalformedURLException: unknown protocol: about java.net.URL.(URL.java:574) java.net.URL.(URL.java:464) java.net.URL.(URL.java:413) com.aptana.ui.util.WorkbenchBrowserUtil.launchExternalBrowser(WorkbenchBrowserUtil.java:35) com.appcelerator.titanium.update.ui.TitaniumSDKReleaseNotesDialog$2.changing(TitaniumSDKReleaseNotesDialog.java:191) org.eclipse.swt.browser.WebKit.webView_decidePolicyForNavigationAction_request_frame_decisionListener(WebKit.java:1493) org.eclipse.swt.browser.WebKit.browserProc(WebKit.java:423) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3610) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334) com.appcelerator.titanium.update.handler.TitaniumUpdateHandler.execute(TitaniumUpdateHandler.java:30) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} It appears that the anchors are showing as file:///#viewtypes",5,train
TISTUD-1528,"TiStudio: Preview Site - At Titanium Studio preview site, the builds are skewed to the right","Environment: FireFox, Chrome, and Safari Steps to reproduce: 1. Go to http://preview.appcelerator.com/studio/ Actual: Notice the Studio builds are skewed to the right. See attachment. Expected: The Studio builds should be properly aligned.",3,train
TISTUD-1527,Titanium Studio: Dashboard: Search and Top Ad open in generic browser with no controls,"Using the dashboard search bar or the top ad link (""Reach 1.5 Million Appcelerator Developers"") launches in a generic browser with no controls, providing difficult navigation. To address this, we'll need to switch the code that launches the browser in this case to be the same as the other cases on the dashboard (all other links open an external browser, and that appears to work correctly). it's a matter of triggering a portal action instead of using target=""_new"" as part of the href.",8,train
TISTUD-1529,Studio will start updating the SDK automatically upon launch without showing there is an update available first,"To reproduce: 1. Remove the latest SDK from the mobile SDK directory if it is already downloaded; 2. Start Studio. Expected result: Studio will show a popup on the lower right corner indicating there is an update available, and clicking on it will show a release note dialog and then start downloading the latest SDK. Actual result: Studio will start downloading the latest SDK right away after launching without any user interaction, and no release note dialog is shown. ",8,train
TISTUD-1530,Success dialog closes immediately after Titanium SDK update,"Steps to repro: 1. Launch studio, and update to the latest sdk (remove the latest sdk if necessary first) 2. Wait for the sdk to download and unzip. Expected result: There should be a success dialog at the end of the unzip process which stays on the screen until the user presses OK Actual result: The success dialog quickly appears and then disappears with the progress bar.",3,train
TISTUD-1534,Titanium Studio: Configuration: Preferences > Titanium Studio > Titanium > Default Android SDK inconsistently sorted,"The Android APIs listed in the preferences are not sorted as they are in the run configurations. Screenshots attached. Steps to Reproduce: 1. In Studio, navigate to Preferences > Titanium Studio > Titanium > Default Android SDK. 2. View the sorting of the Android APIs. Expected: The APIs in the preferences are expected to look as they do in the run configurations, as the run configuration sorting looks more orderly. Actual: The preferences APIs are sorted in a way that is inconsistent with the run configurations and is visually confusing.",3,train
TISTUD-1537,Every time you click 'Enable' for 'Enable Cloud Services' a new app gets created,"In TiStudio open the tiapp.xml file of an app with the 2.0.1 GA, and click 'Enable'. An app is created in the cloud services. Click it again and another app is created... Suggested fix: # Check to see if the file is dirty. If yes, alert the user that enabling cloud services will save the file. They can then choose to proceed, or click cancel. # Enable cloud services. # Save the file. ",5,train
TISTUD-1539,"Dashboard's ""Develop"" tab missing content",After upgrading to version 2.0.2.201204171552 from version 2.0.1.201204132053 the develop tab on the dashboard no longer has any samples listed and only one template option. This does not occur in 2.0.1. Regression. Steps to reproduce: 1. Load Titanium Studio. 2. Load the Dashboard. 3. Click the develop tab. Expected Result: The develop page of the dashboard should contain links to samples and templates for developers. Actual Results: The develop page contains only a single template and no samples.,8,train
TISTUD-1540,"Titanium API not showing up at all in CA of a newly created project if ""Build Automatically"" is turned off","If I create a new mobile project, I don't get Titanium or Ti in my CA at all. I need to right-click on project, go to Prioperties > Project Build Path, change the Titanium API, then change back to the original one I wanted (say from 2.0.1GA2 to 1.8.2, click Ok, then go back and change back to 2.0.1GA2).",8,train
TISTUD-1541,CA popup shifts between proposals,"See the attached images # Open a new JS file # Type 'a'. See popup for alert # arrow down to ""Array"" # Note the popup shift Neither is correct. I believe it should have the horizontal spacing of the ""alert()"" case, but the vertical alignment of the ""Array"" case",8,train
TISTUD-1543,"TiStudio: Dashboard - ""API Docs"" does not take you to the API documentation site","Steps to reproduce: 1. Open TiStudio 2. In the dashboard, click on *API Docs* Actual: Link takes you to http://docs.appcelerator.com/titanium/2.0/index.html Expected: Link should take you to http://docs.appcelerator.com/titanium/2.0/index.html#!/api Note: Not a regression. ",8,train
TISTUD-1545,Fail Titanium Studio build if titanium.core plugin is missing rubles,"based on TISTUD-1539, we should fail the build if the Titanium Rubles fail to package. One suggested approach is to copy the plugin, unzip it and manually check for the bundles and fail if they're not there.",8,train
TISTUD-1546,Installer: The link to the software licence agreement does not work.,The link to the Software licence agreement does not open the licence agreement when clicked. This did not happen in the 2.0.0 installer. Not regression as this functionality is new. Steps to reproduce: 1. Download and run the installer. 2. When prompted for the licence agreement click the link. Expected Results: The licence agreement will open in another window for reading. Actual Results: Nothing happens.,8,train
TISTUD-1549,Titanium Studio: Content Assist - content assist menu persistent in the OS if popup info has focus,"Content Assist menu is persistent in the OS if the assist popup info menu has focus (i.e., by clicking on it). Other OS program windows are now obfuscated by the content assist menu until the focus is shifted back to Titanium Studio proper or the regular content assist menu. Screenshot attached. Note: This is a lesser behavior of the fixed TISTUD-913. Steps to Reproduce: 1. Open Studio and create a new project (or open an existing project). 2. Click in the text editor of app.js (or any .js file). 3. Press control + space to bring up the content assist menu. 4. Select any item from the suggestion list by clicking on it. 5. Click on the secondary popup that appears for that particular content assist item. 6. Open any other program (such as Chrome) and move the other program window over the content assist menu. Expected Result: The content assist menu should disappear behind the other program window, as it should have the same OS hierarchy as Titanium Studio. Actual Result: The content assist menu persists and obfuscates the other program window until the focus shifts back to Studio or a regular content assist item.",8,train
TISTUD-1550,Titanium Studio: Content Assist: assist menu intermittently fails to change focus,"The content assist menu will not close at all if the user clicks away. This is intermittent. This is a lesser behavior of TISTUD-1268, which is fixed. Summary of TISTUD-1268: Content assist would intermittently stay open as a stand-alone window until studio was restarted. The TISTUD-1268 fix: If the content assist menu is up, and studio minimizes, the content assist menu will minimize as well. Current Issue: Steps to Reproduce: 1. Open studio, create a new project, or open an existing javascript file. 2. Open content assist. 3. Click away from content assist. Expected Result: Content assist should close. Actual Result: Content assist intermittently stays open and will not close. This window is also persistent in the OS, though that related issue was fixed (TISTUD-913). When studio is minimized, content assist will minimize as well. When studio is maximized, the content assist menu is still there. The only way I could close content assist window was by opening a new content assist window (cntrl + space), which would close the old one, and open a new one which behaves properly.",13,train
TISTUD-1551,CLONE - Unable to correctly parse git version,"Found in Eric's log file. I though this was a duplicate of another ticket, but I can't find the first version. {code} !ENTRY com.aptana.git.core 4 0 2012-03-30 11:52:03.083 !MESSAGE (Build 3.0.0.1332346356) [ERROR] com.aptana.git.core/debug Unable to correctly parse git version 1.7.7.5 (Apple Git-26) !STACK 0 java.lang.IllegalArgumentException: invalid qualifier: 5 (Apple Git-26) at org.osgi.framework.Version.validate(Version.java:195) at org.osgi.framework.Version.(Version.java:161) at org.osgi.framework.Version.parseVersion(Version.java:225) at com.aptana.git.core.model.GitExecutable.version(GitExecutable.java:399) at com.aptana.git.core.model.GitExecutable.clone(GitExecutable.java:431) at com.aptana.git.ui.CloneJob.run(CloneJob.java:86) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}",5,train
TISTUD-1572,Unable to format titanium.js file generated by Titanium Mobile Web project,The file is generated when you package a Titanium mobile web project as a new project in the workspace. The generated project should have a titanium.js file. When I try to format the file I get the following error: !ENTRY com.aptana.editor.js.formatter 4 0 2012-04-19 15:36:03.866 !MESSAGE (Build 3.0.3.1334796284) [ERROR] com.aptana.formatter.epl/debug Cannot recover from the syntax error !STACK 0 beaver.Parser$Exception: Cannot recover from the syntax error beaver.Parser.recoverFromError(Parser.java:697) com.aptana.editor.js.parsing.JSParser.recoverFromError(JSParser.java:623) beaver.Parser.parse(Parser.java:498) beaver.Parser.parse(Parser.java:439) com.aptana.editor.js.parsing.JSParser.parse(JSParser.java:447) com.aptana.editor.js.formatter.JSFormatter.equalContent(JSFormatter.java:295) com.aptana.editor.js.formatter.JSFormatter.format(JSFormatter.java:246) com.aptana.formatter.ScriptFormattingStrategy.doFormat(ScriptFormattingStrategy.java:185) com.aptana.formatter.ScriptFormattingStrategy$1.run(ScriptFormattingStrategy.java:115) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) com.aptana.formatter.ScriptFormattingStrategy.format(ScriptFormattingStrategy.java:111) org.eclipse.jface.text.formatter.MultiPassContentFormatter.formatMaster(MultiPassContentFormatter.java:193) org.eclipse.jface.text.formatter.MultiPassContentFormatter.format(MultiPassContentFormatter.java:135) !ENTRY com.aptana.formatter.epl 4 0 2012-04-19 15:36:03.870 !MESSAGE (Build 3.0.0.1332346421) [ERROR] com.aptana.formatter.epl/debug Error while formatting the code in your editor. Please submit a bug report through Studio's support and include the relevant code which triggered this error. ,8,train
TISTUD-1556,Titanium Studio: Cloud: enabling app cloud services when offline causes partially blank and inconsistent error messages,"If the user enables cloud services for an app while offline, one of the error messages is blank, and the others does not explicitly notify that studio is offline. There is also an inconsistency between popup errors generated by the tiapp.xml, and the new project wizard. However, the log messages are (correctly) the same for both enablement methods (tiapp.xml and new project wizard). Screenshots attached. Log attached. Steps to Reproduce: 1. Go offline. 2. Create a new project with cloud services enabled. Expected Result: A standard popup should appear indicating studio is offline and cloud services could not be activated. An error should be logged. Actual Result: A new-project-wizard-specific error popup appears indicating cloud services could not be activated. There is no mention of being offline. An error message is (correctly) logged to the console indicating an http failure. 3. Dismiss the popup and enable cloud services using the tiapp.xml overview. Expected Result: A standard popup should appear indicating studio is offline and cloud services could not be activated. An error should be logged. Actual Result: A different error popup appears with blank text in the ""Reason"" section. The same console error from before is (correctly) logged.",8,train
TISTUD-1557,Editor: JavaScript Comment Auto-Complete indentation is inconsistent,"If a javascript comment is auto-completed from a closed pair of parenthesis or a closed pair of curly braces, the indentation of the cursor is farther than usual. Screenshots attached. This is a new fail case, as this feature was not implemented in 2.0.1. Steps to Reproduce: 1. Enter javascript code below in editor. {code} function(){} {code} 2. Insert the cursor between the parenthesis and type ""/*"" and press ""enter"". For example: {code} function(/*){} {code} Expected Result: Cursor indentation should be one space away from the asterisk to the left. Actual Result: Cursor indentation is a few spaces away from the asterisk.",8,train
TISTUD-1558,Titanium Studio: JavaScript Comment Auto-Complete fails if on same line as end of previous comment,"If a javascript comment is auto-completed from a line that contains the end of another auto-completed comment, the new completion will fail to complete the comment. Screenshots attached. Steps to Reproduce: 1. Enter javascript code in editor: {code} function(){} {code} 2. Insert cursor at the beginning of the line, type ""/*"", and press enter. For example: {code} /* * */function(){} {code} 3. Insert cursor at the end of the line, type ""/*"", and press enter. For example: {code} /* * */function(){}/* {code} Expected Result: Auto-completion should succeed, for example: {code} /* * */function(){}/* * */ {code} Actual Result: Auto-complete fails, for example: {code} /* * */function(){}/* * {code}",5,train
TISTUD-1559,Titanium Studio: Snow Leopard: Toggle Full Screen menu item exists but is not supported,"In Titanium Studio, the top menu, Window > Toggle Full Screen exists, but is grey-ed out and non-selectable. Full Screen is not supported on Snow Leopard, only on Lion. Steps to Reproduce: 1. Open Titanium Studio. 2. In the top menu, navigate to the Window drop-down menu. Expected Result: Window > Toggle Full Screen should not exist in the menu on Snow Leopard. Actual Result: Window > Toggle Full Screen exists and is grey/not selectable. Full Screen is not supported on Snow Leopard at this time.",3,train
TISTUD-1571,Titanium Studio: Dashboard: Generic External Browser Crashes Studio on Close,"In the dashboard, when the ad link at the top is clicked (""Forging Titanium""), and the generic external browser is closed, studio will crash. Log attached. Also occurs in 2.0.1. This has only occurred using the ""Forging Titanium"" ad. You must refresh the dashboard until this ad appears. This issue is consistently reproducible. This issue affects Windows and Ubuntu, but I could not reproduce on OS X Snow Leopard. Steps to Reproduce: 1. Open Studio. 2. Open the dashboard. 3. Refresh the dashboard (red appcelerator logo) until the ""Forging Titanium"" ad appears at the top of the dashboard. 4. Click on the link to open a new generic browser with the ad content. 5. Close the browser. Expected Result: The browser should close. Actual Result: Studio hard crashes.",13,train
TISTUD-1574,Titanium Studio: Configuration: Ubuntu 11.10: top menu items intermittenly have random order,"The top menu (File, Edit, Window, etc.) has randomly ordered elements on Ubuntu 11.10 intermittently. This does not occur on Ubuntu 10.04, Snow Leopard, or Windows 7. Screenshots attached. No log. Steps to Reproduce: 1. Open studio. 2. Look at the top menu. Expected Result: Menu items should be consistent. Actual Result: Intermittently, menu items are random, but do change to the correct configuration on a second check.",3,train
TISTUD-1576,Unable to package Android module on OSX,Prereqs Install Android SDK Install Android NDK Update settings in Titanium preferences Steps: 1. Create an android module project 2. Package the module Expected results Module is packaged Actual results: NPE in the AntRunner and this following error (Build 1.0.0.qualifier) [ERROR] /Users/nle/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.v20120410131722/module/android/build.xml:228: exec returned: 2 org.eclipse.core.runtime.CoreException: /Users/nle/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.v20120410131722/module/android/build.xml:228: exec returned: 2 org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:452) org.eclipse.ant.core.AntRunner.run(AntRunner.java:384) com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate$PackagingProcess$1.run(AndroidModulePackageLaunchConfigurationDelegate.java:241) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: /Users/nle/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.v20120410131722/module/android/build.xml:228: exec returned: 2 org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:636) org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:662) org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:487) org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) org.apache.tools.ant.Task.perform(Task.java:348) org.apache.tools.ant.Target.execute(Target.java:357) org.apache.tools.ant.Target.performTasks(Target.java:385) org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) org.apache.tools.ant.Project.executeTarget(Project.java:1306) org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32) org.apache.tools.ant.Project.executeTargets(Project.java:1189) org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:662) org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:495) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.ant.core.AntRunner.run(AntRunner.java:378),13,train
TISTUD-1579,"Given a URL to a module ZIP file, install the newer version","Add a dashboard controller when given the URL to a module .zip file, installs the module to the SDK location on disk. * Allow the user to choose either a global install, or a per-project install. * If for a specific project, update the tiapp.xml file (equivalent to what we do now when packaging a module for local distribution)",13,train
TISTUD-1581,Add support for launching BlackBerry debugger,"The new Blackberry simulator utilizes a VMWare appliance. We'll need to launch against that. Improvements: # Add IP address override to launch configuration (see TISTUD-1597 for root IP specification) # Add password override to launch configuration (see TISTUD-1597 as well) Steps to use the integration: # Launch VMWare Device # Find out IP of device. User enters this in the main preference page, or in the launch configuration # Run launch script, passing in IP address, password as arguments: {panel} --ip_address= # required --device_password= # optional, for password-protected devices {panel}",20,train
TISTUD-1588,Create Mockup of new Studio Dashboard,"This incorporates the new configuration tab, allowing users to choose between a ""simple"" and ""advanced"" perspective.",8,train
TISTUD-1590,Split titanium mobile plugin into ui and core plugins,,8,train
TISTUD-1594,Upgrade Module wizard to support BlackBerry projects,"Similar to other platforms, support the creation of BlackBerry modules. We don't yet know exactly the steps involved. ",8,train
TISTUD-1605,"Javascript preview code doesn't include ""other parentheses"" example code","1. Open Preferences > Studio > Formatter 2. Select javascript on the left of the pref page 3. Click the pencil icon to edit the profile 4. Select the ""Spaces"" tab The preview block of code doesn't seem to have any examples of the ""Other parentheses"" code, since changing those values don't seem to have any effect.",2,train
TISTUD-1610,Add a Preference page to manage Keystore certificates,"We should adopt the Adobe AIR certificate management UI. See attached for Adobe AIR cert. management UI in Studio 1.5 (we can probably reuse this code) There should be a new Android preference page (similar to iOS), that contains a table of current keystore certificates, and an Add and Remove buttons",13,train
TISTUD-1611,Update the existing keystore dialog to allow users to either specify an existing keystore or create a new one,"Add radio buttons to the dialog that allows the user to specify either an existing keystore from the disk or adding a new one. If an existing one is selected, we need to have a password field but not others.",8,train
TISTUD-1612,"Update the Android distribution wizard/launch configuration to allow user to pick from the existing list of certificates (combo box), or to create a new one",-Replace the textbox with a combo box that contains the list of keystore certificates -The certificate added from the Browse button should automatically add the certificate to the list -New button will trigger the same keystore dialog as before,8,train
TISTUD-1613,Allow user to register their GitHub account inside Studio,"I would like to be able to log in to my Github account and save my account information, possibly in our new ""Accounts"" preference page. Store: * Username * Password Additional buttons/links: * Test (to test the login credentials) * Sign up (to sign up for Github, which directs to the website) ",13,train
TISTUD-1614,"When importing a Git project, add available GitHub repos to the options","Update the Git import dialog: # Add a radio button in front of the existing URI option # Add another radio button with ""Github"" below. When the radio button is selected, it shows a list of repos in a dropdown via the Github REST API http://developer.github.com/v3/repos/ ## The destination field is shared between the two fields # If I have not logged into Github, show a message with ""Add Github Account"". Clicking on the link either pops up a u/p field in place, or directs me to the preference page to add the items # Once I've added the u/p, the page refreshes to show my repos. # If I select a Github repo, it then clones it into my local workspace",13,train
TISTUD-1615,Allow a user to upload a new project to GitHub,"This assumes that the project has not created a local repo or the local repo has no remote. # Right click on a project # Team > Create on GitHub... ## Name of repo ## Description of repo ## Organization you wish to publish to ## Public/Private radio button See http://developer.github.com/v3/repos/ for information on publishing a new repo We should be proactive about seeing if we can test if a user has rights to create a repo within an organization, and if they have rights to make a repo private so we can alert them before the creation process. ",13,train
TISTUD-1616,"Add ability to log out of Jira account for ""Submit a ticket""",Once logged into Jira inside Titanium Studio you cannot seem to log out and your name is retained between user logins. Steps to reproduce: 1. Log into Titanium Studio using one account. 2. Open Jira through the Help > Titanium Studio > Submit a ticket 3. Log into Jira via the top of the form and the validate button. 4. Log out of Titanium Studio. 5. Log into Titanium Studio using a second account. 6. Open Jira through the Help > Titanium Studio > Submit a ticket. Expected Result: Previous users Jira account should be cleared and the user should be prompted for username and password. Actual Result: The first user is still logged in with no way to log out.,8,train
TISTUD-1617,"Submit a ticket wizard only submits the first line of the ""Steps to reproduce"" field.",When a user submits a ticket using the Submit a ticket Jira wizard only the first line of the steps to reproduce is passed into the Jira. Steps to reproduce: 1. Submit a ticket with multiple lines in the steps to reproduce field. Expected results: All lines will appear in the Jira ticket on the web site. Actual results: Only the first line is passed into the Jira.,5,train
TISTUD-1622,Need to be able to configure ACS url for staging testing purpose,"Right now studio has hard coded api.cloud.appcelerator.com, in order to test in staging environment, we need to be able to change it to point to api.staging.cloud.appcelerator.com instead",5,train
TISTUD-1626,CLONE - Need to be able to select javascript modules from TiStudio Modules panel,"With support for JavaScript (commonJS and MobileWeb) modules being added, we now need the ability to display and select javascript modules in the TiStudio Modules panel. # Show the (currently-hidden) modules # In the popup to select per-platform versions, for commonjs modules, only show a single drop down for selecting a version which will apply across all platforms.",8,train
TISTUD-1627,Add support for creating javascript modules to TiStudio,"Add the ability to create a javascript module (commonJS or MobileWeb, depending on implementation of MOD-701).",8,train
TISTUD-1630,"""Aptana"" is shown under the main Help menu on Titanium Studio standalone installation","Not necessarily reproduceble, but on a brand new Titanium Studio installation on a Mac 10.7.2 machine, ""Aptana"" instead of ""Titanium Studio"" is displayed under Help. Also the preference page node has Aptana Studio instead Titanium Studio as well, so look like one or more overriding plugins didn't get loaded. Here is how I got into this state: 1. Download Titanium Studio 2.0.1 Mac zip from preview.appcelerator.com/studio; 2. Add http://preview.appcelerator.com/appcelerator/studio/standalone/update/beta/ update site and update to the latest 2.0.2 beta. ",8,train
TISTUD-1631,"File JIRA tickets for Titanium Studio in the ""Titanium Community"" project","When filing a ticket inside Titanium Studio using the new JIRA integration (APSTUD-2916), we need to file the ticket in APSTUD if it came from Aptana Studio, and TC if it came from Titanium community",8,train
TISTUD-1632,Re-configure JIRA ticket submission fields to better match current ticket guidelines ,"When filing a ticket in JIRA, we need to reconfigure the current fields ever so slightly. Instead of a single ""Steps to Reproduce"" we need three fields: * Steps to Reproduce* * Actual Result* * Expected Result (*d fields are required) From a space perspective, ""Steps"" should be 2X the height of the other two. When the ticket is filed, replace any empty fields with ""N/A"", and use the following template: {code} h3. Steps to Reproduce [Steps] h3. Actual Result [Actual] h3. Expected Result [Expected/N/A] {code}",8,train
TISTUD-1633,Titanium Studio: android module fails to create with internal error,"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. Create new android module from studio. Expected Result: Module creates. Actual Result: Module fails to create.",8,train
TISTUD-1640,Titanium Studio: MobileWeb: preview in emulator/browser fails with NPE,"When a mobileweb project is previewed in emulator or browser, there is a silent failure in the UI, and an NPE error in the log. Log attached. This does not occur in Studio 2.0.1. Steps to Reproduce: 1. Create a new mobileweb project. 2. Preview in Browser and Preview in Emulator. Expected Result: App should preview in browser or emulator. Actual Result: Silent UI failure (no popup, no visual response), null pointer exception logged to studio log.",5,train
TISTUD-1642,Titanium Studio: Login: studio does not auto-login on Linux,"When studio launches, the user always has to enter login information (i.e., the auto-login never occurs). Steps to Reproduce: 1. Run studio on Linux. 2. Enter appcelerator login information. 3. Close and relaunch studio. Expected Result: Studio should auto-login. Actual Result: The user is prompted to enter studio login information every time.",13,train
TISTUD-1643,Remove the text in Windows installer about restarting the machine after uninstallation since it is not necessary,"When studio is installed using the installer and the machine is rebooted after prompt, the installer does not relaunch on machine reboot. The installer must be manually run to continue the installation. Steps to Reproduce: 1. Run the studio installer on Windows. 2. Reboot the machine on prompt. Expected Result: Installer should relaunch after machine reboot. Actual Result: Installer does not relaunch. It must be manually relaunched to continue installation.",8,train
TISTUD-1645,Titanium Studio: Titanium Preferences: Default Android SDK changed if not saved and sdk path is reloaded,"In Preferences > Titanium Studio > Titanium, if the Default Android SDK is changed and the user clicks on the Android SDK Home text field, then clicks in a different text field (e.g., Android NDK Home), the Default Android SDK change will be undone if it was not previously saved. This is a usability issue because the user's edits are automatically undone. Steps to Reproduce: 1. Go to Preferences > Titanium Studio > Titanium. 2. In the Default Android SDK drop-menu, change the SDK to a different version (but do not save the changes). 3. Click in the Android SDK Home text field. 4. Click in the Android NDK Home text field. Expected Result: The changes made to the Default Android SDK should remain. Actual Result: The old Default Android SDK is automatically selected.",5,train
TISTUD-1664,TiStudio: Encoding problem with Git Commit Message,"Same problem on Ti Studio. https://jira.appcelerator.org/browse/APSTUD-4043 (Aptana bug) -------- The problem is that when i git commit with comments in Japanese(or Korean), i get unreadable by git log on terminal(utf-8). (I can read in Titanium studio history window. but unreadable by other tools) by the way, One repository that was make another machine (ex:ubuntsu) and it has commit message in UTF-8(Japanese). I Pull to Titanium Studio. The history is unreadable.",8,train
TISTUD-1647,Titanium Studio: MobileWeb: preview in android emulator initially fails with server errors when AVD is first created,"When deploying from studio, or manually running a mobileweb app in the android emulator browser, the app will not run and server related errors log to the console when a new AVD is created. Logs attached. This is not a regression, as it does occur in Studio 2.0.1. Steps to Reproduce: 1. Delete .android/avd/ 2. Create a default mobileweb project. 3. MobileWeb Preview in Emulator. Expected Result: Emulator should launch, emulator browser should load, app should run. Actual Result: Emulator launches, emulator browser does not load. Manually opening the browser and navigating to the app url results in a failed app load.",8,train
TISTUD-1648,Titanium Studio: Modules: android modules created on command line cannot be packaged in studio,"Android modules created from command line cannot be packaged in studio. There is no package option in the UI. Note: Android modules created in studio, and iPhone modules created from the command line, work as expected. Steps to Reproduce: 1. Create an android module from the command line. 2. Import the module into studio. 3. Attempt to package the module (i.e., box icon > Package Android Module). Expected Result: Package option should be available. Actual Result: Package option is not available. h3. Suggested solution When importing an existing Titanium project, check for the existence of a timodule.xml file, and set the builders/natures appropriately.",8,train
TISTUD-1649,Titanium Studio: MobileWeb: no option to package mobileweb modules,"MobileWeb modules do not have the option to package from studio. Note: MobileWeb modules cannot be created in studio 2.0.1, so this feature cannot be tested in studio 2.0.1. This is a new fail case. Steps to Reproduce: 1. Create a mobileweb module. 2. Attempt to package the module (box icon > Package MobileWeb Module). Expected Result: The package option should be available in the packaging drop-down menu. Actual Result: There is no mobileweb module packaging option. MobileWeb projects can be created in studio, but not packaged.",13,train
TISTUD-1650,Titanium Studio: change default workspace to one without spaces to support module development,"Currently, the default studio workspace is Titanium Studio Workspace. Because the workspace contains spaces, Android modules cannot be packaged. One suggestion is to change the default workspace to one without spaces to facilitate module development. As per discussion, it was suggested to use: Titanium_Studio_Workspace",5,train
TISTUD-1666,Restart of Titanium Studio Required for the tiapp editor to display modules added after Studio was launched,"h3.Experience Currently, the list of modules appears to only be loaded into Titanium Studio at startup. Modules added to the Library folder after Titanium Studio has launched are not seen in the Modules pane of the tiapp editor. This requires a restart of Titanium Studio. h3.Expectation When the tiapp editor is opened that all modules are available for inclusion. h3. Solution Modules folder(s) needs to be rescanned when the tiapp editor is opened.",8,train
TISTUD-1656,App is created with NULL creator_user_id.,"h4. Problem Description I published an App to the App Store and Google Play but the app never appeared on ""My Apps"". The original guid was: 2c9e1129-86d4-4f9d-9f0d-4d7bd0cd764a Because I noticed new projects showed up on ""My Apps"" I've created a new project and transplanted the guid to the tiapp.xml of my app. Released it to the Play Store and this enabled the app to show on ""My Apps"" where it says ""122 analytics events were processed for this application since May 1, 2012"" but it still shows 0 users, 0 sessions and ""There were no events logged during between 5/7 and 5/13."" The new guid is: 473b9203-836a-4d48-ac13-2993873efa2c I wrote more about this in http://developer.appcelerator.com/question/136456/my-app-doesnt-show-in-analytics but haven't received any feedback. Can you take a look?",5,train
TISTUD-1662,Editor: JavaScript Comment Auto-Complete initially fails to recognize preexisting blocks and cursor is incorrectly positioned,"JavaScript Comment Auto-Complete initially fails to recognize preexisting blocks and cursor is incorrectly positioned. I am marking this as a bug because the auto-comment partially works, and I can get into this bad state. Screenshot attached. The auto-complete kicks in after pressing enter twice, but the cursor is on the wrong line. Steps to Reproduce: 1. Enter code in JS file: {code} /**/ {code} 2. Insert cursor between the two asterisks (in the middle of the block comment) and press enter. Note: A vertical bar character is used to simulate the resulting position of the cursor. Expected Result: {code} /* * | * */ {code} Actual Result: {code} /* |*/ {code} 3. Press enter again. Expected Result: {code} /* * * | */ {code} Actual Result: {code} /* *|*/ {code} 4. Press enter again. Expected Result: {code} /* * * * | */ {code} Actual Result: {code} /* * *|*/ {code}",8,train
TISTUD-1669,Titanium Studio: Preferences: cannot edit or leave titanium preferences menu with invalid values error,"If the titanium preferences menu is opened, the user cannot navigate to a different menu. There is a pop-up with an invalid values error. Screenshot attached. Also, if individual titanium preferences are edited, the changes cannot be applied. The only way to leave the menu is to press cancel or close the entire preferences window. Screenshot attached. There are no log entries. This does not occur in 2.0.1 (regression). I do not believe this occurred in yesterday's build. Steps to Reproduce: 1. Open studio, navigate to the titanium preferences menu (Preferences > Titanium Studio > Titanium). 2. Attempt to navigate to a different menu (e.g., press General). Expected Result: The menu should change. Actual Result: Pop-up error indicating invalid values. Menu does not change. 3. Change the Android SDK version (or any setting in the titanium preferences menu). 4. Apply the changes (press Apply). Expected Result: The changes should be saved. Actual Result: Apply is not selectable. Note: The titanium preferences menu can only be exited by pressing Cancel or closing the entire preferences menu (press the window X).",5,train
TISTUD-1671,Titanium Studio: Multiline Search: enter newline keyboard shortcuts edit the wrong text area,"When the multiline search box is up, and the enter new line keyboard shortcuts are used, the characters are entered in the active .js file instead of the search field. Screenshot attached. No log files. Not testable in studio 2.0.1 (new fail case). Command + Enter will add new lines to the .js file. Control + Enter will add visible '\n' characters to the end of the first line in the .js file. Steps to Reproduce: 1. Open studio, open a .js file (create a new project if necessary). 2. Open multiline search (Command + f in osx). 3. Click in the search box to give it focus and place the cursor inside the search box. 4. Press Command + Enter a few times (on osx only). 5. Press Control + Enter a few times. Expected Result: New lines should be added to the search box. Actual Result: New lines and visible '\n' characters are added to the active .js file.",8,train
TISTUD-1672,"Titanium Studio: Multiline Search: history and scope icons are inactive, only down arrow displays drop-down list","Search history icon does not function when clicked. Only the small down arrow next to the icon will display the search history drop-down menu. Screenshot attached. This is a valid issue, as this is how the run configuration icons function, in addition to basic usability. This also affects the scope icon. Note: There are two history icons, one for search and one for replace (both fail). Steps to Reproduce: 1. Open studio, open js file (create new project as needed). 2. Activate search (command + f on osx). 3. Click on the history icon (flashlight) or the scope icon. Expected Result: A search history drop-down list should display. Actual Result: The icon blinks. However, the small down arrow next to the icon functions correctly.",5,train
TISTUD-1673,Titanium Studio: Multiline Search: enable horizontal scrolling in search and replace boxes,"In the search and find text areas, vertical scrolling (i.e., by mouse scroll) is enabled, but not horizontal scrolling. This impairs the functionality of the fields because longer text lines cannot be easily navigated. The only way to scroll horizontally is to use the highlight functionality of the cursor (not ideal). Screenshot attached. Steps to Reproduce: 1. Open studio, open a js file. 2. Open search bar (command + f on osx). 3. Enter long line of text (longer than the search field itself) into search field. 4. Attempt to scroll horizontally. Expected Result: Search field (and replace field) should scroll horizontally to easily view the entire line of text. Actual Result: Nothing happens. The workaround is to use the highlight or left/right arrow functionality of the cursor to drag/move left and right.",2,train
TISTUD-1674,"Titanium Studio: Multiline Search: add ""Select All"" command to select all to search and replace boxes","When clicking on text in the search or replace boxes, it is difficult to select all the text. Steps to Reproduce: 1. Open studio, create a new project, open the app.js file. 2. Open search bar (command + f on osx). 3. Copy/paste a larger block of code in the search box. 4. Attempt to use the ""Select All"" command to select all the text Expected Result: All text in the box highlights. Actual Result: Select all doesn't work.",5,train
TISTUD-1677,Multiline Search: find should jump to string matches when scope is set to open files,"When two js files are open, each containing a particular string, and that string is searched-for from the search bar using the scope setting: open files, the find button does not jump the cursor to the matching string instances. The matches are recognized and highlighted when find is pressed, but the specific matches are not iterated using the find button. Steps to Reproduce: 1. Open studio, create a new project. 2. Add a new js file to the project. 3. Add any string (e.g., xxx) to both app.js and the other .js file. 4. Make sure both files are open in the editor. 5. Open the search bar (command + f in osx). 6. Click on Scope (the down arrow next to it) and set it to Open Files. 7. Enter the string that exists in both files (e.g., xxx) into the search field. 8. Click find a few times. Expected Result: The cursor should iterate through the instances of the matching string. Actual Result: All instances highlight, but the cursor does not iterate, and the second file never gets focus (to view it's string match). The cursor",8,train
TISTUD-1678,Android: allow users to launch x86 emulator,"h2. Description Developers need to be able to leverage the Android x86 emulator that was made available with Android SDK r17. It claims to have performance increases beyond the standard emulator making for a better development experience. h2. Proposed Solution(s) It would be good if you could specify by default whether you want to use the x86 or standard emulator for all projects, perhaps in {{Preferences -> Titanium Studio -> Titanium}}. It should be the standard emulator by default as the x86 emulator currently does not include the Google APIs (which would prevent the KitchenSink from running) and it does not support V8, as detailed in the linked ticket. Also, it should be configurable on a per-project basis as well, for the same reasons I listed in the above paragraph. So: # We need to upgrade our AVI detection to show the available ABIs per device # For devices with multiple ABIs we need to allow the user to select which one to use as part of the launch configuration, and that is passed as the first argument to the SDK for SDKs 2.1+. For < 2.1, we only pass the device argument # We could add a preference in Titanium Preferences to default to x86 or standard emulator (were available). This would se the default ABI selection in the launch configuration. ",13,train
TISTUD-1680,Better error hinting with regard to non-UTF-8 characters for android,"h2. Problem When a non-UTF-8 character is found in a Titanium editor window, TiStudio will mark the file containing it with an error in the gutter. Doing a mouse over on this error reveals the following error message. {code:lang=none} File needs to be in UTF-8 encoding for Android. Decoding failed near byte 0. {code} Unfortunately for me, the non-UTF-8 character was no where near byte 0. It was actually at byte 1193 as shown in the Android error log when attempting to ignore TiStudio's error and run the application anyway: {code:lang=none} [ERROR] Exception occured while building Android project: [ERROR] Traceback (most recent call last): [ERROR] File ""/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/builder.py"", line 2125, in [ERROR] s.build_and_run(True, avd_id, device_args=device_args) [ERROR] File ""/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/builder.py"", line 1867, in build_and_run [ERROR] True, project_dir = self.top_dir, include_all_ti_modules=include_all_ti_modules) [ERROR] File ""/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/android.py"", line 301, in create [ERROR] self.build_modules_info(resource_dir, app_bin_dir, include_all_ti_modules=include_all_ti_modules) [ERROR] File ""/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/android.py"", line 170, in build_modules_info [ERROR] compiler.compile(compile_bytecode=False, info_message=None) [ERROR] File ""/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/compiler.py"", line 250, in compile [ERROR] js_contents = self.make_function_from_file(fullpath) [ERROR] File ""/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/compiler.py"", line 209, in make_function_from_file [ERROR] file_contents = codecs.open(path,'r',encoding='utf-8').read() [ERROR] File ""/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/codecs.py"", line 671, in read [ERROR] return self.reader.read(size) [ERROR] File ""/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/codecs.py"", line 477, in read [ERROR] newchars, decodedbytes = self.decode(data, self.errors) [ERROR] UnicodeDecodeError: 'utf8' codec can't decode byte 0xa9 in position 1311: invalid start byte {code} h2. Proposed Solution Return a byte position that more closely represents the location of the offending non-UTF-8 character. Also, if possible, move the error marker in the gutter from the first line of the file to the appropriate line in the file. h2. Test Case The following comments should be enough to show what I mean. The character after the word ""Copyright"" is the one causing the error, but TiStudio reports the error at byte 0. {code:javascript} // ========================================================================= // // xmlw3cdom.js - a W3C compliant DOM parser for XML for