issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
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 <module> [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 <SCRIPT> // // version 3.1 // // ========================================================================= // // Copyright (C) 2002, 2003, 2004 Jon van Noort ([email protected]), David Joham ([email protected]) and Scott Severtson // // This library is free software; you can redistribute it and/or // modify it under the terms of the GNU Lesser General Public // License as published by the Free Software Foundation; either // version 2.1 of the License, or (at your option) any later version. // This library is distributed in the hope that it will be useful, // but WITHOUT ANY WARRANTY; without even the implied warranty of // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU // Lesser General Public License for more details. // You should have received a copy of the GNU Lesser General Public // License along with this library; if not, write to the Free Software // Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA // // visit the XML for <SCRIPT> home page at xmljs.sourceforge.net // // Contains text (used within comments to methods) from the // XML Path Language (XPath) Version 1.0 W3C Recommendation // Copyright � 16 November 1999 World Wide Web Consortium, // (Massachusetts Institute of Technology, // European Research Consortium for Informatics and Mathematics, Keio University). // All Rights Reserved. // (see: http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929/) {code}
| 8 |
train
|
TISTUD-1685
|
Allow users to tab between fields in JIRA "Submit Ticket" dialog
|
h3. Steps to Reproduce # Choose Help > Titanium Studio > Submit Ticket... # Attempt to tab betwen fields # It instead inserts a tab into the current field h3. Actual Result Inserts a tab into the current field h3. Expected Result Tabs between fields
| 3 |
train
|
TISTUD-1681
|
Dashboard's Configure page has two platform "spinners" that never get replaced by content
|
When I load the Dashboard on my Win7 VM and then click the "Configure" tab, MobileWeb appears, but there are two spinner placeholders (for IOS and Android?) that never get replaced by content.
| 8 |
train
|
TISTUD-1682
|
Studio: Local variables do not appear in content assist
|
Local variables do not appear in content assist. This is a regression issue (did not appear in 1.0.9). Steps to reproduce: 1. In a JavaScript file enter: {code} function myFunction(myParam){ var newLocal = my } {code} 2. Invoke content assist after the my on the unfinished line. Expected results: Content assist should suggest myFunction and myParam as options. Actual results: Content assist shows only myFunction as an option. First reported in [this post|http://developer.appcelerator.com/question/137164/titanium-studio-20-autocomplete---local-variables].
| 13 |
train
|
TISTUD-1683
|
Out of Memory error indexing ti.jira module
|
When I was testing module installation in TISTUD-1579, I ran into this issue after the module got unzipped to a project. The module involved was ti.jira 1.2.1 ("JIRA Module" in the marketplace). {code} !ENTRY org.eclipse.core.jobs 4 2 2012-05-21 13:36:05.558 !MESSAGE An internal error occurred during: "Building workspace". !STACK 0 java.lang.OutOfMemoryError: Java heap space java.util.HashMap.<init>(HashMap.java:187) java.util.HashMap.<init>(HashMap.java:199) com.aptana.internal.index.core.DiskIndex.readCategoryTable(DiskIndex.java:1099) com.aptana.internal.index.core.DiskIndex.addQueryResults(DiskIndex.java:303) com.aptana.index.core.Index.query(Index.java:547) com.aptana.editor.js.contentassist.index.JSIndexReader.getFunctions(JSIndexReader.java:306) com.aptana.editor.js.contentassist.JSIndexQueryHelper.getFunctions(JSIndexQueryHelper.java:84) com.aptana.editor.js.contentassist.JSIndexQueryHelper.getMembers(JSIndexQueryHelper.java:192) com.aptana.editor.js.contentassist.JSIndexQueryHelper.getGlobals(JSIndexQueryHelper.java:124) com.aptana.editor.js.inferencing.JSNodeTypeInferrer.visit(JSNodeTypeInferrer.java:641) com.aptana.editor.js.parsing.ast.JSIdentifierNode.accept(JSIdentifierNode.java:33) com.aptana.editor.js.parsing.ast.JSTreeWalker.visit(JSTreeWalker.java:176) com.aptana.editor.js.inferencing.JSNodeTypeInferrer.getTypes(JSNodeTypeInferrer.java:260) com.aptana.editor.js.inferencing.JSNodeTypeInferrer.visit(JSNodeTypeInferrer.java:491) com.aptana.editor.js.parsing.ast.JSFunctionNode.accept(JSFunctionNode.java:46) com.aptana.editor.js.parsing.ast.JSTreeWalker.visit(JSTreeWalker.java:176) com.aptana.editor.js.inferencing.JSSymbolTypeInferrer.processValues(JSSymbolTypeInferrer.java:560) com.aptana.editor.js.inferencing.JSSymbolTypeInferrer.getSymbolPropertyElement(JSSymbolTypeInferrer.java:352) com.aptana.editor.js.inferencing.JSSymbolTypeInferrer.getSymbolPropertyElement(JSSymbolTypeInferrer.java:389) com.aptana.editor.js.inferencing.JSSymbolTypeInferrer.getScopeProperties(JSSymbolTypeInferrer.java:292) com.aptana.editor.js.contentassist.index.JSFileIndexingParticipant.processParseResults(JSFileIndexingParticipant.java:216) com.aptana.editor.js.contentassist.index.JSFileIndexingParticipant.index(JSFileIndexingParticipant.java:104) com.aptana.core.internal.build.IndexBuildParticipant.buildFile(IndexBuildParticipant.java:104) com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) com.aptana.core.build.UnifiedBuilder.buildFile(UnifiedBuilder.java:520) com.aptana.core.build.UnifiedBuilder.doBuildFiles(UnifiedBuilder.java:432) com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:409) com.aptana.core.build.UnifiedBuilder.incrementalBuild(UnifiedBuilder.java:232) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:168) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) {code}
| 8 |
train
|
TISTUD-1694
|
TestFlight Publish confirmation dialog is missing content
|
When a TestFlight publish is complete, the confirmation dialog has yes/no buttons, but does not pose a question. This may apply to the entire publish extension, so the fix may be in the default implementation
| 5 |
train
|
TISTUD-1695
|
Titanium Studio: Project Explorer: Close Project and Open Project not updated until re-click on project
|
Project > Open, and Project > Close command availability are not updated in real time for projects in the Project Explorer. The old project options are still available (e.g., Close is available if the project is already closed). Re-clicking the project in the explorer will update the Project menu options. This is not a regression. There is no log info. Fail Cases: 1. Project Explorer: Cannot open a newly closed project. 2. Project Explorer: Cannot close a newly opened project. Note: Project Explorer: Cannot close a freshly created project. - This is an invalid case as tiapp.xml has focus. Steps to Reproduce: 1. Click a project in Project Explorer to manually refresh Project menu options. 2. Click Project > Close to close project. 3. Click Project. Expected Result: Project > Open should be available. Actual Result: Open is not available. If the project is re-clicked, it will become available. 4. Re-Click project in Project Explorer to manually refresh Project menu options. 5. Click Project > Open to open project. 6. Click Project. Expected Result: Project > Close should be available. Actual Result: Close is not available. If the project is re-clicked, it will become available.
| 8 |
train
|
TISTUD-1697
|
Titanium Studio: App Explorer: opening a project in Project Explorer changes selected project in App Explorer
|
When a project is opened after being closed in the Project Explorer, the App Explorer selected project is updated to the recently opened project. It is expected the selected project in the App Explorer would only change if it is deleted or manually changed. However, the App Explorer selected project is not updated (correctly) if a new project is created. This is not a regression. There is no log info. Steps to Reproduce: 1. Create two projects. 2. In the App Explorer, select the first project. 3. In the Project Explorer, select the second project. 4. Close the second project using Project > Close. 5. Open the project using Project > Open (reselect project if Project menu commands do not update). 6. Navigate to the App Explorer. Expected Result: The first project should be selected (the first one that was selected). Actual Result: The second project is selected (the one that was recently opened).
| 8 |
train
|
TISTUD-1698
|
Titanium Studio: Editor: reopening open project file via Project Explorer Local Filesystem results in duplicate mirror file in editor
|
If a file that is open in the editor is opened again using the Project Explorer Filesystem, there is a resulting mirror copy of the file in the studio editor. This is not a regression. There is no log info. Steps to Reproduce: 1. Create a new project. 2. Open app.js if it isn't open already from the Project Explorer project folder. 3. Go to Project Explorer > Local Filesystem, navigate to app.js (the same file) and open it. Expected Result: The original open version of the file should gain focus. Actual Result: Another copy of the same file will open in the editor resulting in two duplicate open files. Edits to one file are mirrored in real-time to edits in the other file.
| 8 |
train
|
TISTUD-1700
|
"Search > Search" and "Search > File" bring up same menu
|
Search > Search and Search > File bring up the same menu. Alternately, PyDev is missing from the Search drop down (e.g., Search > PyDev...). Titanium Behavior: In the Search drop-down, there are two options (Search, and File...). Search > Search brings up the search menu. Search > File... brings up the search menu with identical settings. There is a second tab in the search menu for PyDev that is not selectable from the command drop-down list. Eclipse Behavior: In Eclipse, there are three search options (Search, File..., and JavaScript...). Search > Search brings up the search menu with the JavaScript tab selected. Search > File... brings up the search menu with the File tab selected. Search > JavaScript... brings up the search menu with the JavaScript tab selected. There is a third Java tab that exists in the menu, but is not accesible from a drop-down command. The issue is Titanium should either remove Search > File... because it brings up a duplicate menu, or add Search > PyDev... to access the PyDev tab in the search menu. This is not a regression. There is no log info. Steps to Reproduce: 1. Open Studio. 2. Go to the Search drop-down menu at the top. Expected Result: Search > File... should not exist, or Search > PyDev... should exist. Actual Result: Search > Search and Search > File... bring up identical menus.
| 8 |
train
|
TISTUD-1701
|
Editor: changing file type then reopening does not reflect new file type
|
If a file is open in the editor, and the file type is edited in the project explorer, the open file in the editor is not fully updated. See info in Expected/Actual Result below. The file will only update if it is closed and reopened. Clicking on the file will not update it. Relaunching studio will not update it. This is not a regression. There is no log info. Steps to Reproduce: 1. Create a new project. 2. Add a generic typeless file to the project. 3. Add JavaScript code to the file. Verify lack of syntax highlighting. 4. While project is open in editor, change the filetype of the file in the project explorer to .js. Expected Result: 1. The filename should change in the project explorer. 2. The icon for the file in the project explorer should update. 3. The filename should change in the open file editor. 4. The icon for the file in the open file editor should update. 5. The syntax highlighting in the open file should update. 6. The error info in the open file should update. Actual Result: 1. The filename should change in the project explorer. - YES 2. The icon for the file in the project explorer should update. - YES 3. The filename should change in the open file editor. - YES 4. The icon for the file in the open file editor should update. - NO 5. The syntax highlighting in the open file should update. - NO 6. The error info in the open file should update. - NO Note: Double-Clicking on file or relaunching studio will not update the file formatting. Only closing and reopening file will reformat it.
| 13 |
train
|
TISTUD-1702
|
Titanium Studio: code selection highlighting artifacts exist in some themes when cursor pressed and dragged down then up
|
In some themes, when the cursor is pressed to highlight a selection, dragged down over code, then dragged back up, there are highlight artifacts in the code editor display. Screenshot attached. No log info. This is not a regression. I tested all themes A-E. Themes affected: Aptana Studio 2.x All Hallow's Eve Eclipse Expresso Libre Steps to Reproduce: 1. Open Studio. 2. Change theme to an affected theme from above (i.e., Aptana Studio 2.x). Preferences > Titanium Studio > Themes. 3. Create a new project. 4. Open app.js. 5. Click and hold down the cursor/mouse button in the middle of the code file. Drag down then up. Expected Result: No highlight artifacts in the lower code. Actual Result: Highlighting artifacts in the lower code. See screenshot.
| 8 |
train
|
TISTUD-1703
|
Titanium Studio: alpha highlight fails for some themes on initial preference change
|
When a block of code is highlighted and the theme preference is changed to certain themes, the highlighting intermittently fails until file reload. This is not a regression. This is only known to affect Windows 7 and Ubuntu 12.04, but not OS X. This is known to affect the following themes: idleFingers iLife 05 Steps to Reproduce: 1. Create a new project, open app.js. 2. Highlight an arbitrary block of code (and keep it highlighted). 3. Go to Preferences > Titanium Studio > Themes. 4. Change the theme to iLife 05 (for example). Click apply. 5. Move the preference window to view app.js. Expected Result: Highlighting alpha should be correctly applied. Actual Result: Highlighting alpha is not working. If the preference is accepted and the file is used, highlighting will be broken until the app is reopened. This is an intermittent issue.
| 8 |
train
|
TISTUD-1704
|
Titanium Studio: App Explorer: Local Filesystem root has no name on Linux
|
On Linux, the Project Explorer Local Filesystem root directory has no name. This does not affect Windows 7 or OS X Snow Leopard. This is not a regression. Steps to Reproduce: 1. Open studio. 2. Navigate to Project Explorer. 3. Navigate to Local Filesystem. 4. Navigate to the root directory. Expected Result: Root directory should have a name. Actual Result: Root directory does not have a name, it is a blank folder. See screenshot.
| 5 |
train
|
TISTUD-1705
|
Titanium Studio: top menu bar receives events on Linux when other menu windows are open
|
Top menu bar receives events on Linux when other menu windows (i.e., Preferences, About, Search) are open. This can result in multiple preference windows being launched. This is not a regression. This does not affect Windows 7 or Snow Leopard. This does not affect Eclipse on Ubuntu. Steps to Reproduce:prav 1. Open studio. 2. Open a menu window (e.g., Preferences, Search). 3. Click on the top menu bar (i.e., File, Edit, etc.). Expected Result: The top menu bar should not receive any click events. Actual Result: The top menu bar can receive events. However, the main editor frame is correctly blocked from receiving events. As a consequence, many info windows can be launched multiple times (i.e., Search, About). However, the main preferences window can only have one instance.
| 8 |
train
|
TISTUD-1751
|
Improve accuracy of Testflight publish progress indicator
|
During the packaging and subsequent upload of a package to Testflight, the progress bar at the bottom of Studio stalls at 71%. User is unable to determine if the process is proceeding as expected or if a problem has occurred. An active progress indicator would alleviate concerns on the part of the user regarding the progress of their distribution.
| 8 |
train
|
TISTUD-1706
|
Studio: Project Explorer: "Promote to Project" causes position shift in full screen mode
|
When trying to promote a folder to a project in full screen / maximised mode, Titanium Studio moves when the Promote to Project dialogue box opens. This bug is a regression, this issue does not happen in 2.0.1. Steps to reproduce: 1. Open Titanium Studio in Maximised Mode. 2. In the Project Explorer open the context menu for a folder. 3. Select "Promote to Project". Expected Results: The Dialogue box would open without a change in Titanium Studio's location on the screen. Actual Results: Window containing Titanium Studio goes into windowed mode and shifts up on Windows 7, The screen shifts up while staying full screen for Mac OS 10.7.3, and Ubuntu 11.10 shifts into windowed mode but does not move.
| 5 |
train
|
TISTUD-1707
|
Titanium Studio: module packaging to project with dirty tiapp.xml fails to write module xml tags
|
If a module is packaged to a project with a dirty tiapp.xml (i.e., a module was just deleted using the red X), the module xml tags will not be written to the project tiapp.xml. This is not a regression. There is no log. This is related to TISTUD-1666, but this is a separate edge case. Steps to Reproduce: 1. Create a new project. 2. Create a new module. 3. Package the module to the project. 4. Delete the module from the project using TiApp Editor Overview (click the red X to delete module). This will dirty the tiapp.xml file and remove the module xml tags, but keep the module folder in the project. 5. While the editor is still dirty, package the module again to the project. Expected Result: Module should package and appear in TiAPP Editor Overview, xml tags for the module should exist in the tiapp.xml file. Actual Result: Module packages, but does not appear in the TiAPP Editor Overview. The xml tags are not generated. It is worth noting the module tags will be added if the tiapp.xml file is dirty from other kinds of edits (i.e., changing the app version from 1.0 to 2.0).
| 8 |
train
|
TISTUD-1708
|
Studio: HTML verification does not mark syntax errors
|
I get warning for the DOCTYPE missing but see no syntax errors being marked. This is on a fresh install of Titanium Studio running default settings in a new work space. This is a regression, HTML validation worked in 2.0.1. Steps to reproduce: 1. Create an HTML file with the following: {code} <html xmlns="http://www.w3.org/1999/xhtml" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>HTML</title> <meta name="author" content="qatester" /> <!-- Date: 2012-05-25 --> </head> <body> <a href="http://google.com" src="this shouldn't work" div>Google</a> <xml>this shouldn't be here</xml> <?import namespace="t" implementation="#default#time2"> <p> This tag is correct.</p> </body> </html> {code} Expected results: Validation should return with warning and errors. Actual results: Only the DOCTYPE warning appears.
| 8 |
train
|
TISTUD-1709
|
Studio: HTML verification does not mark a warning for unknown attribute
|
The following code was used in testing and should throw a warning out on the anchor tag's line. Steps to reproduce: 1. Create a HTML file that contains the following: {code} <html xmlns="http://www.w3.org/1999/xhtml" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>HTML</title> <meta name="author" content="qatester" /> <!-- Date: 2012-05-25 --> </head> <body> <a href="http://google.com" src="this shouldn't work" div>Google</a> </body> </html> {code} Expected Result: A warning should appear on the anchor tag's line. Actual Result: The anchor tag's line does not generate any warning.
| 8 |
train
|
TISTUD-1710
|
Dashboard: "Explore" tab has two $$ next to prices of modules
|
The Titanium Studio dashboard shows two dollar signs next to module prices. See attached images.
| 2 |
train
|
TISTUD-1713
|
The JIRA account preference page should not validate when both username and password are empty
|
From one of our Titans: "Going into the Preferences screen and trying to save yields an error that says that a username must be entered. It is vague, and doesn't say which username or which page the username is on. It turns out it's the JIRA username, but that shouldn't be required for everyone to save their Preferences. Shawn"
| 2 |
train
|
TISTUD-1714
|
Titanium Studio: Preferences menu default size too small to display "Apply" and "Restore Defaults" buttons
|
The Preferences > Titanium Studio > Titanium menu window, by default, is too small to display the "Apply" and "Restore Defaults" buttons. Screenshot attached. Resizing the window will reveal the buttons (and the resize is automatically saved, fixing the problem). This issue did not affect Studio 1.0.9. This is a regression. This does not affect Windows XP. Steps to Reproduce: 1. Delete the meta data for the current workspace (or create a new empty workspace). 2. Restart studio. 3. Go to Preferences > Titanium Studio > Titanium. Expected Result: "Apply" and "Restore Defaults" should be visible. Actual Result: "Apply" and "Restore Defaults" are not visible, window must be resized.
| 3 |
train
|
TISTUD-1716
|
Titanium Studio: Import: Import shows an error with Null Pointer exception when project is created inside a directory within the workspace
|
While trying to import a project that is newly created inside a directory within the workspace then an error message box is shown with Null Pointer exception and the project imported into the project explorer is empty Not a regression, the behavior exists as far as Titanium Studio 1.0.8 Steps to Reproduce: 1. Using the command line interface create a new titanium mobile project within a directory inside the workspace, using the command like: $$ /Users/<username>/Library/Application\ Support/Titanium/mobilesdk/osx/2.0.2.v20120525161324/titanium.py create --platform=iPhone --type=project --dir=<path to studio workspace>/testing --name=iPhoneProject1 --id=com.appcelerator.iphoneproject1 2. From Titanium Studio, using the workspace as mentioned in the command above, go to File >> Import >> Titanium >> Import Existing Titanium Project 3. Select the recently created project (i.e. iphoneproject1) and click Finish Actual: i) A problem occurred message box pops up with java.lang.NullPointerException as details. (Refer to attached screenshot) ii) The project is shown in the project explorer but is empty iii) In the workspace folder on the system, a folder exists with the project name (outside the directory it was created in) and is empty Note: i) If the project is not created within the directory then it can be imported without issues ii) The issue occurs only only on newly created projects and only if the project is created within a directory or sub-directory inside the workspace
| 8 |
train
|
TISTUD-1717
|
Studio: Command menu does not display in Ubuntu.
|
While testing in Ubuntu 12.04 I noticed that the Command menu does not appear in the Unity desktop (it appears fine in a gnome desktop setup). Something in the interaction with Unity is causing it to not display properly. Steps to reproduce: 1. Open Titanium Studio with Unity as it's desktop (default setting) 2. Try to run a command from the command window. Actual result: The command menu is not present. Expected result: The command menu should be present.
| 13 |
train
|
TISTUD-1719
|
Titanium Studio: Android Run Configuration does not auto-select screen type if none exists
|
In the run configurations settings for an android emulator instance, if the sdk version is changed to one that does not have a screen type that existed in the previously selected sdk, there is only a blank screen type, resulting in invalid settings. It would be expected for studio to automatically select the first available screen type from the list if there is none selected on first sdk change. This is not a regression. Steps to Reproduce: 1. Open Studio. 2. Go to the Run Configurations menu. 3. Create a new android emulator run configuration. 4. Select google api's 2.2. Select a screen type. 5. Select google api's 3.0. Expected Result: A screen type should be selected. Actual Result: The screen type is blank, the run configuration is invalid until the screen type is selected.
| 5 |
train
|
TISTUD-1720
|
run configuration menu should open last used run configuration for the selected project in app explorer
|
When a project is selected in the project explorer, and the project explorer Run Configurations menu is selected, it would be convenient if the Run Configurations menu auto-selected the last used run configuration for that selected project (instead of the last run configuration for all projects). Workflow: 1. Create two projects. 2. Run the first project in emulator. 3. Run the second project in emulator. 3. Select the first project and go to Run Configurations. Expected Result: The last used run configuration for project one should be selected when the run configuration menu is brought up. Actual Result: The project two run configuration will be selected because it was the last used.
| 8 |
train
|
TISTUD-1721
|
setting runtime to rhino then back to v8 results in v8 xml tag in tiapp.xml when it should be default
|
In the TiApp Overview, setting the runtime to rhino, then back to v8 results in an xml tag added to the tiapp.xml when there should be none because v8 is default for 1.8.0.1+ sdks. This is not a regression. Steps to Reproduce: 1. Create a new project using a 1.8.0.1+ sdk (e.g., 2.0.1.GA). 2. Set the runtime to rhino. 3. Set the runtime back to v8. 4. Check the tiapp.xml. Expected Result: There should be no runtime tags at all because v8 is default for newer sdks. Actual Result: There is a v8 tag. This causes a related bug TISTUD-820.
| 3 |
train
|
TISTUD-1723
|
Titanium Accounts "Login" button should be disabled until values are entered for Username and Password
|
Steps: 1. Bring up Titanium Studio->Account preferences 2. Enter a value for username. Keep password empty Expected results: Login button is disabled Actual results: Login button is enabled The Login button should be disabled until values are entered for username and password. This applies to JIRA and NodeJITSU logins
| 5 |
train
|
TISTUD-1820
|
Creating an app in studio with "HTML-Based" template shows on "my apps" as "HTML Template" regardless of project name, and has the same GUID regardless of user
|
While testing pricing we noted an application appeared on Neha's "my apps" list shortly after she tried to create an HTML-based template project in studio. The GUID or name of the application on "my apps" did not match the studio project Neha created. The name on "my apps" was "HTML Template". Shortly after creation, and while browsing, Neha's "HTML Template" project disappeared from her apps list. Fortunately Chung witnessed this over our shoulders. Natalie was able to reproduce the "HTML template" entry on her account, and I was able to on mine. Although Neha's went missing, we looked at the GUID enough to see similarity with Natalie's GUID. Comparing that to mine, we all have the same GUID. See attached screens for Natalie's production list and my pre-prod list with the new UI. Steps to reproduce: 1) Create a new studio project using "HTML-Based" template 2) Check "my apps" list for "HTML Template" 3) Check GUID Result: GUID will be as seen for others, project will exist and not match name of studio project or GUID. Expected: App entry in "my apps" should have matching name and matching but unique GUID
| 5 |
train
|
TISTUD-1726
|
Error cleaning titanium project when platform SDK has unusual version string
|
I have an app tied to a special SDK version for blackberry, where the folder name is "blackberry_compat_2.0.1.v20120407201726". When the project is cleaned, we throw an error trying to parse the version. {code} !ENTRY org.eclipse.core.resources 4 75 2012-06-01 10:47:31.436 !MESSAGE Errors occurred during the build. !SUBENTRY 1 com.appcelerator.titanium.core 4 75 2012-06-01 10:47:31.436 !MESSAGE Errors running builder 'Titanium Builder' on project 'blackberry_app'. !STACK 0 java.lang.NumberFormatException: For input string: "blackberry_compat_2" java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) java.lang.Integer.parseInt(Integer.java:449) java.lang.Integer.parseInt(Integer.java:499) org.osgi.framework.Version.<init>(Version.java:127) org.osgi.framework.Version.parseVersion(Version.java:225) com.appcelerator.titanium.core.TitaniumProjectBuilder.clean(TitaniumProjectBuilder.java:72) 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.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:513) org.eclipse.core.internal.resources.Workspace.build(Workspace.java:422) com.aptana.editor.common.preferences.ValidationPreferencePage$ApplyChangesAndBuildJob.run(ValidationPreferencePage.java:130) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 8 |
train
|
TISTUD-1728
|
The module dialog seems to only read modules on startup/restart
|
If you drop a module in Titanium global directory and try and add it using the UI, it won't show up in the list. You must re-start Studio to get it to detect the presence of the new module. We need to re-read each time you launch the dialog
| 5 |
train
|
TISTUD-1730
|
Dashboard: Error:'$H' is undefined
|
When starting Titanium Studio in Windows 7, I am given the following webpage error: Line: 1 Error: '$H' is undefined This is created in the log at about the same time and may be related.: {noformat} !ENTRY com.appcelerator.titanium.core 4 0 2012-06-04 08:22:22.053 !MESSAGE (Build 2.0.2.201205311912) [ERROR] com.appcelerator.titanium.core/debug null !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.core.JVMInfo.hasJavac(JVMInfo.java:265) com.appcelerator.titanium.core.JVMInfo.hasJavac6432(JVMInfo.java:224) com.appcelerator.titanium.core.JVMInfo.parseJavaVersion(JVMInfo.java:204) com.appcelerator.titanium.core.JVMInfo.load(JVMInfo.java:122) com.appcelerator.titanium.core.JVMInfo.<init>(JVMInfo.java:61) com.appcelerator.titanium.core.JVMInfo.getInstance(JVMInfo.java:46) com.appcelerator.titanium.mobile.portal.processor.MobileSDKConfigurationHelper.getVersionInfo(MobileSDKConfigurationHelper.java:141) com.appcelerator.titanium.mobile.ui.portal.processor.MobileSDKConfigurationProcessor.computeStatus(MobileSDKConfigurationProcessor.java:99) com.aptana.configurations.processor.AbstractConfigurationProcessor.getStatus(AbstractConfigurationProcessor.java:154) com.appcelerator.titanium.mobile.ui.portal.actionController.MobileSDKActionController$1.run(MobileSDKActionController.java:124) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {noformat} This is a regression bug, this did not occur in earlier builds of the dashboard (last tested 5/30/2012). Steps to reproduce: 1. Launch Titanium Studio. Expected result: Titanium Studio should start without error. Actual result: Titanium Studio throws the given error and creates the entry in the log file.
| 8 |
train
|
TISTUD-1731
|
Add "continuous integration master" stream to "Install Titanium SDK..."
|
The stream URL is http://builds.appcelerator.com.s3.amazonaws.com/mobile/master/index.json. We need to work with the platform team to regularize the format so it is closer to what the release stream generates (with version information) so we could apply the same logic on both if possible.
| 5 |
train
|
TISTUD-1732
|
Titanium Studio: change default promote project option to titanium mobile
|
When a folder is imported into studio as a "promote to project" option, Web Project is the default setting. It seems like the default option should be "Titanium Mobile Project". Screenshot attached. Import > General > Existing Folder as New Project
| 8 |
train
|
TISTUD-1733
|
Titanium Studio: JIRA Integration: remove priority from bug submission fields
|
In Help > Submit a Ticket, the Priority field needs to be removed.
| 5 |
train
|
TISTUD-1734
|
Titanium Studio: add validation to "promote to project from folder" option for existing projects
|
When a previously existing project is "promoted to project", there is no validation to inform the user a project already exists. Steps to Reproduce: 1. Create a titanium mobile project. 2. Delete the project from the workspace (without removing from disk). 3. Reimport the project using Import > General > Existing Folder as New Project. Expected Result: A notification that the folder has an existing project type. Actual Result: No notification. Existing project info is overwritten.
| 8 |
train
|
TISTUD-1735
|
JavaScript editor is showing a lot more warnings after updating to 2.0.2
|
Steps to reproduce: 1. Import Kitchen Sink sample (or any other sample) from Samples view; 2. Open Preferences > Titanium Studio > Validation > JavaScript and make sure "JSLint Validator" is selected; 3. Click OK and agree to re-build the project if asked. 4. Open Resources/app.js file. Expected result: no validation warning is displayed. Actual result: many validation warnings are shown.
| 8 |
train
|
TISTUD-1737
|
Publish provider wizard does display entire Android platform page
|
Steps: 1. Start the sample publish provider wizard. Publish->Sample Publish Provider->Publish... 2. Select Android and proceed to the platform page Expected results: The entire Android platform page is shown Actual results: The keystore section is cut off, requiring a resize of the wizard
| 5 |
train
|
TISTUD-1738
|
Auto-configure browser list to contain all installed browsers on Mac OSX
|
Description: While attempting to set a browser before running a mobile web preview, I noticed that the list of browsers did not include any specific browsers except firefox. It would be ideal to populate the list of installed browsers rather than have the user populate the list manually. Steps to reproduce: 1) Install Studio 2) Create project with mobile web target 3) Run in browser 4) Select "run configurations" and use the browser selection section Result: Firefox is the only 3rd-party browser listed although I have Chrome, Firefox, and Safari Expected: Firefox not displayed, or all installed browsers displayed Note: The version # of the browser is displayed here as part of the name of the browser.
| 8 |
train
|
TISTUD-1740
|
Titanium Studio: Android Emulator: Not recognized by adb, unable to install to Emulator.
|
When Android emulator deployed, adb fails to recognize the emulator. This is intermittent issue, it effect all emulator versions. This is not an regression it occurred in 2.0.2 Step to reproduce: 1) Create default project. 2) Right Click, Select "Run As", Select "Run Configurations..." 3) Select "Titanium Android Emulator" 4) Select platform Android API: "Google API Android 4.0.3" 5) Apply and Run. Expected Result: adb should recognized the emulator or if this occur then studio should be provide error correction to handle the error properly. Actual Result: adb doesn't recognize the emulator. Studio fails to notified to developer of the failure and App never installed.
| 13 |
train
|
TISTUD-1742
|
Hitting Enter/Return in password field of JIRA login on Submit Ticket dialog doesn't try to log user in
|
It'd be nice to be able to just hit Return/Enter and have it perform "Log In" without needing to click. This does work in the preference page version of the JIRA account login.
| 3 |
train
|
TISTUD-1743
|
Add NodeJS Project wizard to listing in New > menu for Project and App Explorer
|
The NodeJS project wizard is not listed in the "New" submenu like the Web/Ruby/TiMobile/PHP project wizards are.
| 3 |
train
|
TISTUD-1746
|
Titanium Studio: Help > Install Specific Titanium SDK: sdk text field does not have focus when menu first invoked
|
When the Help > Install SDK from URL menu is invoked, the skd text field does not have focus. It did have focus in 2.0.2. This is a usability issue and a regression. Steps to Reproduce: 1. Open Studio. 2. Go to Help > Install Specific Titanium SDK... Expected Result: Menu should pop up and sdk text field should have focus if it is selected. Actual Result: Text field does not have focus if it is selected, user has to manually select the field to paste the URL.
| 3 |
train
|
TISTUD-1752
|
Need BOM (Bill of Materials) for packaged product
|
As part of continued quality control measures, the build and packaging procedure for Titanium releases will now include a BOM verification. This BOM will be generated from the Development environment and will be verified by QE via a fully releasable packaged installation. This procedure was implemented for the 2.0.2 release of SDK package.
| 3 |
train
|
TISTUD-1753
|
Wrong Android screen-type is used when launching a Mobile Web project for the first time
|
# Create a new MobileWeb project # Right click the project and select 'Run As... -> Mobile Web Preview in Emulator' # Open the run configuration dialog and locate the newly create Mobile Web launch configuration. Expected: The newly created launch configuration has the default Android 'screen-type' defined at the Titanium preference page. Actual: The configuration has the first option in the drop-down selected, ignoring the defaults.
| 5 |
train
|
TISTUD-1754
|
Titanium Studio: HTML Editor: invalid closing tag does not generate warning
|
html verification is not working for closing tags. ex: body tags, paragraph tags etc. This is regression as it do work in 2.0.1, there is no log information. Step to reproduce: 1. Create an blank HTML file. 2. Insert the following code: {code} <html> <head> <title> <title> <head> <body> <p> <p> <body> </html> {code} Expected Result: Invalid closing tags should displays the warning icon. Actual Result: No warnings.
| 13 |
train
|
TISTUD-1757
|
Titanium Studio TiApp.xml visual interface does not show common js modules such as the amazon ti.aws
|
Titanium Studio TiApp.xml visual interface does not show common js modules such as the amazon ti.aws Titanium AWS module can be found here: https://github.com/appcelerator-se/aws It is installed sibling to the ti.cloud commonjs module in the /commonJS/ folder After this is installed the tiapp.xml visual editor does not show the ti.aws module as available. it can be manually entered into the tiapp.xml file and works, however the visual interface does not show it PLEASE READ THE FOLLOWING TICKET: there is a bug that is direct conflict with this request: https://jira.appcelerator.org/browse/TISTUD-1318
| 8 |
train
|
TISTUD-1761
|
Titanium Studio: high CPU after removing git-enabled project from workspace
|
When a git-enabled project is imported then deleted (not from disk) from the workspace, the cpu remains abnormally high for a few minutes. CPU: 137% This is not a regression. Attaching stack trace. Steps to Reproduce: 1. Import a git-enabled titanium mobile project. 2. Delete the project (not from disk) from the workspace. 3. Observe CPU usage (i.e., Activity Monitor). Expected Result: CPU should be low (e.g., 1.7%). Actual Result: CPU is high (e.g., 137%) and remains so for a few minutes.
| 8 |
train
|
TISTUD-1769
|
Empty separator in Publish submenu for Web project
|
1. Create a web project using File > New > Web Project; 2. Right-click on the project and select Publish. The pull-over menu will show an empty separator at the top. This doesn't happen on Aptana Studio 3.2.0, nor on Titanium mobile project.
| 5 |
train
|
TISTUD-1771
|
Add new portal dashboard controller to run browser configuration check
|
Related to TISTUD-1414, a portal controller that: # Runs the browser configuration check on demand # Returns back a list of the currently configured browsers
| 8 |
train
|
TISTUD-1772
|
Add "Install Titanium Module" menu option to Help menu
|
Add a menu option (identical to the original Install Titanium SDK screen) that contains: # A text box for a URL # A browse button allowing a user to navigate to a folder on disk This will then install the specified module into the global SDK folder. A note added to the bottom of the screen informing a user of how to install a module for just a project (by dragging it in) would clarify that behavior.
| 8 |
train
|
TISTUD-1791
|
Allow non-commercial iOS developers to deploy iOS applications
|
I am using Titanium as a university student, by sharing a provisioning portal for my institution. This allows for educational use without paying the $99/year for a full iOS Developer account. The problem I have is that Titanium Studio is too knowledgeable of the commercial iOS developer program web site, and automates a few steps that I need to perform manually. I need to be able to input a developer certificate from the filesystem, as well as a provisioning profile also from the filesystem. The wizards should not prevent me from doing this, even though Titanium's test for me being in the iOS developer program fails (wizard error "Please sign up for the iOS Developer Program"). I can't even get by with editing the Launch Configuration. Any advice would be much appreciated, including dirty tricks like editing Titanium Studio config files, etc.
| 3 |
train
|
TISTUD-1776
|
Titanium Studio: Project Explorer: Python option is not available in the list of "New From Template" under python file
|
"Python" option is not visible under "New From Template" list and after generating the new file from "New> File", "Python" option is not visible under "Commands" after right click inside the generated python file. Step to reproduce. (To generate the python file from template) 1) Click inside the "Project Explorer". 2) Select "New From Template" Actual Result: Python option is not visible. Expected Result: Python option should be visible. Step to reproduce. (After generating the python file from "New File" option.) 1)Right click inside the file. 2) Select the "Commands" option. Actual Result: Python option is not visible. Expected Result: Python option should be visible.
| 8 |
train
|
TISTUD-1779
|
Add version information to Windows browser configuration names and refresh version info on demand
|
Related to TISTUD-1414. As discussed, we need to include the version of the browser in question as part of the browser name (see image for example) Ideally, this value would be dynamic, but that appears to be impossible given the current UI. In the case where the user upgrades the browser later, the suggestion is that when the user re-runs the configuration step to auto-search, we replace the version #s of the existing browsers with the newer version.
| 13 |
train
|
TISTUD-1780
|
TiApp.xml incorrectly displays select/enabled deployment targets
|
The enablement of the platform targets is inconsistent Steps: 1. Create a mobile project with just mobile web and SDK >= 2.1.0 2. In the TiApp.xml, enable the android and iphone/ipad targets 3. Change the sdk to < 2.1.0 4. Save the TiApp.xml Results: Checkbox for Android/iphone/ipad are checked but enabled 5. Close the TiApp.xml and reopen it Results Checkbox for Android/iphone/ipad are checked but disabled The checkboxes should be disabled as soon as the SDK is switched (since we can't add/change platforms after the fact in SDK < 2.1)
| 5 |
train
|
TISTUD-1781
|
Create interface to manage existing Titanium SDKs
|
If a user has a large selection of Titanium SDKs, they may want to be able to delete them after the fact. Suggest some management interface that would show a list of all currently installed SDKs and allows users to manage them Perhaps move the list of SDKs to a preference page, and move the "Install SDK from URL" functionality to that page.
| 13 |
train
|
TISTUD-1783
|
Titanium Studio: Run Configurations menu not accessible from simplified Studio perspective
|
When the new default simple Studio perspective is used, the Run Configurations menu from the deployment drop-downs is greyed-out. This does not occur on the original Extended Studio perspective. There is no log info. This is a regression in behavior. Steps to Reproduce: 1. Launch Studio. 2. Create a new project. 3. Select the run icon > Run Configurations... Result: Run Configurations is greyed-out and non-functional. Expected Result: Run Configurations should be functional.
| 3 |
train
|
TISTUD-1785
|
When Ti Studio self-applies an update, a directory with several subdirectories remains on the root of the drive
|
When a Ti Studio update is installed (using the built-in update notification), after the update is complete and Ti Studio is restarted, the following file always gets left on the hard drive: {panel}C:\var\hudson\workspace\titanium-standalone-master\builders\com.appcelerator.titanium.standalone.build\eclipse\artifacts.xml{panel} Note that the "var" directory is left at the root of the install drive...adding to the root directory is frowned upon. This file should either be placed in the Ti Studio install directory, or it should be removed at the end of the update installation process.
| 8 |
train
|
TISTUD-1786
|
Last line in JS editor does not have line number when word wrap is enabled
|
h3. Steps to Reproduce 1. Open JS editor 2. Enable line numbers 3. Copy and paste the following: var win = Ti.UI.createWindow({ backgroundColor : 'white' }) var viewImgShow = Titanium.UI.createImageView({ height : '50', bottom : '50' }); view1_foto.addEventListener('click', function(e) { Ti.API.info('click event fired!!'); Titanium.Media.showCamera({ success : function(event) { my_image = event.media; if (event.mediaType == Ti.Media.MEDIA_TYPE_PHOTO) { viewImgShow.image = my_image; viewImgShow.show(); } }, saveToPhotoGallery : true, allowEditing : true, mediaTypes : [Ti.Media.MEDIA_TYPE_VIDEO, Ti.Media.MEDIA_TYPE_PHOTO] }); }); //this does not have a line number h3. Actual Result You will see that the last line does not have a line number. This seems to choke somewhere after line 30. h3. Expected Result The last line in the editor should have a line number
| 13 |
train
|
TISTUD-1788
|
Android SDK wizard fails with the message "NLS missing message: MobileSDKConfigurationProcessor_updatermessage in: com.appcelerator.titanium.mobile.portal.processor.message"
|
When trying to setup Android inside Titanium Studio, the wizard fails showing a window with the following error message: "NLS missing message: MobileSDKConfigurationProcessor_updatermessage in: com.appcelerator.titanium.mobile.portal.processor.message OK" I managed to install the SDK manually, but I get the same error message when I click the UPDATE button. This is a regression from 2.0.2. This does not occur in 2.0.1.
| 3 |
train
|
TISTUD-1792
|
Titanium Studio: simple perspective not default and can't change back to Studio (extended) if in an old workspace
|
Simple Perspective does not show up and switching to Studio (extended) does not show the toolbar if in an old workspace. Steps to Reproduce: 1. Open Studio. Actual Result: Studio simple perspective is not the default, nor does it exist. The simple perspective is also not available in Window > Open Perspective. Expected Result: Simple perspective is default, exists, and is available in Window > Open Perspective.
| 3 |
train
|
TISTUD-1793
|
Rename "Titanium Mobile [Module] Project" to "Titanium Project" and "Titanium Module Project"
|
In keeping with the removal of Desktop functionality from the core of Studio, we should rename "Titanium Mobile Project" to "Titanium Project" and "Titanium Mobile Module Project" to "Titanium Module Project"
| 13 |
train
|
TISTUD-1795
|
Titanium Studio: Window > Hide Toolbar shows the toolbar instead in new workspace
|
When studio is launched in a new workspace, the simple perspective has a "Window > Hide Toolbar" option, but there is no toolbar. This command will instead show the toolbar. This issue goes away on second launch of studio. Steps to Reproduce: 1. Open Studio in a new workspace. 2. Go to Window > Show Toolbar. Actual Result: Window > Show Toolbar does not exist, it is now called Hide Toolbar. Expected Result: Show Toolbar should exist, Hide Toolbar should not, and Show Toolbar should show the toolbar.
| 3 |
train
|
TISTUD-1796
|
Remove Titanium Desktop Project wizard from being promoted in Simple and Advanced perspectives
|
We need to remove the Titanium Desktop project wizard from the File > New menu, or being "promoted" in any other areas.
| 3 |
train
|
TISTUD-1797
|
Titanium Studio: Menu Options: File: New: File> New, Option doesn't shows all list of Titanium Project LIst - It's only shows the "Project" option.
|
Perspective Studio window, After selecting the File>New displays only "Project...", "File", "Folder", "Untitled Text File" and "Other..." options. Step to reproduce: 1. Open Ti.Studio 2. Select Menu bar "File" 3. Select "New" 4. Check the Actual result 5. Select "Windows" from menu bar 6. Select "Open Perspective" 7. Select "Studio (extended) 8. Select "New" 9. Check the Expected result Expecte result: After selecting the "New" menu bar a list of Titanium Project options, to be user friendly experience. Actual Result: Only options are appearing in "New" menu bar is "Project.."
| 5 |
train
|
TISTUD-1798
|
Studio perspective does not prompt to reset the perspective if there have been changes
|
Steps: 1. Install a 2.1 build on 0618 2. Show the Basic Studio perspective 3. Update Studio to a 2.1 build after 0621 (Studio perspective changed in this build) 4. Open Studio Expected When the studio perspective is opened, we should be prompted to reset the perspective Actual No request is made, the perspective remains out of date
| 5 |
train
|
TISTUD-1800
|
Titanium Studio: Menu bar: Submit a Ticket..., the tab key only jumps between text fields, not all fields
|
This is not a regression, using TAB should select each button or check box in the "Submit a Ticket" Window. Step to reproduce: 1. Select "Help" menu bar 2. Select "Titanium Studio" 3. Select "Submit a Ticket..." 4. Use the TAB button from keyboard Expected result: Tab should select every button, check box, text area on using tab button. Actual result: Tab skipping all the check box and button and only working with text area.
| 3 |
train
|
TISTUD-1804
|
Titanium Studio crashes right after logging in with ClassNotFoundException: com.aptana.ui.PerspectiveChangeResetListener
|
# Download the latest beta release from preview.appcelerator.com (i.e. http://preview.appcelerator.com/appcelerator/studio/standalone/install/beta/Titanium_Studio.dmg) # Run Studio. After logging in, it will crash with the following log: {code} !ENTRY org.eclipse.osgi 4 0 2012-06-22 06:52:25.288 !MESSAGE An error occurred while automatically activating bundle com.appcelerator.titanium.ui (17). !STACK 0 org.osgi.framework.BundleException: The activator com.appcelerator.titanium.ui.TitaniumUIPlugin for bundle com.appcelerator.titanium.ui is invalid org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:171) org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:679) org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299) org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:345) org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229) org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1207) org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174) org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) org.eclipse.ui.internal.util.Util.safeLoadExecutableExtension(Util.java:879) org.eclipse.ui.internal.menus.DynamicToolBarContributionItem.createContributionItem(DynamicToolBarContributionItem.java:183) org.eclipse.ui.internal.menus.DynamicToolBarContributionItem.getContributionItem(DynamicToolBarContributionItem.java:176) org.eclipse.ui.internal.menus.DynamicToolBarContributionItem.createControl(DynamicToolBarContributionItem.java:278) org.eclipse.jface.action.ControlContribution.fill(ControlContribution.java:97) org.eclipse.jface.action.ToolBarManager.update(ToolBarManager.java:353) org.eclipse.jface.action.ToolBarManager.createControl(ToolBarManager.java:111) org.eclipse.ui.internal.menus.TrimContributionManager$ToolBarTrimProxy.dock(TrimContributionManager.java:88) org.eclipse.ui.internal.menus.TrimContributionManager.update(TrimContributionManager.java:265) org.eclipse.ui.internal.WorkbenchWindow.updateLayoutDataForContents(WorkbenchWindow.java:3874) org.eclipse.ui.internal.WorkbenchWindow.setLayoutDataForContents(WorkbenchWindow.java:3885) org.eclipse.ui.internal.WorkbenchWindow.createDefaultContents(WorkbenchWindow.java:1157) org.eclipse.ui.internal.WorkbenchWindowConfigurer.createDefaultContents(WorkbenchWindowConfigurer.java:623) org.eclipse.ui.application.WorkbenchWindowAdvisor.createWindowContents(WorkbenchWindowAdvisor.java:300) org.eclipse.ui.internal.WorkbenchWindow.createContents(WorkbenchWindow.java:1043) org.eclipse.jface.window.Window.create(Window.java:431) org.eclipse.ui.internal.Workbench$68.runWithException(Workbench.java:3664) org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) 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.readAndDispatch(Display.java:3615) org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) org.eclipse.ui.internal.Workbench$33.runWithException(Workbench.java:1600) org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) 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.readAndDispatch(Display.java:3615) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2609) 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) Caused by: java.lang.NoClassDefFoundError: com/aptana/ui/PerspectiveChangeResetListener java.lang.ClassLoader.defineClass1(Native Method) java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) java.lang.ClassLoader.defineClass(ClassLoader.java:615) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:188) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClassHoldingLock(ClasspathManager.java:626) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:608) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:562) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:486) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:459) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) com.appcelerator.titanium.ui.TitaniumUIPlugin.<init>(TitaniumUIPlugin.java:46) sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) java.lang.reflect.Constructor.newInstance(Constructor.java:513) java.lang.Class.newInstance0(Class.java:355) java.lang.Class.newInstance(Class.java:308) org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:166) ... 69 more Caused by: java.lang.ClassNotFoundException: com.aptana.ui.PerspectiveChangeResetListener org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 93 more Root exception: java.lang.NoClassDefFoundError: com/aptana/ui/PerspectiveChangeResetListener java.lang.ClassLoader.defineClass1(Native Method) java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) java.lang.ClassLoader.defineClass(ClassLoader.java:615) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:188) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClassHoldingLock(ClasspathManager.java:626) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:608) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:562) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:486) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:459) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) com.appcelerator.titanium.ui.TitaniumUIPlugin.<init>(TitaniumUIPlugin.java:46) sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) java.lang.reflect.Constructor.newInstance(Constructor.java:513) java.lang.Class.newInstance0(Class.java:355) java.lang.Class.newInstance(Class.java:308) org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:166) org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:679) org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299) org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:345) org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229) org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1207) org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174) org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) org.eclipse.ui.internal.util.Util.safeLoadExecutableExtension(Util.java:879) org.eclipse.ui.internal.menus.DynamicToolBarContributionItem.createContributionItem(DynamicToolBarContributionItem.java:183) org.eclipse.ui.internal.menus.DynamicToolBarContributionItem.getContributionItem(DynamicToolBarContributionItem.java:176) org.eclipse.ui.internal.menus.DynamicToolBarContributionItem.createControl(DynamicToolBarContributionItem.java:278) org.eclipse.jface.action.ControlContribution.fill(ControlContribution.java:97) org.eclipse.jface.action.ToolBarManager.update(ToolBarManager.java:353) org.eclipse.jface.action.ToolBarManager.createControl(ToolBarManager.java:111) org.eclipse.ui.internal.menus.TrimContributionManager$ToolBarTrimProxy.dock(TrimContributionManager.java:88) org.eclipse.ui.internal.menus.TrimContributionManager.update(TrimContributionManager.java:265) org.eclipse.ui.internal.WorkbenchWindow.updateLayoutDataForContents(WorkbenchWindow.java:3874) org.eclipse.ui.internal.WorkbenchWindow.setLayoutDataForContents(WorkbenchWindow.java:3885) org.eclipse.ui.internal.WorkbenchWindow.createDefaultContents(WorkbenchWindow.java:1157) org.eclipse.ui.internal.WorkbenchWindowConfigurer.createDefaultContents(WorkbenchWindowConfigurer.java:623) org.eclipse.ui.application.WorkbenchWindowAdvisor.createWindowContents(WorkbenchWindowAdvisor.java:300) org.eclipse.ui.internal.WorkbenchWindow.createContents(WorkbenchWindow.java:1043) org.eclipse.jface.window.Window.create(Window.java:431) org.eclipse.ui.internal.Workbench$68.runWithException(Workbench.java:3664) org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) 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.readAndDispatch(Display.java:3615) org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) org.eclipse.ui.internal.Workbench$33.runWithException(Workbench.java:1600) org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) 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.readAndDispatch(Display.java:3615) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2609) 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) Caused by: java.lang.ClassNotFoundException: com.aptana.ui.PerspectiveChangeResetListener org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 93 more {code}
| 8 |
train
|
TISTUD-1805
|
Titanium Studio: If Titanium SDK root folder is read-only, Studio will not prompt the user with an error
|
If the root Titanium SDK folder is readonly and latest sdk is not there, Studio will not find an sdk to update when update sdk is called. Step to reproduce: 1. /Users/"Your_home_dir"/Library/Application\ Support/Titanium/mobilesdk/osx 2. Delete the latest version of SDK folder 3. Give "Titanium" folder "read only" permission 4. Open Ti.Studio 5. Select "Help" from menu bar 6. Select "Check for Titanium SDK updates" Actual result: Ti.Studio displaying MSG. "No Ti.SDK update available" Expected result: Documentation web page should load in a browser.
| 5 |
train
|
TISTUD-1809
|
Titanium Studio: Dashboard: remove desktop project from create new project dropdown
|
Dashboard > Develop > Templates > Create New Project still has a dropdown that allows the user to select a desktop project. There should only be one button that only creates a titanium studio project.
| 3 |
train
|
TISTUD-1813
|
Titanium Studio: Run Configuration: new configuration should auto-select current project
|
When a new run configuration is created, it would be helpful if the project were auto-selected based on the project currently in focus (either from the project explorer, or app explorer). Steps to Test: 1. Select a Titanium Mobile project in the project explorer. 2. Go to Run Configurations... 3. Create a new Android Emulator run configuration. Expected Result: The project selected in the project explorer should be the default project in the new configuration. Currently there is no project selected in the new run config, it must be manually selected.
| 8 |
train
|
TISTUD-1815
|
Invalid thread access in AndroidSimulatorLaunchConfigurationDelegate.notifyAppInstallError()
|
Sound in the log file for TISTUD-1814 {code} !ENTRY org.eclipse.text 4 2 2012-06-25 13:57:15.427 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.text". !STACK 0 org.eclipse.swt.SWTException: Invalid thread access 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:774) org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:569) org.eclipse.swt.custom.StyledText.getLinePixel(StyledText.java:4169) org.eclipse.swt.custom.StyledText.handleTextChanging(StyledText.java:6242) org.eclipse.swt.custom.StyledText$6.textChanging(StyledText.java:5612) org.eclipse.ui.internal.console.ConsoleDocumentAdapter.documentAboutToBeChanged(ConsoleDocumentAdapter.java:302) org.eclipse.jface.text.AbstractDocument.fireDocumentAboutToBeChanged(AbstractDocument.java:665) org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1182) org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210) org.eclipse.ui.internal.console.ConsoleDocument.replace(ConsoleDocument.java:82) com.appcelerator.titanium.mobile.ui.android.launch.AndroidSimulatorLaunchConfigurationDelegate.notifyAppInstallError(AndroidSimulatorLaunchConfigurationDelegate.java:475) com.appcelerator.titanium.mobile.ui.android.launch.AndroidSimulatorLaunchConfigurationDelegate.handleAppInstallTermination(AndroidSimulatorLaunchConfigurationDelegate.java:335) com.appcelerator.titanium.mobile.ui.android.launch.AndroidSimulatorLaunchConfigurationDelegate$1.handleDebugEvents(AndroidSimulatorLaunchConfigurationDelegate.java:279) org.eclipse.debug.core.DebugPlugin$EventNotifier.run(DebugPlugin.java:1119) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.debug.core.DebugPlugin$EventNotifier.dispatch(DebugPlugin.java:1153) org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:415) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 3 |
train
|
TISTUD-1817
|
Titanium Studio: Install Titanium Module > Browse while Packaging Module Freezes Studio
|
If the Install Titanium Module... Browse window is open and a module packaging operation completes, studio will freeze. It is not possible to get a stack trace when studio is in this condition. Studio must be force-closed from the Activity Monitor. This is a new fail case, as the Install Module menu is new, and I could not recreate a similar freeze in Studio 2.0.2. Note: I was able to reproduce this every time in OS X, but I could not reproduce at all in Windows 7. Steps to Reproduce: 1. Open Studio. 2. Create a new Android module. 3. Package the module to directory (i.e., /Downloads). 4. While the module is still packaging, go to Help > Install Titanium Module > Install from URL Browse. Actual Result: When the packaging is complete, Studio freezes (screenshot attached). jstack does not work (console logs attached). studio log.txt attached. Expected Result: Studio should not freeze, and the user should be able to continue using it.
| 8 |
train
|
TISTUD-1818
|
Titanium Studio: Upgrade Install Titanium Module to Project to include module in tiapp.xml
|
If a module is installed to project using Help > Install Titanium Module, the module is not added to the tiapp.xml. If a module is packaged to project, it is included in the tiapp.xml. There is no log info. Steps to Reproduce: 1. Create a new Titanium Mobile project. 2. Create a new Titanium Module project. 3. Package the module to a directory (i.e., /Downloads). 4. Go to Help > Install Titanium Module. 5. In Install from URL, select the packaged module zip. 6. In Output, select Project, and select the app project you created. Press OK. Actual Result: Module gets unzipped to project, but the module is not in the tiapp.xml. Expected Result: Module should unzip to project, and a module xml tag should be added to tiapp.xml. The module should be visible in the TiApp Overview.
| 8 |
train
|
TISTUD-1821
|
Titanium Studio: unable to create android module at non-default project location
|
When creating a module in studio, the creation fails with internal error: could not move file. Screenshot and log attached. This only occurs with android modules. However, android modules can be created from the command line. Steps to Reproduce: 1. Go to New > Titanium Mobile Module Project. 2. Type in a project name and module id. 3. Deselect Use Default Location. 4. Browse to a new location (i.e., Desktop/ti). 5. Create the module. Actual Result: Error. Expected Result: New Module.
| 8 |
train
|
TISTUD-1824
|
Add per-platform mobile configuration tab for tiapp.xml editor
|
Each platform for Titanium Mobile has extra content placed into a <platform-name> tab. approximately something like: {code} <?xml version="1.0" encoding="UTF-8"?> <ti:app xmlns:ti="http://ti.appcelerator.org"> ... <iphone> ... </iphone> <android xmlns:android="http://schemas.android.com/apk/res/android"> <manifest> <application> ... </application> </manifest> </android> <modules> </modules> </ti:app> {code} Add a mechanism whereby each platform can contribute a tab (similar to that shown in the screenshot, and via an extension point) that contains additional configuration information. As an initial pass, suggest just showing the text content of the tiapp.xml for that platform in a text box so it can be edited. In the future, we could amend this to show additional UI. The "All Platforms" in the screenshot is not applicable.
| 13 |
train
|
TISTUD-1825
|
Add JDK installation to the Titanium Studio installer
|
Based on this: http://nsis.sourceforge.net/Java_Runtime_Environment_Dynamic_Installer Install the JDK as noted from http://titanium-studio.s3.amazonaws.com/jdk/jdk-6u25-windows-i586.exe It can evidently be run silently using the commands here: http://www.oracle.com/technetwork/java/javase/install-windows-189425.html
| 13 |
train
|
TISTUD-1827
|
Detect if node.js is installed, if not, run installer
|
http://nodejs.org/#download # Check to make sure node.js is installed ## For linux, install for Ubuntu, otherwise ask user to install themselves. # If it is, confirm it's within the currently supposed version range. # If not, inform the user to upgrade or install a new version # If it's not installed, download the current package from an appcelerator web site (so we can ship a stable version)
| 40 |
train
|
TISTUD-2002
|
Android: Distribute to Android App Store doesn't give any finalization message
|
When deploying an app to Google Play from Titanium Studio (Publish | Distribute Android App Store), you no longer get a "success" or other finalization message saying that the process is complete. The last line that appears in the Console log is the zipalign command: {panel} "C:\Program Files (x86)\Android\tools\zipalign.exe" -v 4 C:\{MyTitaniumDir}\{MyWorkspaceDir}\{MyAppName}\{MyDistributionLocation}\{MyAppName}.apk C:\{MyTitaniumDir}\{MyWorkspaceDir}\{MyAppName}\{MyDistributionLocation}\{MyAppName}.apkz {panel}
| 5 |
train
|
TISTUD-1828
|
Titanium Studio: intermittent freeze when importing git-enabled project
|
When importing a project with git information, studio freezes intermittently. This is intermittent and difficult to conclusively regression test. Steps to Reproduce: 1. Import KitchenSink from titanium_mobile using Import... > Existing Titanium Project. Actual Result: Studio unresponsive in Activity Monitor, spinning beach ball instead of arrow cursor, Studio not receiving user events. Expected Result: Project should import and git information should display in Project Explorer.
| 8 |
train
|
TISTUD-1831
|
Signup link in Ti Studio login dialog does not work if browser preferences are changed
|
1. Logout of Studio and shut it down and restart 2. You should be presented with the signin screen 3. Click on Signup EXPECTED RESULT: taken to a signup page ACTUAL RESULT: Safari pops up in the background with a "cannot find file". file:///Applications/Titanium%20Studio/TitaniumStudio.app/Contents/MacOS/https:/my.appcelerator.com/auth/signup
| 5 |
train
|
TISTUD-1832
|
Titanium Studio: Preferences > Titanium Studio > Titanium: Titanium SDK Path not correctly re-validated
|
In Preferences > Titanium Studio > Titanium > Titanium SDK Home, if you enter an invalid path (e.g., by removing the last two characters), then add in a valid path (e.g., add the last two characters back), studio will not re-validate the path. There is no log info. This is a regression. This does not occur in Studio 2.1.0. Steps to Reproduce: 1. Open Titanium Studio. 2. Go to Preferences > Titanium Studio > Titanium. 3. Edit the Titanium SDK Home path to make it invalid (i.e., delete the last two characters of text from the path). Studio should display an error. 4. Edit the Titanium SDK Home path to make it valid again (i.e., re-add the last two characters of text from the path). Actual Result: The error remains, the path has not been re-validated. However, the changes can be saved, and the error goes away on preferences menu re-open. Expected Result: The Titanium SDK path should immediately re-validate and the error should go away.
| 5 |
train
|
TISTUD-1833
|
Titanium Studio: Preferences > Titanium Studio > Titanium: Android SDK path can't save if no Android SDKs installed
|
In Preferences > Titanium Studio > Titanium > Android SDK Home, if a fresh Android install is loaded into the path, the preferences cannot be saved. Note: The fresh Android install was just downloaded from http://developer.android.com/sdk/index.html and unzipped, no Android SDKs were installed. There is no log info. This is not a regression. Steps to Reproduce: 1. Download the Android SDK from http://developer.android.com/sdk/index.html. 2. Open Titanium Studio. 3. Go to Preferences > Titanium Studio > Titanium. 4. In Android SDK Home, enter the path to the new Android install. Actual Result: Cannot save the changes to the preferences menu. Expected Result: Can save the changes to the preferences menu. The dashboard config utility should be able use this path to continue the Android SDK installation.
| 8 |
train
|
TISTUD-1834
|
BackingStoreException in the log when creating mobile module project
|
When using File > New > Titanium Mobile Module Project to create an Android module project, I see the following in the log (the project is created successfully): {code} !ENTRY org.eclipse.core.resources 4 4 2012-07-02 15:22:40.110 !MESSAGE Exception occurred while saving project preferences: /tistud1648/.settings/com.aptana.editor.common.prefs. !STACK 1 org.eclipse.core.internal.resources.ResourceException: A resource already exists on disk '/Users/mxia/Documents/workspace/runtime-New_configuration_ts2/tistud1648/.settings'. 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.ProjectPreferences$1.run(ProjectPreferences.java:566) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.core.internal.resources.ProjectPreferences.save(ProjectPreferences.java:590) org.eclipse.core.internal.preferences.EclipsePreferences.internalFlush(EclipsePreferences.java:440) org.eclipse.core.internal.resources.ProjectPreferences.flush(ProjectPreferences.java:350) com.aptana.editor.common.contentassist.UserAgentManager.savePreference(UserAgentManager.java:722) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.applyPreferenceValues(BasicNewTitaniumProjectWizard.java:487) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:392) com.appcelerator.titanium.mobile.ui.module.wizard.NewMobileModuleProjectWizard.finalizeProjectCreation(NewMobileModuleProjectWizard.java:290) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:349) com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:252) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 1 org.eclipse.core.resources 4 272 2012-07-02 15:22:40.111 !MESSAGE A resource already exists on disk '/Users/mxia/Documents/workspace/runtime-New_configuration_ts2/tistud1648/.settings'. !ENTRY com.aptana.editor.common 4 0 2012-07-02 15:22:40.189 !MESSAGE (Build 0.0.0.qualifier) [ERROR] Error saving the user-agent preferences. !STACK 0 org.osgi.service.prefs.BackingStoreException: Exception occurred while saving project preferences: /tistud1648/.settings/com.aptana.editor.common.prefs. org.eclipse.core.internal.resources.ProjectPreferences.save(ProjectPreferences.java:600) org.eclipse.core.internal.preferences.EclipsePreferences.internalFlush(EclipsePreferences.java:440) org.eclipse.core.internal.resources.ProjectPreferences.flush(ProjectPreferences.java:350) com.aptana.editor.common.contentassist.UserAgentManager.savePreference(UserAgentManager.java:722) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.applyPreferenceValues(BasicNewTitaniumProjectWizard.java:487) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:392) com.appcelerator.titanium.mobile.ui.module.wizard.NewMobileModuleProjectWizard.finalizeProjectCreation(NewMobileModuleProjectWizard.java:290) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:349) com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:252) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code}
| 8 |
train
|
TISTUD-1835
|
Incorrect items appear under Publish menu the first time right-clicking on a project
|
Steps to reproduce: 1. Open Studio on a workspace with existing projects; 2. right-click on a Titanium mobile project (other types of project shows the behavior too) and select Publish to generate its submenus. Expected result: only the menu items appropriate for the project type will appear. Actual result: the submenus are not filtered, and all items contributed to the Publish menu show up. This only happens the first time the publish menu is generated. The correct menu items will appear when right-clicking again, even without a change in selection.
| 8 |
train
|
TISTUD-1836
|
Titanium Studio: Dashboard: Configuration Wizard: Android SDK: Cancel before download begins freezes process
|
In the Dashboard Configuration Wizard for Android, if the installer is canceled before the Android SDK download begins, the process will freeze. jstack cannot get a stack trace when Studio is in this state, but Studio is useable as the process is running in the background. This is not a regression. This is not intermittent. Steps to Reproduce: 1. Open Titanium Studio. 2. Open Preferences > Titanium Studio > Titanium and delete the Android SDK Home path. 3. Go to the Dashboard > Configure > Android > Install/Upgrade to run the Configuration Wizard. 4. Enter a path to download the Android SDK (e.g., Desktop/TestAndroidSDK) but do not press OK yet. 5. Very quickly (for reliable reproduction), press OK, then Cancel in the previous menu. Actual Result: Process freeze. Expected Result: Cancel the process.
| 8 |
train
|
TISTUD-1839
|
Add check for pre-existing files to Titanium Mobile Project creation wizards
|
Alert: Please save you Desktop or Document links, folders and file and create sample folder to test this bug. This is not a regression. Creating the Titanium Mobile Project on Desktop or Document folder and deleting it from the desktop, clean up all the folders and files. Step to reproduce: 1. Create Ti.Mobile Project 2. Change the default location to the Desktop 3. See if the Ti.Mobile Project is get created in project Explorer 4. Delete the Project and select delete the project form the disk Actual result: Pressing the delete from disk will delete all the contents from the desktop. Expected result: User should be presented with a warning or be restricted from deleting a project from a directory that isn't the same as the project. This way a situation like deleting the Desktop or Documents directory doesn't occur.
| 8 |
train
|
TISTUD-1840
|
Error while selecting JavaScript Formatter in Preferences
|
1. Open Preferences in Titanium Studio. 2. Select Titanium Stduio->Formatter 3. Select JavaScript and Preview. 4. Error is seen. ( Screenshot attached). 5. After this step, 'preferences' cannot be opened. Screenshot is attached. ( Studio has to be restarted)
| 8 |
train
|
TISTUD-1842
|
Improve prompt when Titanium Module can't be downloaded
|
h3. Steps to replicate # Select *Help > Install Module from URL* # Paste in URL https://developer.appcelerator.com/package/download/12/581/ti.barcode-iphone-1.8.1-android-1.7-2.3.2.zip h3. Expected result Module is behind a redirect. If we can't download, alert the user with the message: "Unable to download module from specified URL. Is the URL valid?" Then re-open the dialog box so they can check and try again. h3. Actual Result Process starts but fails without warning
| 5 |
train
|
TISTUD-1843
|
handle URL redirects in module download/installation
|
h3. Steps to replicate # Select *Help > Install Module from URL* # Paste in URL https://developer.appcelerator.com/package/download/12/581/ti.barcode-iphone-1.8.1-android-1.7-2.3.2.zip h3. Expected result Module downloads. h3. Actual Result Nothing happens.
| 8 |
train
|
TISTUD-1846
|
Titanium Studio: Available Updates: Object Teams Patch for JDT/Core is not applicable to the current configuration and will not be installed
|
When updating Titanium Studio, the JDT plug-in generates warnings. {code} !MESSAGE "Object Teams Patch for JDT/Core" is not applicable to the current configuration and will not be installed. {code} This is not a regression. This issue also occurs in Eclipse Indigo 3.7.2. Steps to Reproduce: 1. Install JDT plugin in Studio: https://wiki.appcelerator.org/display/guides2/Installing+the+Java+Development+Tools 2. Restart Studio. 3. Go to Help > Check for Updates. 4. Install the JDT Patch. Restart Studio. 5. Go to Help > Check for Updates. Actual Result: JDT plugin generates errors. Have to deselect JDT to update regular Studio updates. Expected Result: JDT should be able to install.
| 8 |
train
|
TISTUD-1848
|
Include offline API and Help documentation
|
h4. Problem Description If you don't have a working internet connection, you won't be able to browse the Ti Mobile SDK Docs from the help menu in the Ti Studio. Would be nice if we include the doc in SDK's Zipfile, so you can get the exact doc according to which SDK you are using. This will make easier to work with Titanium when in a flight or similar places. This should be a separate feature added to the update site.
| 20 |
train
|
TISTUD-1851
|
Install Alloy package using NPM
|
The determination of whether or not this needs to be run under sudo may not be easy for us to determine. We may need to assume no need for sudo? If we do need to run under sudo we'll need to handle prompting for the sudo password and piping it along to the command. {code} [sudo] npm install -g alloy {code}
| 8 |
train
|
TISTUD-1852
|
Move Template selection to front of project wizards
|
We move project template selection to the first screen in the project wizard (see Xcode for an example here) This allows the user to focus on what they want to create (blank project, game, rss reader, master/detail, etc.). We then ask the user to fill in the name/location/etc later. (Basically swap the first and second page in most project wizards).
| 5 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.