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
|
|---|---|---|---|---|---|
311 |
TISTUD-1485
|
04/03/2012 13:57:03
|
Update sites for Openshift/TestFlight should not contain both plugin and feature node
|
When we install from an update site using the result from the TestFlight and Openshift builds, the categorized nodes are the plugin and the feature nodes. Typically it should just contain the Feature install, which would pull in the plugin as part of it. In this case, if we check just the feature and not the plugin, the install is an invalid one, resulting in an invalid install.
| 8 |
312 |
TISTUD-1489
|
04/04/2012 08:37:39
|
Update IPublishType.publish() method to explicitly pass in PlatformType, output location and publish target
|
For clarity, we should pass in the parameters we know about explicitly - Publish target, platform type, and output location.
| 5 |
313 |
TISTUD-1490
|
04/04/2012 11:46:46
|
Titanium Studio: SDK: updating to readonly sdk folder gives no such directory error
|
When updating SDK to an SDK folder with readonly access, a directory not found error is presented (instead of invalid permissions). Steps to Reproduce: 1. Change the permissions of the Titanium SDK folder to readonly (e.g., folder right click -> properties -> permissions, etc.). 2. Update the SDK to a different version. Update Option 1: Go to http://builds.appcelerator.com.s3.amazonaws.com/index.html, copy an SDK location. Go to Studio: Help -> Install Titanium SDK From URL, paste the link, update. Update Option 2: Remove the last live version of the SDK from the SDK folder. Go to Studio: Help -> Check For Titanium SDK Updates. Expected Result: There should be an error indicating the SDK folder does not have write permissions. Actual Result: Directory not found error.
| 5 |
314 |
TISTUD-1494
|
04/04/2012 16:47:35
|
Building for iOS device in Studio 2.0 against SDK 2.0.0GA (Ad-Hoc certs and PUSH issues)
|
when I build for an iOS Device Xcode bounces in the dock for nearly a minute before it will unlock beachball and allow me to make a selection, it happens once before the first window shows and then once again before build. If I select Manage option - this whole Xcode bouncing in the dock repeatedly (like its loading and quitting again and again) happens ... its very slow. Compared to 1.x Studio which is much faster. The preselected provisioning profiles is not clear, and somehow I managed to build against an ad-hoc certificate, i did not consciously choose this) but it caused my Push Notification Process to throw up errors. I tried 2 possible certs that were available to me and both times it must have used an ad-hoc certificate. I went back to 1.x and rebuilt it. I preferred the ability to remove and add certificates manually at this stage. Always avoided confusion for me.
| 8 |
315 |
TISTUD-1496
|
04/05/2012 11:21:47
|
Trailing semicolon after curly brace in conditional causes error in JS formatting
|
Steps to reproduce: 1. Create a new .js file in a project 2. Copy the following code and paste it into the .js file {code} if ( i == _i) {} else {}; {code} 3. Press command+shift+f on mac to format the pasted code Actual result: The following error is generated in the log file: !ENTRY com.aptana.formatter.epl 4 0 2012-04-05 11:14:39.664 !MESSAGE (Build 3.0.0.1332346356) [ERROR] com.aptana.formatter.epl/debug Error while formatting the code in your editor. Please submit a bug report through Studio's support and include the relevant code which triggered this error. Expected result: The code is formatted correctly. It appears to be that last trailing semicolon. Delete that, and it works.
| 5 |
316 |
TISTUD-1497
|
04/05/2012 14:17:39
|
Studio displays iOS ad hoc provisioning profiles as "development" when it should be "distribution"
|
Studio displays Ad hoc provisioning profiles incorrectly as "development". This causes confusion in the following areas: -Preferences displays the displays the type incorrectly -The iOS distribution wizard displays Apple iTunes, Ad hoc, and development profiles (should only display Apple iTunes and Ad hoc profiles) -The iOS Run on device wizard displays Apple iTunes, Ad hoc, and development profiles (should only display development profiles) Special attention must be made to the way we cache provisioning profiles, since a fix to the SDK will not update the "type" of the cached provisioning profiles. We have to trigger a flush of the cache if there is a presence of SDK 2.2.0, where previously there wasn't. This is blocked by an SDK bug
| 8 |
317 |
TISTUD-1503
|
04/06/2012 12:16:36
|
Fix padding on release notes dialog
|
The current release notes template is very specific about what content it expects to style. However, this can lead to release notes not having any padding around the edge of the content. Recommend adjusting the styling slightly to accommodate.
| 3 |
318 |
TISTUD-1506
|
04/10/2012 13:12:19
|
Titanium Studio: Configuration: Preferences > Titanium Studio > Titanium freezes studio
|
Navigating to Preferences > Titanium Studio > Titanium freezes studio. This does not occur in the last studio build. Regression. Steps to Reproduce: 1. Open Studio. 2. Navigate to Preferences > Titanium Studio > Titanium. Expected Result: Titanium Preferences should open. Actual Result: Studio freezes, need to force-close.
| 8 |
319 |
TISTUD-1507
|
04/10/2012 14:54:27
|
Error opening the Titanium preferences when the Desktop SDK is incomplete
|
An attached log to TISTUD-1506 revealed this problem. {code} !ENTRY org.eclipse.jface 4 2 2012-04-10 12:55:28.904\ !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".\ !STACK 0\ java.lang.NullPointerException\ at com.appcelerator.titanium.desktop.DesktopSDKEntity.setModules(DesktopSDKEntity.java:54)\ at com.appcelerator.titanium.desktop.DesktopSDKEntity.<init>(DesktopSDKEntity.java:39)\ at com.appcelerator.titanium.desktop.TitaniumDesktopSDKLocator.initialize(TitaniumDesktopSDKLocator.java:169)\ at com.appcelerator.titanium.desktop.TitaniumDesktopSDKLocator.<init>(TitaniumDesktopSDKLocator.java:52)\ at com.appcelerator.titanium.ui.preferences.TitaniumSDKDirectoryFieldEditor.doCheckState(TitaniumSDKDirectoryFieldEditor.java:94)\ at org.eclipse.jface.preference.StringFieldEditor.checkState(StringFieldEditor.java:193)\ at org.eclipse.jface.preference.StringFieldEditor.refreshValidState(StringFieldEditor.java:409)\ at org.eclipse.jface.preference.FieldEditor.load(FieldEditor.java:501)\ at org.eclipse.jface.preference.FieldEditorPreferencePage.initialize(FieldEditorPreferencePage.java:307)\ at org.eclipse.jface.preference.FieldEditorPreferencePage.createContents(FieldEditorPreferencePage.java:233)\ at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232)\ at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501)\ at org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258)\ at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)\ at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)\ at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)\ at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252)\ at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:674)\ at org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708)\ at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)\ at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704)\ at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:888)\ at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)\ at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)\ at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)\ at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:886)\ at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1226)\ at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1251)\ at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:262)\ at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:256)\ at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:433)\ 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:3938)\ at org.eclipse.swt.widgets.Display.observerProc(Display.java:3525)\ at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879)\ at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226)\ at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220)\ at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1092)\ at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2052)\ at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1084)\ at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2528)\ at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2007)\ at org.eclipse.swt.widgets.Display.windowProc(Display.java:5471)\ at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220)\ at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095)\ at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253)\ at org.eclipse.swt.widgets.Display.windowProc(Display.java:5535)\ at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989)\ at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138)\ 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:3610)\ at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)\ at org.eclipse.jface.window.Window.open(Window.java:801)\ at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215)\ at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54)\ at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)\ at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)\ at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:178)\ at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runCommand(CocoaUIEnhancer.java:393)\ at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:535)\ at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:520)\ at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879)\ at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226)\ at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)\ at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94)\ at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3607)\ 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 |
320 |
TISTUD-1510
|
04/11/2012 09:09:35
|
Run iOS preference page loading in the background
|
See parent
| 8 |
321 |
TISTUD-1513
|
04/11/2012 11:38:59
|
TiStudio: Mobile Projects - When creating mobile projects offline, two projects with same guid will sporadically be created in my.appcelerator.com/apps site
|
Steps to reproduce: 1. Launch Studio with internet connection disabled 2. Create a TiMobile project 3. Relaunch Studio with internet connection enabled 4. Check https://my.appcelerator.com/apps *May need to repeat steps 1 - 4 a couple of times* Actual: Two projects with the same guid are created in my.appcelerator.com/apps site. See attachments. Expected: One project should be created at my.appcelerator.com/apps site *Note:* * Bug not reproducible on Titanium Studio, build: 2.0.0 and 1.0.9 * Bug not reproducible on Windows 7 machine * Bug not reproducible when working from home
| 8 |
322 |
TISTUD-1514
|
04/11/2012 17:29:43
|
TiStud: Workspace - When switching workspaces from within TiStudio, TiStudio will not launch
|
Steps to reproduce: 1. Launch TiStudio 2. Go to File > Switch Workspace 3. Select a different workspace Actual: TiStudio will stay stuck at the log in/splash screen. See attachments. Expected: Should be able to launch TiStudio after switching to different workspace Note: Bug does *not* occur on Windows 7 and Lion (10.7.3)
| 13 |
323 |
TISTUD-1515
|
04/12/2012 10:59:29
|
Blocker: Android : Templates : SingleWindow - After creating an Android only single window template a null pointer exception occurred when launching to the emulator
|
Steps to reproduce: 1. Create a Android only single window application 2. Launch on the Emulator Actual result: A null pointer error occurs *Note* This occurred consistently, then I cleared out my avds and sdcards and the issue went away Here is the output to the log {code} !ENTRY org.eclipse.core.jobs 4 2 2012-04-11 16:45:17.583 !MESSAGE An internal error occurred during: "Launching Titanium Android Emulator - singleAnd". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.mobile.launching.FastDevLaunchConfigurationDelegate$1.terminate(FastDevLaunchConfigurationDelegate.java:56) at org.eclipse.debug.core.Launch.terminate(Launch.java:252) at com.appcelerator.titanium.core.launching.AbstractSharedProcessLaunch.findOrLaunch(AbstractSharedProcessLaunch.java:170) at com.appcelerator.titanium.core.launching.AbstractSharedProcessLaunch.launch(AbstractSharedProcessLaunch.java:92) at com.appcelerator.titanium.mobile.android.launching.AndroidSimulatorLaunchConfigurationDelegate.launch(AndroidSimulatorLaunchConfigurationDelegate.java:182) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} *Screenshot attached* Expected result: The app is launched to the simulator
| 5 |
324 |
TISTUD-1516
|
04/12/2012 14:34:34
|
Titanium Studio RCP contains JDT plugins
|
I was trying to verify TISTUD-1442 and found out that I do have JDT plugins in my standalone by default. This is almost a clone of APSTUD-1378 (but this is for Titanium standalone).
| 13 |
325 |
TISTUD-1517
|
04/12/2012 14:44:08
|
ClassCastException when opening the index.html of a packaged mobile web project
|
Running from a dev workspace with latest code in the release branch: 1. Created a Titanium Mobile project with Mobile Web selected as one of the deployment targets; 2. Run Publish > Package Mobile Web and select to create a new project for the Mobile Web app; 3. Open the index.html file from the packaged mobile web project. Actual result: the following exception is generated in the console: {code} Exception in thread "com.aptana.editor.common.text.reconciler.CommonReconciler" java.lang.ClassCastException: com.aptana.editor.js.parsing.ast.JSAssignmentNode cannot be cast to com.aptana.editor.html.parsing.ast.HTMLElementNode at com.aptana.editor.html.validator.HTMLTidyValidator.handleNode(HTMLTidyValidator.java:400) at com.aptana.editor.html.validator.HTMLTidyValidator.access$0(HTMLTidyValidator.java:394) at com.aptana.editor.html.validator.HTMLTidyValidator$1.include(HTMLTidyValidator.java:386) at com.aptana.editor.html.validator.HTMLTidyValidator$1.include(HTMLTidyValidator.java:1) at com.aptana.parsing.util.ParseUtil.treeApply(ParseUtil.java:155) at com.aptana.parsing.util.ParseUtil.treeApply(ParseUtil.java:121) at com.aptana.editor.html.validator.HTMLTidyValidator.validateAST(HTMLTidyValidator.java:382) at com.aptana.editor.html.validator.HTMLTidyValidator.buildFile(HTMLTidyValidator.java:164) at com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) at com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.runParticipants(CommonReconcilingStrategy.java:277) at com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:238) at com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:205) at com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.initialReconcile(CommonReconcilingStrategy.java:137) at com.aptana.editor.common.text.reconciler.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:113) at com.aptana.editor.common.text.reconciler.CommonReconciler.initialProcess(CommonReconciler.java:188) at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173) {code} Expected result: no exception occurs.
| 3 |
326 |
TISTUD-1518
|
04/12/2012 14:44:55
|
TiStudio: Dashboard - Drop down does not refresh properly when trying to "Create new project" template
|
Steps to reproduce: 1. Launch TiStudio 2. In Dashboard, go to Develop tab 3. Under Templates, find *Create new project* 4. Hover above drop down Actual: Drop down does not appear. Need to move mouse down to refresh properly. See no_drop_down.png Expected: Drop down should immediately display *Desktop* and *Mobile*. See drop_down.png Notes: Bug does *not* appear on Lion (10.7.3) and Windows 7
| 8 |
327 |
TISTUD-1522
|
04/13/2012 13:38:11
|
Android and iOS module packagers have launch configuration types but no tab group defined
|
When opening "Run Configuration..." dialog, we see Android Module Packager and iOS Module Packager in the list, but double-clicking on them causes an error showing there is no corresponding tab group defined.
| 13 |
328 |
TISTUD-1523
|
04/16/2012 09:48:44
|
Fail Jenkins build if Studio contains JDT plugins
|
As a way of keeping ourselves from accidentally releasing JDT into the wild as part of Studio, we need to fail the Aptana Studio and Titanium Studio builds if either the plugin or standalone versions come packaged with the JDT plugins. This prevents half-baked JDT installs which hen keep a user from later installing the whole JDT proper for module development.
| 8 |
329 |
TISTUD-1525
|
04/17/2012 00:36:05
|
Unable to click on anchor links in release notes
|
# Delete SDK 2.0.1.GA. # Prompt for SDK updates # When the release notes pop up, click on an anchor # View the log file. You'll see a set of errors like: {code} !ENTRY com.aptana.ui 4 0 2012-04-16 23:23:49.344 !MESSAGE (Build 3.0.3.1331579821) [ERROR] unknown protocol: about !STACK 0 java.net.MalformedURLException: unknown protocol: about at java.net.URL.<init>(URL.java:574) at java.net.URL.<init>(URL.java:464) at java.net.URL.<init>(URL.java:413) at com.aptana.ui.util.WorkbenchBrowserUtil.launchExternalBrowser(WorkbenchBrowserUtil.java:35) at com.appcelerator.titanium.update.ui.TitaniumSDKReleaseNotesDialog$2.changing(TitaniumSDKReleaseNotesDialog.java:191) at org.eclipse.swt.browser.WebKit.webView_decidePolicyForNavigationAction_request_frame_decisionListener(WebKit.java:1493) at org.eclipse.swt.browser.WebKit.browserProc(WebKit.java:423) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) 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:3610) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334) at com.appcelerator.titanium.update.handler.TitaniumUpdateHandler.execute(TitaniumUpdateHandler.java:30) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) 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} It appears that the anchors are showing as file:///#viewtypes
| 5 |
330 |
TISTUD-1528
|
04/17/2012 16:14:36
|
TiStudio: Preview Site - At Titanium Studio preview site, the builds are skewed to the right
|
Environment: FireFox, Chrome, and Safari Steps to reproduce: 1. Go to http://preview.appcelerator.com/studio/ Actual: Notice the Studio builds are skewed to the right. See attachment. Expected: The Studio builds should be properly aligned.
| 3 |
331 |
TISTUD-1527
|
04/17/2012 16:24:10
|
Titanium Studio: Dashboard: Search and Top Ad open in generic browser with no controls
|
Using the dashboard search bar or the top ad link ("Reach 1.5 Million Appcelerator Developers") launches in a generic browser with no controls, providing difficult navigation. To address this, we'll need to switch the code that launches the browser in this case to be the same as the other cases on the dashboard (all other links open an external browser, and that appears to work correctly). it's a matter of triggering a portal action instead of using target="_new" as part of the href.
| 8 |
332 |
TISTUD-1529
|
04/17/2012 16:51:54
|
Studio will start updating the SDK automatically upon launch without showing there is an update available first
|
To reproduce: 1. Remove the latest SDK from the mobile SDK directory if it is already downloaded; 2. Start Studio. Expected result: Studio will show a popup on the lower right corner indicating there is an update available, and clicking on it will show a release note dialog and then start downloading the latest SDK. Actual result: Studio will start downloading the latest SDK right away after launching without any user interaction, and no release note dialog is shown.
| 8 |
333 |
TISTUD-1530
|
04/17/2012 17:29:43
|
Success dialog closes immediately after Titanium SDK update
|
Steps to repro: 1. Launch studio, and update to the latest sdk (remove the latest sdk if necessary first) 2. Wait for the sdk to download and unzip. Expected result: There should be a success dialog at the end of the unzip process which stays on the screen until the user presses OK Actual result: The success dialog quickly appears and then disappears with the progress bar.
| 3 |
334 |
TISTUD-1534
|
04/17/2012 19:08:50
|
Titanium Studio: Configuration: Preferences > Titanium Studio > Titanium > Default Android SDK inconsistently sorted
|
The Android APIs listed in the preferences are not sorted as they are in the run configurations. Screenshots attached. Steps to Reproduce: 1. In Studio, navigate to Preferences > Titanium Studio > Titanium > Default Android SDK. 2. View the sorting of the Android APIs. Expected: The APIs in the preferences are expected to look as they do in the run configurations, as the run configuration sorting looks more orderly. Actual: The preferences APIs are sorted in a way that is inconsistent with the run configurations and is visually confusing.
| 3 |
335 |
TISTUD-1537
|
04/18/2012 05:02:28
|
Every time you click 'Enable' for 'Enable Cloud Services' a new app gets created
|
In TiStudio open the tiapp.xml file of an app with the 2.0.1 GA, and click 'Enable'. An app is created in the cloud services. Click it again and another app is created... Suggested fix: # Check to see if the file is dirty. If yes, alert the user that enabling cloud services will save the file. They can then choose to proceed, or click cancel. # Enable cloud services. # Save the file.
| 5 |
336 |
TISTUD-1538
|
04/18/2012 09:44:54
|
Preview button in global toolbar is invisible
|
When attempting to verify TISTUD-1381, I noticed the Preview button in the global toolbar was invisible.
| 0 |
337 |
TISTUD-1539
|
04/18/2012 09:51:53
|
Dashboard's "Develop" tab missing content
|
After upgrading to version 2.0.2.201204171552 from version 2.0.1.201204132053 the develop tab on the dashboard no longer has any samples listed and only one template option. This does not occur in 2.0.1. Regression. Steps to reproduce: 1. Load Titanium Studio. 2. Load the Dashboard. 3. Click the develop tab. Expected Result: The develop page of the dashboard should contain links to samples and templates for developers. Actual Results: The develop page contains only a single template and no samples.
| 8 |
338 |
TISTUD-1540
|
04/18/2012 09:53:01
|
Titanium API not showing up at all in CA of a newly created project if "Build Automatically" is turned off
|
If I create a new mobile project, I don't get Titanium or Ti in my CA at all. I need to right-click on project, go to Prioperties > Project Build Path, change the Titanium API, then change back to the original one I wanted (say from 2.0.1GA2 to 1.8.2, click Ok, then go back and change back to 2.0.1GA2).
| 8 |
339 |
TISTUD-1543
|
04/18/2012 11:45:12
|
TiStudio: Dashboard - "API Docs" does not take you to the API documentation site
|
Steps to reproduce: 1. Open TiStudio 2. In the dashboard, click on *API Docs* Actual: Link takes you to http://docs.appcelerator.com/titanium/2.0/index.html Expected: Link should take you to http://docs.appcelerator.com/titanium/2.0/index.html#!/api Note: Not a regression.
| 8 |
340 |
TISTUD-1545
|
04/18/2012 14:17:13
|
Fail Titanium Studio build if titanium.core plugin is missing rubles
|
based on TISTUD-1539, we should fail the build if the Titanium Rubles fail to package. One suggested approach is to copy the plugin, unzip it and manually check for the bundles and fail if they're not there.
| 8 |
341 |
TISTUD-1546
|
04/18/2012 14:23:35
|
Installer: The link to the software licence agreement does not work.
|
The link to the Software licence agreement does not open the licence agreement when clicked. This did not happen in the 2.0.0 installer. Not regression as this functionality is new. Steps to reproduce: 1. Download and run the installer. 2. When prompted for the licence agreement click the link. Expected Results: The licence agreement will open in another window for reading. Actual Results: Nothing happens.
| 8 |
342 |
TISTUD-1549
|
04/19/2012 12:35:49
|
Titanium Studio: Content Assist - content assist menu persistent in the OS if popup info has focus
|
Content Assist menu is persistent in the OS if the assist popup info menu has focus (i.e., by clicking on it). Other OS program windows are now obfuscated by the content assist menu until the focus is shifted back to Titanium Studio proper or the regular content assist menu. Screenshot attached. Note: This is a lesser behavior of the fixed TISTUD-913. Steps to Reproduce: 1. Open Studio and create a new project (or open an existing project). 2. Click in the text editor of app.js (or any .js file). 3. Press control + space to bring up the content assist menu. 4. Select any item from the suggestion list by clicking on it. 5. Click on the secondary popup that appears for that particular content assist item. 6. Open any other program (such as Chrome) and move the other program window over the content assist menu. Expected Result: The content assist menu should disappear behind the other program window, as it should have the same OS hierarchy as Titanium Studio. Actual Result: The content assist menu persists and obfuscates the other program window until the focus shifts back to Studio or a regular content assist item.
| 8 |
343 |
TISTUD-1550
|
04/19/2012 13:09:49
|
Titanium Studio: Content Assist: assist menu intermittently fails to change focus
|
The content assist menu will not close at all if the user clicks away. This is intermittent. This is a lesser behavior of TISTUD-1268, which is fixed. Summary of TISTUD-1268: Content assist would intermittently stay open as a stand-alone window until studio was restarted. The TISTUD-1268 fix: If the content assist menu is up, and studio minimizes, the content assist menu will minimize as well. Current Issue: Steps to Reproduce: 1. Open studio, create a new project, or open an existing javascript file. 2. Open content assist. 3. Click away from content assist. Expected Result: Content assist should close. Actual Result: Content assist intermittently stays open and will not close. This window is also persistent in the OS, though that related issue was fixed (TISTUD-913). When studio is minimized, content assist will minimize as well. When studio is maximized, the content assist menu is still there. The only way I could close content assist window was by opening a new content assist window (cntrl + space), which would close the old one, and open a new one which behaves properly.
| 13 |
344 |
TISTUD-1552
|
04/19/2012 16:34:31
|
Add BlackBerry platform support
|
An umbrella feature to encapsulate support for the new QNX-based BlackBerry mobile platform. This platform will have all the same functionality as we would need for iOS and Android: * New project wizard * Launch configurations to run in simulator/emulator * Launch configuration to run in debugger * Module wizard changes * New packaging wizards * Tiapp.xml editor changes ** Deploy target ** SDK version restrictions ** Add platform to modules table ** Validation changes * Icons * Preference pages * Dashboard Configuration Wizard
| 0 |
345 |
TISTUD-1572
|
04/19/2012 16:41:59
|
Unable to format titanium.js file generated by Titanium Mobile Web project
|
The file is generated when you package a Titanium mobile web project as a new project in the workspace. The generated project should have a titanium.js file. When I try to format the file I get the following error: !ENTRY com.aptana.editor.js.formatter 4 0 2012-04-19 15:36:03.866 !MESSAGE (Build 3.0.3.1334796284) [ERROR] com.aptana.formatter.epl/debug Cannot recover from the syntax error !STACK 0 beaver.Parser$Exception: Cannot recover from the syntax error at beaver.Parser.recoverFromError(Parser.java:697) at com.aptana.editor.js.parsing.JSParser.recoverFromError(JSParser.java:623) at beaver.Parser.parse(Parser.java:498) at beaver.Parser.parse(Parser.java:439) at com.aptana.editor.js.parsing.JSParser.parse(JSParser.java:447) at com.aptana.editor.js.formatter.JSFormatter.equalContent(JSFormatter.java:295) at com.aptana.editor.js.formatter.JSFormatter.format(JSFormatter.java:246) at com.aptana.formatter.ScriptFormattingStrategy.doFormat(ScriptFormattingStrategy.java:185) at com.aptana.formatter.ScriptFormattingStrategy$1.run(ScriptFormattingStrategy.java:115) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at com.aptana.formatter.ScriptFormattingStrategy.format(ScriptFormattingStrategy.java:111) at org.eclipse.jface.text.formatter.MultiPassContentFormatter.formatMaster(MultiPassContentFormatter.java:193) at org.eclipse.jface.text.formatter.MultiPassContentFormatter.format(MultiPassContentFormatter.java:135) !ENTRY com.aptana.formatter.epl 4 0 2012-04-19 15:36:03.870 !MESSAGE (Build 3.0.0.1332346421) [ERROR] com.aptana.formatter.epl/debug Error while formatting the code in your editor. Please submit a bug report through Studio's support and include the relevant code which triggered this error.
| 8 |
346 |
TISTUD-1556
|
04/20/2012 16:14:37
|
Titanium Studio: Cloud: enabling app cloud services when offline causes partially blank and inconsistent error messages
|
If the user enables cloud services for an app while offline, one of the error messages is blank, and the others does not explicitly notify that studio is offline. There is also an inconsistency between popup errors generated by the tiapp.xml, and the new project wizard. However, the log messages are (correctly) the same for both enablement methods (tiapp.xml and new project wizard). Screenshots attached. Log attached. Steps to Reproduce: 1. Go offline. 2. Create a new project with cloud services enabled. Expected Result: A standard popup should appear indicating studio is offline and cloud services could not be activated. An error should be logged. Actual Result: A new-project-wizard-specific error popup appears indicating cloud services could not be activated. There is no mention of being offline. An error message is (correctly) logged to the console indicating an http failure. 3. Dismiss the popup and enable cloud services using the tiapp.xml overview. Expected Result: A standard popup should appear indicating studio is offline and cloud services could not be activated. An error should be logged. Actual Result: A different error popup appears with blank text in the "Reason" section. The same console error from before is (correctly) logged.
| 8 |
347 |
TISTUD-1557
|
04/23/2012 16:50:24
|
Editor: JavaScript Comment Auto-Complete indentation is inconsistent
|
If a javascript comment is auto-completed from a closed pair of parenthesis or a closed pair of curly braces, the indentation of the cursor is farther than usual. Screenshots attached. This is a new fail case, as this feature was not implemented in 2.0.1. Steps to Reproduce: 1. Enter javascript code below in editor. {code} function(){} {code} 2. Insert the cursor between the parenthesis and type "/*" and press "enter". For example: {code} function(/*){} {code} Expected Result: Cursor indentation should be one space away from the asterisk to the left. Actual Result: Cursor indentation is a few spaces away from the asterisk.
| 8 |
348 |
TISTUD-1558
|
04/23/2012 16:59:12
|
Titanium Studio: JavaScript Comment Auto-Complete fails if on same line as end of previous comment
|
If a javascript comment is auto-completed from a line that contains the end of another auto-completed comment, the new completion will fail to complete the comment. Screenshots attached. Steps to Reproduce: 1. Enter javascript code in editor: {code} function(){} {code} 2. Insert cursor at the beginning of the line, type "/*", and press enter. For example: {code} /* * */function(){} {code} 3. Insert cursor at the end of the line, type "/*", and press enter. For example: {code} /* * */function(){}/* {code} Expected Result: Auto-completion should succeed, for example: {code} /* * */function(){}/* * */ {code} Actual Result: Auto-complete fails, for example: {code} /* * */function(){}/* * {code}
| 5 |
349 |
TISTUD-1559
|
04/23/2012 18:28:42
|
Titanium Studio: Snow Leopard: Toggle Full Screen menu item exists but is not supported
|
In Titanium Studio, the top menu, Window > Toggle Full Screen exists, but is grey-ed out and non-selectable. Full Screen is not supported on Snow Leopard, only on Lion. Steps to Reproduce: 1. Open Titanium Studio. 2. In the top menu, navigate to the Window drop-down menu. Expected Result: Window > Toggle Full Screen should not exist in the menu on Snow Leopard. Actual Result: Window > Toggle Full Screen exists and is grey/not selectable. Full Screen is not supported on Snow Leopard at this time.
| 3 |
350 |
TISTUD-1560
|
04/23/2012 19:07:26
|
Titanium Studio: Usability: OS X Lion: extra horizontal bar in drop down full screen menu
|
When Titanium Studio is in full screen mode on OS X Lion, and the top drop down menu is active (by moving the cursor near the top), there is an extra horizontal bar below the top menu. Screenshot attached. Steps to Reproduce: 1. Open Titanium Studio in OS X Lion. 2. Go into full screen mode (Window > Toggle Full Screen). 3. Move cursor to top of screen to bring down top menu. Expected Result: The menu should appear with only the menu items. Actual Result: The menu appears, along with a separate empty horizontal bar beneath it.
| 0 |
351 |
TISTUD-1571
|
04/25/2012 15:39:51
|
Titanium Studio: Dashboard: Generic External Browser Crashes Studio on Close
|
In the dashboard, when the ad link at the top is clicked ("Forging Titanium"), and the generic external browser is closed, studio will crash. Log attached. Also occurs in 2.0.1. This has only occurred using the "Forging Titanium" ad. You must refresh the dashboard until this ad appears. This issue is consistently reproducible. This issue affects Windows and Ubuntu, but I could not reproduce on OS X Snow Leopard. Steps to Reproduce: 1. Open Studio. 2. Open the dashboard. 3. Refresh the dashboard (red appcelerator logo) until the "Forging Titanium" ad appears at the top of the dashboard. 4. Click on the link to open a new generic browser with the ad content. 5. Close the browser. Expected Result: The browser should close. Actual Result: Studio hard crashes.
| 13 |
352 |
TISTUD-1574
|
04/26/2012 15:24:25
|
Titanium Studio: Configuration: Ubuntu 11.10: top menu items intermittenly have random order
|
The top menu (File, Edit, Window, etc.) has randomly ordered elements on Ubuntu 11.10 intermittently. This does not occur on Ubuntu 10.04, Snow Leopard, or Windows 7. Screenshots attached. No log. Steps to Reproduce: 1. Open studio. 2. Look at the top menu. Expected Result: Menu items should be consistent. Actual Result: Intermittently, menu items are random, but do change to the correct configuration on a second check.
| 3 |
353 |
TISTUD-1576
|
04/27/2012 17:23:20
|
Unable to package Android module on OSX
|
Prereqs Install Android SDK Install Android NDK Update settings in Titanium preferences Steps: 1. Create an android module project 2. Package the module Expected results Module is packaged Actual results: NPE in the AntRunner and this following error (Build 1.0.0.qualifier) [ERROR] /Users/nle/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.v20120410131722/module/android/build.xml:228: exec returned: 2 org.eclipse.core.runtime.CoreException: /Users/nle/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.v20120410131722/module/android/build.xml:228: exec returned: 2 at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:452) at org.eclipse.ant.core.AntRunner.run(AntRunner.java:384) at com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate$PackagingProcess$1.run(AndroidModulePackageLaunchConfigurationDelegate.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: /Users/nle/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.v20120410131722/module/android/build.xml:228: exec returned: 2 at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:636) at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:662) at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:487) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:662) at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:495) 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.ant.core.AntRunner.run(AntRunner.java:378)
| 13 |
354 |
TISTUD-1578
|
04/29/2012 23:19:47
|
Display list of currently installed modules in Studio Dashboard
|
Similar to https://marketplace.appcelerator.com/myapps and the Explore tab of the dashboard (attached as a screenshot) * Shows me all modules I have available, broken into several groups or states (see iPhone App Store UI for possible ideas on this) ** Installed and up-to-date ** Installed, but out of date and needs to be updated ** Purchased/available, but not installed on this machine Information for each module: * The version available for update * The date of the last update available * Some information about the update * An icon for each module Behaviors/Notes: * We auto-check for updates when switching to the tab, but we also have a manual "check" button * The width of the screen should match the explore tab size. The height can scroll (but important info should be at the top) * Preferably, this would be another state of the Explore tab (similar to switching between shopping for modules, and then managing your purchases). If this isn't possible, we could add another tab to the existing dashboard, or perhaps add it to the "Configure" tab).
| 0 |
355 |
TISTUD-1579
|
04/29/2012 23:21:21
|
Given a URL to a module ZIP file, install the newer version
|
Add a dashboard controller when given the URL to a module .zip file, installs the module to the SDK location on disk. * Allow the user to choose either a global install, or a per-project install. * If for a specific project, update the tiapp.xml file (equivalent to what we do now when packaging a module for local distribution)
| 13 |
356 |
TISTUD-1581
|
04/29/2012 23:30:33
|
Add support for launching BlackBerry debugger
|
The new Blackberry simulator utilizes a VMWare appliance. We'll need to launch against that. Improvements: # Add IP address override to launch configuration (see TISTUD-1597 for root IP specification) # Add password override to launch configuration (see TISTUD-1597 as well) Steps to use the integration: # Launch VMWare Device # Find out IP of device. User enters this in the main preference page, or in the launch configuration # Run launch script, passing in IP address, password as arguments: {panel} --ip_address=<address> # required --device_password=<password> # optional, for password-protected devices {panel}
| 20 |
357 |
TISTUD-1583
|
04/29/2012 23:54:58
|
Update Studio to support new command-line SDK
|
Linked to TIMOB-8662 (and blocked on that), once platform has decided on a new CLI, we will need to add support for this new model. * There may be a change in technology (Python 3.0 and Node.js have been discussed) * This command-line will only work on newer 2.1+ versions of the SDK, so we have to support the old model for some time * Perhaps convert current calls to use a template style to make future changes easier
| 0 |
358 |
TISTUD-1588
|
04/30/2012 00:52:22
|
Create Mockup of new Studio Dashboard
|
This incorporates the new configuration tab, allowing users to choose between a "simple" and "advanced" perspective.
| 8 |
359 |
TISTUD-1594
|
05/01/2012 12:39:47
|
Upgrade Module wizard to support BlackBerry projects
|
Similar to other platforms, support the creation of BlackBerry modules. We don't yet know exactly the steps involved.
| 8 |
360 |
TISTUD-1599
|
05/01/2012 12:54:53
|
Add BlackBerry platform to Dashboard configuration screen
|
# Add the path to the simulator to the BlackBerry preference screen # Update the sdk_info.json with links to the blackberry NDK download and simulator downloads (https://bdsc.webapps.blackberry.com/native/download) # Upgrade the configuration code to look for those two preferences # Upgrade the configuration UI (similar to iOS) to alert the user where and how to download them if they aren't set
| 0 |
361 |
TISTUD-1605
|
05/02/2012 08:13:19
|
Javascript preview code doesn't include "other parentheses" example code
|
1. Open Preferences > Studio > Formatter 2. Select javascript on the left of the pref page 3. Click the pencil icon to edit the profile 4. Select the "Spaces" tab The preview block of code doesn't seem to have any examples of the "Other parentheses" code, since changing those values don't seem to have any effect.
| 2 |
362 |
TISTUD-1610
|
05/04/2012 08:35:27
|
Add a Preference page to manage Keystore certificates
|
We should adopt the Adobe AIR certificate management UI. See attached for Adobe AIR cert. management UI in Studio 1.5 (we can probably reuse this code) There should be a new Android preference page (similar to iOS), that contains a table of current keystore certificates, and an Add and Remove buttons
| 13 |
363 |
TISTUD-1611
|
05/04/2012 08:36:22
|
Update the existing keystore dialog to allow users to either specify an existing keystore or create a new one
|
Add radio buttons to the dialog that allows the user to specify either an existing keystore from the disk or adding a new one. If an existing one is selected, we need to have a password field but not others.
| 8 |
364 |
TISTUD-1612
|
05/04/2012 08:37:20
|
Update the Android distribution wizard/launch configuration to allow user to pick from the existing list of certificates (combo box), or to create a new one
|
-Replace the textbox with a combo box that contains the list of keystore certificates -The certificate added from the Browse button should automatically add the certificate to the list -New button will trigger the same keystore dialog as before
| 8 |
365 |
TISTUD-1613
|
05/04/2012 09:07:46
|
Allow user to register their GitHub account inside Studio
|
I would like to be able to log in to my Github account and save my account information, possibly in our new "Accounts" preference page. Store: * Username * Password Additional buttons/links: * Test (to test the login credentials) * Sign up (to sign up for Github, which directs to the website)
| 13 |
366 |
TISTUD-1614
|
05/04/2012 09:17:40
|
When importing a Git project, add available GitHub repos to the options
|
Update the Git import dialog: # Add a radio button in front of the existing URI option # Add another radio button with "Github" below. When the radio button is selected, it shows a list of repos in a dropdown via the Github REST API http://developer.github.com/v3/repos/ ## The destination field is shared between the two fields # If I have not logged into Github, show a message with "Add Github Account". Clicking on the link either pops up a u/p field in place, or directs me to the preference page to add the items # Once I've added the u/p, the page refreshes to show my repos. # If I select a Github repo, it then clones it into my local workspace
| 13 |
367 |
TISTUD-1616
|
05/04/2012 10:40:54
|
Add ability to log out of Jira account for "Submit a ticket"
|
Once logged into Jira inside Titanium Studio you cannot seem to log out and your name is retained between user logins. Steps to reproduce: 1. Log into Titanium Studio using one account. 2. Open Jira through the Help > Titanium Studio > Submit a ticket 3. Log into Jira via the top of the form and the validate button. 4. Log out of Titanium Studio. 5. Log into Titanium Studio using a second account. 6. Open Jira through the Help > Titanium Studio > Submit a ticket. Expected Result: Previous users Jira account should be cleared and the user should be prompted for username and password. Actual Result: The first user is still logged in with no way to log out.
| 8 |
368 |
TISTUD-1617
|
05/04/2012 11:11:43
|
Submit a ticket wizard only submits the first line of the "Steps to reproduce" field.
|
When a user submits a ticket using the Submit a ticket Jira wizard only the first line of the steps to reproduce is passed into the Jira. Steps to reproduce: 1. Submit a ticket with multiple lines in the steps to reproduce field. Expected results: All lines will appear in the Jira ticket on the web site. Actual results: Only the first line is passed into the Jira.
| 5 |
369 |
TISTUD-1622
|
05/04/2012 21:36:14
|
Need to be able to configure ACS url for staging testing purpose
|
Right now studio has hard coded api.cloud.appcelerator.com, in order to test in staging environment, we need to be able to change it to point to api.staging.cloud.appcelerator.com instead
| 5 |
370 |
TISTUD-1623
|
05/06/2012 22:27:01
|
Package Node.js with Studio
|
There is a growing demand for a pre-packaged install of Node.js to be shipped with Titanium Studio. We should detect if node.js is currently installed and if not, run latest node.js installer in our installer.
| 0 |
371 |
TISTUD-1626
|
05/07/2012 09:16:09
|
CLONE - Need to be able to select javascript modules from TiStudio Modules panel
|
With support for JavaScript (commonJS and MobileWeb) modules being added, we now need the ability to display and select javascript modules in the TiStudio Modules panel. # Show the (currently-hidden) modules # In the popup to select per-platform versions, for commonjs modules, only show a single drop down for selecting a version which will apply across all platforms.
| 8 |
372 |
TISTUD-1627
|
05/07/2012 09:17:28
|
Add support for creating javascript modules to TiStudio
|
Add the ability to create a javascript module (commonJS or MobileWeb, depending on implementation of MOD-701).
| 8 |
373 |
TISTUD-1630
|
05/07/2012 15:05:59
|
"Aptana" is shown under the main Help menu on Titanium Studio standalone installation
|
Not necessarily reproduceble, but on a brand new Titanium Studio installation on a Mac 10.7.2 machine, "Aptana" instead of "Titanium Studio" is displayed under Help. Also the preference page node has Aptana Studio instead Titanium Studio as well, so look like one or more overriding plugins didn't get loaded. Here is how I got into this state: 1. Download Titanium Studio 2.0.1 Mac zip from preview.appcelerator.com/studio; 2. Add http://preview.appcelerator.com/appcelerator/studio/standalone/update/beta/ update site and update to the latest 2.0.2 beta.
| 8 |
374 |
TISTUD-1631
|
05/08/2012 09:02:48
|
File JIRA tickets for Titanium Studio in the "Titanium Community" project
|
When filing a ticket inside Titanium Studio using the new JIRA integration (APSTUD-2916), we need to file the ticket in APSTUD if it came from Aptana Studio, and TC if it came from Titanium community
| 8 |
375 |
TISTUD-1632
|
05/08/2012 09:42:52
|
Re-configure JIRA ticket submission fields to better match current ticket guidelines
|
When filing a ticket in JIRA, we need to reconfigure the current fields ever so slightly. Instead of a single "Steps to Reproduce" we need three fields: * Steps to Reproduce* * Actual Result* * Expected Result (*d fields are required) From a space perspective, "Steps" should be 2X the height of the other two. When the ticket is filed, replace any empty fields with "N/A", and use the following template: {code} h3. Steps to Reproduce [Steps] h3. Actual Result [Actual] h3. Expected Result [Expected/N/A] {code}
| 8 |
376 |
TISTUD-1633
|
05/08/2012 13:19:57
|
Titanium Studio: android module fails to create with internal error
|
When creating a module in studio, the creation fails with internal error: could not move file. Screenshot and log attached. This only occurs with android modules. However, android modules can be created from the command line. Steps to Reproduce: 1. Create new android module from studio. Expected Result: Module creates. Actual Result: Module fails to create.
| 8 |
377 |
TISTUD-1640
|
05/08/2012 15:02:44
|
Titanium Studio: MobileWeb: preview in emulator/browser fails with NPE
|
When a mobileweb project is previewed in emulator or browser, there is a silent failure in the UI, and an NPE error in the log. Log attached. This does not occur in Studio 2.0.1. Steps to Reproduce: 1. Create a new mobileweb project. 2. Preview in Browser and Preview in Emulator. Expected Result: App should preview in browser or emulator. Actual Result: Silent UI failure (no popup, no visual response), null pointer exception logged to studio log.
| 5 |
378 |
TISTUD-1642
|
05/08/2012 18:02:53
|
Titanium Studio: Login: studio does not auto-login on Linux
|
When studio launches, the user always has to enter login information (i.e., the auto-login never occurs). Steps to Reproduce: 1. Run studio on Linux. 2. Enter appcelerator login information. 3. Close and relaunch studio. Expected Result: Studio should auto-login. Actual Result: The user is prompted to enter studio login information every time.
| 13 |
379 |
TISTUD-1643
|
05/08/2012 18:19:57
|
Remove the text in Windows installer about restarting the machine after uninstallation since it is not necessary
|
When studio is installed using the installer and the machine is rebooted after prompt, the installer does not relaunch on machine reboot. The installer must be manually run to continue the installation. Steps to Reproduce: 1. Run the studio installer on Windows. 2. Reboot the machine on prompt. Expected Result: Installer should relaunch after machine reboot. Actual Result: Installer does not relaunch. It must be manually relaunched to continue installation.
| 8 |
380 |
TISTUD-1645
|
05/08/2012 19:03:37
|
Titanium Studio: Titanium Preferences: Default Android SDK changed if not saved and sdk path is reloaded
|
In Preferences > Titanium Studio > Titanium, if the Default Android SDK is changed and the user clicks on the Android SDK Home text field, then clicks in a different text field (e.g., Android NDK Home), the Default Android SDK change will be undone if it was not previously saved. This is a usability issue because the user's edits are automatically undone. Steps to Reproduce: 1. Go to Preferences > Titanium Studio > Titanium. 2. In the Default Android SDK drop-menu, change the SDK to a different version (but do not save the changes). 3. Click in the Android SDK Home text field. 4. Click in the Android NDK Home text field. Expected Result: The changes made to the Default Android SDK should remain. Actual Result: The old Default Android SDK is automatically selected.
| 5 |
381 |
TISTUD-1664
|
05/08/2012 19:04:07
|
TiStudio: Encoding problem with Git Commit Message
|
Same problem on Ti Studio. https://jira.appcelerator.org/browse/APSTUD-4043 (Aptana bug) -------- The problem is that when i git commit with comments in Japanese(or Korean), i get unreadable by git log on terminal(utf-8). (I can read in Titanium studio history window. but unreadable by other tools) by the way, One repository that was make another machine (ex:ubuntsu) and it has commit message in UTF-8(Japanese). I Pull to Titanium Studio. The history is unreadable.
| 8 |
382 |
TISTUD-1647
|
05/09/2012 15:59:50
|
Titanium Studio: MobileWeb: preview in android emulator initially fails with server errors when AVD is first created
|
When deploying from studio, or manually running a mobileweb app in the android emulator browser, the app will not run and server related errors log to the console when a new AVD is created. Logs attached. This is not a regression, as it does occur in Studio 2.0.1. Steps to Reproduce: 1. Delete .android/avd/ 2. Create a default mobileweb project. 3. MobileWeb Preview in Emulator. Expected Result: Emulator should launch, emulator browser should load, app should run. Actual Result: Emulator launches, emulator browser does not load. Manually opening the browser and navigating to the app url results in a failed app load.
| 8 |
383 |
TISTUD-1648
|
05/09/2012 18:26:54
|
Titanium Studio: Modules: android modules created on command line cannot be packaged in studio
|
Android modules created from command line cannot be packaged in studio. There is no package option in the UI. Note: Android modules created in studio, and iPhone modules created from the command line, work as expected. Steps to Reproduce: 1. Create an android module from the command line. 2. Import the module into studio. 3. Attempt to package the module (i.e., box icon > Package Android Module). Expected Result: Package option should be available. Actual Result: Package option is not available. h3. Suggested solution When importing an existing Titanium project, check for the existence of a timodule.xml file, and set the builders/natures appropriately.
| 8 |
384 |
TISTUD-1649
|
05/09/2012 18:42:15
|
Titanium Studio: MobileWeb: no option to package mobileweb modules
|
MobileWeb modules do not have the option to package from studio. Note: MobileWeb modules cannot be created in studio 2.0.1, so this feature cannot be tested in studio 2.0.1. This is a new fail case. Steps to Reproduce: 1. Create a mobileweb module. 2. Attempt to package the module (box icon > Package MobileWeb Module). Expected Result: The package option should be available in the packaging drop-down menu. Actual Result: There is no mobileweb module packaging option. MobileWeb projects can be created in studio, but not packaged.
| 13 |
385 |
TISTUD-1650
|
05/10/2012 11:49:20
|
Titanium Studio: change default workspace to one without spaces to support module development
|
Currently, the default studio workspace is Titanium Studio Workspace. Because the workspace contains spaces, Android modules cannot be packaged. One suggestion is to change the default workspace to one without spaces to facilitate module development. As per discussion, it was suggested to use: Titanium_Studio_Workspace
| 5 |
386 |
TISTUD-1666
|
05/14/2012 06:06:43
|
Restart of Titanium Studio Required for the tiapp editor to display modules added after Studio was launched
|
h3.Experience Currently, the list of modules appears to only be loaded into Titanium Studio at startup. Modules added to the Library folder after Titanium Studio has launched are not seen in the Modules pane of the tiapp editor. This requires a restart of Titanium Studio. h3.Expectation When the tiapp editor is opened that all modules are available for inclusion. h3. Solution Modules folder(s) needs to be rescanned when the tiapp editor is opened.
| 8 |
387 |
TISTUD-1656
|
05/14/2012 17:02:58
|
App is created with NULL creator_user_id.
|
h4. Problem Description I published an App to the App Store and Google Play but the app never appeared on "My Apps". The original guid was: 2c9e1129-86d4-4f9d-9f0d-4d7bd0cd764a Because I noticed new projects showed up on "My Apps" I've created a new project and transplanted the guid to the tiapp.xml of my app. Released it to the Play Store and this enabled the app to show on "My Apps" where it says "122 analytics events were processed for this application since May 1, 2012" but it still shows 0 users, 0 sessions and "There were no events logged during between 5/7 and 5/13." The new guid is: 473b9203-836a-4d48-ac13-2993873efa2c I wrote more about this in http://developer.appcelerator.com/question/136456/my-app-doesnt-show-in-analytics but haven't received any feedback. Can you take a look?
| 5 |
388 |
TISTUD-1658
|
05/14/2012 18:54:57
|
JavaScript Formatter: Spaces preferences contains edge case failures
|
Titanium Studio > Preferences > Titanium Studio > Formatter > JavaScript contains edge cases where the formatting fails. The sample code is below, all spacing is set to 5. {code} /* * Parentheses: Loop Expressions * * */ // // no spaces in do-while parentheses // do { } while(x); /* * Parentheses: Array Access Expressions * * */ // // no spaces for array access in switch parentheses // switch (xyz[2]) { default : return xyz; } // // no spaces for array access in do-while parentheses // do { } while(xyz[2]); // // no spaces for array access in case statements // switch(x) { case xyz[0]: break; } /* * Parentheses: Other Parentheses * * */ // // no spaces in switch parentheses // switch (theDay) { default: document.write ( "Donno :(" ); } // // no spaces in catch parentheses // try { } catch(err) { } // // no spaces in grouping parentheses // (function fooInGroup ( ) { }) return ! (xyz [ 0 ] > 0); switch(x) { case (z): break; case (x < y): break; default: break; } /* * Operators * * */ // // no spaces for any operators in switch parentheses // switch (hour + 12) { } switch (hour >= 12) { } switch (!x) { } switch (x = 12) { } switch (x ? 12 : 0) { } // // no spaces for any operators in case parentheses // switch(0) { case (hour + 12): break; case (hour >= 12): break; case (!x): break; case (x = 12): break; case (x ? 12 : 0): break; } // // no spaces for any operators in do-while parentheses // do { } while (hour + 12); do { } while (hour >= 12); do { } while (!x); do { } while (x = 12); do { } while (x ? 12 : 0); /* * Operators: Assignments * * */ // // no spaces after assignment operators followed by function // var a = function ( b , c , d ) { alert ( b + c + d ); } // // no spaces after assignment operators followed by curly brace object // var bb = { "a" : 1 , "b" : 2 , "c" : 3 }; // // no spaces after assignment operators followed by ternary expression // var c = a ? 10 : 20; /* * Operators: Key-Value Operator * * */ // // no spaces after key-value operators followed by function // new MyFunctions ( { onComplete : function ( ) { } , onClick : function ( ) { } , myVar : {} } ); // // no spaces after key-value operators followed by curly brace object // new MyFunctions ( { myVar : {} } ); // // no spaces after key-value operators followed by ternary expression // new MyFunctions ( { myVar : x ? 10 : 20 } ); {code}
| 0 |
389 |
TISTUD-1661
|
05/15/2012 15:48:35
|
JavaScript Formatter: Spaces preferences contains edge case improvements
|
Titanium Studio > Preferences > Titanium Studio > Formatter > JavaScript contains edge cases where the formatting fails. The sample code is below, all spacing is set to 5. {code} /* * Punctuation Elements: End Statement Semicolons * * */ // // no spaces before or after end statements // var x = function ( ) { }; var x; var x = new Array ( ); /* * Operators: Switch Scope Operator * * */ // // no spaces before or after : operator in switch case statement // switch(x) { case 'x': break; case z: break; case (z): break; case (x < y): break; default: break; } /* * Keywords * * */ // // no spaces before variable name declarations // function foo ( ) { }; var i = x; void s; // // no spaces before type instantiations // c = new Array ( a , b , c ); // // no spaces after return keyword before implicit groupings // switch (x) { default : return xyz [ 0 ] > 2 ? 10 : 20; } return x; return function ( ) { }; return {}; // // no spaces between else and if // if ( x ) { } else if ( z ) { } // // no spaces after case // switch(x) { case x: break; } {code}
| 0 |
390 |
TISTUD-1662
|
05/15/2012 18:11:27
|
Editor: JavaScript Comment Auto-Complete initially fails to recognize preexisting blocks and cursor is incorrectly positioned
|
JavaScript Comment Auto-Complete initially fails to recognize preexisting blocks and cursor is incorrectly positioned. I am marking this as a bug because the auto-comment partially works, and I can get into this bad state. Screenshot attached. The auto-complete kicks in after pressing enter twice, but the cursor is on the wrong line. Steps to Reproduce: 1. Enter code in JS file: {code} /**/ {code} 2. Insert cursor between the two asterisks (in the middle of the block comment) and press enter. Note: A vertical bar character is used to simulate the resulting position of the cursor. Expected Result: {code} /* * | * */ {code} Actual Result: {code} /* |*/ {code} 3. Press enter again. Expected Result: {code} /* * * | */ {code} Actual Result: {code} /* *|*/ {code} 4. Press enter again. Expected Result: {code} /* * * * | */ {code} Actual Result: {code} /* * *|*/ {code}
| 8 |
391 |
TISTUD-1669
|
05/17/2012 15:52:03
|
Titanium Studio: Preferences: cannot edit or leave titanium preferences menu with invalid values error
|
If the titanium preferences menu is opened, the user cannot navigate to a different menu. There is a pop-up with an invalid values error. Screenshot attached. Also, if individual titanium preferences are edited, the changes cannot be applied. The only way to leave the menu is to press cancel or close the entire preferences window. Screenshot attached. There are no log entries. This does not occur in 2.0.1 (regression). I do not believe this occurred in yesterday's build. Steps to Reproduce: 1. Open studio, navigate to the titanium preferences menu (Preferences > Titanium Studio > Titanium). 2. Attempt to navigate to a different menu (e.g., press General). Expected Result: The menu should change. Actual Result: Pop-up error indicating invalid values. Menu does not change. 3. Change the Android SDK version (or any setting in the titanium preferences menu). 4. Apply the changes (press Apply). Expected Result: The changes should be saved. Actual Result: Apply is not selectable. Note: The titanium preferences menu can only be exited by pressing Cancel or closing the entire preferences menu (press the window X).
| 5 |
392 |
TISTUD-1671
|
05/17/2012 17:32:52
|
Titanium Studio: Multiline Search: enter newline keyboard shortcuts edit the wrong text area
|
When the multiline search box is up, and the enter new line keyboard shortcuts are used, the characters are entered in the active .js file instead of the search field. Screenshot attached. No log files. Not testable in studio 2.0.1 (new fail case). Command + Enter will add new lines to the .js file. Control + Enter will add visible '\n' characters to the end of the first line in the .js file. Steps to Reproduce: 1. Open studio, open a .js file (create a new project if necessary). 2. Open multiline search (Command + f in osx). 3. Click in the search box to give it focus and place the cursor inside the search box. 4. Press Command + Enter a few times (on osx only). 5. Press Control + Enter a few times. Expected Result: New lines should be added to the search box. Actual Result: New lines and visible '\n' characters are added to the active .js file.
| 8 |
393 |
TISTUD-1672
|
05/17/2012 17:44:14
|
Titanium Studio: Multiline Search: history and scope icons are inactive, only down arrow displays drop-down list
|
Search history icon does not function when clicked. Only the small down arrow next to the icon will display the search history drop-down menu. Screenshot attached. This is a valid issue, as this is how the run configuration icons function, in addition to basic usability. This also affects the scope icon. Note: There are two history icons, one for search and one for replace (both fail). Steps to Reproduce: 1. Open studio, open js file (create new project as needed). 2. Activate search (command + f on osx). 3. Click on the history icon (flashlight) or the scope icon. Expected Result: A search history drop-down list should display. Actual Result: The icon blinks. However, the small down arrow next to the icon functions correctly.
| 5 |
394 |
TISTUD-1673
|
05/17/2012 17:58:27
|
Titanium Studio: Multiline Search: enable horizontal scrolling in search and replace boxes
|
In the search and find text areas, vertical scrolling (i.e., by mouse scroll) is enabled, but not horizontal scrolling. This impairs the functionality of the fields because longer text lines cannot be easily navigated. The only way to scroll horizontally is to use the highlight functionality of the cursor (not ideal). Screenshot attached. Steps to Reproduce: 1. Open studio, open a js file. 2. Open search bar (command + f on osx). 3. Enter long line of text (longer than the search field itself) into search field. 4. Attempt to scroll horizontally. Expected Result: Search field (and replace field) should scroll horizontally to easily view the entire line of text. Actual Result: Nothing happens. The workaround is to use the highlight or left/right arrow functionality of the cursor to drag/move left and right.
| 2 |
395 |
TISTUD-1674
|
05/17/2012 18:06:10
|
Titanium Studio: Multiline Search: add "Select All" command to select all to search and replace boxes
|
When clicking on text in the search or replace boxes, it is difficult to select all the text. Steps to Reproduce: 1. Open studio, create a new project, open the app.js file. 2. Open search bar (command + f on osx). 3. Copy/paste a larger block of code in the search box. 4. Attempt to use the "Select All" command to select all the text Expected Result: All text in the box highlights. Actual Result: Select all doesn't work.
| 5 |
396 |
TISTUD-1677
|
05/17/2012 18:42:28
|
Multiline Search: find should jump to string matches when scope is set to open files
|
When two js files are open, each containing a particular string, and that string is searched-for from the search bar using the scope setting: open files, the find button does not jump the cursor to the matching string instances. The matches are recognized and highlighted when find is pressed, but the specific matches are not iterated using the find button. Steps to Reproduce: 1. Open studio, create a new project. 2. Add a new js file to the project. 3. Add any string (e.g., xxx) to both app.js and the other .js file. 4. Make sure both files are open in the editor. 5. Open the search bar (command + f in osx). 6. Click on Scope (the down arrow next to it) and set it to Open Files. 7. Enter the string that exists in both files (e.g., xxx) into the search field. 8. Click find a few times. Expected Result: The cursor should iterate through the instances of the matching string. Actual Result: All instances highlight, but the cursor does not iterate, and the second file never gets focus (to view it's string match). The cursor
| 8 |
397 |
TISTUD-1678
|
05/18/2012 08:19:39
|
Android: allow users to launch x86 emulator
|
h2. Description Developers need to be able to leverage the Android x86 emulator that was made available with Android SDK r17. It claims to have performance increases beyond the standard emulator making for a better development experience. h2. Proposed Solution(s) It would be good if you could specify by default whether you want to use the x86 or standard emulator for all projects, perhaps in {{Preferences -> Titanium Studio -> Titanium}}. It should be the standard emulator by default as the x86 emulator currently does not include the Google APIs (which would prevent the KitchenSink from running) and it does not support V8, as detailed in the linked ticket. Also, it should be configurable on a per-project basis as well, for the same reasons I listed in the above paragraph. So: # We need to upgrade our AVI detection to show the available ABIs per device # For devices with multiple ABIs we need to allow the user to select which one to use as part of the launch configuration, and that is passed as the first argument to the SDK for SDKs 2.1+. For < 2.1, we only pass the device argument # We could add a preference in Titanium Preferences to default to x86 or standard emulator (were available). This would se the default ABI selection in the launch configuration.
| 13 |
398 |
TISTUD-1680
|
05/18/2012 10:14:05
|
Better error hinting with regard to non-UTF-8 characters for android
|
h2. Problem When a non-UTF-8 character is found in a Titanium editor window, TiStudio will mark the file containing it with an error in the gutter. Doing a mouse over on this error reveals the following error message. {code:lang=none} File needs to be in UTF-8 encoding for Android. Decoding failed near byte 0. {code} Unfortunately for me, the non-UTF-8 character was no where near byte 0. It was actually at byte 1193 as shown in the Android error log when attempting to ignore TiStudio's error and run the application anyway: {code:lang=none} [ERROR] Exception occured while building Android project: [ERROR] Traceback (most recent call last): [ERROR] File "/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/builder.py", line 2125, in <module> [ERROR] s.build_and_run(True, avd_id, device_args=device_args) [ERROR] File "/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/builder.py", line 1867, in build_and_run [ERROR] True, project_dir = self.top_dir, include_all_ti_modules=include_all_ti_modules) [ERROR] File "/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/android.py", line 301, in create [ERROR] self.build_modules_info(resource_dir, app_bin_dir, include_all_ti_modules=include_all_ti_modules) [ERROR] File "/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/android.py", line 170, in build_modules_info [ERROR] compiler.compile(compile_bytecode=False, info_message=None) [ERROR] File "/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/compiler.py", line 250, in compile [ERROR] js_contents = self.make_function_from_file(fullpath) [ERROR] File "/Users/tlukasavage/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2/android/compiler.py", line 209, in make_function_from_file [ERROR] file_contents = codecs.open(path,'r',encoding='utf-8').read() [ERROR] File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/codecs.py", line 671, in read [ERROR] return self.reader.read(size) [ERROR] File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/codecs.py", line 477, in read [ERROR] newchars, decodedbytes = self.decode(data, self.errors) [ERROR] UnicodeDecodeError: 'utf8' codec can't decode byte 0xa9 in position 1311: invalid start byte {code} h2. Proposed Solution Return a byte position that more closely represents the location of the offending non-UTF-8 character. Also, if possible, move the error marker in the gutter from the first line of the file to the appropriate line in the file. h2. Test Case The following comments should be enough to show what I mean. The character after the word "Copyright" is the one causing the error, but TiStudio reports the error at byte 0. {code:javascript} // ========================================================================= // // xmlw3cdom.js - a W3C compliant DOM parser for XML for <SCRIPT> // // version 3.1 // // ========================================================================= // // Copyright (C) 2002, 2003, 2004 Jon van Noort ([email protected]), David Joham ([email protected]) and Scott Severtson // // This library is free software; you can redistribute it and/or // modify it under the terms of the GNU Lesser General Public // License as published by the Free Software Foundation; either // version 2.1 of the License, or (at your option) any later version. // This library is distributed in the hope that it will be useful, // but WITHOUT ANY WARRANTY; without even the implied warranty of // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU // Lesser General Public License for more details. // You should have received a copy of the GNU Lesser General Public // License along with this library; if not, write to the Free Software // Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA // // visit the XML for <SCRIPT> home page at xmljs.sourceforge.net // // Contains text (used within comments to methods) from the // XML Path Language (XPath) Version 1.0 W3C Recommendation // Copyright � 16 November 1999 World Wide Web Consortium, // (Massachusetts Institute of Technology, // European Research Consortium for Informatics and Mathematics, Keio University). // All Rights Reserved. // (see: http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929/) {code}
| 8 |
399 |
TISTUD-1681
|
05/21/2012 08:38:12
|
Dashboard's Configure page has two platform "spinners" that never get replaced by content
|
When I load the Dashboard on my Win7 VM and then click the "Configure" tab, MobileWeb appears, but there are two spinner placeholders (for IOS and Android?) that never get replaced by content.
| 8 |
400 |
TISTUD-1682
|
05/21/2012 11:30:10
|
Studio: Local variables do not appear in content assist
|
Local variables do not appear in content assist. This is a regression issue (did not appear in 1.0.9). Steps to reproduce: 1. In a JavaScript file enter: {code} function myFunction(myParam){ var newLocal = my } {code} 2. Invoke content assist after the my on the unfinished line. Expected results: Content assist should suggest myFunction and myParam as options. Actual results: Content assist shows only myFunction as an option. First reported in [this post|http://developer.appcelerator.com/question/137164/titanium-studio-20-autocomplete---local-variables].
| 13 |
401 |
TISTUD-1683
|
05/21/2012 11:44:49
|
Out of Memory error indexing ti.jira module
|
When I was testing module installation in TISTUD-1579, I ran into this issue after the module got unzipped to a project. The module involved was ti.jira 1.2.1 ("JIRA Module" in the marketplace). {code} !ENTRY org.eclipse.core.jobs 4 2 2012-05-21 13:36:05.558 !MESSAGE An internal error occurred during: "Building workspace". !STACK 0 java.lang.OutOfMemoryError: Java heap space at java.util.HashMap.<init>(HashMap.java:187) at java.util.HashMap.<init>(HashMap.java:199) at com.aptana.internal.index.core.DiskIndex.readCategoryTable(DiskIndex.java:1099) at com.aptana.internal.index.core.DiskIndex.addQueryResults(DiskIndex.java:303) at com.aptana.index.core.Index.query(Index.java:547) at com.aptana.editor.js.contentassist.index.JSIndexReader.getFunctions(JSIndexReader.java:306) at com.aptana.editor.js.contentassist.JSIndexQueryHelper.getFunctions(JSIndexQueryHelper.java:84) at com.aptana.editor.js.contentassist.JSIndexQueryHelper.getMembers(JSIndexQueryHelper.java:192) at com.aptana.editor.js.contentassist.JSIndexQueryHelper.getGlobals(JSIndexQueryHelper.java:124) at com.aptana.editor.js.inferencing.JSNodeTypeInferrer.visit(JSNodeTypeInferrer.java:641) at com.aptana.editor.js.parsing.ast.JSIdentifierNode.accept(JSIdentifierNode.java:33) at com.aptana.editor.js.parsing.ast.JSTreeWalker.visit(JSTreeWalker.java:176) at com.aptana.editor.js.inferencing.JSNodeTypeInferrer.getTypes(JSNodeTypeInferrer.java:260) at com.aptana.editor.js.inferencing.JSNodeTypeInferrer.visit(JSNodeTypeInferrer.java:491) at com.aptana.editor.js.parsing.ast.JSFunctionNode.accept(JSFunctionNode.java:46) at com.aptana.editor.js.parsing.ast.JSTreeWalker.visit(JSTreeWalker.java:176) at com.aptana.editor.js.inferencing.JSSymbolTypeInferrer.processValues(JSSymbolTypeInferrer.java:560) at com.aptana.editor.js.inferencing.JSSymbolTypeInferrer.getSymbolPropertyElement(JSSymbolTypeInferrer.java:352) at com.aptana.editor.js.inferencing.JSSymbolTypeInferrer.getSymbolPropertyElement(JSSymbolTypeInferrer.java:389) at com.aptana.editor.js.inferencing.JSSymbolTypeInferrer.getScopeProperties(JSSymbolTypeInferrer.java:292) at com.aptana.editor.js.contentassist.index.JSFileIndexingParticipant.processParseResults(JSFileIndexingParticipant.java:216) at com.aptana.editor.js.contentassist.index.JSFileIndexingParticipant.index(JSFileIndexingParticipant.java:104) at com.aptana.core.internal.build.IndexBuildParticipant.buildFile(IndexBuildParticipant.java:104) at com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) at com.aptana.core.build.UnifiedBuilder.buildFile(UnifiedBuilder.java:520) at com.aptana.core.build.UnifiedBuilder.doBuildFiles(UnifiedBuilder.java:432) at com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:409) at com.aptana.core.build.UnifiedBuilder.incrementalBuild(UnifiedBuilder.java:232) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:168) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) {code}
| 8 |
402 |
TISTUD-1687
|
05/21/2012 17:39:59
|
Titanium Studio: run configuration platform drop-down icons missing on Linux
|
The platform deployment icons in the project run configuration drop-down are missing on Linux. Screenshot attached. Does not occur on Snow Leopard or Windows 7. Unable to regression test on Linux against 2.0.1 due to https://jira.appcelerator.org/browse/TISTUD-1514. This is not a regression as it occurs in 2.0.0 and 1.0.9. Steps to Reproduce: 1. Open Studio, Create a Project. 2. Click on the Run arrow in the Project Explorer. Expected Result: A drop-down menu should appear with all platform deployment options. Each option should have an icon on the left. Actual Result: Menu appears without icons.
| 0 |
403 |
TISTUD-1694
|
05/24/2012 14:40:09
|
TestFlight Publish confirmation dialog is missing content
|
When a TestFlight publish is complete, the confirmation dialog has yes/no buttons, but does not pose a question. This may apply to the entire publish extension, so the fix may be in the default implementation
| 5 |
404 |
TISTUD-1695
|
05/24/2012 15:08:34
|
Titanium Studio: Project Explorer: Close Project and Open Project not updated until re-click on project
|
Project > Open, and Project > Close command availability are not updated in real time for projects in the Project Explorer. The old project options are still available (e.g., Close is available if the project is already closed). Re-clicking the project in the explorer will update the Project menu options. This is not a regression. There is no log info. Fail Cases: 1. Project Explorer: Cannot open a newly closed project. 2. Project Explorer: Cannot close a newly opened project. Note: Project Explorer: Cannot close a freshly created project. - This is an invalid case as tiapp.xml has focus. Steps to Reproduce: 1. Click a project in Project Explorer to manually refresh Project menu options. 2. Click Project > Close to close project. 3. Click Project. Expected Result: Project > Open should be available. Actual Result: Open is not available. If the project is re-clicked, it will become available. 4. Re-Click project in Project Explorer to manually refresh Project menu options. 5. Click Project > Open to open project. 6. Click Project. Expected Result: Project > Close should be available. Actual Result: Close is not available. If the project is re-clicked, it will become available.
| 8 |
405 |
TISTUD-1696
|
05/24/2012 15:15:54
|
Titanium Studio: App Explorer: cannot use Close project command if project resources are selected
|
In the App Explorer window, if project resources are selected, the project cannot be closed using Project > Close. This is not a regression. There is no log info. Steps to Reproduce: 1. Create a new project. 2. View the project info in the App Explorer. 3. Click on the Resources folder (or any project resource). 4. Click Project > Close. Expected Result: Project should close. Actual Result: Project > Close is not highlighted/selectable. Clicking in the empty area of the App Explorer will unselect the resource and give the project focus, allowing Project > Close to function.
| 0 |
406 |
TISTUD-1697
|
05/24/2012 15:30:20
|
Titanium Studio: App Explorer: opening a project in Project Explorer changes selected project in App Explorer
|
When a project is opened after being closed in the Project Explorer, the App Explorer selected project is updated to the recently opened project. It is expected the selected project in the App Explorer would only change if it is deleted or manually changed. However, the App Explorer selected project is not updated (correctly) if a new project is created. This is not a regression. There is no log info. Steps to Reproduce: 1. Create two projects. 2. In the App Explorer, select the first project. 3. In the Project Explorer, select the second project. 4. Close the second project using Project > Close. 5. Open the project using Project > Open (reselect project if Project menu commands do not update). 6. Navigate to the App Explorer. Expected Result: The first project should be selected (the first one that was selected). Actual Result: The second project is selected (the one that was recently opened).
| 8 |
407 |
TISTUD-1698
|
05/24/2012 16:44:55
|
Titanium Studio: Editor: reopening open project file via Project Explorer Local Filesystem results in duplicate mirror file in editor
|
If a file that is open in the editor is opened again using the Project Explorer Filesystem, there is a resulting mirror copy of the file in the studio editor. This is not a regression. There is no log info. Steps to Reproduce: 1. Create a new project. 2. Open app.js if it isn't open already from the Project Explorer project folder. 3. Go to Project Explorer > Local Filesystem, navigate to app.js (the same file) and open it. Expected Result: The original open version of the file should gain focus. Actual Result: Another copy of the same file will open in the editor resulting in two duplicate open files. Edits to one file are mirrored in real-time to edits in the other file.
| 8 |
408 |
TISTUD-1700
|
05/24/2012 17:14:36
|
"Search > Search" and "Search > File" bring up same menu
|
Search > Search and Search > File bring up the same menu. Alternately, PyDev is missing from the Search drop down (e.g., Search > PyDev...). Titanium Behavior: In the Search drop-down, there are two options (Search, and File...). Search > Search brings up the search menu. Search > File... brings up the search menu with identical settings. There is a second tab in the search menu for PyDev that is not selectable from the command drop-down list. Eclipse Behavior: In Eclipse, there are three search options (Search, File..., and JavaScript...). Search > Search brings up the search menu with the JavaScript tab selected. Search > File... brings up the search menu with the File tab selected. Search > JavaScript... brings up the search menu with the JavaScript tab selected. There is a third Java tab that exists in the menu, but is not accesible from a drop-down command. The issue is Titanium should either remove Search > File... because it brings up a duplicate menu, or add Search > PyDev... to access the PyDev tab in the search menu. This is not a regression. There is no log info. Steps to Reproduce: 1. Open Studio. 2. Go to the Search drop-down menu at the top. Expected Result: Search > File... should not exist, or Search > PyDev... should exist. Actual Result: Search > Search and Search > File... bring up identical menus.
| 8 |
409 |
TISTUD-1701
|
05/24/2012 18:49:12
|
Editor: changing file type then reopening does not reflect new file type
|
If a file is open in the editor, and the file type is edited in the project explorer, the open file in the editor is not fully updated. See info in Expected/Actual Result below. The file will only update if it is closed and reopened. Clicking on the file will not update it. Relaunching studio will not update it. This is not a regression. There is no log info. Steps to Reproduce: 1. Create a new project. 2. Add a generic typeless file to the project. 3. Add JavaScript code to the file. Verify lack of syntax highlighting. 4. While project is open in editor, change the filetype of the file in the project explorer to .js. Expected Result: 1. The filename should change in the project explorer. 2. The icon for the file in the project explorer should update. 3. The filename should change in the open file editor. 4. The icon for the file in the open file editor should update. 5. The syntax highlighting in the open file should update. 6. The error info in the open file should update. Actual Result: 1. The filename should change in the project explorer. - YES 2. The icon for the file in the project explorer should update. - YES 3. The filename should change in the open file editor. - YES 4. The icon for the file in the open file editor should update. - NO 5. The syntax highlighting in the open file should update. - NO 6. The error info in the open file should update. - NO Note: Double-Clicking on file or relaunching studio will not update the file formatting. Only closing and reopening file will reformat it.
| 13 |
410 |
TISTUD-1702
|
05/24/2012 19:17:36
|
Titanium Studio: code selection highlighting artifacts exist in some themes when cursor pressed and dragged down then up
|
In some themes, when the cursor is pressed to highlight a selection, dragged down over code, then dragged back up, there are highlight artifacts in the code editor display. Screenshot attached. No log info. This is not a regression. I tested all themes A-E. Themes affected: Aptana Studio 2.x All Hallow's Eve Eclipse Expresso Libre Steps to Reproduce: 1. Open Studio. 2. Change theme to an affected theme from above (i.e., Aptana Studio 2.x). Preferences > Titanium Studio > Themes. 3. Create a new project. 4. Open app.js. 5. Click and hold down the cursor/mouse button in the middle of the code file. Drag down then up. Expected Result: No highlight artifacts in the lower code. Actual Result: Highlighting artifacts in the lower code. See screenshot.
| 8 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.