issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-2754
|
Publish: Web Deployment Wizard: Capistrano missing icon
|
Publish: Web Deployment Wizard: Capistrano missing icon. See screenshot. Steps to Reproduce: 1. Create Web Project. 2. Publish > Web Deployment Wizard... Actual Result: Capistrano missing icon. Expected Result: All options have an icon.
| 5 |
train
|
TISTUD-2755
|
Remove Run Web Deployment Wizard option from the Node.ACS Project
|
Node.ACS: Titanium Project Service Publish missing Web Deployment Wizard option. See screenshot. Steps to Reproduce: 1. Create Titanium Project. 2. Add New Node.ACS Service to project. 3. Select Publish > ... Actual Result: There is no 'Run Web Deployment Wizard...' option with the other ACS options. Expected Result: Titanium Project Services should have same deployment options as Node.ACS Projects. 'Run Web Deployment Wizard...' should appear for both.
| 5 |
train
|
TISTUD-2757
|
Node.ACS: add custom icon for Node.ACS projects instead of Titanium Classic icons
|
Currently the Node.ACS natures are using Titanium Classic icons. This causes visual conflict and contextual conflict. See deployment menus, project explorer, new project icons, and project nature icons to see the context of this issue. Ideally Titanium Projects and Modules would use the Titanium Classic icons for all these scenarios, and Node.ACS features would have a separate icon. See screenshots.
| 8 |
train
|
TISTUD-2764
|
Node.ACS: post-publish url pop-up has spelling and info errors
|
When a user publishes a node.acs service, and the pop-up appears that contains the url, there is one spelling error and some outdated info. See screenshot. 'apps' should be 'app's' version should be '' (removed as it no longer applies) Steps to Reproduce: 1. Create Node.ACS Project. 2. Publish and view URL dialog. Actual Result: Spelling and factual errors. Expected Result: No spelling or factual errors.
| 1 |
train
|
TISTUD-6269
|
Ti Studio should be smart enough to know when your trying to add a New Controller to a Widget
|
From the App Explorer Window in Ti Studio - right click the custom widget folder that you would like to add a controller. Select New->Alloy Controller Expected Behavior: A new alloy controller is created in your widget Actual Behavior A new alloy controller is added to the main app folder tree
| 5 |
train
|
TISTUD-2766
|
Failed to execute runnable (java.lang.IllegalArgumentException: Index out of bounds)
|
Found while testing TISTUD-2679: {code} !ENTRY org.eclipse.ui 4 0 2012-11-08 12:48:37.161 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Index out of bounds) at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) Caused by: java.lang.IllegalArgumentException: Index out of bounds at org.eclipse.swt.SWT.error(SWT.java:4263) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.custom.StyledText.setStyleRanges(StyledText.java:9661) at org.eclipse.swt.custom.StyledText.replaceStyleRanges(StyledText.java:7713) at org.eclipse.jface.text.TextViewer.addPresentation(TextViewer.java:4811) at org.eclipse.jface.text.TextViewer.changeTextPresentation(TextViewer.java:4890) at com.aptana.editor.common.text.reconciler.CommonPresentationReconciler$1.run(CommonPresentationReconciler.java:227) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164) at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 22 more !ENTRY com.aptana.editor.common 2 0 2012-11-08 12:48:37.163 !MESSAGE (Build 3.0.0.201211071923) [WARNING] Was unable to add folding position. Start: 1,545,140, end: 0 {code} Steps to Reproduce: 1. Edit large attached file in studio. 2. Scroll top to bottom 3. Cut the contents 4. Paste them back 5. Save the file 6. Repeat steps 3 thru 5. Actual Result: The above output Expected Result: Studio should not throw an error.
| 8 |
train
|
TISTUD-2768
|
Splash: login fields need focus when menu appears
|
When splash screen logins are loaded, the user field does not have focus. This occurs for registration and login. See screenshots for current and expected behavior. This is not a regression. Steps to Reproduce: 1. Logout and restart Studio. 2. Select either 'Login' or 'Register' from radio button and click 'Next'. Actual Result: User field is not selected, user must manually select field to edit. Expected Result: User field should have focus, user should be able to begin typing right away.
| 3 |
train
|
TISTUD-2770
|
Windows 8: npm isn't recognized as installed until restart
|
Windows 8: npm isn't recognized as installed until restart. See log attached. There is a GUI error. Steps to Reproduce: 1. Clean install Titanium Studio. 2. Take all Titanium Updates. Actual Result: npm error. node modules not installed. restart allows modules to install. Expected Result: npm installs correctly. node modules install correctly. studio does not require restart.
| 8 |
train
|
TISTUD-2775
|
Add support for running on BlackBerry device
| null | 20 |
train
|
TISTUD-2776
|
Titanium CLI: Pass in Titanium SDK directory to CLI
|
If the Titanium SDK is in a non-default location, the cli will not recognize the new location unless it is explicitly passed in from studio. See TIMOB-11753 for cli commands. Steps to Reproduce: 1. Move Titanium SDK to Desktop. 2. Set Titanium SDK to new location in Studio Preferences. 3. Create a new Titanium project using Titanium SDK 3.0.0+. Actual Result: Fail. This works in Studio 2.1.2. Expected Result: Studio passes in the Titanium SDK to the cli at some point, and the scripts work.
| 8 |
train
|
TISTUD-2777
|
Project imported from git cannot be built
|
h1. Problem description I've imported a project from git in 3 different ways: 1. clone the repository and then use "Import" 2. clone the repository and then use "Promote to project" 3. using the integrated "Import from git" feature In all cases, the project does not show any option to build. The tiapp.xml has the right settings (Android, iPhone and iPad are active), but the menu does not show any build option. The debug button is disabled.
| 5 |
train
|
TISTUD-2778
|
Showing Toolbar does not persist after restart when in simple Studio perspective
|
1. Start Titanium Studio on a new empty workspace; 2. Select Window > Show Toolbar from the main menu to make toolbar visible; 3. Restart Studio. Expected result: the toolbar stays visible. Actual result: the toolbar is hidden again. Workaround: after making toolbar visible, switch to extended Studio perpsective, then restart Studio. After that, switch back to simple perspective and the toolbar will persist afterward.
| 5 |
train
|
TISTUD-2780
|
Checkbox not appearing in splash screen on Windows when system has a large font size
|
See the attached screenshot. We should use a fix size instead of relying on system's font size.
| 3 |
train
|
TISTUD-2783
|
Provide Content Assist for Alloy Elements in view XML files
|
Alloy uses XML files to define views. We should provide content assist for the elements (tags). {code:xml} <Alloy> <View /> </Alloy> {code} The list of elements is defined as Titanium.UI.* types. There will likely be a need to further refine/filter the subtypes that make sense. Additionally Alloy uses some non-standard namespace mappings for some elements, so there are tags which are not Titanium.UI.* such as {{Toolbar}} which is mapped to {{Titanium.UI.iOS.Toolbar}}. Lastly, the root tag is {{Alloy}} and you can have {{<Require>}} tags.
| 13 |
train
|
TISTUD-2784
|
Provide Content Assist for attribute names in Alloy view XML files
|
Alloy uses XML files to define views. We should provide content assist for the attributes of elements. {code:xml} <Alloy> <View class="my_class" id="myLabel" onClick="" /> </Alloy> {code} For attribute CA we need to look up the properties for the given element's type in the JS index, as well as the events. To look up the type name, we take the element name as the type name and determine the namespace prefix. The default prefix is {{Titanium.UI.}}. If there is an {{ns}} attribute, use it's value as the namespace. Alloy will provide us with the exceptions to the rule for namespace mappings. e.g. {{View}} -> {{Titanium.UI.View}} {{Label}} -> {{Titanium.UI.Label}} {{<View ns="Ti.Map"/>}} -> {{Titanium.Map.View}} {{Toolbar}} -> {{Titanium.UI.iOS.Toolbar}} The list of attribute name proposals is: # The list of properties of the type # The list of events of the type. Each event name is transformed to be {{"on" + Character.toUppercase(event.name().charAt(0)) + event.name().substring(1);}} - i.e. "click" -> "onClick" # The common set of attributes: {{class}}, {{id}} and {{ns}}. It should be noted that the {{Alloy}} element may only have {{class}} and {{id}} attributes. The special {{Require}} element may have {{class}}, {{id}}, {{src}}, and {{type}}.
| 13 |
train
|
TISTUD-2785
|
Hook up a special Content Assist processor for Alloy view XML files
|
We need to provide Content Assist specific to Alloy view XML files. They use a standard *.xml file extension. We'll need to add an Alloy XML Editor and hook up a specialized content assist processor so that for *.xml files in an alloy project (under the app/view/ tree) we have the Alloy-specific CA hooked up.
| 8 |
train
|
TISTUD-2789
|
Create a TSS lexer
|
We need to generate a TSS lexer to feed the parser. See the PEGJS grammar here: https://github.com/appcelerator/alloy/blob/master/Alloy/grammar/tss.pegjs We'll need to extract a JFlex TSS.lex file from the rules there.
| 13 |
train
|
TISTUD-2790
|
Create a TSS parser
|
We need to generate a TSS Parser. See the PEGJS grammar here: https://github.com/appcelerator/alloy/blob/master/Alloy/grammar/tss.pegjs We'll need to generate an LALR grammar from that and then use beaver to generate a parser. We may be able to simply copy the JSON.grammar and modify slightly to handle the changes that alloy introduces.
| 13 |
train
|
TISTUD-2791
|
Create a TSS editor
|
Once we have a TSS grammar and lexer, we need to create a TSS editor and associate it with *.tss files. We should remove the old association between JSON and *.tss.
| 8 |
train
|
TISTUD-2792
|
Colorize TSS files
|
Once we have a TSS editor, we'll need to hook up coloring. This involves setting up partitions, a partition scanner, and token scanners for the partitions. We can look to {{JSONSourceConfiguration}} as the example to copy and slightly modify. We can likely re-use the lexer/grammar that the TSS parser uses.
| 8 |
train
|
TISTUD-2793
|
Validate TSS file syntax
|
Once we have a proper parser we can use it to highlight syntax errors. This will involve creating a build participant that simply grabs the context's AST, asks for the SyntaxErrors and hooks them as problems to the BuildContext. See {{JSParserValidator}}
| 8 |
train
|
TISTUD-2796
|
Offer content assist on TSS keys - UI types
|
We need to offer up content assist for the keys of the JSON like objects in TSS files. {code} "Window": { backgroundColor: '#fff' } {code} The {{"Window"}} token is what we'd suggest. The list of elements to suggest is the same list of types of elements we'd suggest in the XML view files from TISTUD-2783. Please see that ticket for the list of types.
| 8 |
train
|
TISTUD-2797
|
Offer content assist on TSS keys - classes and IDs
|
We need to offer up content assist for the keys of the JSON-like objects in TSS files. This ticket specifically addresses offerring up the list of classes and IDs found in the view files. {code} <!-- index.xml --> <Label id="myLabel"/> // index.tss "#myLabel": { text: 'some text' } {code} The {{"#myLabel"}} token is what we'd suggest. IDs use a {{#}} prefix like in CSS, and classes use {{.}}. The list of classes and ids is found by querying the indexed values from TISTUD-2798. app.tss should query all files. For other tss files we can limit the scope to just the associated view (same hierarchy and basename).
| 8 |
train
|
TISTUD-2798
|
Index Alloy view XML files to record id and class declarations with type info
|
We'll need to begin indexing alloy's XML files to record the list of classes and ids used. This will then be used for TSS code assist. The involves adding a new IndexBuildParticipant for XML files. In the participant we may filter when we activate to only projects with alloy nature and files under app/views/. The participant would parse the XMl file and traverse the AST to get the class/id attribute info. When we record a class or id reference, we will likely also want to record the fully qualified type name of the element it is on. {code} <!-- index.xml --> <Alloy> <Window> <!-- implicit id of "index" --> <Label id="myLabel"/> </Window> </Alloy> {code} In this case we'd record that index.xml has a Titanium.UI.Label with an id value of "myLabel". The type is required to determine the property list in TSS content assist, as well as content assist in controller JS. The type namespace mapping is the same as in TISTUD-2783. Please note that the top-level widget (the child under the {{<Alloy>}} tag) in a view has an implicit id of the file's basename, so the top-level {{Window}} of index.xml would have an id of "index").
| 8 |
train
|
TISTUD-2799
|
Provide content assist for property names in TSS
|
We need to provide content assist for the list of property names for a given element in TSS files. {code} "Window": { backgroundColor: '#fff' } {code} {{backgroundColor}} is the token we'd suggest. We should take the string which is the key of the surrounding object, convert it to a fully qualified type name (see TISTUD-2783), then query the list of properties for that type. If the string is not the name of a type, but is a class or id, we need to query the class/id index from the view files to resolve it to the type it is hanging off.
| 8 |
train
|
TISTUD-2806
|
Fresh installation of Titanium SDK does not appear in the project creation dialog
|
Have a newly installed Studio, and no Titanium SDK. # Install an SDK via the "Install Specific Titanium SDK..." menu, or via the Studio prompt to install on startup. # Let the Studio complete the installation. # Click to create a new Mobile project. Notice that the Titanium SDK version drop-down is empty. Restarting the Studio fixes the problem. This issue does not effect versions where there is already (at least) one SDK version installed.
| 5 |
train
|
TISTUD-2813
|
Studio: node.acs - Cannot set cname for a deployed node.acs project
|
*Details:* After deploying a node.acs app, I cannot set the cname for the deployed app. *Steps to reproduce:* 1. In TiStudio, right-click on the Project Explorer and go to New > Node.ACS Project 2. Specify a project name and press finish 3. Right-click on the newly created project and go to Publish > Deploy App 4. Wait for published URL to appear and press ok 5. Link the published URL in your domain DNS setting 6. Back in TiStudio, right-click on the project and go to Node.ACS > Set CNAME 7. Enter your cname URL *Actual:* Studio returns a "Failed to Set CName" error dialog. See attachments. *Expected:* Studio should allow you to set the cname. *Note:* Steps to work around this: 1. Open your terminal/cmd 2. cd into node.acs project 3. Use the following command: *acs cname --set <CNAME_URL>*
| 2 |
train
|
TISTUD-2827
|
Errors occur when extracting a module or sdk to the Titanium dir
|
Extracting a module or sdk to the Titanium directory generates errors in Studio, see below. There are a large number of errors and it looks like they are all the same. {code} !ENTRY org.eclipse.ui 4 4 2012-11-19 11:04:51.055 !MESSAGE An internal error has occurred. !STACK 0 java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?) org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1681) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppSDKSection.updateControlsData(TiAppSDKSection.java:324) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppSDKSection$1$1.runInUIThread(TiAppSDKSection.java:105) org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) 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.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} h4. Steps to repro: 1. Open a project in Studio 2. unzip a module into your Titanium directory (../Application Support/Titanium) 3. notice the error dialog that pops up and the errors in the log.
| 5 |
train
|
TISTUD-2829
|
Node.ACS: adopt standard capitalization on tail logs and set cname menu commands
|
currently the capitalization of the node.acs tail logs and set cname menu commands is non-standard. See screenshot. Current Capitalization: Tail logs, Set CNAME Expected Capitalization: Tail Logs, Set CName Steps to Reproduce: 1. Create Node.ACS Project. 2. Context Click > Node.ACS > ...
| 2 |
train
|
TISTUD-2831
|
Cannot open the browser correctly when running MobileWeb code
|
Not a regression. h1. Problem description When running an app using "MobileWeb Preview in Browser", the chosen browser is not correctly used. Sometimes, Firefox is used (although I set the default browser or Chrome), other times I get this error: "Could not launch external web browser for http://127.0.0.1:8020/index.html. Check the Web Browser Preferences." Attached the settings screen: as you can see, the Chrome browser is chosen.
| 8 |
train
|
TISTUD-2832
|
Inconsistent functionality in login windows
|
The cancel button's action for the first selection page and the existing account page differ from the cancel button action on the new user signup page. Clicking cancel on the initial screen exits the program. Clicking cancel on the existing user log in page exits the program. Clicking cancel on the new user signup page takes the user back to the initial page. This is inconsistent and may cause user confusion. Steps to reproduce: 1. Open Titanium Studio without having logged in. 2. Select "I don't have an account with Appcelerator" 3. Click Cancel. 4. Select "I do have an account with Appcelerator" 5. Click Cancel. 6. Start Titanium Studio again. 7. Click Cancel. Expected results: Initial cancel closes program. Both secondary cancel buttons either takes the user back to the initial screen or exit the program. Actual results: Canceling on the page with the user signup takes you back, while the cancel on the existing user page closes the program.
| 5 |
train
|
TISTUD-2837
|
Android Preferences: android sdks not detected until titanium sdk path is set and studio restarts
|
In the Titanium Preferences, if the titanium sdk path is set for the first time, then the android sdk path is set for the first time, the android sdks will not list and there is an error. Restarting studio fixes the issue. This did not occur in Studio 2.1.2. This is a regression. Titanium Preferences: {code} Problems detected with the SDK settings. {code} Titanium Preferences Details: {code} An error was detected with the SDKs configuration. Reason: [ANDROID SDK Home] No platform SDKs were found. Click 'Configure' to install new platforms. {code} Steps to Reproduce: 1. Open Titanium Studio. 2. Open Preferences > Titanium. 3. Delete Titanium SDK path. 4. Delete Android SDK path. 5. Apply changes. 6. Enter valid Titanium SDK path. 7. Enter valid Android SDK path. Actual Result: Errors in preferences, can't select android sdk. Android SDK is correctly installed. Restarting studio fixes issue. Expected Result: No errors. Android SDKs listed.
| 5 |
train
|
TISTUD-2842
|
ACS: no protocol: Unable to parse URL for publish
|
When trying to publish an ACS project on Windows 8, I get the success window with the error no protocol: Unable to parse URL for publish. I get the following error in my log file: {code} !ENTRY com.aptana.ui 4 0 2012-11-21 07:59:21.018 !MESSAGE (Build 3.0.0.201211202053) [ERROR] no protocol: Unable to parse URL for publish !STACK 0 java.net.MalformedURLException: no protocol: Unable to parse URL for publish java.net.URL.<init>(Unknown Source) java.net.URL.<init>(Unknown Source) java.net.URL.<init>(Unknown Source) com.aptana.ui.util.WorkbenchBrowserUtil.launchExternalBrowser(WorkbenchBrowserUtil.java:35) com.aptana.ui.dialogs.HyperlinkMessageDialog.openLink(HyperlinkMessageDialog.java:115) com.aptana.ui.dialogs.HyperlinkMessageDialog$1.widgetSelected(HyperlinkMessageDialog.java:89) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1094) org.eclipse.swt.widgets.Link.wmNotifyChild(Link.java:1071) org.eclipse.swt.widgets.Control.wmNotify(Control.java:5534) org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:1896) org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:5086) org.eclipse.swt.widgets.Control.windowProc(Control.java:4584) org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1610) org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2061) org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2425) org.eclipse.swt.widgets.Link.callWindowProc(Link.java:172) org.eclipse.swt.widgets.Widget.wmLButtonUp(Widget.java:2057) org.eclipse.swt.widgets.Control.WM_LBUTTONUP(Control.java:4912) org.eclipse.swt.widgets.Link.WM_LBUTTONUP(Link.java:909) org.eclipse.swt.widgets.Control.windowProc(Control.java:4565) org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2531) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334) com.appcelerator.titanium.acs.ui.deploy.NodeACSDeployProvider$4.run(NodeACSDeployProvider.java:254) 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:4140) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} This is a regression as ACS previously published. Steps to reproduce: 1. Create a new ACS project. 2. Publish ACS (Publish > Deploy App) Expected result: The project should correctly publish to ACS servers Actual result: The project fails to publish and throws the above error.
| 5 |
train
|
TISTUD-2843
|
Studio repeatedly prompts to install the same node.js modules NPM_CONFIG_PREFIX
|
I'm repeatedly prompted to install the same Node.js packages (CLI, ACS, and Alloy), despite the fact that they appear to install successfully each time. It appears (since Studio is prompting me with the admin password) that it is failing to respect the NPM_CONFIG_PREFIX I have set in my environment, but that when node is actually invoked, it's looking for modules based on the NPM_CONFIG_PREFIX. I have Node configured to install modules under $HOME specifically so I don't have to do sudo to install modules. Studio should provide a means to configure the NPM_CONFIG_PREFIX so it can use the correct set.
| 13 |
train
|
TISTUD-2844
|
Projects: non-default save location should be pre-populated with old path and have existing file warnings
|
In the new project wizard (for any project type), if the user selects the 'non-default location' checkbox, the previously readonly path should remain, and if the non-default location contains existing files, there should be a warning in the new project wizard. This is not standard eclipse behavior, but it is standard ADT behavior, and it is a major usability issue. Steps to Reproduce: 1. Create a new folder with a new file (i.e., Downloads/myfolder/myfile). 2. Bring up New Project Wizard in Studio (any project type, Titanium Project for example). 3. Select 'non-default location' for project location. 4. Select the 'newfolder' as project location. Actual Result: No pre-existing 'workspace/newproject' path in the text field. User must manually select path. No warnings of existing files in new selected folder. Expected Result: Old 'workspace/newproject' path is in the text field. Selecting a folder with existing files generates a warning in the wizard.
| 5 |
train
|
TISTUD-2847
|
dirty files not selected for save when binding Node.ACS service to titanium project
|
When a titanium project has a dirty app.js file and 'project context click > node.acs > bind node.acs service' is called, the app.js file is not selected by default. Steps to Reproduce: 1. Create Titanium Project. 2. Create Node.ACS Project. 3. Edit titanium project app.js, don't save. 4. Titanium Project Context Click > Node.ACS > Bind Node.ACS Service and proceed to the save menu. Actual Result: app.js is not selected, the process will quit Expected Result: app.js should be selected by default, as with other save prompts
| 5 |
train
|
TISTUD-2850
|
Windows 7: Error :"URI is not absolute " is coming while creating titanium project.
|
Test Steps: 1. Open Titanium Studio. 2.Create default titanium studio project. Expected results: Project should be created. Actual result: Error is thrown.Please see logs and screenshot attached.
| 3 |
train
|
TISTUD-2852
|
Studio: Create Alloy project option does not appear even after complete installation. "Unable to find 'alloy' binary." exception occurs.
|
Steps to Reproduce: 1. Install Studio 3.0 with all updates. 2. Go to File>New>Titanium Project Actual: Observe option to create alloy project does not appear. And Studio Logs show "org.eclipse.core.runtime.CoreException: Unable to find 'alloy' binary." exception. [Note: If Logs do not show any message then Restart studio and run 2nd step again.] Expected: No exception must appear and Create Alloy project option must appear. Also Run Diagnostic test must display correct information about installed and uninstalled programs. Refer Diagnostic.png
| 5 |
train
|
TISTUD-2853
|
Studio: Installation issues with node.ACS shown even after complete installation of ACS
|
Steps to Reproduce: 1. Install Studio 3.0 with all updates. 2. Go to File>New>Node.ACS Project 3. Provide any appropriate name and click Finish. Actual: "Node.ACS is not configured properly. The "acs" executable/node package is not installed." message appears. Expected: Project must get created without ny ero
| 5 |
train
|
TISTUD-2855
|
Content Assist: Content Assist window does not display "Ti" in suggestions.
|
Steps To Reproduce: 1. Install 3.0 with all updates. 2. Create a project and open app.js 4. Press Ctrl+space to bring content assist window. Ex: No suggestions for "Ti.API.info("");" or Ti.UI.Window Actual: "Ti." does not appear in suggestions. Expected: "Ti." must appear in content assist window.
| 5 |
train
|
TISTUD-2872
|
Not able to run updates: NPE
|
*Problem description* When i try to search for updates via help menu I receive the following error: "java.lang.NullPointerException" I need to run the update to get access to the mobile SDK.
| 3 |
train
|
TISTUD-2859
|
Update the version of Node.js we download to 0.8.14
|
The current version we host is 0.8.3. We should update to the latest 0.8.14 to avoid issues like NODEJS-493.
| 3 |
train
|
TISTUD-2860
|
CLI: old python scripts called for all commands
|
Test Steps : 1. Install Titanium Studio latest version. 2.Update CLI to latest version. 3.Enable Preferences > Titanium Studio > Troubleshooting: Debug => All. 4. Create a Titanium ACS project. 5.Clean that project. 6.Observe log file. Expected Result: new cli: "/usr/local/bin/titanium" should be used. Actual Result: old cli:"/usr/bin/python" is being used by Titanium Studio.
| 2 |
train
|
TISTUD-2861
|
Studio: "java.lang.UnsupportedOperationException" occurs while switching on new workspace and initializing node.ACS.
|
Steps to Reproduce: 1. Install 3.0 latest version studio. 2. Now switch to new workspace. Actual: An internal error occurred during: "Initializing Node.ACS". "java.lang.UnsupportedOperationException" occurs after switching to new workspace. [Refer attached Screenshot and text log.] Expected: No exception should appear.
| 3 |
train
|
TISTUD-2863
|
Dashboard: Update Android SDK to r21 on Staging
|
Dashboard: Update Android SDK to 21 on Staging
| 3 |
train
|
TISTUD-2865
|
TiStudio: Projects - A pane is missing when creating the default Titanium project on Ubuntu 12.04
|
Details: If you try to create the default Titanium project on Ubuntu 12.04, then the pane is missing. This bug *does not appear* on Mac OS X Lion (10.7.5), Windows 7, and Ubuntu 10.04 Steps to reproduce: 1. On Ubuntu 12.04, Open TiStudio 2. Right-click in the Project Explorer space 3. Select New > Titanium Project Actual: A pane is missing on the right side (see ubuntu_1204.png) Expected: A pane should appear on the right side (see on_mac.png)
| 5 |
train
|
TISTUD-2866
|
Xcode 4.3.3 : Distribute Ad hoc/ Enterprise with 'ipa' format is throwing error
|
Test Steps: 1.Install latest studio . 2.Install Xcode 4.3.3 . 3.Create a Titanium Mobile project with iphone only. 4.Package the iPhone Project with Distribute Ad hoc/ Enterprise. 5. Select 'ipa' as format. 6.Create a new folder and browse to that specified location. 7.Select 'Publish' P.S. : The provisioning file is working fine . I am able to package same project with 'app' format .Also "Distribute Apple iTune store' publish option is working fine. Actual result: [ERROR] Error copying iOS ipa output to destination.
| 8 |
train
|
TISTUD-2889
|
Allow user to set preference to NodeJS source path
|
NodeJS's core modules are defined in JS files under the lib subdir of the Node source package. This is not installed when the binary is. If the user has a source package on their system, we should allow them to point to it so we can look up those core modules. This would involve setting up a preference constant to use as the key to store the path, as well as the UI fields to set/edit it in the Node preference page (which already exists and has a field for setting the path to the binary install).
| 5 |
train
|
TISTUD-2890
|
Index NodeJS source install's core modules under lib dir
|
Once the user is able to set the path to the NodeJS source folder we need to be able to index it to get the details of the core modules under lib. These are straight JS files, so we can index them using our current mechanism. This should be treated like a 3rd-party library that can be attached to JS projects (much like an external JAR for JDT, possibly even just attaching "Node" to a project entirely which would be like attaching a JDK so it attaches the core modules form source and the $NODE_PATH from the binary install).
| 8 |
train
|
TISTUD-2871
|
Allow pluggable inferencing/lookup of require calls
|
Titanium SDK's usage of {{require}} is slightly different than what NodeJS/CommonJS uses as it has an implicit base path of {{<project>/Resources}} An example: {code} var r = require('http'); {code} In Node, we'd load the core 'http' module. In Titanium we'd look for {{<project>/Resources/http.js}}. Additionally, Titanium merges the platform-specific subfolders of Resources. So... {code} var taskWindow = require('ui/TaskWindow'); {code} Would look up {{Resources/iphone/ui/TaskWindow.js}} and {{Resources/android/ui/TaskWindow.js}} Additionally you can specify a native Titanium module id to load.
| 13 |
train
|
TISTUD-2892
|
Add button to download and unzip NodeJS source for user
|
To make things easier for users we should offer to download and unzip the NodeJS source for them. That way they don't need to google it download it and then hook up the location.
| 8 |
train
|
TISTUD-2880
|
Allow user to install Node.ACS feature from the dashboard
|
Add a link in dashboard to install Node.ACS into Studio (need a mock up). We also need to check a portal action exists to install plugins from a specific url.
| 8 |
train
|
TISTUD-2881
|
Preferences: Android SDK List Persists When Path Deleted
|
Not a regression. If Android SDK path is deleted in the Preferences, the Default Android SDKs list is still populated. The list should clear if there is no valid path selected. The list will correctly go away if the Preferences are reloaded. Steps to Reproduce: 1. Open Preferences > Titanium. 2. Delete Android SDK path. Actual Result: Default Android SDK List Persists. Expected Result: Default Android SDK List Disappears. Screen Types List Disappears.
| 5 |
train
|
TISTUD-2882
|
Dashboard: Previous Android SDK Installations Not Recognized
|
Not a regression. If Android SDK is installed, and that path is used to install the Android SDK using the dashboard config utility, the SDK will download again and ignore the current SDK installation at that path. Steps to Reproduce: 1. Have existing Android SDK installation. 2. Delete Android SDK path in Studio Preferences. 3. Run Dashboard Configure Android and enter path to existing Android SDK. 4. Begin Installation. Actual Result: Android SDK downloads again. Expected Result: Currently existing Android SDK in the specified path should be recognized and the SDK Manager should launch.
| 5 |
train
|
TISTUD-2884
|
Verify the existence of a Local Node.ACS Server when launching one for a Node.ACS project
|
Currently, when a Node.ACS project is being created, the Studio adds a local server settings in the Servers view. # Create a new Node.ACS project. # Open the Studio's Servers view. # Delete the created server. # Click the project and select the 'Run' option to launch a 'Local Node.ACS Server' The launch happens, even without the server in the servers view, and no server is being recreated. Expected: A recreation of the local server.
| 5 |
train
|
TISTUD-2885
|
A Local Node.ACS launch is not using its defined server's settings
|
When creating a new Node.ACS project, a new server is being added to the Servers view. # Create a new Node.ACS project. # Open the Studio's Servers View. # Click to edit the port number for the newly added server. # Launch the project's 'Run -> Local Node.ACS Server'. Result: The console indicate that the server is running. However, the port is not the same as the one that was defined. Changing the port again and re-launching does not make any difference. The Server settings and the server that runs seem as un-connected.
| 5 |
train
|
TISTUD-2886
|
Deleting a Node.ACS project does not delete its local server definition
|
When creating a new Node.ASC project, the Studio creates a new Server setting in the Servers view. # When deleting the project, the server is there to stay. # When launching the server via the Run menu, and then deleting the project, the server is still running. Expected: Shut down the server and remove it when needed.
| 3 |
train
|
TISTUD-2896
|
Import Project: Exception in log file when mobile project path contains apostrophe
|
On trying to import a titanium mobile project from a folder which has apostrophe in folder name, shows an exception in logs though the project imports successfully and also can be installed on emulator/simulator successfully. The issue also occurs on Studio 2.1.2 Steps to Reproduce: 1. Create a titanium mobile project in any folder outside the workspace that has the apostrophe in its name 2. Remove the project from project explorer and import it again 3. Check the studio logs Actual: An error is shown in the studio logs. (as attached) Expected: No error should be shown on importing a project
| 3 |
train
|
TISTUD-2898
|
(Windows) Cannot set Android SDK Home in Titanium Settings pane
|
The error can be seen in the attached error-1.jpg. Basically it's "Unknown command: --no-banner", then "Unexpected character (A) at position 0". This appears to be very similar to TISTUD-778. The only error in the log is this: http://pastie.org/5454102. I think I have fairly aggressive logging turned on (see troubleshooting_settings.jpg attached here), yet I cannot even see what command is being executed that is resulting in this error. I confirmed the following: * I can successfully run {{android list targets}} from a command prompt. * I have no ANDROID_SDK environment variable set. * I can successfully run {{python c:\Users\bill\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0\android\avd.py c:\Users\bill\android\android-sdk}} from a command prompt and see the expected results. I also completely uninstalled Ti Studio, completely removed my workspace folder, then re-downloaded the Studio RC and created a new workspace. Still the same error when trying to set my Android SDK Home.
| 5 |
train
|
TISTUD-2899
|
Preferences: Android SDK List Not Updated After Android SDK Install From Dashboard Until Studio Restart
|
When Android SDK is installed from Dashboard, the Android SDK list in the Preferences is not updated until Studio restart. This does not occur in Studio 2.1.2. This is a regression. Steps to Reproduce: 1. Delete Android SDK path in Preferences. 2. Install Android SDK from Dashboard. 3. In SDK Manager, install at least one compatible Google API SDK and the all the tools. 4. When update finishes, close SDK Manager, and open Studio Preferences > Titanium. Actual Result: Android SDK path is set, but Android SDKs are not listed until Studio restart. Expected Result: Android SDK path is set, Android SDKs and screen types are listed below without Studio restart.
| 5 |
train
|
TISTUD-2900
|
TiApp Editor: Titanium SDK List Not Updated Until TiApp editor Restart
|
If the Titanium SDK path is switched to another valid SDK path, the SDK list in the TiApp Editor is not updated in realtime. Studio must be restarted. This does not occur in Studio 2.1.2. This is a regression. Steps to Reproduce: 1. Copy full Titanium (sdk) folder to another location. 2. In the Titanium copy, delete a few SDKs (to provide contrast). 3. Open a Titanium Project. Open tiapp.xml, note the drop-down list of SDKs. 4. Change Preferences > Titanium SDK Path to another SDK installation (i.e., the copy). 5. Open the drop-down list in the tiapp.xml again. Actual Result: The SDK list is the same because it wasn't refreshed on Preference change. The TiApp editor must be restarted. Expected Result: SDK list immediately updated as it is in Studio 2.1.2.
| 5 |
train
|
TISTUD-2901
|
Dashboard: Installing Android SDK - Selecting an existing SDK directory still starts a download
|
# Remove any Android SDK paths from the Titanium Preferences. # Open the Dashboard and click the Android SDK installation button. # When the disk location dialog appears, select a location that has an existing Android SDK installation. # Click OK. Result: A download process begins. Expected: The selected location is a valid existing SDK installation, so we should just show the Android package dialog. No need to download a new SDK.
| 5 |
train
|
TISTUD-2902
|
Windows 8 Clean Install: NPM not recognized when File > Restart is run
|
When NPM is first installed and studio is restarted using File > Restart, npm is never recognized. Studio must be Exited to recognize npm. Steps to Reproduce: 1. Install node.js. 2. File > Restart. 3. check for titanium updates Actual Result: npm not found error, alerts user to restart studio as a work-around Expected Result: file > restart behaves the same as exit-reopen, npm is recognized if it is installed
| 8 |
train
|
TISTUD-2903
|
Ubuntu: splash screen radio buttons have odd rendering
|
The login splash has odd rendering near the radio buttons. There is a strange orange half-rectangle to the right of the buttons. Steps to Reproduce: 1. Logout and restart studio. Actual Result: Radio buttons have odd rendering just to the right of the buttons. Expected Result: Radio buttons render 'correctly'.
| 5 |
train
|
TISTUD-2905
|
TiApp editor: Grayed out deployment targets and modules when switching to a different Ti SDK
|
# Have two different Titanium SDKlocations. Have them contain different SDKs. # Create a Mobile app and have the TiApp editor open. # Go to the Titanium preferences and pick a different Titanium SDK location. # Apply and OK. Result: You will notice that the SDK combo changes its values. However, the 'Deployment Targets' and the 'Modules' sections are getting grayed out and have warnings.
| 3 |
train
|
TISTUD-2909
|
Content assist : JS Built in Types for 'Ma' and 'Docu' are not displayed in Content Assist for app.js file
|
1. Install Titanium Studio, build: 3.0.0.201211291910 2. Create a new project. 3. Create a new .JS file in the Resources folder 4. Type 'Ma' or 'Docu' After Step 3: Content Assist should appear and 'Math' and 'Document' respectively should be highlighted
| 5 |
train
|
TISTUD-2910
|
Content Assist: 'Testing' function info popup in app.js is showing all three parameters as (Object, object, object).
|
Test steps 1. Create a new project 2. Create a new .JS file in the Resources folder 3. Place the following content into the JS file sample.js /** * @param {String} a * This is the first parameter * @param {Object} b * The second parameter * @param {Number} c * Last one */ function testing(a, b, c) {} 4. In the JS file, type test followed by ctrl-space Expected result After step 4. Make sure that "testing" is highlighted in the popup. Make sure that the info popup shows three parameters for this function. The arguments should be String, Object, Number. Actual Result: Info popup for testing function is show all three parameters as (Object, object, object).
| 5 |
train
|
TISTUD-2912
|
Titanium Studio: Android Updater prompt which appears at the bottom right hand side of studio displays 'OK' which is unnecessary.
|
This is not a regression bug. Test Steps : Install latest studio and set path for Android SDK . Dashboard > Configure > Android. Update the android and after update process finishes , close that window. Observe that Android Updater prompt which appears at the bottom right hand side of titanium studio contais 'OK' which is unnecessary.Please refer attached screenshot.
| 2 |
train
|
TISTUD-2913
|
Investigate JS indexing of Alloy source/JSDuck comments
|
We'd like to provide CA for alloy APIs. We need to look into whether we can simply index the alloy source with the JSDuck comments to do so. We may need to extend our SDoc support to cover more tags provided by JSDuck (https://github.com/senchalabs/jsduck) If we can simply index the JS files with the JSDuck comments, then we can pretty easily fold this into our general node modules indexing, since the source will be available in the alloy module (/usr/local/lib/alloy/Alloy)
| 8 |
train
|
TISTUD-2914
|
Index NodeJS/npm modules
|
We should be able to index NodeJS/npm install's node modules. We can query npm for the install paths and then index all the modules we find underneath. We'd need a way to attach these loadpaths/indices to a project. Our current load provider support re-uses the index for the project, which isn't really correct - and it is assumed to return a lit of files to index, which we can do, but it may be easier to just return the directories. Ideally the NodeJS install as a whole would be a single "entry" (like a JRE/KDK for JDT) and it resolves to it's various paths and is indexed to it's own index/indices. Then the projects just add them to their list of indices to search/query.
| 13 |
train
|
TISTUD-2917
|
Implement Titanium require resolution
|
Titanium handles require slightly differently than Node/CommonJS. The value could be a module id for a native module or CommonJS module that exists int he project or the SDK itself. We need to be able to handle these cases.
| 13 |
train
|
TISTUD-2919
|
Console/build log needs to indicate which Titanium CLI is being called
|
Steps To Reproduce: 1. Build an application with CLI enabled Actual: Can't tell whether CLI was used Expected: To be able to log whether CLI is enable or disabled
| 5 |
train
|
TISTUD-2920
|
TiApp Editor with invalid sdk value opens in dirty state with no notification
|
Steps: 1. Open a tiapp.xml with invalid sdk value (open tiapp.xml in text editor and change version to an invalid one. Open in tiapp.xml editor) Expected results: 1. The editor should have error/warning about the invalid sdk version, or update to the latest sdk value and open a message dialog stating the sdk version was changed to a valid version Actual results: There are warnings displayed for a split second, then the warnings disappears and the editor is in dirty state
| 5 |
train
|
TISTUD-2922
|
MobileWeb Run Configuration: displayed selected browser does not refresh immediately after installed browser search
|
When a MobileWeb run config is opened, and the browser list is updated after searching for installed browsers, 'Default Browser' is always displayed as selected in the run config browser list. Selecting another browser does not change the display. The issue goes away if the run config is reopened. Steps to Reproduce: 1. Open MobileWeb Run Config. 2. Browser Drop-Down List > Search Installed Browsers, and select/recognize all browsers. 3. Select a browser in the run config drop-down list. Actual Result: After a browser is selected, 'Default Browser' always appears as the selected item. Reopening the run config fixes the issue. Expected Result: Browser list refreshes correctly after search for installed browsers is first run.
| 5 |
train
|
TISTUD-2924
|
NPE in the log when starting Studio
|
Ingo saw the following in the log: {code} !ENTRY org.eclipse.core.jobs 4 2 2012-11-30 16:22:47.527 !MESSAGE An internal error occurred during: "Start Ruble bundle manager". !STACK 0 java.lang.NullPointerException at java.lang.String.startsWith(Unknown Source) at java.lang.String.startsWith(Unknown Source) at com.aptana.scripting.model.BundleManager.getBundlePrecedence(BundleManager.java:1309) at com.aptana.scripting.model.BundleManager.getBundlePrecedence(BundleManager.java:1282) at com.aptana.scripting.model.BundleManager.isUserBundleDirectory(BundleManager.java:1912) at com.aptana.scripting.model.BundleManager.loadProjectBundles(BundleManager.java:2087) at com.aptana.scripting.model.BundleManager.loadBundles(BundleManager.java:2058) at com.aptana.scripting.ScriptingActivator$1.run(ScriptingActivator.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} Haven't been able to reproduce it though.
| 3 |
train
|
TISTUD-2925
|
Alloy: alloy.js plugin hook showing "read-only" JavaScript error
|
When creating a new alloy project, I'm seeing an error about a variable being "read-only" This is important as we warn people before running an application if it has errors in it. # Create a new Alloy project # Note the error on alloy.js I appear to only have our JS Syntax Validator turned on
| 5 |
train
|
TISTUD-2926
|
On a very large jsca file, Studio crashes with out-of-memory and 'Java heap space' error
|
This is a regression bug as it doesn't happen in 2.1.2 Steps to Reproduce: 1.Launch latest studio. 2.Create a project . Package ios ,android and web modules in that project. 3.Debug that project in emulator. Launch debugger multiple times for multiple projects. Also a I have added a long file onehundredsixtythousand.jsca (found on Barcelona: Appcelerator/QE/TestApplications/Content Assit/onehundredsixtythousand.jsca)in that project and debugged it. Actual Result: Studio becomes very slow and then freezes and crashes.Error prompt and logs have been attached. Also the logs have become vanished when I relaunched Studio and also update for Node.acs plugin feature again appear ( it was already installed but after studio crashes , it got removed )
| 8 |
train
|
TISTUD-2929
|
'Unhandled event loop exception' error is shown in logs when package a mobile web project and select third option 'create a new project for a mobile web app'
|
This is not a regression bug.It happens in Studio 2.1.2 with sdk 2.1.2 GA Test Steps: 1.Install latest studio. 2.Create a Titanium mobile two tabbed project only for mobile web. 3.From project explorer, package the mobile web project created in 2nd step. 4.Select the third option 'create a new project for a mobile web app'. 5.Give any name to the new project eg test234. 6.Pakage the project. Actual Error: Unhandled event loop exception error is coming.Logs attached. !ENTRY org.eclipse.ui 4 0 2012-12-03 10:51:31.374 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed) org.eclipse.swt.SWT.error(SWT.java:4282) org.eclipse.swt.SWT.error(SWT.java:4197) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) Caused by: org.eclipse.swt.SWTException: Widget is disposed org.eclipse.swt.SWT.error(SWT.java:4282) org.eclipse.swt.SWT.error(SWT.java:4197) org.eclipse.swt.SWT.error(SWT.java:4168) org.eclipse.swt.widgets.Widget.error(Widget.java:774) org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:568) org.eclipse.swt.widgets.Label.setText(Label.java:518) org.eclipse.jface.wizard.ProgressMonitorPart.updateLabel(ProgressMonitorPart.java:367) org.eclipse.jface.wizard.ProgressMonitorPart.subTask(ProgressMonitorPart.java:358) org.eclipse.jface.wizard.WizardDialog$4.subTask(WizardDialog.java:707) org.eclipse.jface.operation.AccumulatingProgressMonitor$Collector.run(AccumulatingProgressMonitor.java:94) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 22 more
| 5 |
train
|
TISTUD-2930
|
'Finish' tab should be disabled when first opened Titanium Studio > Help > 'Install specific Titanium SDK from URL'
|
This is not a regression bug . I have recreated this bug with Titanium 2.1.2. Steps to reproduce: 1)Open Titanium Studio. 2)Help >'Install specific titanium SDK ' > 'install from URL'. 3)Without entering anything in the text-box, press 'finish tab. 4)Observe that if you check the radio button "install from update stream" then finish tab for Install specific titanium SDK ' > 'install from URL' will be disabled. Actual result: 'Your Titanium SDKs have been updated' pop up window is appearing.Also logs shws [ERROR] NULL. Logs and screenshot attached. Expected Result: Finish tab should be disabled if URL textbox is empty.
| 3 |
train
|
TISTUD-2933
|
Node.ACS: adopt to the change in "acs list" command
|
The command to call "acs list" under a project dir to show an app info has been deprecated; instead, we should run "acs list <appname>". The acs change is in the latest git. We should verify the syntax we call to "acs list" in Studio and make appropriate changes.
| 3 |
train
|
TISTUD-2934
|
Not to show the error message when first opening package Mobile Web wizard
|
This is not a regression bug.It happens in Studio 2.1.2 . Test Steps: 1.Install latest studio. 2.Create a Titanium project which must support mobile web . 3.Project explorer > Package - Mobile web > observe the window. Actual Result: A red cross with a message 'Project Directory must be specified' is displayed though I haven't chosen any of the three actions mentioned on that window. Expected Result: By default first action would be selected with the launch of the package -mobile web window but before choosing any action red cross error shouldn't appear. The error message behavior should be same as Help > 'Install specific titanium SDK from URL'
| 3 |
train
|
TISTUD-2936
|
Titanium Studio: 'Module packaging successful' prompt should display correct directory location path for packaged module zipped file.
|
This is a regression. Test Steps: 1.Install latest studio. 2.Create a New Titanium module project for mobile web. 3.From project explorer, package mobile web module created in 2nd step. 4.Select the third option ' package mobile web module to a directory'. 5.Give any location on the local machine. Actual Result: 'Module packaging successful' prompt displays wrong directory location where zip file is stored. It doesn't show the directory path given in the third option where actual packaged mobile web zipped file is stored. Expected Result: 'Module packaging successful' prompt should read and display correct directory location for packaged mobile web module zipped file. P.S. This erroneous behavior is found for all three ios , android and mobile web modules respectively.
| 5 |
train
|
TISTUD-2949
|
CLI: ERROR Invalid ios version value
|
This appears to be a regression issue. Since it works fine in 2.1.2 Studio. iOS Simulator 5.0/5.1 runs in Studio 2.1.2 build. Steps To Reproduce: 1. Install Xcode and Studio 3.0 2. Create a default project. 3. Try running app in iOS simulator. Actual: Error appears in console. [ERROR] Invalid --ios-version value '5.0' Accepted values: 6.0 5.1 Expected: iOS simulator 5.0/5.1 must run for default project.
| 13 |
train
|
TISTUD-2940
|
Unable to finish Android SDK installation with Titanium Studio open.
|
While installing the Android SDK via the dashboard I get a warning from the android tools that TitaniumStudio.exe is locking the tools directory and I can not continue the install with Studio open (see screenshot). This may be caused by trying to install the new Android SDK Tools, v21. Steps to reproduce: 1. Launch studio. 2. Install the Android SDK via the Configure Native SDKs in the dashboard. 3. Start the default install Expected result: Android should be able to correctly install without closing Titanium Studio. Actual results: Above warning error. Note this only happens on Windows.
| 8 |
train
|
TISTUD-2941
|
Alloy view element content assist not respecting ns attribute value
|
{code} <| ns="Titanium.Map"> {code} Given that code, we should only be suggesting "Annotation" and "View" (as per http://docs.appcelerator.com/titanium/latest/#!/api/Titanium.Map) We're not filtering properly and are showing all elements.
| 5 |
train
|
TISTUD-2942
|
XML Editor isn't auto-closing <> pairs
|
When typing a '<', I don't get a '>' character to close the pair. Maybe we're not including the XML ruble? Maybe the pairs aren't defined properly?
| 5 |
train
|
TISTUD-2944
|
Use same stylesheet for Alloy release notes as Titanium SDK
|
When we show the Alloy release notes int he update dialog, it doesn't look the same as the Titanium SDK notes. It'd be nice to make sure they look similar and are easily readable.
| 5 |
train
|
TISTUD-2945
|
Feature parity between XML and HTML editor CA behavior
|
The XML editor lacks a lot of the refinements of the HTML in terms of CA. Specifically: the length/location of replacement strings, tabstop locations, what proposals to show when pointer is in specific locations: {code} < |ns="Titanium.Map"> // attribute names should be proposed? Or element? < |> // element names should be proposed <Label id="mylabel"| onClick=""> // attribute names {code}
| 8 |
train
|
TISTUD-2947
|
XML Editor doesn't open CA proposals after typing '<'
|
In HTML, if you type ',", we auto-pop CA. That isn't the case for XML. We should make it do so (mainly for alloy, because normal XML doesn't actually have any proposals).
| 5 |
train
|
TISTUD-2948
|
Add Alloy samples to Samples view
|
After we have alloy samples from ALOY-412, we should integrate them in Samples view, with Alloy as a top level category and individual samples underneath.
| 8 |
train
|
TISTUD-2950
|
iOS Simulator: intermittent error cleaning the build before launching
|
Error cleaning when deploying Titanium Project to iOS Simulator. Steps to Reproduce: 1. Deploy app to iPad Simulator. 2. Using same run config, run app in iPhone Simulator. Actual Result: Clean error. Could be causing related ticket. Expected Result: No error.
| 8 |
train
|
TISTUD-2953
|
Port HTML content assist unit tests to XML
|
Porting the large amount of HTML unit tests should help us identify the area in content assist where functionality exists in HTML but not XML.
| 8 |
train
|
TISTUD-2955
|
Unable to find Titanium SDK when tiapp.xml is opened on startup
|
When tiapp.xml is opened on startup, Studio is unable find Titanium Mobile SDK and report errors about unable to locate the SDK. However, closing and re-opening tiapp.xml file fixes this issue. At this time, the problem is reproducible only in dev environment.
| 5 |
train
|
TISTUD-2958
|
Studio display two update dialogs if user initiates "Check for Titanium Updates"
|
Steps: 1. Start a titanium studio that will prompt for updates to the sdk/node/acs/etc 2. While studio is loading, right away click Help->Check for Titanium Updates Expected results: One update dialog is displayed Actual: Two dialogs are displayed. If a dialog is requested manually, the check that runs during startup should not be displayed
| 5 |
train
|
TISTUD-2960
|
Dashboard: Change the button to Launch Recent project after creating a project
|
In the new workspace, the dashboard show 'Create a new mobile web project' button and once the user creates a new project using this button, it does not update the button to 'launch recently created project'. The user has to explicitly refresh the dashboard to get the option.
| 5 |
train
|
TISTUD-2965
|
NPE: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources"
|
Following NPE on shutdown: {code} !ENTRY org.eclipse.core.resources 4 2 2012-12-04 08:30:57.294 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.NullPointerException com.aptana.core.build.UnifiedBuilder.getBuildParticipantManager(UnifiedBuilder.java:282) com.aptana.core.build.UnifiedBuilder.doBuildFiles(UnifiedBuilder.java:433) com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:414) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:307) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) 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) 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.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} Steps to reproduce: 1. Close Titanium Studio 2. Reopen Titanium Studio 3. View the Log file Expected result: Titanium Studio should close without error. Actual result: The above NPE shows in the log.
| 3 |
train
|
TISTUD-2966
|
Disparity in CLI reports from Windows and Ubuntu to Mac OS
|
When checking the diagnostic print out, Titanium Studio, build: 3.1.0.201212031735 now shows if the new CLI is being used. I see "Titanium CLI Enabled: true" for Windows and Ubuntu, and "Titanium CLI Enabled: false" for Mac with default flag settings. This functionality does not exist in Titanium Studio 3.0.0 or 3.0.1. Steps to reproduce: 1. On Mac OS start Titanium Studio. 2. Run the Diagnostic test (Help > Titanium Studio > Run Diagnostic Test...) 3. On Windows start Titanium Studio. 4. Run the Diagnostic test (Help > Titanium Studio > Run Diagnostic Test...) 5. Compare the results. Expected Result: Results for CLI usage with default flag settings should match. Actual Result: Windows (and Ubuntu) reads "Titanium CLI Enabled: true" Mac OS reads "Titanium CLI Enabled: false"
| 3 |
train
|
TISTUD-2967
|
Allow users to package multiple module projects as one zip
|
Currently Studio only allows packaging of single module projects. For cross-platform modules and multi-version modules, there is no easy way to package other than packaging each module individually and then manually combining them into one zip. Manually combining projects does not validate best practices for module creation. We should: -Module package wizard has an option for "Package for multiple platforms" option, which allows the user to specify additional projects to package along with the targeted project -The following validation is done: module id matches, guid matches
| 8 |
train
|
TISTUD-2969
|
iOS: Developer name passed to CLI is trimming ID
|
QE discovered a problem where the developer identity is not correctly set. In this case, it was determined that the developer name which should read something like "Eric Merriman (9JU76422)" is being trimmed by studio and passed as "Eric Merriman". The problem with this technique is that we were trying to use Developer name "Eric Merriman (W6xxxxx)" and were getting a certificate mismatch. To prevent this, the full developer name should be passed, including the "(9JU76422)" Steps to reproduce: 1) Using a configured system that includes multiple identities, attempt to build for device using one of the multiple identities (the one appearing second in "Titanium info") Result: Studio reports that the identity (the one you didn't select) doesn't match the provision, and fails Expected: The identity selected in the build dialog is the one used for the build
| 5 |
train
|
TISTUD-2970
|
Studio: Distribution name seems to be using developer name, which is incorrect
|
After discovering an identity bug, the investigation also uncovered that Studio is using the developer name (plus ID) in place of the distribution name. The correct value shows in the build dialog, but according to Chris, the developer name is being passed in place of the distribution name. Steps to reproduce: 1) Create a project in studio 2) Package for distribution Result: Studio passes the developer name e.g. "Eric Merriman (9JUJ8DJW9G)" instead of the distribution name, eg "Eric Merriman" Expected: Studio passes the distribution name as part of a packaging attempt.
| 5 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.