id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
1,511 |
TISTUD-5075
|
07/03/2013 15:15:53
|
Re-use iOS "simulator" launch config type for "profile" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the iOS "profile on simulator" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 5 |
1,512 |
TISTUD-5076
|
07/03/2013 15:18:08
|
Re-use iOS "device" launch config type for "debug" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the iOS "debug on device" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 5 |
1,513 |
TISTUD-5077
|
07/03/2013 15:18:17
|
Re-use iOS "device" launch config type for "test" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the iOS "test on device" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 5 |
1,514 |
TISTUD-5078
|
07/03/2013 15:18:26
|
Re-use iOS "device" launch config type for "profile" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the iOS "profile on device" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 5 |
1,515 |
TISTUD-5079
|
07/03/2013 19:39:38
|
Make JSCA handling forgiving of arbitrary new properties
|
Looks like the platform wants to be able to add additional data to the JSCa file to be used in Ti.Next. Unfortunately our JSCA support currently blows up (throws a runtime exception that effectively breaks our parsing) when we encounter unexpected properties and their values. See https://github.com/appcelerator/titanium_mobile/pull/4429 We need to eat up the new property value (whether its a primitive, array, or object) while ignoring it rather than blowing up because it's a property we don't understand.
| 5 |
1,516 |
TISTUD-5084
|
07/08/2013 09:13:49
|
XML code completion adds closing tag when fully typing a self-closed tag
|
Start typing {{<Label /}} in the Studio XML editor (e.g. Alloy view). Now if you wait a sec and then type {{>}} everything is OK. You have created a self-closed {{<Label />}} tag with no problem. But the following cases don't: * Type {{<Label />}} without stopping and you'll get {{<Label />></Label>}} * Type {{<Label foo="bar" />}} and you'll get {{<Label foo="bar">></Label>}} This can be very irritating when typing lots of self closed-tags, e.g. Alloy view elements.
| 5 |
1,517 |
TISTUD-5089
|
07/09/2013 22:14:05
|
Studio: the Plugin zip does not exist on the update site
|
This applies to both Titanium Studio and Appcelerator Studio. Clicking on the "Download Plugin Update Site" link in http://preview.appcelerator.com/appcelerator/studio/standalone/update/stable/ leads to a non-existent URL.
| 5 |
1,518 |
TISTUD-5101
|
07/12/2013 18:40:11
|
Improve Github PR submission
|
The Github PR submission works OK, but could use some improvement in behavior/UI: - If I have long commit messages the dialog gets very wide. It should have a max width set and just use horizontal scrolling if necessary - The actual PR submission should happen asynchronously, it currently runs in the UI thread. (Schedule as user job, and show error in error dialog, success in toast as we do) - The UI doesn't summarize the two endpoints being proposed for merging (let alone let user modify them). The dialog should show the name of the target repo and branch and the name of the current repo and branch. - The success toast should give more details (like the generated PR number) and allow the user to click the toast to open the PR in a browser.
| 8 |
1,519 |
TISTUD-5104
|
07/15/2013 19:39:36
|
List open pull requests for git repo attached to github, selecting PR opens in browser
|
Now that we can generate pull requests in Studio, it'd be nice to see the list of open PRs against a given repo and select them to open the PR in a browser (internal?). http://developer.github.com/v3/pulls/#list-pull-requests We already have a very simple pull request model to parse the JSON that describes a PR returned by the Github API. So the work here is to call the new API endpoint, iterate over the array of PRs turning them into objects, and hooking menu extensions to show the listing and open the PR's URL when selected.
| 8 |
1,520 |
TISTUD-5105
|
07/15/2013 19:41:15
|
Allow user to merge an open pull request for a git repo attached to github
|
Now that we can generate pull requests in Studio, it'd be nice to see the list of open PRs against a given repo and select them to merge the PR. http://developer.github.com/v3/pulls/#merge-a-pull-request-merge-buttontrade We need to hook a menu extension to show the listing of open PRs and merge the PR when selected. (The user could optionally supply a commit message, but I think for a first cut we just send no commit message and they will likely generate a default)
| 8 |
1,521 |
TISTUD-5106
|
07/15/2013 23:07:12
|
Alloy project: Add right-click menu items to navigate from XML to JS and TSS files
|
When a xml file in Alloy project is selected in the Project Explorer, we should provide right-click menu items to open the corresponding .js and .tss files. The same menu should also be available when right-clicking in the xml editor if it's from an Alloy project.
| 8 |
1,522 |
TISTUD-5107
|
07/15/2013 23:09:56
|
Alloy project: Add right-click menu items to navigate from JS to XML and TSS files
|
When a js file in Alloy project is selected in the Project Explorer, we should provide right-click menu items to open the corresponding .xml and .tss files. The same menu should also be available when right-clicking in the JS editor if it's from an Alloy project.
| 5 |
1,523 |
TISTUD-5108
|
07/15/2013 23:11:25
|
Alloy project: Add right-click menu items to navigate from TSS to XML and JS files
|
When a tss file in Alloy project is selected in the Project Explorer, we should provide right-click menu items to open the corresponding .xml and .js files. The same menu should also be available when right-clicking in the TSS editor if it's from an Alloy project.
| 5 |
1,524 |
TISTUD-5109
|
07/16/2013 00:24:54
|
Silent failure when creating a Git pull request
|
I have a git project that is on "development" branch. It's not forked, and is linked directly to the 'development' origin. Do a right-click on the project and select Team -> Create Pull Request. At this point, nothing happens and we get this error in the log: {code} !ENTRY org.eclipse.ui 4 0 2013-07-15 16:20:08.110 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.e4.core.di.InjectionException: org.eclipse.core.commands.ExecutionException: Unable to get repository details from github API at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: org.eclipse.core.commands.ExecutionException: Unable to get repository details from github API at com.aptana.git.ui.internal.actions.CreatePullRequestHandler.doExecute(CreatePullRequestHandler.java:118) at com.aptana.git.ui.internal.actions.AbstractGitHandler.execute(AbstractGitHandler.java:108) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) ... 40 more Caused by: org.eclipse.core.runtime.CoreException: Not Found at com.aptana.git.internal.core.github.GithubAPI.get(GithubAPI.java:99) at com.aptana.git.internal.core.github.GithubUser.getRepo(GithubUser.java:55) at com.aptana.git.ui.internal.actions.CreatePullRequestHandler.doExecute(CreatePullRequestHandler.java:114) ... 48 more {code}
| 3 |
1,525 |
TISTUD-5110
|
07/16/2013 02:09:55
|
NPE when launching the Studio after a fresh install
|
Launched an installed Studio for the first time on a Windows 7 VM and got an exception right at the start. {code} !ENTRY org.eclipse.core.jobs 4 2 2013-07-15 18:06:52.401 !MESSAGE An internal error occurred during: "Computing SDK Info...". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.core.internal.mobile.SDKInfoManager.getSDKInfo(SDKInfoManager.java:59) at com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationHelper.getVersionInfo(MobileSDKConfigurationHelper.java:93) at com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationProcessor.computeStatus(MobileSDKConfigurationProcessor.java:70) at com.aptana.configurations.processor.AbstractConfigurationProcessor.getStatus(AbstractConfigurationProcessor.java:154) at com.appcelerator.titanium.ui.portal.actionController.MobileSDKActionController$1.run(MobileSDKActionController.java:127) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code}
| 3 |
1,526 |
TISTUD-5112
|
07/16/2013 02:21:00
|
Errors in the TailLog after deleting a deployed Node.ACS project
|
# Create Node.ACS Project named 'np'. # Deploy App. # Activate Tail Logs. # Delete project. The project is deleted. However, the Tail Log console remains open and an error appear every few seconds: {code} [ERROR] Server returned error. No app found {code}
| 5 |
1,527 |
TISTUD-5116
|
07/17/2013 01:52:51
|
Create a 16x16 LiveView icon
|
In order to implement TISTUD-4817, we need a LiveView icon that will be displayed in the Project and App Explorer toolbar.
| 5 |
1,528 |
TISTUD-5139
|
07/18/2013 00:51:18
|
Android SDK Path is misinterpreted
|
h3. Steps to Reproduce On OSX 10.6.8 (outdated, yes, but probably applies to more versions) With a fresh install, use the dashboard link to install the Android SDK. When it requests a path, enter ~/.android (or any path beginning with ~) Install as normal h3. Actual Result SDK is installed to /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/~/.android SDK directory is stored as the path entered, so Titanium Studio cannot find the appropriate SDKs without tracking down where the SDK Manager installed it and entering that directory in the preferences. h3. Expected Result SDK is installed to ~/.android (more specifically: /Users/[username]/.android or at least SDK is installed to /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/~/.android and the directory is set to the same so that Titanium Studio recognizes the installed files.
| 5 |
1,529 |
TISTUD-5121
|
07/18/2013 01:20:20
|
Add a toggle button in App/Project Explorer toolbar to enable/disable LiveView for the next run
|
This will be a global state to control if the next applicable launch (run on iOS/Android and simulator/device at the moment) will be run with LiveView on or off. Initially the button is toggled off, and the workflow is as followed: 1. User toggles the button on and do Run > iOS Simulator, the simulator will be run with liveview; 2. User toggles it off, do Run > Android Emulator, the emulator will be run without liveview; 3. To run the iOS simulator without liveview, user will just do Run > iOS Simulator again since now the setting is off.
| 5 |
1,530 |
TISTUD-5122
|
07/18/2013 01:23:51
|
LiveView: Remove the launch configuration contribution
|
Remove the contribution to applicable launch configurations for enabling LiveView as we will be using the global toggle to control the setting. For existing launch configs, we should ignore the liveview attribute and also use the global setting.
| 3 |
1,531 |
TISTUD-5127
|
07/18/2013 22:46:16
|
Support optional comma in tss file
|
When a .tss file contains certain grammars, Titanium Studio cannot parse for display in the Outline View, and the entire Outline View goes blank. Examples: Example 1) {noformat}"#topShadow[platform=android]":{ left: 0, right: 0, top: 0, height: 4, backgroundColor: "yellow", backgroundGradient: { type: 'linear', startPoint: {x:0,y:0}, endPoint:{x:0,y:"100%"}, colors: [{color: "#919191", offset:0},{color: "#919191", offset:0.125},{color:"#f2f2f2",offset:1}] } },{noformat} The {{colors}} line contains an array of objects. This is a legitimate style in a tss file, but its presence causes the whole outline view to go blank. Example 2) {noformat}"#OrderListSection[platform=ios]":{ text:"List Settings", top:10, },{noformat} The {{top:10,}} has an extra comma in it. This isn't necessarily a correct grammar, but a .tss will compile with it in place. However, it breaks the Outline View for the entire page. I use the Outline View quite heavily when working with tss files, it's hard to go without a working tss. Example 2 has an acceptable workaround, but Example 1 does not.
| 2 |
1,532 |
TISTUD-5132
|
07/22/2013 15:43:12
|
Studio: Update out-dated tiapp.xml files in project templates
|
The {{tiapp.xml}} files in the Studio project templates are out-dated. They still contain the deprecated top-level iOS elements and the {{<iphone />}} section instead of the new {{<ios />}}. Since these templates are the starting point for both beginners and advanced devs, I think they should always reflect the latest best practice.
| 5 |
1,533 |
TISTUD-5151
|
07/25/2013 11:15:48
|
Errors occurred while refreshing git index ( importing KitchenSink from Samples)
|
Test Steps: 1.Launch Appcelerator Studio. 2.Samples > KitchenSink > import . 3. No sepearate GIT activity has been done , still I received 'Errors occurred while refreshing git index' Screenshot and logs attached. {code} !ENTRY com.aptana.git.core 4 1 2013-07-25 15:14:10.168 !MESSAGE Errors occurred while refreshing git index !SUBENTRY 1 com.aptana.git.core 4 0 2013-07-25 15:14:10.169 !MESSAGE Unable to run update-index: fatal: Not a git repository (or any parent up to mount point /Volumes/MacintoshHD) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). !ENTRY com.appcelerator.titanium.360.soasta 1 0 2013-07-25 15:14:38.559 !MESSAGE (Build 3.1.2.201307232148) [INFO] Running MATT for Kitchen Sink. Utility returned Will configure following JS File: /Volumes/MacintoshHD/Users/deepti.pandey/Documents/Appcelerator_Studio_Workspace_beta_1/Kitchen Sink/Resources/app.js Mobile App Object "KitchenSink_9104c364-f669-47ce-93b1-a5a15fa91ee0_iOS" representing your Application "KitchenSink" has been created in CloudTest Repository. Mobile App Object "KitchenSink_9104c364-f669-47ce-93b1-a5a15fa91ee0_Android" representing your Application "KitchenSink" has been created in CloudTest Repository. !ENTRY com.appcelerator.titanium.mobile 1 0 2013-07-25 15:14:38.563 !MESSAGE (Build 3.1.2.201307232148) [INFO] Module check for com.appcelerator.apm: version: true platform: true !ENTRY com.appcelerator.titanium.mobile 1 0 2013-07-25 15:14:38.565 !MESSAGE (Build 3.1.2.201307232148) [INFO] Module check for com.appcelerator.apm: version: true platform: true {code}
| 5 |
1,534 |
TISTUD-5154
|
07/25/2013 23:33:19
|
SWTException when closing tiapp editor
|
I was closing editors and saw error dialogs popped up. Here is the exception in the log: {code} !ENTRY org.eclipse.ui 4 4 2013-07-25 15:30:20.018 !MESSAGE An internal error has occurred. !STACK 0 org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.SWT.error(SWT.java:4283) at org.eclipse.swt.widgets.Widget.error(Widget.java:783) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:573) at org.eclipse.swt.widgets.Control.getBounds(Control.java:1606) at org.eclipse.ui.internal.forms.MessageManager.update(MessageManager.java:504) at org.eclipse.ui.internal.forms.MessageManager.updateForm(MessageManager.java:499) at org.eclipse.ui.internal.forms.MessageManager.removeMessage(MessageManager.java:374) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.validateSection(TiAppDeployTargetsSection.java:529) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppSDKSection.updateDependentSections(TiAppSDKSection.java:300) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppSDKSection.access$0(TiAppSDKSection.java:294) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppSDKSection$5.runInUIThread(TiAppSDKSection.java:283) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) {code}
| 3 |
1,535 |
TISTUD-5158
|
07/26/2013 01:50:54
|
Run Configurations dialog: create new iOS Application Installer config failed with exception
|
Opened Run Configurations dialog and double-click on Appcelerator iOS Application Installer to create a new launch config, but none was created. Checked the log and saw the following exception: {code} !ENTRY org.eclipse.ui 4 0 2013-07-25 17:46:58.544 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)) at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?) at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1681) at com.appcelerator.titanium.ios.ui.launching.packaging.SimpleiPhonePackagingComponent$9.run(SimpleiPhonePackagingComponent.java:550) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 23 more {code}
| 3 |
1,536 |
TISTUD-5160
|
07/26/2013 03:33:40
|
Appcelerator Studio is asking for updates every single time user opens studio
|
User opens Appcelerator Studio, then studio prompt to install updates, the user click on the update button, studio download all the updates and says that they has been installed, but the log file is showing errors (attached log file), also , the user try to login on acs with his account (cli -> acs login) and throws an error: RangeError: Maximum call stack size exceeded. If we create a new user and enable that user into another dummy organization, and we log in with those credentials on a different machine we can log in with no issues, then if the user with his machine try to login, shows the same error and if we go to the other machine (the one that before has been logged in successfully) shows that error message now.
| 8 |
1,537 |
TISTUD-5166
|
07/26/2013 23:58:38
|
Appcelerator Studio: stuck on the splash screen when restart
|
h5. Problem description After hard restarting the system (for everything was completely frozen), Appcelerator Studio was not starting anymore. After launching it and choosing an existing workspace, the login screen didn't appear - only the red Studio Splashscreen was being displayed. Here is the console details: {code} fcasaliMBP:MacOS fcasali$ ./AppceleratorStudio !SESSION 2013-07-26 14:38:39.771 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_51 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/fcasali/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86 -keyring /Users/fcasali/.eclipse_keyring -consoleLog -showlocation !ENTRY org.eclipse.core.resources 2 10035 2013-07-26 14:39:27.612 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. !ENTRY org.eclipse.core.net 1 0 2013-07-26 14:39:39.868 !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences ^CException in thread "Thread-1" org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.widgets.Widget.error(Widget.java:774) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:661) at org.eclipse.swt.widgets.Shell.closeWidget(Shell.java:611) at org.eclipse.swt.widgets.Shell.windowWillClose(Shell.java:2262) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5445) at org.eclipse.equinox.launcher.JNIBridge._takedown_splash(Native Method) at org.eclipse.equinox.launcher.JNIBridge.takeDownSplash(JNIBridge.java:167) at org.eclipse.equinox.launcher.Main.takeDownSplash(Main.java:2050) at org.eclipse.equinox.launcher.Main$SplashHandler.run(Main.java:111) {code} h5. Workaround After deleting the ~/.eclipse folder, Studio would start correctly.
| 8 |
1,538 |
TISTUD-5168
|
07/27/2013 01:40:54
|
Proxy settings not used when downloading APM module from AWS S3 bucket
|
Customer is behind proxy server, but checking for updates shows APM 1.0.4, when he downloads, errors out. See attached for logs
| 5 |
1,539 |
TISTUD-5169
|
07/27/2013 01:42:21
|
Proxy settings do not apply when re-launching into AppC Studio with cached login
|
Customer logs into AppC Studio behind proxy (with beta 3.1.3 build that had proxy fix) and it works first time, then on subsequent close/open, reports that Studio is in Offline mode. Have to logout, then launch and login for it to show as online. See attached logs
| 5 |
1,540 |
TISTUD-5195
|
08/02/2013 19:31:14
|
When importing an existing Titanium Mobile project, refer to the tiapp.xml instead of the manifest file
|
Currently, Studio requires a Titanium Mobile project to contain a "manifest" file in order to import the project. This file only exists to facilitate importing projects into Studio. In Titanium SDK 3.2.0, the "manifest" file will be removed (TIMOB-13166). Studio will need to read the tiapp.xml to get whatever info it needs.
| 5 |
1,541 |
TISTUD-5199
|
08/02/2013 22:16:25
|
BlackBerry project validation: message has incorrect grammar
|
BlackBerry project validation: message has incorrect grammar. See screenshot. Test Steps: 1. Create Titanium BlackBerry project with project name containing invalid character. Result: Error message 'A BlackBerry project cannot any of these characters in its name:'. Expected Result: Error message 'A BlackBerry project cannot contain any of these characters in its name:'
| 2 |
1,542 |
TISTUD-5200
|
08/05/2013 16:03:34
|
Allow create Alloy Application Templates using Rubles
|
Using rubles, one can create Titanium Mobile templates - however, this doesn't work when trying to create a template for an Alloy based project. Issues as I've noticed them are: * Alloy nature is not properly applied * Alloy plugin is not added to the tiapp.xml as expected * Alloy assets are not generated appropriately (lack of call to CLI 'alloy new') Multiple work arounds have been tried such as including all required files and the .project file so that the nature is preserved, but this doesn't work as those files are apparently overwritten For more details see the email thread attached
| 8 |
1,543 |
TISTUD-5205
|
08/07/2013 01:54:28
|
Localization properties set in Alloy .tss files are marked as an error
|
h5. Problem description Specifying a String localized in the Styles .tss, Appclerator Studio marks it as an error (unexpected token "L"). 1. Create a new Alloy project 2. Edit views/index.xml {code} <Alloy> <Window> <!-- Localization via XML attribute --> <Label class="header">via XML attribute:</Label> <Label text="L('hello_world')"/> <!-- Localization via TSS --> <Label class="header">via TSS:</Label> <Label id="viaTss"/> <!-- Localization via JS code in controller --> <Label class="header">via controller:</Label> <Label id="viaController"/> </Window> </Alloy> {code} 3. Edit styles/styles.tss {code} 'Label': { top: '5dp', color: '#222', font: { fontSize: '42dp', fontWeight: 'bold' }, height: Ti.UI.SIZE, width: Ti.UI.SIZE, textAlign: 'center' } '.header': { top: '30dp', color: '#a00', font: { fontSize: '24dp', fontWeight: 'normal' } } '#index': { backgroundColor: '#fff', fullscreen: false, exitOnClose: true, layout: 'vertical' } '#viaTss': { text: L('hello_world') } {code} 4. Edit controllers/index.js {code} $.viaController.text = L('hello_world'); $.index.open(); {code} Result: Studio is showing two error markings in the styles/index.tss - the first on the first line ('Cannot recover from the syntax error'), the second on the localization line (unexpected token "L").
| 8 |
1,544 |
TISTUD-5206
|
08/07/2013 07:25:08
|
Appcelerator Studio Dashboard - Learn >> Developer Reference >> Titanium Studio Guide link navigates to a proper page but the page displays a 'Page not found' message
|
Dashboard: Learn: Documentation Links Test steps: 1. Click the Titanium Studio Guide link for Developer Reference and observe the page that it navigates to. Actual Result: The link navigates to a page which has a 'Page not found' message on it. Please refer the attached screen shot for more clarification.
| 3 |
1,545 |
TISTUD-5223
|
08/08/2013 18:11:46
|
Field Service: In description of Field Service Sample in Dashboard we should state to read the ReadMe to configure
|
There are users and partners that have not been able to get the Field Service App to work. It turns out many of them is because they didn't look at the ReadMe. I believe that if we state it in the description, then more users will actually look at the readme and this should increase the overall success of the Field Service App. "Please read the ReadMe file in order to complete the configuration of the application." Or something like that.
| 2 |
1,546 |
TISTUD-5225
|
08/08/2013 23:26:40
|
Liveview: iOS: Second launch of LV enabled project in iOS simulator fails
|
h5. Description: When launching a Liveview enabled simulator session, it works as expected. When you attempt to rebuild the project again, the simulator fails to launch and this error presented: {code} [INFO] : Finished building the application in 1s 97ms [LiveView] Closing file/event server process id: 34204 [INFO] : Running application in iOS Simulator [LiveView] version 0.1.32 [LiveView] File Server Started on Port 8324 [LiveView] Event Server Started on Port 8323 [INFO] : Launching application in iOS Simulator [INFO] : Focusing the iOS Simulator [ERROR] : Failed to focus the iPhone Simulator window [ERROR] : /Users/emerriman/Library/Application Support/Titanium/mobilesdk/osx/3.1.2.v20130807171139/iphone/iphone_sim_activate.scpt: execution error: iPhone Simulator got an error: Connection is invalid. (-609) [INFO] : Application has exited from iOS Simulator [INFO] : Project built successfully in 3s 58ms {code} This occurs with both the iPad and iPhone simulators. The order of the console output may vary slightly. Also note that the behavior prevents the user from turning off LV and then launching on the first attempt. The first launch with LV off after encountering this error will fail with the same console output. The second launch with LV off seems to work fine. This may be a clue as to root cause. h5. Steps to reproduce: 1) Create a default classic project in Studio 2) Enable Liveview and launch in the simulator 3) Make some edits if you wish 4) Relaunch the simulator - leaving liveview enabled h5. Result: Project fails to launch correctly in the simulator. Turning off LV and launching will also fail, but will work on the next and subsequent launches with LV off. h5. Expected Result: Project launches as expected and allows real-time editing h5. Notes I monitored the processes here, and it may be expected but subsequent launches of Liveview were killing the existing node PID and launching a new one. Process list: Normal non-LV launch: {code} 39786 1.6 0.8 3104976 67028 ?? S 3:07PM 0:02.09 node /usr/local/bin/titanium --no-colors --no-prompt build --platform ipad --sdk 3.1.2.v20130807171139 --log-level trace --target simulator --ios-version 6.1 --device-family ipad --skip-js-minify {code} Normal LV enabled launch {code} 39891 1.5 0.2 3063424 19808 ?? Ss 3:08PM 0:13.73 /usr/local/bin/node /Applications/Appcelerator_Studio/plugins/com.appcelerator.titanium.liveview.core_1.0.0.1375925433/node_modules/liveview/bin/liveview-server start --project-dir /Users/emerriman/Documents/anewworkspace/Yuntastic --platform ios --no-colors 39873 1.8 1.1 3120336 96244 ?? S 3:08PM 0:16.16 node /usr/local/bin/titanium --no-colors --no-prompt build --platform ipad --sdk 3.1.2.v20130807171139 --log-level trace --target simulator --ios-version 6.1 --device-family ipad --skip-js-minify --liveview --deploy-type development {code} Failed LV enabled launch: {code} 39978 1.6 0.2 3053660 17976 ?? Ss 3:24PM 0:00.29 /usr/local/bin/node /Applications/Appcelerator_Studio/plugins/com.appcelerator.titanium.liveview.core_1.0.0.1375925433/node_modules/liveview/bin/liveview-server start --project-dir /Users/emerriman/Documents/anewworkspace/Yuntastic --platform ios --no-colors 39959 0.0 0.7 3102660 58440 ?? S 3:24PM 0:02.03 node /usr/local/bin/titanium --no-colors --no-prompt build --platform ipad --sdk 3.1.2.v20130807171139 --log-level trace --target simulator --ios-version 6.1 --device-family ipad --skip-js-minify --liveview --deploy-type development {code} First launch non LV failure: No processes Second launch non LV: {code} 40678 2.5 0.7 3102660 58916 ?? S 3:26PM 0:01.99 node /usr/local/bin/titanium --no-colors --no-prompt build --platform ipad --sdk 3.1.2.v20130807171139 --log-level trace --target simulator --ios-version 6.1 --device-family ipad --skip-js-minify {code}
| 8 |
1,547 |
TISTUD-5224
|
08/09/2013 00:51:40
|
Studio: Toast says android build succeeded when build failed
|
If a build fails, TiStudio still says it succeeded, console says (correctly) build failed. See screenshot. The problem is if the build callback receives an error, it says there was an error, but doesn't exit with a non-zero exit code.
| 5 |
1,548 |
TISTUD-5235
|
08/09/2013 03:57:01
|
Node.ACS - tiapp.xml property always points to locally running endpoint of node.ACS web service
|
Repro steps: 1. Create a new node.ACs proj 2. Publish it to Node.ACS cloud 3. Create a new timob project 4. Import Node.ACS bindings 5. Select the project created in step 1 6. Replace the value of following property in your timob project <property name="acs-service-baseurl-<NodeACSWebserviceProjectName>">http://localhost:64075</property> From localhost:64075 to the actual published URL. 7. Save tiapp.xml 8. Build the timob project for iphone simulator 9. Once the iphone simulator comes up 10. Open the tiapp.xml and you will see that the value of the above property is changed back to localhost:64075
| 5 |
1,549 |
TISTUD-5236
|
08/09/2013 23:28:32
|
Preferences > Studio > Updates: hitting Apply after switching a stream has no effects on the selected update site
|
1. Open Preferences > Studio > Updates page; 2. Switch from "Stable Release" to Release Candidate Build"; 3. Hit Apply; 4. Switch to Preferences > Install/Update > Available Software Sites. Expected result: the new list of update sites are generated, and the RC one is selected. Actual result: no change occurs to the list of update sites. The update sites do get updated correctly after OK is clicked.
| 3 |
1,550 |
TISTUD-5240
|
08/12/2013 06:33:07
|
Build the new platform configuration wizard in Studio
|
See https://wiki.appcelerator.org/display/tools/Platform+Configuration+Workflow+in+Studio#PlatformConfigurationWorkflowinStudio-V2 and TISTUD-5051 for the details.
| 0 |
1,551 |
TISTUD-5241
|
08/12/2013 07:08:56
|
Allow user to configure for iOS development in the platform configuration wizard
|
In the platform configuration wizard, there should be an entry for iOS. It will have an Advanced Settings section to customize the Xcode location. By default, the location should be filled with "/Applications/Xcode.app", and the text next to the checkbox should say "Not Configured". This ticket just covers the UI aspect. There will be separate tickets for dealing with the actual configuration once "Configure" is clicked as well as auto-detecting if Xcode is already installed in the default location to update the UI state accordingly.
| 8 |
1,552 |
TISTUD-5242
|
08/12/2013 07:09:37
|
Allow user to configure for Android development in the platform configuration wizard
|
In the platform configuration wizard, there should be an entry for Android, and it should contain an expandable "Advanced Settings" section where user could customize the following: # Set a path for the root Android SDK location. It will be filled initially by a default path, e.g. ~/Android. # Choose what Android SDK versions to install. The list should contain from the minimum version (currently 2.3.3) we support to the maximum version available. By default, the minimum version and the maximum available version are selected. The text next to the checkbox should say "Not Configured" by default. This ticket just covers the UI aspect. There will be separate tickets for dealing with the actual configuration once "Configure" is clicked as well as auto-detecting if Android SDK is installed in the default location to update the UI state accordingly.
| 13 |
1,553 |
TISTUD-5243
|
08/12/2013 07:20:14
|
Allow user to configure for BlackBerry development in the platform configuration wizard
|
In the platform configuration wizard, there should be an entry for BlackBerry, and it should contain an expandable "Advanced Settings" section where user could set a path for the root BlackBerry NDK location. It will be filled initially by a default path, e.g. ~/BlackBerry. The text next to the platform checkbox should say "Not Configured" by default. This ticket just covers the UI aspect. There will be separate tickets for dealing with the actual configuration once "Configure" is clicked as well as auto-detecting if BlackBerry is already installed in the default location to update the UI state accordingly.
| 8 |
1,554 |
TISTUD-5246
|
08/12/2013 07:35:33
|
Allow user to configure for Tizen development in the platform configuration wizard
|
In the platform configuration wizard, there should be an entry for Tizen, and it should contain an expandable "Advanced Settings" section where user could set a path for the root Tizen SDK location. It will be filled initially by a default path, e.g. ~/Tizen. The text next to the checkbox should say "Not Configured" by default. This ticket just covers the UI aspect. There will be separate tickets for dealing with the actual configuration once "Configure" is clicked as well as auto-detecting if Tizen is already installed in the default location to update the UI state accordingly.
| 8 |
1,555 |
TISTUD-5247
|
08/12/2013 15:50:53
|
Unable to import projects from dashboard
|
- Open Dashboard -> Develop. - Importing any project does not show up import wizard. The error log indicates exception indicating no handler for the import action. !MESSAGE (Build 3.2.0.201308102436) [ERROR] There is no handler to execute for command com.aptana.samples.ui.commands.import !STACK 0 org.eclipse.core.commands.NotHandledException: There is no handler to execute for command com.aptana.samples.ui.commands.import at org.eclipse.core.commands.Command.executeWithChecks(Command.java:512) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420) at com.aptana.portal.ui.dispatch.actionControllers.CommandHandlerActionController.execute(CommandHandlerActionController.java:95) at com.aptana.samples.ui.portal.actionController.SamplesActionController.importSample(SamplesActionController.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.aptana.portal.ui.dispatch.actionControllers.AbstractActionController.invokeAction(AbstractActionController.java:103) at com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.dispatch(DispatcherBrowserFunction.java:142) at com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.function(DispatcherBrowserFunction.java:126) at com.aptana.portal.ui.internal.BrowserWrapper$2.function(BrowserWrapper.java:51) at org.eclipse.swt.browser.WebKit.callJava(WebKit.java:1778) at org.eclipse.swt.browser.WebKit.browserProc(WebKit.java:406) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2104) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2318) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5620) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5057) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5206) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3648)
| 5 |
1,556 |
TISTUD-5251
|
08/12/2013 23:36:01
|
Unified Builder error thrown on project creation
|
When creating a new default project in Appcelerator Studio, the error:!MESSAGE Errors running builder 'Studio Unified Builder' on project 'sakthi' is shown. This occured for multiple project creations and in attempts to resolve the issue, the SDK was reinstalled and metadata was cleared from workspace. See logfile for further information.
| 3 |
1,557 |
TISTUD-5257
|
08/13/2013 22:35:18
|
Platform configuration wizard: Provide progress on the download/install when the platforms are being configured
|
After user selects the platforms and clicks "Configure", we should provide a progress dialog where we indicate the progress on individual platforms. User should be able to put it in the background or cancel the operation.
| 13 |
1,558 |
TISTUD-5263
|
08/14/2013 16:05:55
|
New remote's branches aren't listed in advanced pull for git
|
If a user adds a new remote but doesn't perform an action that would actually fetch or hit the remote, git doesn't "grab" the list of branches at that remote. When a user adds a remote through studio we can pass a flag that forces an immediate fetch to help alleviate this.
| 5 |
1,559 |
TISTUD-5266
|
08/15/2013 20:26:57
|
Platform Config Wizard: Auto-check if Xcode is already installed in the default location
|
This is an extension of TISTUD-5241. When the wizard is opened, we should auto-detect if Xcode is already installed in the default location or if the iOS preference page already has the path (meaning user has configured it). If so, we should display the corresponding version, e.g. XCode 5.0, next to the platform checkbox instead of "Not Configured".
| 5 |
1,560 |
TISTUD-5267
|
08/15/2013 21:06:13
|
Platform Config Wizard: Auto-check if Android is already installed or configured
|
This is an extension of TISTUD-5242. When the wizard is opened, we should check if Android is already installed in the default location or if the preference page already has a valid SDK path set (meaning user has configured it either through the wizard or set the path directly in preferences). If so, we should display the latest installed version, e.g. Android 4.3, next to the platform checkbox instead of "Not Configured".
| 3 |
1,561 |
TISTUD-5268
|
08/15/2013 21:21:06
|
Platform Config Wizard: Auto-check if BlackBerry is already installed or configured
|
This is an extension of TISTUD-5243. When the wizard is opened, we should check if BlackBerry is already installed in the default location or if the preference page already has a valid SDK path set (meaning user has configured it either through the wizard or set the path directly in preferences). If so, we should display the installed version next to the platform checkbox instead of "Not Configured".
| 3 |
1,562 |
TISTUD-5269
|
08/15/2013 21:22:39
|
Platform Config Wizard: Auto-check if Tizen is already installed or configured
|
This is an extension of TISTUD-5246. When the wizard is opened, we should check if Tizen is already installed in the default location or if the preference page already has a valid SDK path set (meaning user has configured it either through the wizard or set the path directly in preferences). If so, we should display the installed version next to the platform checkbox instead of "Not Configured".
| 3 |
1,563 |
TISTUD-5270
|
08/15/2013 21:38:01
|
Confirm support for JDK 7
|
According to a variety of tickets, it _appears_ that JDK 7.0 should work for both Studio and SDK, but we currently require JDK 6. We should confirm JDK 7 works as expected, or correct (if possible) the reasons that prevent it from working.
| 5 |
1,564 |
TISTUD-5271
|
08/15/2013 21:49:26
|
Platform Configure Wizard: Configure the iOS SDK
|
Once user clicks "Configure" with iOS selected, we should open App Store with Xcode highlighted. Since we have no control on when user actually completes the install, we should poll the installation directory to check when a valid SDK is there and indicate in the progress dialog that it's complete.
| 8 |
1,565 |
TISTUD-5272
|
08/15/2013 21:50:52
|
Platform Configure Wizard: Configure the Android SDK
|
Once user clicks "Configure" with Android selected, we should download the selected versions from their respective URLs. The progress dialog should indicate the proper progress since we have the control on the process.
| 8 |
1,566 |
TISTUD-5274
|
08/15/2013 22:28:11
|
Platform Config Wizard: Investigate the steps to setup Tizen on various OSes
|
We will host the necessary Tizen installers/zips on our server (TISTUD-5245). However, we need to figure out if we can install silently into a specific location (preferred), if we have to run the installer for users and wait for the completion, and other potential unknowns.
| 8 |
1,567 |
TISTUD-5278
|
08/16/2013 23:19:15
|
Android debug on device does not work
|
Android debug on device fail to connect. The log indicates that the app is actually being launched without the debug parameters, so something probably went wrong when refactoring some of the code.
| 5 |
1,568 |
TISTUD-5281
|
08/19/2013 05:46:20
|
Studio Building workspace every time I save a file
|
h3. Steps to Reproduce 1. Open project 2. Edit some thing 3. Run on simulator 4. Building workspace dialog shown 5. Wait for Building workspace dialog complete 6. Edit something 7. Run on simulator 8. Building workspace dialog shown 9. So on h3. Actual Result Building workspace dialog shown every time i save a file h3. Expected Result Building workspace 1 time only
| 8 |
1,569 |
TISTUD-5279
|
08/19/2013 14:29:47
|
Unable to set global JSLint options
|
The preferences page for the JSLint validator used to have an open text field for setting options using JSON. It no longer does. Users can still set options using /*jslint comment directives in their code.
| 5 |
1,570 |
TISTUD-5283
|
08/20/2013 19:39:19
|
Studio: warn, info, debug not outputting when debugging on phone
|
*Problem* When debugging an application on the phone (iPhone 4S), the Ti.API.info, warn and debug commands produce no output. *Test case* {code} var win = Ti.UI.createWindow({ backgroundColor: 'white' }); var b1 = Ti.UI.createButton({ title: 'Button', top: 50, height: Ti.UI.SIZE, width: Ti.UI.SIZE }); b1.addEventListener('click', function() { Ti.API.warn('this is warn output'); Ti.API.info('this is info output'); Ti.API.debug('this is debug output'); }); win.add(b1); win.open(); {code} *Output* (nothing - console is blank) *Expected output* {code} [WARN] : this is warn output [DEBUG] : this is debug output [INFO] : this is info output {code}
| 8 |
1,571 |
TISTUD-5285
|
08/21/2013 14:29:05
|
Unable to view file in Resource History for git from editor
|
If you right-click in a file opened in the editor that is inside a git attached project, the entry for Team > Show In Resource History is disabled.
| 3 |
1,572 |
TISTUD-5289
|
08/22/2013 17:57:16
|
iOS Preference page: the Configure button should open the new platform configuration wizard
|
The Configure button currently opens the dashboard. With the platform configuration wizard implemented, it should open the wizard instead, with only iOS item checked by default.
| 3 |
1,573 |
TISTUD-5290
|
08/22/2013 17:57:55
|
Android Preference page: the Configure button should open the new platform configuration wizard
|
The Configure button currently opens the dashboard. With the platform configuration wizard implemented, it should open the wizard instead, with only Android item checked by default.
| 3 |
1,574 |
TISTUD-5293
|
08/22/2013 22:10:20
|
BlackBerry: 10.2 update prevents Studio from using BB NDK
|
h3. Description: BlackBerry has changed the flow of how we can get and install the BB 10 NDK. This prevents Studio users (and in particular, new BB users) from installing and using BB support. h4. Previously: # We get the BB 10 NDK from the BB developer website link: http://developer.blackberry.com/native/download/ provided in the appcelerator docs for BB. # Install the NDK manually. # Point studio to the NDK folder installed in the above step in preferences. h4. The new flow: # When we go to the link to download the NDK, there is no way we can download just the discreet NDK. We instead download the Momentics IDE # The Momentics installs the NDK in new locations with different paths than before. Referencing the path inside Studio prompts the user with an error about missing directories with prefix '[install]' h3. Related They also have changed the flow to get the signing keys. Now it is done through Momentics or through the website. In both cases you have to register for blackberry ID & then only can get the signing keys
| 5 |
1,575 |
TISTUD-5294
|
08/23/2013 01:04:48
|
Exception in Studio Console related to loading the Ruble
|
h5. Problem description When recompiling a project (Alloy), I've seen the following error in the Studio Console, which seems to be related to loading Ruble. Project is correctly compiled and built. {code} [2013-08-22 13:06:15] An error occurred while processing the invoke block for the command Comment Line / Selection in C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass at Comment.newline(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:72) at LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:223) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:217) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:56) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:53) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:52) at org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) at org.jruby.RubyProc.call(org/jruby/RubyProc.java:233) [2013-08-22 13:06:16] An error occurred while processing the invoke block for the command Comment Line / Selection in C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass at Comment.newline(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:72) at LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:223) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:217) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:56) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:53) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:52) at org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) at org.jruby.RubyProc.call(org/jruby/RubyProc.java:233) [2013-08-22 13:06:16] An error occurred while processing the invoke block for the command Comment Line / Selection in C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass at Comment.newline(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:72) at LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:223) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:217) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:56) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:53) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:52) at org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) at org.jruby.RubyProc.call(org/jruby/RubyProc.java:233) [2013-08-22 13:06:17] An error occurred while processing the invoke block for the command Comment Line / Selection in C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass at Comment.newline(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:72) at LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:223) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:217) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:56) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:53) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) at #<Class:0x1007d0686>.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:52) at org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) at org.jruby.RubyProc.call(org/jruby/RubyProc.java:233) {code}
| 5 |
1,576 |
TISTUD-5295
|
08/23/2013 02:45:13
|
Add diagnostic tests for troubleshooting npm configuration issues
|
If any user has npm installation issues either with or without prefix configured, then it might not be very easy to judge the problem on the user's machine, especially with npm prefix configuration. Instead of asking user each time to run a series of commands on their machine to figure out the underlying problem, we can add those commands in the diagnostic tests and that should let us give a fair idea on what is going on user's machine with just the diagnostic test logs. When the NPM updates are invoked, either during startup or by the user - 1) It verifies whether the package is installed on the machine using 'npm -g ls <package>' command. 1.1) If the above command fails for any reason, then invokes 'npm -p ls -g' 2) If the package is available on the machine, it figures out the installed version and latest available version using 'npm view <package> version' command. Also, since PREFIX is one of those dark areas, we need to add the prefix configuration to the diagnostic logs. 1) Environment variable : Get the system property for NPM_CONFIG_PREFIX 2) Get the prefix key from the npm configuration : npm config get prefix 3) If only the environment variable is set, then the local prefix config value differs from the global one. That can lead to discrepancies in the installation of npm packages. So we should get the output for : 'sudo npm config get prefix'. However, since we don't hold user's password, this might not be a feasible value to store in the diagnostic tests.
| 5 |
1,577 |
TISTUD-5296
|
08/23/2013 19:42:46
|
Validate app id for BlackBerry mobile modules
|
Steps to reproduce : 1) New -> Mobile Module Project. 2) Select BlackBerry platform. 3) Enter the AppId as a1.b@~1 The New mobile module wizard does not show any error about malformed appId, as other platforms. It allows to create the project, but all the required files are not generated after the module creation. Expected: Show the error about the malformed appId as other platforms.
| 5 |
1,578 |
TISTUD-5300
|
08/24/2013 01:45:23
|
Improve platform configuration wizard UI
|
The current platform configuration wizard might need to be polished to get the design closer to the UX designed by Tyrus. 1) Increase spacing between Android SDK Entities : The Android SDK entities looks busy as they are very close to each other. 2) Version should be prepended to the versions being displayed : The current version displayed for each platform is just the number and does not indicate what it is for. It should be prepended by 'Version' or 'SDK'. 3) Remove the gap between separators : When the advance details is expanded, the gap between details section and separator should be avoided. 4) Expand the details section to cover all the width. 5) Hide the Advanced Details button/label incase if the platform has nothing to display in the details section. 6) If the SDK location path is very big, then wizard is expanded to wide enough to show the complete path. We need to set a maximum width for the configuration wizard.
| 0 |
1,579 |
TISTUD-5302
|
08/26/2013 05:40:10
|
Launch the platform configuration wizard at startup if it is the first run
|
If this is the first time user has launched Studio after installation, we should prompt the platform configuration wizard after Studio starts. For subsequent launches, we should not prompt.
| 3 |
1,580 |
TISTUD-5303
|
08/26/2013 06:04:45
|
Add access point to the new platform configuration wizard in new mobile project wizard
|
In the new mobile project wizard, instead of disabling a platform when it is not configured, we should enable all, but only check the ones user already configured by defaul. When user selects one or more unconfigured platforms and proceeds, we will prompt to indicate those platforms are not yet configured and ask if they would like to configure them. When user selects yes, we will open the platform configuration wizard with the unconfigured platforms that user has selected checked by default.
| 0 |
1,581 |
TISTUD-5304
|
08/26/2013 06:05:54
|
Add access point to the new platform configuration wizard in new module project wizard
|
In the new module project wizard, instead of disabling a platform when it is not configured, we should enable all, and when user choose a unconfigured platform (for module project, only one platform could be selected), we will prompt to indicate that platform is not yet configured and ask if they would like to configure it. When user selects yes, we will open the platform configuration wizard with the selected platform checked by default.
| 0 |
1,582 |
TISTUD-5305
|
08/26/2013 06:08:59
|
Add access point to the new platform configuration wizard in tiapp editor
|
In the tiapp editor, instead of showing a platform as diabled when it is not configured, we should enable them, and when user selects one and saves the editor, we will prompt to indicate the platform(s) are not yet configured and ask if they would like to configure them. When user selects yes, we will open the platform configuration wizard with the unconfigured platforms that user has selected checked by default.
| 0 |
1,583 |
TISTUD-5307
|
08/26/2013 22:59:14
|
Platform Config Wizard: Make the version string more clear
|
The current version displayed for each platform in the wizard is just the number and does not indicate clearly what it is for. It should be prepended by say 'Version' or 'SDK'.
| 3 |
1,584 |
TISTUD-5308
|
08/26/2013 23:16:18
|
Platform Config Wizard: Improve the layout for Advanced Settings section
|
When the Advanced Settings section is expanded, the section should cover the entire width of the wizard.
| 5 |
1,585 |
TISTUD-5309
|
08/26/2013 23:19:32
|
Platform Config Wizard: Hide Advanced Settings button and section for iOS
|
The wizard should allow the ability for a platform to indicate it does not need an Advanced Settings section, e.g. iOS, and hide the section accordingly.
| 3 |
1,586 |
TISTUD-5310
|
08/26/2013 23:22:46
|
Platform Config Wizard: Not to resize the wizard width when expanding the Advanced Settings section
|
Currently when the Advanced Settings section is expanded and if the SDK location path is long, the wizard will get expanded to a width enough to show the complete path. That looks jarring. Instead, we should maintain the wizard width and set a width hint on the text field.
| 3 |
1,587 |
TISTUD-5311
|
08/26/2013 23:24:53
|
Platform Config Wizard: The "Advanced Settings" text should not appear grayed out
|
The "Advanced Settings" text should appear normal like for "Hide Settings" when the section is expanded.
| 2 |
1,588 |
TISTUD-5312
|
08/27/2013 01:38:45
|
Improve performance of Android preference page
|
The preference page of Android does not react immediately to user actions. For instance, - Takes long time to open the preference page. - If Configure button is clicked, then it takes a long time to open the dialog that shows the list of Android SDKs. - It takes a long time to initialize the status based on the new SDK location.
| 8 |
1,589 |
TISTUD-5327
|
08/27/2013 08:46:23
|
When Importing Project, give user option to create a copy of the project directory
|
When customers are importing projects (especially when moving them from Ti Studio to AppC Studio) would be useful to have an option in the import dialog to make a folder copy to the AppC Studio workspace and then import it. This way any changes made to the app when enabling services in AppC Studio would not impact the original project if we run into any issues getting the customer setup in AppC Studio (e.g. services don't enable correctly, modules fail etc., customer will want to rollback to working copy of the app while we figure things out).
| 5 |
1,590 |
TISTUD-5314
|
08/27/2013 13:53:50
|
Remove help image and link next to unconfigured platforms, use decorators and hover UI from project wizard
|
The existing UI for unconfigured platforms adds a help/info image which you must click on to view details. Replace with some sort of decorator with details on hover or in some summary section, like we do in the new project wizard.
| 5 |
1,591 |
TISTUD-5315
|
08/27/2013 13:56:34
|
Add an "Install..." button to the deploy target section. Enable when user has selected an unconfigured platform
|
We must enable all the deploy targets by default. If a user selects an unconfigured platform, enable an "Install..." button (much like the "Enable Services" button in Appc Studio). When clicked the button will open the new config/install wizard with the unconfigured platform(s) selected in tiapp pre-selected in wizard. Show listing of all platforms in case user wants to install multiple at same time (though selecting another platform won't affect tiapp of project that got us here).
| 5 |
1,592 |
TISTUD-5316
|
08/27/2013 13:59:14
|
Add wrench icon after each configured platform in tiapp editor to open platform prefs, remove "Configure..." link
|
We currently have a "Configure..." link at bottom of the listing that opens all the pref pages for the platforms. Remove that link and instead have a small wrench icon next to each configured platform that when clicked will open the preference page for that particular platform. May need to do the same next to the titanium SDK drop down to open Titanium SDK pref page?
| 3 |
1,593 |
TISTUD-5317
|
08/27/2013 14:02:07
|
Enable unconfigured platforms, reduce severity of decorators
|
We currently disable unconfigured platforms in the listing. We should enable them, but not pre-select them. The severity of all warnings/errors about their not being configured should be reduced to Info icons.
| 3 |
1,594 |
TISTUD-5318
|
08/27/2013 14:02:59
|
Remove the "Configure SDKs" link
|
We find the link to be an extreme edge case most users won't need now that we're providing installation of unconfigured platforms inside the wizard.
| 2 |
1,595 |
TISTUD-5319
|
08/27/2013 14:06:01
|
When unconfigured platform is selected, dynamically add install page as next page
|
If user selects an unconfigured page, disable "Finish" and enable "Next". Make next page be the install wizard page. Filter that page down to only the selected and unconfigured platforms. When user finishes wizard we'll install unconfigured platforms, then create project. If a platform fails to install we'll need to prompt if it's OK to create project with that platform and let them know how to install it later through tiapp editor?
| 8 |
1,596 |
TISTUD-5320
|
08/27/2013 14:08:28
|
Order Android SDK Versions in Install Wizard sorted vertically, not row with wrapping
|
Currently we add Android versions into a two column grid layout so the sorting looks a bit odd: {code} 4.3 4.2 4.1 3.2 ... {code} Switch to column sorting: {code} 4.3 3.1 4.2 2.3 4.1 2.2 3.2 {code}
| 3 |
1,597 |
TISTUD-5321
|
08/27/2013 14:18:08
|
Install Wizard: Disable installed Android versions, but select them
|
Disable installed SDK versions, but select them to indicate they're installed, but can not be uninstalled through the wizard.
| 2 |
1,598 |
TISTUD-5322
|
08/27/2013 14:20:07
|
Replace the "Configure" Button in Android Pref page with "Install SDKs..."
|
The "Configure" button now opens the install wizard which seems shoe-horned. Replace the button with an "Install SDKs..." button that opens a dialog that contains only the Android SDK listing (currently inside the install wizard's advanced settings section for Android) and lets you choose additional versions to install.
| 8 |
1,599 |
TISTUD-5324
|
08/27/2013 14:22:12
|
Make iOS SDK/XCode path uneditable label in pref page
|
If the user cannot set it through a preference then we should change from a text field to an uneditable label.
| 3 |
1,600 |
TISTUD-5325
|
08/27/2013 14:24:37
|
Replace "Configure" button in iOS pref page with "Install" or "Update" button
|
Clicking "Configure" doesn't make much sense to then bring up the install wizard. If there's a valid XCode detected, replace with an "Update..." button that opens Mac App Store to Update tab. If there's no valid Xcode selected, replace with "Install..." button that opens Mac App Store to XCode page (like the install wizard does).
| 5 |
1,601 |
TISTUD-5326
|
08/27/2013 14:26:18
|
Show some visual indicator in install Wizard UI to indicate when an install will happen for a platform
|
We want to be able to indicate to the user when we're going to actually download and install something versus when we'll just take the SDK path and save it. They may have made a typo in typing path to an existing install, so it'd be nice for them to see if we were unable to find an SDK at the path and are going to install one to the path.
| 8 |
1,602 |
TISTUD-5329
|
08/27/2013 19:03:28
|
Auto select platform if the advance section details are modified
|
In the platform configuration wizard, in case if Android is not selected and if the user modifies any SDK entities in its advance section, then the Android platform has to be selected automatically for the user. This will be application for all platforms in case if the SDK location path is modified.
| 5 |
1,603 |
TISTUD-5330
|
08/27/2013 19:25:08
|
Enable unconfigured platforms, reduce severity of decorators
|
We currently disable unconfigured platforms in the listing. We should enable them, and the severity of all warnings/errors about them not being configured should be reduced to Info icons.
| 3 |
1,604 |
TISTUD-5331
|
08/27/2013 19:27:42
|
Remove the "Configure SDKs" link
|
We find the link to be an extreme edge case most users won't need now that we're providing installation of unconfigured platforms inside the wizard.
| 2 |
1,605 |
TISTUD-5332
|
08/27/2013 19:29:32
|
When unconfigured platform is selected, dynamically add install page as next page
|
If user selects an unconfigured platform, disable "Finish" and enable "Next". Make next page be the install wizard page. Filter that page down to only the selected platform. When user finishes wizard we'll install the unconfigured platform first, then create project. If a platform fails to install we'll need to prompt if it's OK to create project with that platform and let them know how to install it later through tiapp editor?
| 8 |
1,606 |
TISTUD-5337
|
08/29/2013 01:11:29
|
Loading iOS provisioning profiles: Improve the error message when CLI is not found
|
If the CLI is not installed or if it is installed to a location that is not in user's PATH, user will run into a NPE when the provision profiles are loaded. We should better handle such cases.
| 5 |
1,607 |
TISTUD-5339
|
08/29/2013 15:10:31
|
Android: Emulator: Enable Fastdev for 3.1.3+ SDK
|
Application with fastdev enabled in the tiapp.xml when executed in emulator, Fastdev server doesn't run. Fastdev is enabled and server runs with android 2.3.3 on emulator. Issue occurs with Android version 4.1 and later. Steps to reproduce: 1. Create a default project in the appcelerator studio. 2. Add <property name="ti.android.fastdev" type="bool">true</property> in the tiapp.xml. 3. Run the app with Android 4.1.2 on emulator. Expected: App should run with fastdev server running. Should get log as " Fastdev server running, deploying in Fastdev mode" Actual: Getting log as "Fastdev enabled but server isn't running" on the console.
| 3 |
1,608 |
TISTUD-5338
|
08/29/2013 18:05:53
|
Unable to format TSS files in TiStudio 3.1.2 + 3.1.2, works in TiStudio 3.1.1
|
1. Install Titanium Studio 3.1.2 or 3.1.3 and Update SDKs, install Alloy 2. Create a new Mobile Project, Alloy Default Template 3. Load the App.tss file 4. Click MENU / SOURCE / FORMAT or CMD + Shift + F 5. Error reported in the status bar, "Unable to format" and log will show Formatter error: startOffset > endOffset Also reported if you go to Menu > Titanium Studio > Preferences, go to Formatting and click the TSS entry - OSX will "beep" and the error is reported in the status bar / log. Does not occur on Titanium Studio 3.1.1 but upgrading to 3.1.2+ will create the behaviour. Reported by user here:- http://developer.appcelerator.com/question/156297/formating-tss-file-formatter-error-startoffset--endoffset with log details.
| 5 |
1,609 |
TISTUD-5345
|
09/03/2013 23:34:10
|
Show indefinite progress for iOS SDK configuration with status message
|
The iOS SDK configuration/installation status does not show any progress and the SDK installation status message 'Installing..' may not be applicable for iOS. 1) Show indefinite progress for the iOS sdk installation. 2) Show the sdk status message indicating that we are waiting for user to install Xcode
| 3 |
1,610 |
TISTUD-5350
|
09/06/2013 19:42:22
|
Platform Config Wizard: iOS: move the visual indicator for downloading to the right-most column
|
Related to TISTUD-5326. For iOS, currently there is no Advanced Settings section, and the visual indicator will appear in its place, making the UI feel inconsistent. The suggestion is to line it up on the right as indicators for other platforms are.
| 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.