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,111 |
TISTUD-3468
|
02/12/2013 16:16:19
|
Advertisement on the header of dashboard should be missing
|
Steps To Reproduce: 1. Open Studio>Dashboard Actual: Notice header above "Welcome back, <Username>". Studio Advertisements are not appearing Expected: Studio Ads must appear.
| 5 |
1,112 |
TISTUD-3474
|
02/12/2013 23:46:10
|
Not to use legacy scripts if CLI is not installed and SDK is 3.0.0+
|
Remove Legacy Scripts if CLI is not installed and SDK is 3.0.0+. One example of the consequences of supporting legacy scripts on SDK 3.0.0+ is TISTUD-3452.
| 8 |
1,113 |
TISTUD-3476
|
02/13/2013 11:27:47
|
Titanium Project: Terminating new Node.ACS project creation process is throwing error
|
This is a regression. It did not happen in Studio 3.0.1. Test Steps: 1.File > New > Node.ACS Project. 2.Enter project name. 3.Press Finish. 4.Before the creation of the project folder, cancel it by clicking on the red square at the bottom. Observe the error. Screenshots and logs attached.
| 8 |
1,114 |
TISTUD-3480
|
02/13/2013 21:11:38
|
Windows: Android SDKs not recognized without moving them
|
This is a regression. Works correctly in TISTUD 2.1.2. Windows: Android SDKs not recognized in Preferences. Steps to Reproduce: 1. Open Titanium Studio. 2. Open Preferences > Titanium Studio > Titanium. 3. Clear Android SDK Path and Apply. 4. Browse to Android SDK to select path. Actual Result: Android SDKs not recognized. Expected Result: Android SDKs recognized.
| 8 |
1,115 |
TISTUD-3484
|
02/13/2013 23:57:06
|
Add an option to publish to the Oracle Mobile Server
|
Reference https://wiki.appcelerator.org/display/guides2/Adding+a+new+Publish+Provider#AddinganewPublishProvider-ContributetoPublishMenus for contributing to the Publish menu. The action should be visible only if the project has Android as a deploy target. When invoked, it will launch the publishing wizard (see TISTUD-3485). See https://wiki.appcelerator.org/display/tools/Publish+Apps+to+Oracle+Mobile+Server for the Oracle integration document.
| 5 |
1,116 |
TISTUD-3485
|
02/14/2013 01:12:34
|
Contribute a publish provider for publishing to Oracle mobile server
|
Reference https://wiki.appcelerator.org/display/guides2/Adding+a+new+Publish+Provider#AddinganewPublishProvider-PublishProviderExtensionPoint for using the publish provider extension. 1. The supported platform is Android; 2. The publish target is the Oracle Mobile Server. We have a test server as specified in https://wiki.appcelerator.org/display/tools/Publish+Apps+to+Oracle+Mobile+Server.
| 8 |
1,117 |
TISTUD-3486
|
02/14/2013 01:19:29
|
Implement publishing to the Oracle Mobile Server using their APIs
|
The publishing should happen through Oracle APIs(check the Resource Manager APIs). See http://docs.oracle.com/cd/E22663_01/doc.11100/e22677/sync.htm#i1007512. Use the Resource Manager APIs to create the publication, package it with an application, and publish it to the mobile server. See the oracle.mobile.admin.MobileResourceManager in the Oracle Database Mobile Server JavaDoc, which is located off the ORACLE_HOME/Mobile/doc/index.htm page. Reference the doc at https://wiki.appcelerator.org/display/tools/Publish+Apps+to+Oracle+Mobile+Server.
| 13 |
1,118 |
TISTUD-3487
|
02/14/2013 01:23:07
|
Warn user it will overwrite when re-publishing the project to Oracle server
|
When re-publishing an Oracle module integrated app, the developer should be alerted that an overwrite of a previously published application is going to occur. Reference the doc at https://wiki.appcelerator.org/display/tools/Publish+Apps+to+Oracle+Mobile+Server.
| 5 |
1,119 |
TISTUD-3493
|
02/14/2013 22:44:09
|
Tizen: Create icons for Tizen platform integration
|
As we are you integrating Tizen platform into Studio, it requires Tizen based images/icons to represent Tizen SDK platform in the menus, toolbars and module tables. The icon/image might be similar to the icon referred to Tizen at https://developer.tizen.org/ It need images for elcl12, elcl16 and obj16 formats.
| 8 |
1,120 |
TISTUD-3496
|
02/15/2013 20:01:36
|
Alloy templates sometimes do not show up
|
Haven't been able to reproduce locally, but we have seen a number of reports from users that alloy templates do not show up in Titanium project wizard. When we checked the log, the "alloy info templates" command doesn't appear to get called. We need to check under what condition it could occur. Attached a user log. Also we had user try running "alloy info templates" directly from the command line, and it returns the expected json output.
| 5 |
1,121 |
TISTUD-3498
|
02/15/2013 23:28:03
|
Tizen: Add Dashboard Configure
|
Tizen: Add Dashboard Configure. See Screenshot.
| 0 |
1,122 |
TISTUD-3501
|
02/18/2013 22:09:41
|
Unable to create Titanium project when offline: failed to load project templates
|
Jeff saw the following exception when trying to create a project while offline: {code} !ENTRY org.eclipse.ui 4 0 2013-02-17 22:10:11.389 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Unsupported or unrecognized format 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.internal.image.FileFormat.load(FileFormat.java:82) at org.eclipse.swt.graphics.ImageLoader.load(ImageLoader.java:130) at org.eclipse.swt.graphics.ImageDataLoader.load(ImageDataLoader.java:22) at org.eclipse.swt.graphics.ImageData.<init>(ImageData.java:331) at org.eclipse.jface.resource.URLImageDescriptor.getImageData(URLImageDescriptor.java:71) at org.eclipse.jface.resource.ImageDescriptor.createImage(ImageDescriptor.java:273) at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:159) at org.eclipse.jface.resource.ImageDescriptor.createImage(ImageDescriptor.java:227) at com.aptana.projects.wizards.ProjectTemplateSelectionPage.getImage(ProjectTemplateSelectionPage.java:444) at com.aptana.projects.wizards.ProjectTemplateSelectionPage.setSelectedTag(ProjectTemplateSelectionPage.java:359) at com.aptana.projects.wizards.ProjectTemplateSelectionPage.setSelectedTemplate(ProjectTemplateSelectionPage.java:428) at com.aptana.projects.wizards.ProjectTemplateSelectionPage.createControl(ProjectTemplateSelectionPage.java:198) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1247) at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1239) at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1228) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1226) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:117) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) 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(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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !ENTRY org.eclipse.ui 4 0 2013-02-17 22:10:12.088 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at com.aptana.projects.wizards.ProjectTemplateSelectionPage$3.widgetDisposed(ProjectTemplateSelectionPage.java:158) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1461) at org.eclipse.swt.widgets.Widget.release(Widget.java:1299) at org.eclipse.swt.widgets.Control.release(Control.java:2826) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:903) at org.eclipse.swt.widgets.Widget.release(Widget.java:1302) at org.eclipse.swt.widgets.Control.release(Control.java:2826) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:903) at org.eclipse.swt.widgets.Widget.release(Widget.java:1302) at org.eclipse.swt.widgets.Control.release(Control.java:2826) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:903) at org.eclipse.swt.widgets.Widget.release(Widget.java:1302) at org.eclipse.swt.widgets.Control.release(Control.java:2826) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:903) at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:331) at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java:391) at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:1372) at org.eclipse.swt.widgets.Widget.release(Widget.java:1302) at org.eclipse.swt.widgets.Control.release(Control.java:2826) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:662) at org.eclipse.jface.window.Window.close(Window.java:335) at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:979) at org.eclipse.jface.dialogs.TrayDialog.close(TrayDialog.java:221) at org.eclipse.jface.wizard.WizardDialog.hardClose(WizardDialog.java:892) at org.eclipse.jface.wizard.WizardDialog.close(WizardDialog.java:486) at org.eclipse.jface.wizard.WizardDialog.cancelPressed(WizardDialog.java:473) at org.eclipse.jface.wizard.WizardDialog$1.widgetSelected(WizardDialog.java:323) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:117) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) 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(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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code}
| 3 |
1,123 |
TISTUD-3504
|
02/19/2013 20:08:39
|
Add Node.ACS plugin to default Titanium Studio installation
|
The Node.ACS plugin should be added into the default Titanium Studio install as part of 3.1.0, rather than remaining a separate, optionally-installed plugin.
| 3 |
1,124 |
TISTUD-3505
|
02/19/2013 20:16:41
|
Linux: Titanium Updates Prompt Never Goes Away
|
Linux: Titanium Updates Prompt Never Goes Away and SDK Not Recognized as Installed. Regression. Works in Studio 3.0.1 on Ubuntu 10.04 & 12.04. Steps to Reproduce: 1. Run Studio. 2. Check for Titanium Updates. Actual Results: Updates Menu asks to install everything again even if it is already installed.
| 5 |
1,125 |
TISTUD-3506
|
02/19/2013 21:33:18
|
Support Enterprise Proxy Environment
|
Support Enterprise Proxy Environment.
| 0 |
1,126 |
TISTUD-3509
|
02/19/2013 23:16:34
|
Linux: Titanium SDK updates not recognized
|
Linux: Titanium SDK updates not recognized. Regression. Works in Studio 2.1.2. Reproduction Method 1: 1. Uninstall stable Titanium SDK. 2. Check for Titanium Updates. Failure: No updates detected. Reproduction Method 2: 1. Install Titanium SDK... 2. From Stream > Release. Failure: No SDKs listed.
| 5 |
1,127 |
TISTUD-3511
|
02/20/2013 06:48:12
|
Not seeing the new SDK release until restarting Studio
|
It appears we are caching the list of SDKs that we parsed from the response of hitting the release URL, in TitaniumSDKUpdater.getSDKReleases(). This causes an issue that when we push a new SDK release, user will need to restart Studio to see the update; checking for updates manually without restarting doesn't work since we checked for updates automatically when Studio is launched and already cached the previous result. We should either have the method accept a force parameter to not use the cache if there are different cases to distinguish or always not to cache.
| 5 |
1,128 |
TISTUD-3512
|
02/20/2013 16:32:06
|
Tizen is marked as an error in the deploy target listing in tiapp.xml validation
|
Looking at a tiapp.xml that had tizen listed (and turned off) on my Mac, the validation marked the listing as an error. We seem to have a hard-coded list of enumerated values that doesn't include tizen. We likely need to hook up the validation to loop through the platform extensions and verify the id is in there.
| 2 |
1,129 |
TISTUD-3513
|
02/20/2013 16:36:01
|
Dashboard : Improve load time performance during its startup
|
During the startup of Studio, it appears to hang for a few seconds while it is trying to load/show dashboard. I think Dashboard needs to re-worked (either calling the services and caching the portal action results in the background) to improve the performance of its startup so it does not hang the Studio UI.
| 8 |
1,130 |
TISTUD-3514
|
02/20/2013 22:11:21
|
Studio becomes sluggish & we get 'Out of memory error'
|
This has happened to me 4-5 times as of now Description: 1.Start the version of studio mentioned in the environment 2.Build & run some apps 3.Notice the performance of studio Actual Result: 1.The studio becomes sluggish & we get the out of memory error We get the following errors in the log: {code} !ENTRY org.eclipse.core.jobs 4 2 2013-02-20 13:54:11.963 !MESSAGE An internal error occurred during: "Decoration Calculation". !STACK 0 java.lang.OutOfMemoryError: Java heap space at org.eclipse.core.runtime.Path.toOSString(Path.java:905) at com.aptana.git.core.model.ChangedFile.<init>(ChangedFile.java:49) at com.aptana.git.core.model.ChangedFile.<init>(ChangedFile.java:38) at com.aptana.git.core.model.GitIndex.changedFiles(GitIndex.java:325) at com.aptana.git.core.model.GitIndex.resourceOrChildHasChanges(GitIndex.java:634) at com.aptana.git.core.model.GitRepository.resourceOrChildHasChanges(GitRepository.java:1729) at com.aptana.git.ui.internal.GitLightweightDecorator.decorateFolder(GitLightweightDecorator.java:150) at com.aptana.git.ui.internal.GitLightweightDecorator.decorate(GitLightweightDecorator.java:126) at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:370) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:330) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.jobs 4 2 2013-02-20 13:55:32.871 !MESSAGE An internal error occurred during: "Decoration Calculation". !STACK 0 java.lang.OutOfMemoryError: Java heap space at java.lang.String.substring(String.java:1939) at org.eclipse.core.runtime.Path.computeSegments(Path.java:486) at org.eclipse.core.runtime.Path.initialize(Path.java:602) at org.eclipse.core.runtime.Path.fromPortableString(Path.java:106) at com.aptana.git.core.model.ChangedFile.<init>(ChangedFile.java:49) at com.aptana.git.core.model.ChangedFile.<init>(ChangedFile.java:38) at com.aptana.git.core.model.GitIndex.changedFiles(GitIndex.java:325) at com.aptana.git.core.model.GitIndex.resourceOrChildHasChanges(GitIndex.java:634) at com.aptana.git.core.model.GitRepository.resourceOrChildHasChanges(GitRepository.java:1729) at com.aptana.git.ui.internal.GitLightweightDecorator.decorateFolder(GitLightweightDecorator.java:150) at com.aptana.git.ui.internal.GitLightweightDecorator.decorate(GitLightweightDecorator.java:126) at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:370) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:330) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.jobs 4 2 2013-02-20 13:56:26.074 !MESSAGE An internal error occurred during: "Attaching Git repos". !STACK 0 java.lang.NullPointerException at org.eclipse.core.internal.resources.WorkspaceRoot.getFileForLocation(WorkspaceRoot.java:137) at com.aptana.git.core.model.GitIndex.getResourceForChangedFile(GitIndex.java:697) at com.aptana.git.core.model.GitIndex.getChangedResources(GitIndex.java:684) at com.aptana.git.core.model.GitRepository.getChangedResources(GitRepository.java:1779) at com.aptana.git.ui.internal.GitLightweightDecorator.repositoryAdded(GitLightweightDecorator.java:374) at com.aptana.git.core.model.GitRepositoryManager.fireRepositoryAddedEvent(GitRepositoryManager.java:227) at com.aptana.git.core.model.GitRepositoryManager.attachExisting(GitRepositoryManager.java:213) at com.aptana.git.core.GitResourceListener$GitAutoAttachProjectJob.run(GitResourceListener.java:193) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} Expected Result: 1.The studio should run properly
| 13 |
1,131 |
TISTUD-3517
|
02/21/2013 11:32:33
|
Studio: Run diagnostic test is displaying - Default system web browser: null (null)
|
Test Steps: Launch Titanium Studio. Help > Titanium Studio > Run Diagnostic Test > Verify value for 'Default system web browser' Actual Result: Default system web browser: null (null) is displayed in " Run Diagnostic Test ' window
| 5 |
1,132 |
TISTUD-3521
|
02/21/2013 21:24:38
|
Decouple the IMobileLaunchConfigurationContributor from ILaunchConfiguration
|
At the moment, the IMobileLaunchConfigurationContributor is coupled with ILaunchConfiguration and ILaunchConfigurationWorkingCopy instances that are passed in when loading defaults, applying changes and such. This task includes: # Decoupling this dependency and allow passing in a generic Map that will hold the attributes. # Refactoring the existing calles to pass in the launch-configuration attributes (a Map). Then, in cases where the map is modified, re-apply the map on the launch configuration (working copy).
| 8 |
1,133 |
TISTUD-3532
|
02/22/2013 22:32:11
|
Update the Studio code to support Tizen when checking for the supported platforms
|
Updating the Studio code to support Tizen when checking for the supported platforms. This includes the work to update the sdk_info.json file with link to the Tizen SDK download (https://developer.tizen.org/downloads/tizen-sdk).
| 8 |
1,134 |
TISTUD-3533
|
02/22/2013 22:43:37
|
Update the Dashboard to check for Tizen SDK and display corresponding message
|
Update the Dashboard side to call the SDK-Info command with a "tizen" key. Then, parse the result and display any info (like we do with the rest of the platforms). The Tizen section in Dashboard will look similar to what BlackBerry one shows.
| 5 |
1,135 |
TISTUD-3534
|
02/22/2013 22:50:15
|
Prevent duplicate deployment targets for 'Tizen' & 'MobileWeb' platforms
|
Description: 1.Click on create new titanium app 2.Select the desired template 3.Click next 4.Look in the 'deployment targets' options Actual result: 1.You see 2 target options for 'Tizen' & 'MobileWeb' Note: You will see the duplicate targets in the tiapp.xml for the older app's created on previous versions of studio Expected Result: 1.You should see only one target option for tizen & mobileweb respectively
| 3 |
1,136 |
TISTUD-3537
|
02/23/2013 02:16:36
|
Allow user to switch between different update streams (Stable/RC/Beta/Nightly) easily
|
Suggest to have a group of radio buttons or a combo-box in preferences page with options Stable, RC, Beta, and Nightly. Stable will be the default choice, and when user switches to another selection, e.g. RC, we will scan the list of available update sites and replace the ones containing /stable with urls containing /rc. So for the base Studio, http://preview.appcelerator.com/appcelerator/studio/standalone/update/stable/ with be disabled and http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/ will be added and enabled. This will apply to the add-on plugins that we provide as well, and we will keep the update url naming convention consistent across all the features. It will help reduce the likelihood of having incompatible versions of plugins installed against each other. We could also have a remote file that contains the list of our update url prefixes, and we will append the right update stream type for the full URL to add and remove. This avoids the issue of user modifying the list of update sites manually and we no longer able to find the original url to replace.
| 13 |
1,137 |
TISTUD-3538
|
02/23/2013 02:22:48
|
Remove PHP/Ruby/Pydev features from Titanium Studio
|
We need to make PHP/Ruby/Pydev not part of the base Titanium Studio install.
| 8 |
1,138 |
TISTUD-3539
|
02/23/2013 02:28:16
|
Publish PHP/Ruby/Pydev features to their own update sites
|
The builds are in place; we just need to update the sync-nightly job (and sync-beta and sync-rc) to publish the respective Jenkins build to a public update site. The url will be in the form of http://preview.appcelerator.com/appcelerator/studio/php/update/nightly.
| 8 |
1,139 |
TISTUD-3542
|
02/23/2013 03:01:37
|
Proxy : Unable to clear the proxy settings during login screen
|
In the login screen, after the proxy details are setup, there is no way to clear the proxy settings and proceed only with the login credentials. The proxy dialog displays error that invalid host details if trying to clear the proxy details and proceed with login credentials.
| 5 |
1,140 |
TISTUD-3547
|
02/25/2013 21:24:09
|
Titanium Updates: add code processor update stream release notes docs
|
Steps to Reproduce: 1. Clean install Titanium Studio 3.1.0. 2. Check for Titanium updates. 3. Select Titanium Code Processor. Actual Result: The documentation is minimal. Expected Result: We should have change logs similar to what we have with CLI.
| 5 |
1,141 |
TISTUD-3555
|
02/26/2013 00:11:54
|
Add a preference page for Denso platform
|
The preference page node will be under Platforms, and the content will contain a field for the Denso SDK location and a browse button. It should validate the path and generate DensoSDKLocator from it. The IVI SDK is at https://github.com/DensoITLab/VehicleAPI/tree/develop/src/VehicleModule/VehicleModule_IVI.
| 8 |
1,142 |
TISTUD-3556
|
02/26/2013 00:16:49
|
Run > Tizen Device menu should be in the same group as other run-on-device menu items
|
The Tizen Device menu under Run is currently in the same group as all the simulator/emulator ones. It should be moved to under the separator.
| 3 |
1,143 |
TISTUD-3557
|
02/26/2013 00:19:42
|
Not to show the Settings group in Tizen's main launch configuration tab
|
There is currently no options under the Settings group for Tizen's launch configuration tab. In this case, we should just not show the group.
| 3 |
1,144 |
TISTUD-3576
|
02/26/2013 07:30:44
|
Titanium project wizard template should pre-select Alloy templates as default type
|
Feedback from Gabe: Currently Studio pre-selects the Titanium Classic templates. Now that Alloy has GA'ed and it has been used by customers, it should be the default template type for users.
| 3 |
1,145 |
TISTUD-3584
|
02/26/2013 22:04:08
|
Dashboard: Update Android SDK to r21.1 on Staging
|
Dashboard: Update Android SDK to 21.1 on staging.
| 3 |
1,146 |
TISTUD-3592
|
02/27/2013 21:42:03
|
Packaging success notification appears even there is a packaging failure
|
When there is a failure in packaging Tizen project (should be applicable to Android and BlackBerry as well), the launch configuration error dialog is displayed indicating about the error. However, the packaging success dialog appears along with launch configuration error dialog. This problem happened when a Tizen project is packaged using the Titanium SDK that posted in http://preview.appcelerator.com/studio/tizen/
| 5 |
1,147 |
TISTUD-3597
|
02/28/2013 01:22:22
|
Package JDK in the Windows installer
|
We currently package a specific version of JRE (1.6.0_v24) when installed Studio on Windows. The suggestion is to package an equivalent version of JDK instead. We should also add the JDK path to the system path variable.
| 8 |
1,148 |
TISTUD-3600
|
02/28/2013 11:18:48
|
Preferences > Default Titanium SDK path saved even after being canceled
|
Test steps: 1. In Studio, navigate to Preferences > Titanium Studio > Titanium > Default Titanium SDK. 2. Change the Default SDK path to a different location and click on "Apply" 3. It displays a prompt for saying that the path location does not contain SDK 4. Select "No" from the prompt window 5. Now click "Cancel" from the Titanium Configuration screen. 6. Now again, navigate to Preferences > Titanium Studio > Titanium > Default Titanium SDK. Actual Result: The path which was changed from the default SDK location still persist on the Titanium SDK Home tab. Expected Result: The The path which was changed from the default SDK location should not persists.The Titanium General configuration window should either display a error message when user tries to close the window after setting invalid path or the default SDK location path should get reset when the window si closed without applying the changes.
| 5 |
1,149 |
TISTUD-3601
|
02/28/2013 18:25:20
|
Allow users to specify to be warned about missing semicolons
|
In ticket TIMOB-12894 we appear to have an issue where a developer forgot to add a semicolon in a crucial location. Because of a problem with bad minification in 2.1.X branches of the SDK, it caused a break once the app was deployed to the App Store. The code is below: {code} var USPostalReg = /^\d{5}(-\d{4})?$/ if (!USPostalReg.test(textFields_array[i].value)) { inValidValue = true; } {code} We need to allow users to specify semicolons as required (and probably make this as default for now)
| 8 |
1,150 |
TISTUD-3625
|
03/01/2013 19:34:18
|
Refactor the Deployment Targets section of tiapp.xml to have ios plugin contribute its entry
|
We should be able to re-use the attributes defined from TISTUD-3053 for the "Deployment Targets" section of tiapp.xml, as the idea here is to also have mobileweb plugin contribute the name, platform type, and if it's supported on the current system.
| 5 |
1,151 |
TISTUD-3624
|
03/01/2013 19:34:18
|
Refactor the Titanium project wizard to have ios plugin contribute its entry
|
Currently the Titanium project wizard defines all the checkboxes for deployment targets. We should have the ios plugin contribute the following attributes through the extension point from TISTUD-3066: 1. A display name ("iOS"); 2. A string for platform type ("ios") that will be used by CLI and other necessary operations; 3. A mean to check if the requirement for platform support is met, i.e. if the Titanium SDK contains the platform, if the platform SDK is installed (not applicable to Mobile Web), and if the OS supports the platform (not applicable here either), so the project wizard could enable/disable the checkbox as appropriate. It should return a status so we could display a warning or error message if needed. 4. Potentially a post-project creation hook to perform any iOS specific task needed (don't think we have any?). 5. An optional "priority" attribute to control the order of the platforms both here and in tiapp.xml. Currently we are sorting them in alphabetical order, but there might be a case in the future where we like to have the flexibility.
| 8 |
1,152 |
TISTUD-3623
|
03/01/2013 19:34:18
|
Refactor iOS code from mobile.* plugins into its own ios.core and ios.ui plugins
|
The idea is to have no iOS related code or constants in com.appcelerator.titanium.mobile and com.appcelerator.titanium.mobile.ui plugins. The subtasks will capture the work needed in the various areas to make this happen.
| 0 |
1,153 |
TISTUD-3627
|
03/01/2013 19:34:19
|
Have iOS plugin contribute to the preferences page
|
We should have a subnode for each platform under Preferences > Titanium Studio > Titanium and move the respective section from Titanium preference page there. The ios.ui plugin will contribute the iOS preference page and handle its preference settings.
| 5 |
1,154 |
TISTUD-3626
|
03/01/2013 19:34:19
|
Move Run > iPad Simulator action to ios plugin(s)
|
This involves moving the launch shortcut and related classes for contributing the Run > iPad Simulator action to ios' own plugins.
| 8 |
1,155 |
TISTUD-3632
|
03/01/2013 19:34:20
|
Move all references of iOS from the mobile and core plugins to ios plugins
|
Once all the subtasks of refactoring the mobileweb code into its own plugin is completed, all the references of ios from the titanium.core and mobile.ui has to be either removed or moved to ios ui/core plugins. All the constants, resources and utility methods corresponding to ios should only be available in ios plugins.
| 8 |
1,156 |
TISTUD-3631
|
03/01/2013 19:34:20
|
Move Publish > Package - iTunes action to iOS plugin
|
This involves moving the command/handler/menu/launch-config definitions and related classes for contributing the Publish > Package - iTunes action to ios' own plugins.
| 8 |
1,157 |
TISTUD-3630
|
03/01/2013 19:34:20
|
Move Run > iPhone Simulator action to iOS plugin(s)
|
This involves moving the launch shortcut definitions and related classes for contributing the Run > iPhone Simulator action to ios' own plugins.
| 8 |
1,158 |
TISTUD-3629
|
03/01/2013 19:34:20
|
Refactor the modules table section of tiapp.xml to have ios plugin contribute its column
|
The plugin will need to contribute the icon. We also need a mechanism to parse out the module version for Mobile Web to be shown in the table. Is the platform type enough, and the tiapp model could parse the directory structure from there?
| 3 |
1,159 |
TISTUD-3633
|
03/01/2013 19:34:21
|
Refactor the Titanium module project wizard to have iOS plugin contribute its entry
|
Refactor the Titanium module project wizard to have ios plugin contribute its entry as shown in the screenshot.
| 8 |
1,160 |
TISTUD-3634
|
03/01/2013 19:44:53
|
Move Publish > Package - Adhoc action to iOS plugin
|
This involves moving the command/handler/menu/launch-config definitions and related classes for contributing the Publish > Package - Adhoc action to ios' own plugins.
| 8 |
1,161 |
TISTUD-3635
|
03/01/2013 23:14:01
|
Android fails to build on emulator & device with the latest nightly studio 3.1.0.201302281824
|
I was testing tizen setup instructions for the tizen release & had tizen required software installed before I saw this issue. Description: 1.Update the nightly studio to the latest 3.1.0.201302281824 2.Create an app 3.Select target as android 4.Run in emulator/device Actual result: 1.the build fails. 2.Build log is as follows; {code} Logfile initialized [INFO] logfile = C:\Users\QEtester\Desktop\tistud\tistud-nightly\workspace\test\build.log [INFO] logfile = C:\Users\QEtester\Desktop\tistud\tistud-nightly\workspace\test\build.log [DEBUG] C:\Users\QEtester\AppData\Roaming\Titanium\mobilesdk\win32\3.1.0.v20130301142454\android\builder.py simulator test C:\Users\QEtester\Desktop\android\android-sdk C:\Users\QEtester\Desktop\tistud\tistud-nightly\workspace\test com.app.test 2 WVGA854 [DEBUG] C:\Users\QEtester\AppData\Roaming\Titanium\mobilesdk\win32\3.1.0.v20130301142454\android\builder.py emulator test C:\Users\QEtester\Desktop\android\android-sdk C:\Users\QEtester\Desktop\tistud\tistud-nightly\workspace\test com.app.test 2 WVGA854 [INFO] Building test for Android ... one moment [INFO] Launching Android emulator...one moment [DEBUG] From: C:\Users\QEtester\Desktop\android\android-sdk\tools\emulator.exe [DEBUG] SDCard: C:\Users\QEtester\.titanium\android2.sdcard [DEBUG] AVD ID: 2 [DEBUG] AVD Skin: WVGA854 [DEBUG] SDK: C:\Users\QEtester\Desktop\android\android-sdk [INFO] Titanium SDK version: 3.1.0 (03/01/13 14:24 66f7cce) [DEBUG] Waiting for device to be ready ... [TRACE] adb devices returned 0 devices/emulators [ERROR] Exception occured while building Android project: [ERROR] Traceback (most recent call last): [ERROR] File "C:\Users\QEtester\AppData\Roaming\Titanium\mobilesdk\win32\3.1.0.v20130301142454\android\builder.py", line 2479, in <module> [ERROR] builder.run_emulator(avd_id, avd_skin, avd_name, avd_abi, add_args) [ERROR] File "C:\Users\QEtester\AppData\Roaming\Titanium\mobilesdk\win32\3.1.0.v20130301142454\android\builder.py", line 619, in run_emulator [ERROR] avd_name = self.create_avd(avd_id, avd_skin, avd_abi) [ERROR] File "C:\Users\QEtester\AppData\Roaming\Titanium\mobilesdk\win32\3.1.0.v20130301142454\android\builder.py", line 538, in create_avd [ERROR] available_avds = avd.get_avds(self.sdk) [ERROR] File "C:\Users\QEtester\AppData\Roaming\Titanium\mobilesdk\win32\3.1.0.v20130301142454\android\avd.py", line 23, in get_avds [ERROR] for line in run.run([sdk.get_android(),'list','target'],debug=False).split("\n"): [ERROR] AttributeError: 'NoneType' object has no attribute 'split' [TRACE] adb devices returned 0 devices/emulators [TRACE] adb devices returned 0 devices/emulators [TRACE] adb devices returned 0 devices/emulators [TRACE] adb devices returned 0 devices/emulators [TRACE] adb devices returned 0 devices/emulators [ERROR] Timed out waiting for emulator to be ready, you may need to close the emulator and try again {code} Expected Result: 1.The build should succeed on device & simulator
| 8 |
1,162 |
TISTUD-3642
|
03/04/2013 16:30:11
|
Special characters in passwords fails to create, start projects
|
I get the error on creating a new project, if I use a complex password, like "Login failed: Error: Invalid username or password. If you have forgotten your password, please visit https://my.appcelerator.com/." Try: "%OEUK+guO:v'48I= ;M5W" (i lost the original, because I auto generate it) An alphanumeric password fixes the issue.
| 5 |
1,163 |
TISTUD-3648
|
03/05/2013 17:32:57
|
Project Context Menu: Run As and Debug As missing from bottom of list
|
Run As and Debug As missing from project context menu. Regression. Does not occur in 3.0.2. Steps to Reproduce: 1. Project Context Click > Run As. Actual Result: Missing. Expected Result: There.
| 8 |
1,164 |
TISTUD-3669
|
03/06/2013 21:44:20
|
Studio: Expose android keystore for Android non-production builds
|
Studio asks for keystore, alias, and password when packaging Android applications. This information is not requested when running in emulator or on device. If the android builder.py is not passed a keystore it uses the default keystore shipped with the SDK. The issue with this is that people who wish to use an app key, for say Google maps v2, are directed to use the default keystore to generate a debug key, and to generate their own keystore to create a production key. This could eventually lead to situations where multiple keys are associated with the same keystore on the google side. Steps to reproduce: 1) Create an android project in studio 2) Attempt to package the project - note the dialog requesting Keystore info 3) Attempt to run on device Result: THe default keystore is used since no keystore passed to builder.py. Expected: Prompt for keystore
| 8 |
1,165 |
TISTUD-3695
|
03/07/2013 22:20:05
|
Run Configurations: rename Enable minification to Enable JavaScript Minification
|
Run Configurations: rename Enable minification to Enable JavaScript Minification. Also note the capitalization of 'minification', it should be capitalized. This is usability issue, 'enable minification' is ambiguous to most users. Steps to Reproduce: 1. Create a run configuration for packaging (ios, etc.). Actual Result: Checkbox that says 'Enable minification' Expected Result: Checkbox that says either 'Enable Minification' or 'Enable JavaScript Minification' (preferred)
| 1 |
1,166 |
TISTUD-3696
|
03/07/2013 23:02:58
|
NPM installs does not work behind proxies
|
Something Max and Allen had issues with at Oracle. For interactions with NPM, we need to set the config properties: proxy https-proxy They should be set as follows: http://<username>:<password>@<proxy-url>:<proxy-port> I'm not sure if the Eclipse proxy utilities we use has a mechanism to generate the url
| 8 |
1,167 |
TISTUD-3697
|
03/07/2013 23:07:50
|
Titanium sign-up splash has no way of setting proxy settings
|
For users that are creating a new accounts, there is no way to specify the proxy settings on the sign-up page. For Enterprise, this would mean they can't actually sign up through Studio. Work-around would be to sign up via the Appcelerator.com site
| 3 |
1,168 |
TISTUD-3716
|
03/08/2013 21:49:26
|
Failed to install NodeJS. when sdk is prompted for overwrite
|
Failed to install NodeJS. when sdk is prompted for overwrite. See logs and screenshots. Steps to Reproduce: 1. Delete stable SDK (keep modules). 2. Delete Node.js (restart Studio as needed). 3. Check for Titanium Updates. 4. SDK downloads and partially installs, SDK prompt for overwrite. 5. Continue. Actual Result: Node.js fails to install.
| 8 |
1,169 |
TISTUD-3729
|
03/10/2013 22:28:22
|
Denso: New Titanium Module fails and generates npe in log: ImageDecoratorUtil
|
New > Titanium Module Project has no UI result. Error in log. Does not occur in regular Titanium Studio nightly. {code} !ENTRY org.eclipse.ui 4 0 2013-03-10 15:06:28.536 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at com.aptana.ui.util.ImageDecoratorUtil$CenteredCompositeImageDescriptor.<init>(ImageDecoratorUtil.java:71) at com.aptana.ui.util.ImageDecoratorUtil.getCompositeDescriptor(ImageDecoratorUtil.java:37) at com.aptana.ui.util.ImageDecoratorUtil.getCompositeWizbanDescriptor(ImageDecoratorUtil.java:48) at com.appcelerator.titanium.mobile.ui.module.wizard.NewMobileModuleProjectWizard.initializeDefaultPageImageDescriptor(NewMobileModuleProjectWizard.java:126) at org.eclipse.ui.wizards.newresource.BasicNewResourceWizard.init(BasicNewResourceWizard.java:89) at com.aptana.projects.wizards.AbstractNewProjectWizard.init(AbstractNewProjectWizard.java:495) at com.appcelerator.titanium.mobile.ui.module.wizard.NewMobileModuleProjectWizard.init(NewMobileModuleProjectWizard.java:114) at org.eclipse.ui.internal.navigator.wizards.WizardShortcutAction.run(WizardShortcutAction.java:84) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) 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(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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code}
| 2 |
1,170 |
TISTUD-3730
|
03/10/2013 22:33:26
|
Denso: splash login field does not have focus on startup
|
Denso: splash login field does not have focus on startup. See screenshot. Steps to Reproduce: 1. Log out of Studio. 2. Open Studio and proceed to login menu. Actual Result: Email text field does not have focus.
| 3 |
1,171 |
TISTUD-3737
|
03/11/2013 16:57:02
|
The title in console when running on Tizen device refers to emulator
|
Steps to reproduce: 1. Create a project with Tizen platform enabled; 2. In Project Explorer, run Run > Tizen on Device. The text in the console should say "Launching Tizen app on device".
| 2 |
1,172 |
TISTUD-3740
|
03/11/2013 18:19:03
|
CLI: support creating a project with Denso platform support
|
The Denso platform, called IVI, will be Mobile Web based. This ticket is to support the additional "ivi" option for the --platforms flag in "titanium create --platforms=[iphone,ipad,ios,android,blackberry,mobileweb,etc.]" call to create a Titanium project. For IVI, we could just follow the instruction in https://wiki.appcelerator.org/display/CLI/Adding+a+Platform+to+the+CLI, specifically the following part, as there are no additional setup steps needed on the IVI side for the moment: "Create a <platform> folder in the Titanium SDK distribution and then update the array of platforms in the SDK's manifest.json to include the platform."
| 13 |
1,173 |
TISTUD-3741
|
03/11/2013 18:24:04
|
CLI: "build" command for Denso apps
|
This task is for writing the {{build}}, {{install}}, and {{run}} builtins for the CLI for Denso platform (IVI) only, as per the [CLI spec|https://wiki.appcelerator.org/display/spe/Command+Line+Interface]. Please see https://wiki.appcelerator.org/display/CLI/Adding+a+Platform+to+the+CLI for reference.
| 13 |
1,174 |
TISTUD-3753
|
03/11/2013 22:28:34
|
Create a plugin that holds Google's implementation for reading Source-Maps
|
# Create a new APL plugin ("com.google.debugging.sourcemap") # Grab the code from https://code.google.com/p/closure-compiler/source/browse/#git%2Fsrc%2Fcom%2Fgoogle%2Fdebugging%2Fsourcemap and extract the relevant classes that deals with source mapping.
| 5 |
1,175 |
TISTUD-3755
|
03/11/2013 23:00:41
|
Create a new source map extension point
|
Create a new source map extension point that will allow a contribution of IJSSourceMap contributors. Also allow prioritizing source-map contributions, so we could potentially contribute several mappers in the future. Each contributor should use the source-map mechanism to map back and forth source paths and line numbers. See TISTUD-3753.
| 8 |
1,176 |
TISTUD-3758
|
03/11/2013 23:48:09
|
Modify JSDebugTarget to use the source-map extension point
|
Use the source-map extension point whenever needed in the JSDebugTarget to map source files when sending breakpoints information to the session, handling breakpoint suspensions and creating IJSScriptElement.
| 13 |
1,177 |
TISTUD-3760
|
03/12/2013 00:14:15
|
Run Configurations: MobileWeb Preview On Emulator Locks Studio
|
Run Configurations: MobileWeb Preview On Emulator Locks Studio. Logs attached. Steps to Reproduce: 1. Open Run Configurations... 2. Create new MobileWeb Preview On Emulator run configuration. Actual Result: Studio locks. Log Overview: {code} !ENTRY org.eclipse.help 4 0 2013-03-11 16:19:14.838 !MESSAGE Error reading help table of contents file /"com.aptana.documentation/html/reference/api/JSCore.toc.xml" (skipping file) !STACK 0 java.io.FileNotFoundException at org.eclipse.help.internal.toc.TocFileParser.parse(TocFileParser.java:49) {code} {code} !ENTRY org.eclipse.jface 4 2 2013-03-11 16:59:39.289 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.ui.launching.BaseTitaniumLaunchConfigurationTab.initializeFrom(BaseTitaniumLaunchConfigurationTab.java:329) {code} {code} !ENTRY org.eclipse.jface 4 2 2013-03-11 16:59:47.629 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.ui.launching.BaseTitaniumLaunchConfigurationTab.dispose(BaseTitaniumLaunchConfigurationTab.java:528) {code} {code} !ENTRY org.eclipse.ui 4 0 2013-03-11 17:01:07.604 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Device is disposed at org.eclipse.swt.SWT.error(SWT.java:4282) {code}
| 3 |
1,178 |
TISTUD-3769
|
03/12/2013 01:19:50
|
Node.ACS: project explorer packaging dropdown list is misaligned
|
Node.ACS: project explorer packaging dropdown list is misaligned. See screenshot. No errors in log. Click on Packaging icon for Node.ACS project to reproduce.
| 5 |
1,179 |
TISTUD-3770
|
03/12/2013 01:35:21
|
Project Templates: template order is random
|
Project Templates: make correct defaults for All and Titanium Classic. Note: Alloy has correct defaults. Currently the defaults are: All => Single Window Application Titanium Classic => Single Window Application The defaults should be: All => Alloy Default Application Titanium Classic => Default Application Verify by creating new Titanium Project.
| 5 |
1,180 |
TISTUD-3776
|
03/12/2013 20:08:32
|
TiApp Overview: blackberry checkbox missing info icon
|
TiApp Overview: blackberry checkbox missing info icon. If blackberry sdk not installed, needs info icon. For comparison, tizen has an info icon. Screenshot attached.
| 5 |
1,181 |
TISTUD-3778
|
03/12/2013 20:18:58
|
TiApp Overview: make module id column width higher by default
|
TiApp Overview: make module id column width higher by default. Module id is difficult to see. Screenshot attached.
| 3 |
1,182 |
TISTUD-3780
|
03/12/2013 20:53:52
|
Due to CLI changes all iPhone Simulators run non retina iPhone only
|
No matter which simulator you chose, Studio will launch non retina iPhone. Test steps: 1. Run App as iPhone Simulator 2. Go to iOS simulator > Hardware > Device and chose any simulator 3. Repeat step 1 Actual result: only non retina iPhone launches Expected result: The chosen iphone simulator type should launch *regression*
| 8 |
1,183 |
TISTUD-3782
|
03/12/2013 21:48:13
|
Improve Inactive Account Toast Message
|
When users upgrade to titanium studio 3.0.2 they then receive an error message that their account is inactive, After having checked their accounts they are already activated. Error message received: "Inactive Account" Suggested Improvement: ~"Email verification required. Please click link in activation email".
| 2 |
1,184 |
TISTUD-3788
|
03/13/2013 00:24:54
|
Code completion broken in Alloy TSS for selectors with IDs not defined in a view
|
h5. Problem Code completion is throwing an exception and displaying an error dialog for Alloy .tss files. h5. Steps to reproduce 1. Create a new Alloy project 2. Open and edit the index.tss file to be: {code} "#Window": { } {code} 3. Invoking content assist inside the braces throws an uncaught NPE and displays an error dialog.
| 8 |
1,185 |
TISTUD-3804
|
03/13/2013 17:11:27
|
Add validation of ids/classes defined in TSS but not views for Alloy
|
If a user refers to an id/class inside a TSS file that doesn't exist in any views, then the rule is effectively a "dead" one. We should be able to find and highlight styles applied to ids and classes that are never defined/referred to in views.
| 8 |
1,186 |
TISTUD-3805
|
03/13/2013 17:38:38
|
Add Auto-indent to TSS file
|
When we have the following code in a tss file: {code} #Window {|} {code} and hit Enter, it becomes {code} #Window { |} {code} The expected result is to auto-indent to {code} #Window { | } {code}
| 5 |
1,187 |
TISTUD-3808
|
03/13/2013 19:38:36
|
Code completion assistance doesn't automatically appear on Alloy TSS files
|
h5. Problem Code completion is not automatically being displayed for Alloy TSS files. h5. Steps to reproduce 1. Create a new Alloy project 2. Open and edit the index.tss file - for example: {code} "Window": { b } {code} Property name proposals (beginning with b) should automatically appear after hitting the 'b' character on the newline between the curly braces. Instead, user has to hit Ctrl+Space to invoke CA manually.
| 5 |
1,188 |
TISTUD-3814
|
03/13/2013 23:49:47
|
Alloy: add hover info for element names in Alloy .xml file
|
h5. Improvement description Alloy projects .xml files should also present the hover info like for .js files. When passing the mouse over an .xml element, information should be displayed as a popup like for objects in the .js files.
| 8 |
1,189 |
TISTUD-3820
|
03/14/2013 18:08:12
|
Alloy: Missing some items in the markup and controller code for content assist
|
For the XML markup, content assist does not suggest: * Collection, Model or Widget for tags. (Alloy and Require work.) * formFactor, platform for attributes. (id, class and ns work.) See the tables at the end of the 'Introduction' section, http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_XML_Markup There is also dataCollection, dataFilter, and dataTransform attributes for Ti proxies that support data binding, such as TableView and View. Tony introduced some other ones for Alloy 1.1.0. For the controller code, content assist does not suggest any of the elements in the Alloy namespace, such as Alloy.Globals, Alloy.createController, etc. See http://docs.appcelerator.com/titanium/latest/#!/api/Alloy.
| 5 |
1,190 |
TISTUD-3835
|
03/15/2013 21:48:56
|
BlackBerry Preferences: intermittent The currently displayed page contains invalid values
|
BlackBerry Preferences: intermittent The currently displayed page contains invalid values. The BlackBerry SDK is not set, this could be the cause of the intermittent error. The error seems to appear once (i.e., the first time), perhaps related to a new workspace. This is more of an improvement, though technically a bug. Test Steps: 1. Possibly delete workspace. 2. Open Studio. 3. Open Preferences > Studio > Platforms > BlackBerry. Actual Result: Error prompt appears only on this first click, never again.
| 5 |
1,191 |
TISTUD-3837
|
03/15/2013 23:13:33
|
Add Retina Support to iOS Simulator Run Config
|
Open iOS General Preferences, notice the Retina config options. Create iOS Simulator Run Config. Notice the missing Retina UI in the Run Config.
| 8 |
1,192 |
TISTUD-3838
|
03/15/2013 23:55:23
|
'Shift+Control+Space' keys binding for displaying Context Informations does not work
|
h5. Problem By default, Studio is setting the key binding 'Shift+Control+Space' for displaying Context Informations. It does not work anywhere in any project or file type. Also, going into 'Titanium Studio - Preferences - Keys', it's not possible to set the 'Shift+Control+Space' binding for any Command. In this case, 'Shift+Control' signs are displayed but the 'Space' is not, so it's not possible to save this Binding for any Command. Changing the Binding for the Context Information to something else (for example, 'Shift+Alt+Space') works as expected and in this case the Context Informations are displayed correctly. Tested and reproduced on 3.0.2.GA and latest 3.1.X nightly build. Not a regression.
| 5 |
1,193 |
TISTUD-3842
|
03/16/2013 03:14:34
|
Android Keystore Preferences missing from TiApp Overview Configure Link
|
Android Keystore Preferences missing from TiApp Overview Configure Link. See screenshots. The Keystore Preference is being erroneously filtered. TiApp Editor Overview : Deployment Targets : Configure...
| 3 |
1,194 |
TISTUD-3861
|
03/18/2013 22:32:55
|
Improve performance of Titanium SDK installation
|
Troubleshooting the installation of Titanium SDK reveals that a process is invoked for every unzipped entry of SDK to grant permission. Kicking off process for every unzipped entry degrades the performance of Titanium SDK installation. To improve the performance, one viable option is to set the permission only on the parent folder and set it to inherit the permission to all child files.
| 8 |
1,195 |
TISTUD-3863
|
03/19/2013 18:50:22
|
List github repos from user's organizations in import wizard
|
We only show the user's personal repos in the listings. We should also look for the repos they have access to from their organizations. http://developer.github.com/v3/orgs/
| 8 |
1,196 |
TISTUD-3875
|
03/20/2013 21:57:13
|
iOS Device Run: Launch menu changes result in extra run configuration
|
iOS Device Run: Launch menu changes result in extra run configuration. If a project has an existing iOS Device Run Configuration instance, and iOS Device Run is launched from Run Icon, and the user Edits a run configuration value, a new run configuration will be created. It is expected the existing run configuration be preserved and edited. Test Steps: 1. Run iOS Device from Run Icon and deploy. 2. Inspect Run Configurations... to verify Run Configuration exists. 3. Run iOS Device from Run Icon again, edit a value in the launch menu, and deploy. 3. Inspect Run Configurations... to verify Run Configuration exists (with edits). Current Behavior: A new run configuration was created based on the edits in the launch menu. Expected Result: The same run configuration exists with new edits applied.
| 8 |
1,197 |
TISTUD-3880
|
03/21/2013 00:59:40
|
Code Processor: View Current Results displays results from other projects
|
Code Processor: View Current Results displays results from other projects. This is an edge-case where if the project has the same name as a previously existing project, the results from the old project are erroneously displayed. Test Steps: 1. Create Appcelerator Project with specific name and app id. 2. Run Code Processor. 3. Delete project from disk. 4. Create Appcelerator Project with identical name and app id. 5. Invoke Code Processor > Display Current Results. Current Behavior: Results appear, though the code processor has never been run on this project.
| 5 |
1,198 |
TISTUD-3889
|
03/21/2013 19:48:26
|
Titanium Project: new project that includes blackberry target uses legacy python script
|
Titanium Project: new project that includes blackberry target uses legacy python script. If a new Titanium Project is created, and BlackBerry is included as a selected deployment target, the old python creation script will be called instead of the standard CLI script. Project Creation Script Overview: {code} "/usr/bin/python" "/Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.1.0.v20130320145648/project.py" "BlackBerryOnly" "com.blackberryonly" "/Users/dhyde/Desktop/tistud/tistud-nightly/workspace" "blackberry" "--blackberry_ndk" "/Users/dhyde/Desktop/blackberry/blackberry-sdk" "/usr/bin/python" "/Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.1.0.v20130320145648/project.py" "AllPlatforms" "com.allplatforms" "/Users/dhyde/Desktop/tistud/tistud-nightly/workspace" "iphone" "android" "mobileweb" "tizen" "/Users/dhyde/Desktop/android/android-sdk" "blackberry" "--blackberry_ndk" "/Users/dhyde/Desktop/blackberry/blackberry-sdk" "/usr/bin/python" "/Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.1.0.v20130320145648/project.py" "AllPlatformsExceptAndroid" "com.allplatformsexceptandroid" "/Users/dhyde/Desktop/tistud/tistud-nightly/workspace" "iphone" "mobileweb" "tizen" "blackberry" "--blackberry_ndk" "/Users/dhyde/Desktop/blackberry/blackberry-sdk" "/usr/local/bin/titanium" "create" "--platforms" "android" "--type" "app" "--id" "com.androidonly" "--sdk" "3.1.0.v20130320145648" "--workspace-dir" "/Users/dhyde/Desktop/tistud/tistud-nightly/workspace" "--name" "AndroidOnly" "--verbose" "--force" "--no-colors" "--no-prompt" "--no-banner" "/usr/local/bin/titanium" "create" "--platforms" "iphone" "--type" "app" "--id" "com.iphoneonly" "--sdk" "3.1.0.v20130320145648" "--workspace-dir" "/Users/dhyde/Desktop/tistud/tistud-nightly/workspace" "--name" "iPhoneOnly" "--verbose" "--force" "--no-colors" "--no-prompt" "--no-banner" "/usr/local/bin/titanium" "create" "--platforms" "tizen" "--type" "app" "--id" "com.tizenonly" "--sdk" "3.1.0.v20130320145648" "--workspace-dir" "/Users/dhyde/Desktop/tistud/tistud-nightly/workspace" "--name" "TizenOnly" "--verbose" "--force" "--no-colors" "--no-prompt" "--no-banner" "/usr/local/bin/titanium" "create" "--platforms" "ipad" "--type" "app" "--id" "com.ipadonly" "--sdk" "3.1.0.v20130320145648" "--workspace-dir" "/Users/dhyde/Desktop/tistud/tistud-nightly/workspace" "--name" "iPadOnly" "--verbose" "--force" "--no-colors" "--no-prompt" "--no-banner" "/usr/local/bin/titanium" "create" "--platforms" "mobileweb" "--type" "app" "--id" "com.mobilewebonly" "--sdk" "3.1.0.v20130320145648" "--workspace-dir" "/Users/dhyde/Desktop/tistud/tistud-nightly/workspace" "--name" "MobileWebOnly" "--verbose" "--force" "--no-colors" "--no-prompt" "--no-banner" "/usr/local/bin/titanium" "create" "--platforms" "ios,android,mobileweb,tizen" "--type" "app" "--id" "com.allplatformsexceptblackberry" "--sdk" "3.1.0.v20130320145648" "--workspace-dir" "/Users/dhyde/Desktop/tistud/tistud-nightly/workspace" "--name" "AllPlatformsExceptBlackBerry" "--verbose" "--force" "--no-colors" "--no-prompt" "--no-banner" {code} Test Steps: 1. Verify BlackBerry is Installed. 2. Create Titanium Project (all deployment targets, including blackberry). Current Behavior: Python script is called. Expected Result: CLI script is called.
| 3 |
1,199 |
TISTUD-3895
|
03/21/2013 22:37:31
|
Platform supported icons are no longer visible in content assistance
|
h5. Problem description In the content assistance popup, icons showing supported platforms (iOS, Android...etc) for the specific API are no longer present. See screenshot attached.
| 5 |
1,200 |
TISTUD-3901
|
03/22/2013 00:18:03
|
Studio: Code changes in app.js are not being reflected in simulator
|
While running app on simulator I encountered this issue. When changes in JS code are made to app.js, they were not reflected in the simulator. Only deleting the project's build folder or cleaning project applies changes. Test steps: 1. Run the following code in the simulator {code} var win = Ti.UI.createWindow({ backgroundColor:"green" }); var button = Ti.UI.createButton({ title:"click me" }); var Cloud = require('ti.cloud'); button.addEventListener("click", function() { Ti.API.info('click fired'); Cloud.Users.login({ login : 'user', password : 'password' }, function(e) { if (e.success) { alert('worked'); } else { alert('error'); Ti.API.info(e.message); } }); }); win.add(button); win.open(); {code} 2. Change the following backgroundColor:"green" to backgroundColor:"blue" 3. Run the app in simulator again without cleaning Actual result: 1. Screen is green 3. Screen is green Expected result: 1. Screen should be green 2. Screen should be blue Also we were able to reproduce this issue using an Alloy project and Studio. Building using CLI from the terminal works as expected. The environment: 1) TiStudio: 3.1.0.201303202340 TiSDK: 3.1.0.v20130319125050 TiCLI: CLI version 3.0.24 Node version: 0.8.17 Alloy: 1.1.0 2) TiStudio: 3.1.0.201303202340 TiSDK: 3.1.0.v20130321105651 TiCLI: CLI version 3.0.25 Node: 0.8.17 Alloy: 1.1.0
| 5 |
1,201 |
TISTUD-3918
|
03/23/2013 22:52:44
|
Tizen app fails to run on emulator at first launch
|
Studio fails to launch tizen app on the emulator/device for the first time the machine is started. When sdb devices command is invoked for first time, it starts the daemon server and it outputs additional lines before listing the running emulator/device instances.
| 8 |
1,202 |
TISTUD-3931
|
03/25/2013 19:13:03
|
Tizen : Running the same app second time throws errors & all clears all fields in tiapp.xml overview
|
Description: 1.Follow the setup instructions on the preview page & do the tizen setup 2.Launch an instance of the emulator 3.Create an app with tizen as target 4.Run on emulator 5.After the first run, run the same app again on the emulator Actual results 1.It throws error Please refer the attached screenshots for the error 2.We cannot use the same app again,we have to create a new app.basically it makes the app useless Expected Results: 1.The same app should run again in the emulator
| 8 |
1,203 |
TISTUD-3942
|
03/26/2013 23:20:19
|
If the Titanium update dialog pops up while a system dialog is displayed, Studio is locked
|
This is related to the deadlock we've seen with showing a Dialog from the background thread while a system dialog is shown. 1. In Studio, select Help->Check for Studio updates 2. Quickly select the File>Open File... menu 3. Leave the file browser open. Wait for the Studio Updates dialog to appear Expected: The Studio updates dialog appears and is actionable Actual: The Studio updates dialog appears and is not dismissible. Neither is the File browser window
| 5 |
1,204 |
TISTUD-3949
|
03/27/2013 20:18:49
|
TiApp Overview editor still shows error after the tiapp source was corrected
|
Steps to reproduce: 1. Create a mobile project; 2. Open the tiapp.xml and switch to source view; 3. Add the following block after <mobileweb></mobileweb>: {code} <tizen appid="knx3nUT6zF"> <tizen:privilege name="http://tizen.org/privilege/application.launch"/> <access origin="*" subdomains="true"/> </tizen> {code} 4. Switch to the Overview tab and verify that it shows the error at the top correctly and all the fields are empty; 5. Switch back to the source tab and remove the added block; 6. Switch back to the Overview tab again. Expected result: the fields are filled and enabled, and the error disappears. Actual result: the fields are filled and enabled, but the error persists. Closing the editor and reopen fixed the issue.
| 3 |
1,205 |
TISTUD-3953
|
03/27/2013 22:20:21
|
BlackBerry: simulator run config lists BlackBerry SDK instead of BlackBerry NDK
|
BlackBerry: simulator run config lists BlackBerry SDK instead of BlackBerry NDK. Preferences list NDK, run config lists SDK. BlackBerry website calls it NDK in the URL and Native SDK everywhere else. Either way we need to be consistent. See screenshots. Test Steps: 1. Preferences > Studio > Platforms > BlackBerry. Expected Result: reference to BlackBerry NDK 2. Run Configurations... BlackBerry Simulator. Expected Result: reference to BlackBerry NDK. Actual Result: reference to BlackBerry SDK.
| 3 |
1,206 |
TISTUD-3954
|
03/27/2013 22:26:06
|
BlackBerry: Packager run configuration Revert not activated by project name field edit
|
BlackBerry: run configuration Revert not activated by project name field edit. Test Steps: 1. Run Configurations... BlackBerry Packager. 2. Edit Run Config project name. Expected Result: Revert button becomes activated, clicking Revert reverts changes to project name. Actual Result: Revert button does not become activated. Revert does not work.
| 3 |
1,207 |
TISTUD-3958
|
03/27/2013 22:51:26
|
BlackBerry: device run config password and token field edits do not Revert
|
BlackBerry: device run config password and token field edits do not Revert. See screenshot. Test Steps: 1. Run Configurations... BlackBerry Device. 2. Edit Password and Token fields. 3. Press Revert. Actual Result: Nothing happens.
| 3 |
1,208 |
TISTUD-3962
|
03/28/2013 00:45:14
|
Rename "Password Help" link in the splash screen to "Forgot Password"
|
The "Password Help" link opens the page to reset the password, so the text should be renamed to a more standard "Forgot Password".
| 1 |
1,209 |
TISTUD-3963
|
03/28/2013 00:49:37
|
Improve the error message when login failed
|
Login splash error should state "Sign in" failed, not "Logging in" failed.
| 2 |
1,210 |
TISTUD-3964
|
03/28/2013 00:54:57
|
Re-order the Test items under the main Run menu
|
The order should be Run, Debug, Profile, Test. The Profile and Test contributions should occur after the "Inspect" and "Watch" groups.
| 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.