id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
1,611 |
TISTUD-5352
|
09/06/2013 23:02:22
|
Platform Config Wizard: update the description once we are in the progress page
|
When we move into the progress page, we should update the description to indicate we are now configuring for the selected platforms.
| 2 |
1,612 |
TISTUD-5353
|
09/06/2013 23:06:28
|
Platform Config Wizard: the progress page should only contain the platforms we're configuring
|
Currently we show all the platforms, but it feels confusing to me in seeing the other platforms that I didn't choose to configure there. User could feel they can still do something with the other platforms in the mean time even though they always indicated they are not interested in them at this point. We should just show the selected platforms and their progress instead.
| 5 |
1,613 |
TISTUD-5354
|
09/06/2013 23:10:43
|
Platform Config Progress Page: remove the progress bar and cancel icon when a platform is completed
|
When we finish configuring a platform, we update the status and its icon in the middle, but the cancel icon and progress bar on the right still remain. They should be hidden at this point. Similarly when user cancelled the operation, we should hide the progress bar once the cancellation process is done as well.
| 3 |
1,614 |
TISTUD-5355
|
09/06/2013 23:15:53
|
Platform Config Wizard: modify the status when we finish configuring a platform
|
When we finished configuring a platform, we should update the status area to display two lines: the regular check mark and latest installed version on top, and the installation location below. The Settings text and arrow should remain hidden. If the installation is canceled, we should show "Canceled" status but without any icon.
| 5 |
1,615 |
TISTUD-5359
|
09/07/2013 00:14:45
|
Store platform SDK paths preference in configuration scope instead of instance scope
|
Currently we save platform SDK paths in InstanceScope; that means the settings are per workspace, and each time user switches to a new workspace, they need to re-configure the platform SDK paths. The suggestion is to save platform SDK paths in ConfigurationScope so they persist per installation. We need to make sure we migrate existing paths from InstanceScope so users don't need to re-configure after update, and once we make the change, the auto-launch of platform configuration wizard should happen per installation instead of per workspace as well.
| 5 |
1,616 |
TISTUD-5360
|
09/07/2013 00:20:37
|
Platform Config Wizard: Android advanced section: list available SDKs horizontally by major version
|
There are a lot of empty spaces to the right when Android advanced settings section is expanded. This is because the versions are listed vertically with a height limit. The suggestion is to list them in three rows: one for 4.x, one for 3.x, and one for 2.x.
| 5 |
1,617 |
TISTUD-5362
|
09/07/2013 00:28:28
|
Platform Config Wizard: modify the wizard description to provide more info
|
Currently the description just says "Select platforms to configure". It doesn't really add more information to the title in explaining what the wizard does. We should improve the message. A suggestion: "Download, install, and configure required SDKs for the mobile platforms you would like to develop for."
| 2 |
1,618 |
TISTUD-5364
|
09/07/2013 01:06:05
|
Platform Config Wizard: disable Finish button when there is an error in inputs
|
I entered an Android SDK directory that I do not have write permission to; an error is displayed next to the text field, but the Finish button is still enabled.
| 5 |
1,619 |
TISTUD-5365
|
09/07/2013 01:10:32
|
Platform Config Wizard: selection and enablement of Android SDKs do not get updated when directory changes
|
My Android location was pointing to one with existing versions installed. When I switch to a brand new location, the state of checkboxes does not get updated accordingly. I would expect all of them to get enabled with only the minimum version (2.3.3) and probably the most popular version selected.
| 3 |
1,620 |
TISTUD-5439
|
09/07/2013 23:58:34
|
CLI: Change in required query from "ioscerts" to "certs" causes Studio NPE and inability to build for iOS device
|
h5. Description: Trying to build for iOS device with CLI 3.2.0 and SDK 3.2.0 results in failure to open Studio dialog requesting info on developer cert and SDK info. Looking in the log you can see that there is a null pointer exception. Looking at the ti info -t ios -o json output, you can see with 3.1.2 CLI it's: "iosCerts": { with 3.2.0 CLI it's: "certs": { h5. Steps to reproduce: 1) Install CLI 3.2.0 (sudo npm install -g git://github.com/appcelerator/titanium.git) 2) Acquire a 3.2.0 SDK 3) In studio, try to build a project for iOS device h5. Result: Failure with NPE in studio log h5. Expected Result: Device build succeeds
| 5 |
1,621 |
TISTUD-5366
|
09/08/2013 00:59:51
|
Platform Config Wizard: only auto-check the platform entry when the state in advanced settings section is different from original
|
Currently we auto-check the platform entry in platform config wizard when user modifies any fields in Advanced Settings section. However, this creates the following situation: 1. Uncheck Android, expand Advanced Settings section and check one of the uninstalled Android versions (e.g. 4.2); this will make Android correctly checked. 2. Then uncheck Android again and uncheck the same Android version (e.g. 4.2); the Android platform will become checked again, even though we are actually back to the original state when the wizard first opened. Expected result: we should only auto-check the platform entry when the state is different from the original.
| 5 |
1,622 |
TISTUD-5368
|
09/08/2013 01:05:00
|
Platform Config Wizard: Display the EULAs for selected platforms in separate dialog
|
Since we are downloading and installing Android, BlackBerry, and Tizen SDKs directly from the platform config wizard, we need to display the respective EULAs for user to accept. This ticket is to implement the UI for accepting EULA. We will open a separate dialog for EULA when user clicks Finish to configure the list of selected platforms. The dialog will just contain a large multi-line text field where it contains the EULA text for each platform in sequential order. The dialog will have two buttons - Accept and Decline, and user doesn't need to scroll down to the bottom of the text to have Accept enabled. When accepted, we will move to the progress page; when declined, we will close the platform config wizard.
| 8 |
1,623 |
TISTUD-5369
|
09/08/2013 01:13:31
|
Tiapp Editor: make the wrench and info icons on the same side
|
Currently the wrench icon appears on the left of platform checkbox, while info icon appears on the lower right. Since the two are mutually exclusive, i.e. only one could appear at any time, the suggestion is to line them up on the same side.
| 5 |
1,624 |
TISTUD-5370
|
09/08/2013 01:18:20
|
Tiapp Editor: prompt user when saving tiapp with unconfigured platforms selected
|
In 3.2.0, users could select platforms that they haven't configured Studio with yet, and the concern is that it could cause confusion if user doesn't see the Install button and wonders why he/she can't run the app from menus after selecting the platform in tiapp. The suggestion is when tiapp editor is saved, if there are unconfigured platforms selected, we prompt users so they could setup the platforms there.
| 3 |
1,625 |
TISTUD-5378
|
09/08/2013 09:23:34
|
Formatter fails on javascript "switch/default" braces block
|
var a; switch(a) { case 1: { a = b; break; } case 2: { a = b; break; } default: { /* this braces are the cause of formatter crash */ b = a; } }
| 5 |
1,626 |
TISTUD-5372
|
09/09/2013 19:44:45
|
Platform Config Wizard: Android: select 4.1.2 and 2.3.3 by default when a new SDK home is specified
|
Currently we are only selecting Android 2.3.3 by default. Instead, we should select it and the most popular version, currently 4.1.x (36.6% as of 09/04/13), and make the most popular one the default.
| 3 |
1,627 |
TISTUD-5381
|
09/11/2013 02:00:37
|
Studio: Add support for iOS 7 64 bit simulator
|
h5. Description: Xcode 5 GM seed includes a new simulator that is not exposed via the launch configurations within studio. This new simulator is iOS 7 only, "iPhone 5 (4-inch 64-bit)". We should add support for running this simulator to Studio. h5. Steps to reproduce: 1) Install Xcode 5 GM seed 2) Install command-line tools 3) Open iOS simulator and navigate to hardware>device - note the new simulator 4) Open run configuration in Studio for iOS sim h5. Result: No options are available to configure launch of the 64 bit simulator h5. Expected Result: The 64 bit simulator can be configured and launched
| 5 |
1,628 |
TISTUD-5383
|
09/13/2013 01:46:08
|
Add platform image to each platform section
|
As shown in the screenshot, a image has to be added prior to platform checkbox button. The chopped 1st half of the image should appear in the platform section and the other half in the advance section. So when the advance section is expanded, the complete platform image should appear (as shown in the screenshot).
| 8 |
1,629 |
TISTUD-5385
|
09/13/2013 19:44:07
|
Platform Config Wizard: Improve the initial layout
|
# Make the Advanced Settings text and arrow right-aligned # Move the arrow to the right of the text # Modify the text to say "Settings" when collapsed and "Hide" when expanded # Make the status center-aligned # Remove warning icon for "Not Yet Configured"
| 5 |
1,630 |
TISTUD-5386
|
09/13/2013 21:36:00
|
Platform Config Wizard: Change Hide button to Close and remove Cancel button when all platforms are finished configuring
|
When all selected platforms are done configuring (or the process got canceled), we should change the Hide button to Close and remove Cancel.
| 5 |
1,631 |
TISTUD-5387
|
09/13/2013 21:37:47
|
Platform Config Wizard: Change "Finish" button to "Configure"
|
In the initial page, "Configure" makes more sense as an action than "Finish".
| 1 |
1,632 |
TISTUD-5388
|
09/13/2013 21:46:11
|
Platform Config Wizard: create a gradient effect from the platform section to its settings section
|
To improve the background transition from the main platform section to settings section, a suggestion is to add a gradient in the middle.
| 5 |
1,633 |
TISTUD-5389
|
09/13/2013 21:53:22
|
Platform Config Wizard: improve the wizard image
|
Tyrus provided the attached image to replace the gear.
| 2 |
1,634 |
TISTUD-5390
|
09/13/2013 21:57:20
|
Platform Config Wizard: Align the start of text in settings section with the platform entry
|
The screenshot shows the left bound of settings section matches with the checkbox. The suggestion is to match it with platform name instead. If that causes too much space on the left visually, then we will revert to implement based on this screenshot.
| 5 |
1,635 |
TISTUD-5392
|
09/13/2013 22:05:20
|
Have a separate progress job for the platform configuration process
|
Besides the progress bars inside the platform config wizard, we should have a progress job for the overall process as well so it would be available in Progress view, and if user hides the wizard and loses it for some reason, they could still check on the progress in Progress view.
| 5 |
1,636 |
TISTUD-5393
|
09/13/2013 22:12:01
|
Show a toast when platform configuration process completes
|
When platform configuration process completes, if the wizard is still up, user could just check on the status there, but if user hide the wizard, we should show a toast with message like "Platforms are configured. Please click to see more details." When user clicks on the toast, we will re-open the platform config wizard that shows the status and installation location for each platform.
| 5 |
1,637 |
TISTUD-5395
|
09/13/2013 22:55:07
|
Platform Config Wizard: Progress page: use the stop icon for cancel
|
The current cancel icon looks disabled. The suggestion is to use the stop icon seen in Console and Debug views.
| 2 |
1,638 |
TISTUD-5400
|
09/16/2013 23:44:24
|
Show link in the progress job to open the configuration wizard
|
If the platform configuration wizard is hidden, then we show the toast message to get back the hidden dialog. However, if the user accidentally closes the toast message, then there is no way to get back the configuration wizard dialog. - As the Eclipse jobs support adding a link with the progress task, add a link in the progress job to allow users to open the hidden configuration wizard dialog. - Parameterize the command so that the wizard dialog shell can be passed around to display back the wizard dialog.
| 5 |
1,639 |
TISTUD-5403
|
09/18/2013 06:19:16
|
Platform Config Wizard: Keep status icons and messages vertically-aligned respectively
|
The latest screenshot from Tyrus was indicating we wanted to make the middle column center-aligned, and we implemented as part of TISTUD-5385. However, with everything else vertically aligned, it seems to make more sense if we keep both status icons and status messages vertically aligned respectively, while still keeping the overall column as centered as possible.
| 3 |
1,640 |
TISTUD-5408
|
09/18/2013 23:44:16
|
Update JDK version included in Studio installer to JDK7
|
We currently include JDK6 in Studio installer. Since we confirmed Studio and SDK work with JDK7, we should update the version.
| 5 |
1,641 |
TISTUD-5416
|
09/20/2013 15:38:00
|
Make npm packages required installs and not allow user to dismiss required installs
|
We currently prompt for some required installs/updates but not in some cases. An example is that if the user has no Titanium SDK installed we will silently install one for them. But we prompt the user to install Titanium SDK updates, NPM packages (and updates), Node.js. If a given component is required, we should not allow the user to dismiss the install - thus helping to avoid invalid setups because user's didn't accept. Obviously, this will still force sudo prompts on Mac/Linux for some of the installs right now (since npm packages are installed globally, and I think we need sudo rights for installing Node?). From Aditya: {quote} I can't count the number of times over the past several weeks where we have worked with every developer, tester, partner etc. and they only complete half the setup because they don't read the docs. E.g. "Oh I need Xcode/Android sdk?" or "Oh I ignored that failure message on setting up node.js" or "oh I need to accept and install all the updates from Studio?" {quote}
| 5 |
1,642 |
TISTUD-5417
|
09/20/2013 15:39:42
|
Inconsistent PATH lookup for Node and other components
|
From Aditya: {quote} We also run into issues where the system path has been changed by the dev for some components (e.g. Node.js) but is not the same as the path that we check for our updates, which causes challenges when running updates. This pathing issue is both a Mac issue (where they edit their .bash profile and install paths e.g. VMware put node in /opt instead of the default location and then the installer went into loop checking for node updates and installing) and Windows issue (where IT redirects installs from the user directory to some other path that they standardize on an NFS share for all end users) {quote} I think we need more details here. Are they installing multiple Node.js installations? Does this mean they're pointing at a specific install in the prefs but we're not honoring it? Are we just not picking up existing installs?
| 5 |
1,643 |
TISTUD-5418
|
09/20/2013 15:46:10
|
Add detection of existing BlackBerry installs
|
Right now we force the user to set the path to their BlackBerry install and then we "double-check" it by looking in a known location for the list of installs and matching the path value. The configuration wizard helps in providing default paths that are common for OSes, but still requires the user to go through the wizard (and assumes they have installed to this known default path). Instead we can simply look at the config path where BlackBerry has a listing of SDK installs. We should schedule a job on startup to do this if no valid value is set in prefs. {{BlackBerrySDKLocator.getBlackBerryConfigurationPath()}} and {{SdkManagerActionUtils.getQNXConfigurationPath()}} both deal with looking at this known location and reading the XML files listing the installs.
| 5 |
1,644 |
TISTUD-5419
|
09/20/2013 15:49:40
|
Improve detection of existing Node.js installs using registry on Windows
|
Our current detection of Node.JS looks in the PATH and some known default locations: For Windows: {code} private static final String PROGRAM_FILES_X86_NODEJS_NODE_PATH = "%ProgramFiles(x86)%\\nodejs"; //$NON-NLS-1$ private static final String PROGRAM_FILES_NODEJS_NODE_PATH = "%PROGRAMFILES%\\nodejs"; //$NON-NLS-1$ {code} For Mac/Linux: {code} private static final String USR_LOCAL_BIN_NODE = "/usr/local/bin"; //$NON-NLS-1$ {code} While that should generally pick up installs if the user's PATh is set properly, it's also possible we can grab information on Node installs from the Windows registry.
| 5 |
1,645 |
TISTUD-5421
|
09/20/2013 20:40:45
|
If user has error in advanced settings and unchecks platform, they're still unable to proceed
|
If I enter a bad path to Android SDK (not writable or file already exists at that path), then decide to uncheck Android - the wizard won't let me proceed because of the sdk path error.
| 3 |
1,646 |
TISTUD-5422
|
09/20/2013 20:51:33
|
UI blocked during install of Selected Platform SDK
|
I added Tizen in my tiapp and saved. I was then prompted to set up Tizen, so I chose to. It started installing in the wizard and showing progress. I chose "Hide" and saw that the UI is now "blocked". I get a black and white ball when I try to interact with the tiapp editor, change editor tabs, change view tabs. I think this may only happen if the wizard is invoked during the tiapp save?
| 5 |
1,647 |
TISTUD-5423
|
09/20/2013 21:52:09
|
Invalid thread access exception while changing the tiapp sdk preference
|
I have notice the below exception after playing around with tiapp file and sdk locations. ENTRY org.eclipse.equinox.preferences 4 2 2013-09-20 13:48:35.238 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences". !STACK 0 org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.SWT.error(SWT.java:4283) at org.eclipse.swt.widgets.Widget.error(Widget.java:783) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:574) at org.eclipse.swt.widgets.Combo.getSelectionIndex(Combo.java:888) at org.eclipse.jface.viewers.ComboViewer.listGetSelectionIndices(ComboViewer.java:124) at org.eclipse.jface.viewers.AbstractListViewer.getSelectionFromWidget(AbstractListViewer.java:280) at org.eclipse.jface.viewers.StructuredViewer.getSelection(StructuredViewer.java:1045) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppSDKSection.getSupportedPlatformSDKs(TiAppSDKSection.java:436) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.updateControlsEnablement(TiAppDeployTargetsSection.java:370) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection$1.preferenceChange(TiAppDeployTargetsSection.java:167) at org.eclipse.core.internal.preferences.EclipsePreferences$3.run(EclipsePreferences.java:896) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:899) at org.eclipse.core.internal.preferences.EclipsePreferences.put(EclipsePreferences.java:912) at com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.setSDKPath(BaseMobilePlatformConfigurer.java:102) at com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.doConfigure(BaseMobilePlatformConfigurer.java:68) at com.appcelerator.titanium.tizen.ui.configuration.TizenSDKConfigurer.doConfigure(TizenSDKConfigurer.java:77) at com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.configure(BaseMobilePlatformConfigurer.java:44) at com.appcelerator.titanium.ui.wizard.PlatformsConfigurationWizard$1.run(PlatformsConfigurationWizard.java:119) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
| 3 |
1,648 |
TISTUD-5424
|
09/20/2013 21:54:13
|
NPE while creating Android advance section details
|
There are series of NPEs while opening and playing around with the platform configuration wizard : !ENTRY com.appcelerator.titanium.android.ui 2 0 2013-09-20 11:52:15.304 !MESSAGE (Build 3.2.0.201309201506) [WARNING] null !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.android.internal.ui.update.SDKReleaseProvider.collectMainRepositoryItems(SDKReleaseProvider.java:386) at com.appcelerator.titanium.android.internal.ui.update.SDKReleaseProvider.getReleases(SDKReleaseProvider.java:103) at com.appcelerator.titanium.android.internal.ui.update.SDKReleaseProvider.getEligiblePlatformReleases(SDKReleaseProvider.java:503) at com.appcelerator.titanium.android.internal.ui.configuration.AndroidSDKComposite$1.run(AndroidSDKComposite.java:89) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
| 3 |
1,649 |
TISTUD-5425
|
09/20/2013 22:20:23
|
Improve the advance section layout of platforms configuration page in new mobile wizard
|
In the new mobile project wizard, if the unconfigured platforms are selected, it adds a new page for configuring the platforms. The layout of advance details section has to be improved to remove the empty space (as shown in the screenshot).
| 5 |
1,650 |
TISTUD-5431
|
09/23/2013 23:20:25
|
Node Package Installer: application npm install location is incorrect
|
1. Delete Global Appcelerator NPM Packages. 2. Install Titanium/Appcelerator Studio. 4. Run Studio and accept npm package updates. Result: The updates are locally installed to a folder other than the one studio was run from. See screenshot. Expected Result: The updates are globally installed. Note: If you try to run studio commands that require the npm packages, they will fail. {code} Launching simulator process failed Unable to locate the CLI executable. Please restart Studio or use Help > Check for Appcelerator Updates to install Titanium CLI. {code} Studio looks here no matter what (and the commands fail): {code} /Applications/Appcelerator/Appcelerator_Studio_3.1.3/AppceleratorStudio.app/Contents/MacOS/Password:/usr/local/lib ├── [email protected] ├── [email protected] ├── [email protected] └── [email protected] {code} Workaround: {code} npm set prefix /usr/local {code}
| 8 |
1,651 |
TISTUD-5433
|
09/24/2013 19:21:24
|
Unable to run a Mobile Web project with Studio 3.2.0
|
ENVIRONMENT: Titanium Studio, build: 3.1.3.201309132423 Appcelerator Studio, build: 3.2.0.201309202153 TiCLI from master 9/18 node-appc from master 9/18 TiSDK 3.1.3.GA and 3.2.0.v20130918150842 Chrome Version 29.0.1547.65 Android 4.2.2 Emulator REPRODUCTION: Create a default project in Studio 3.2.0 and run for Mobile Web in the Browser or Emulator. RESULTS: Receiving a "Wait for <IP_ADDRESS>" message in the browser. App does not run. NOTE: Works fine for Studio 3.1.3 and TiSDK version did not matter.\ Attaching complete diagnosis test and console log of build.
| 5 |
1,652 |
TISTUD-5434
|
09/25/2013 00:03:48
|
Avoid installing npm packages globally
|
Studio should install npm packages locally into a folder accessible to the user without sudo permissions (to avoid problems described at TISTUD-5428) In order to accomplish this - 1) Currently we set global flag for any npm package installation. Mark all actions with npm packages without global to make them local installations. 2) The npm packages can not be installed/queries in the .titanium or .npm folders under home directory. The folder name can not start with dot. 3) Remove the check for alias bin files in the /usr/local directory - as the local installation will not create symlink files in /usr/local directory. 4) Cleaning the cache sometimes requires sudo permissions - so we still need to prompt for password. However, use this password only for cleaning the cache.
| 8 |
1,653 |
TISTUD-5441
|
09/26/2013 18:38:17
|
Studio doesn't disable platforms that aren't supported by the Titanium SDK version
|
Our New project wizard and the tiapp editor, we changed to allow users to be able to select "unconfgiured/uninstalled" platforms. We did so by forcing any status validation down to an info level and never disabling platforms. The reality is that there is a definite case where platforms need to be disabled: when the Titanium SDK version chosen has no support for that platform.
| 3 |
1,654 |
TISTUD-5444
|
09/27/2013 01:37:01
|
Improve the performance of Build workspace job
|
The build workspace job is constantly invoking the external process to query the version of node and modules prefix path. The Studio log contains a series of references to the external processes during workspace build operation. !ENTRY com.aptana.core 1 0 2013-09-26 17:12:16.378 !MESSAGE (Build 0.0.0.qualifier) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/node" "-v" Working directory: null Environment: null !ENTRY com.aptana.core 1 0 2013-09-26 17:12:16.417 !MESSAGE (Build 0.0.0.qualifier) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/node" "/usr/local/bin/npm" "config" "get" "prefix" Working directory: null Environment: null Since the values of these parameters are unlikely to change, we should cache those values and reuse them for every inquiry.
| 5 |
1,655 |
TISTUD-5446
|
09/28/2013 00:24:26
|
Show EULA dialogs when the platform is installed through new mobile wizard
|
We currently show the EULA dialog only when the platforms are installed through Platform configuration wizard. However, if the platforms are initiated to get installed through new mobile app or module wizard, then the EULA dialog is not prompted to the user.
| 3 |
1,656 |
TISTUD-5452
|
09/30/2013 23:45:40
|
Modify launch shortcuts to use device profiles rather than generic iPad/iPhone sim targets
|
We currently have generic "iPhone Simulator", "iPad Simulator", "Android Emulator" shortcuts defined for generating pre-canned launch configs. We need to move towards pre-defined "device profiles". The first step is replacing these generic shortcuts with ones for target devices, like "iPhone 3.5-inch" or "iPhone 4" (the same listing as XCode). These launch shortcuts will pre-populate the config attributes to toggle tall/retina/etc flags for the user.
| 8 |
1,657 |
TISTUD-5453
|
09/30/2013 23:47:44
|
Modify the config UIs to have combo boxes for device profiles rather attribute checkmarks for tall/retina
|
Once we have device profiles defined (by CLI, and given to us by "ti info"?). We should replace the current UI we have in launch configs for tall/retina with a combobox to select from the device profiles. We should "migrate" existing configs to pre-select the most applicable/relevant device based on settings. We'll likely also need to pass the device name down to the CLI (or expand out it's args and pass those?)
| 8 |
1,658 |
TISTUD-5454
|
09/30/2013 23:49:21
|
Collapse the Run/Debug/Profile/Test/Package icons into UI like XCode/Momentics
|
We have each mode broken out as it's own pulldown menu. We should adopt the XCode/Momentics UI where there's a giant "play"/Run button that is pulldown to select mode (and clickable to launch), and then a trailing combo with the shortcuts/targets to launch. Decision is to not mimic the big stop button for now (and handle version later). This will be available in the global toolbar, and the corresponding icons will be removed from local toolbar of App/Project Explorer.
| 8 |
1,659 |
TISTUD-5455
|
09/30/2013 23:50:16
|
Remember last mode/config per-project and change UI to last one when project selection changes
|
Once we have the new UI, we should remember the last launched mode/target/config for each project and when project selection changes reset the Ui to match the last chosen for that project.
| 5 |
1,660 |
TISTUD-5457
|
10/01/2013 00:24:45
|
Combine update mechanisms
|
We currently have two major update mechanisms, prompts and UIs. We have our own for NPM packages, Node, SDK - and then we have the standard eclipse p2 mechanism for updating Studio and plugins. The result is two separate prompts, two separate UIs and an inconsistency in installation. We want to only prompt once, all at the same time and be able to resolve dependencies between the two systems (i.e. if the CLI makes a breaking change that requires a new studio update).
| 8 |
1,661 |
TISTUD-5459
|
10/01/2013 22:31:24
|
Combine our update popups
|
We currently have two separate update popups/checks: one is the Eclipse p2 update check and will update Studio itself. The second is our own check for updates to NPM packages, the SDK and other modules/components. This results in an inconsistent UI. We should ideally update Studio through the same update check job and UI. There are wiki pages devoted to how you can alter p2 behavior at http://wiki.eclipse.org/Equinox/p2/Adding_Self-Update_to_an_RCP_Application#Reassembling_the_UI The basic gist of it is that we may want to copy and fork the p2.ui.sdk.scheduler plugin rather than just include it. That includes the standard automatic updates check and popup. We can then make our version do both checks and present our own UI. Another alternative is to write p2 repository related code to allow loading the SDK metadata/artifacts and NPM package metadata/artifacts and converting them into the p2 model. That would make the same check for update job check all of them, but we'd still need our own custom UI override (though we may then be able to add metadata to the CLI package.json to do dependency checking against Studio?).
| 8 |
1,662 |
TISTUD-5462
|
10/02/2013 22:46:47
|
The default user agents for Alloy and Node.ACS should refer to mobile platforms
|
The current default preferences for Alloy and Node.ACS project's user agent refers to the browsers such as Chrome, Firefox and IE. For Titanium and Appcelerator Studio, the default user agent should refer to mobile platforms (such as Android, iOS and others if required).
| 3 |
1,663 |
TISTUD-5465
|
10/04/2013 00:50:26
|
Studio freezes for a moment when loading Deploy Targets section of tiapp editor
|
If Studio is closed with an active TiApp editor, then during the restart of Studio, it tries to activate the TiApp editor from the previous session. While it tries to open the TiApp editor, it ends up in loading the Android AVDs and that causes freeze momentarily. Here is the stacktrace excerpt during the startup of Studio : at com.aptana.core.util.ProcessUtil.processData(ProcessUtil.java:232) at com.aptana.core.util.ProcessUtil.processData(ProcessUtil.java:187) at com.aptana.core.util.ProcessUtil.processResult(ProcessUtil.java:142) at com.appcelerator.titanium.core.cli.NodeJSExecuter.runCommand(NodeJSExecuter.java:210) at com.appcelerator.titanium.core.cli.NodeJSExecuter.runCommandWithNoLogin(NodeJSExecuter.java:410) at com.appcelerator.titanium.android.core.launching.AndroidNodeJSCommandsHelper.getAndroidTargets(AndroidNodeJSCommandsHelper.java:118) at com.appcelerator.titanium.android.core.AndroidSDKLocator.getAVDs(AndroidSDKLocator.java:254) at com.appcelerator.titanium.android.core.AndroidSDKLocator.initialize(AndroidSDKLocator.java:132) at com.appcelerator.titanium.core.mobile.SDKLocator.lazyInitialize(SDKLocator.java:149) - locked <7b0ae4158> (a com.appcelerator.titanium.android.core.AndroidSDKLocator) at com.appcelerator.titanium.core.mobile.SDKLocator.getAvailable(SDKLocator.java:274) at com.appcelerator.titanium.core.internal.mobile.MobilePlatformsRegistry$LazyMobilePlatform.configurationStatus(MobilePlatformsRegistry.java:310) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.updateControlsEnablement(TiAppDeployTargetsSection.java:456) at com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.initialize(AbstractTiAppSection.java:72) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.initialize(TiAppDeployTargetsSection.java:208) at com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.<init>(AbstractTiAppSection.java:55) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.<init>(TiAppDeployTargetsSection.java:144) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppFormPage.createFormContent(TiAppFormPage.java:100) at org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:152) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150)
| 8 |
1,664 |
TISTUD-5467
|
10/04/2013 22:36:30
|
Clean up icons in the global toolbar
|
We want to go through each icon in the global toolbar and remove the ones rarely used by users. The suggestion is to remove the following: # Save # Save All # Print # Theme # Run/Debug/Profile/Test related actions (since we will re-design them in TISTUD-5454) # Open URL # Toggle Block Selection # Show Whitespace Characters
| 5 |
1,665 |
TISTUD-5468
|
10/04/2013 22:40:17
|
By default do not show text for the list of open perspectives in global toolbar
|
Momentics has the "Show Text" off by default, and it saves space in global toolbar.
| 2 |
1,666 |
TISTUD-5469
|
10/04/2013 22:44:05
|
Editor: remove the black folding gutter or color it correctly
|
We should find a way to not have the black gutter affect the visual appeal.
| 3 |
1,667 |
TISTUD-5470
|
10/04/2013 22:51:58
|
Remove App Explorer
|
The feeling is App Explorer doesn't add compelling value and feels redundant next to Project Explorer. We will hide/deprecate it from default Studio perspectives but keep the plugin.
| 3 |
1,668 |
TISTUD-5471
|
10/04/2013 22:54:35
|
Remove Local Filesystem from Project Explorer
|
It is unlikely user would use Studio to browse local filesystem, and Titanium development is very much project-based, so we should remove the node for Titanium/Appcelerator Studio. We will still keep it for Aptana Studio.
| 5 |
1,669 |
TISTUD-5472
|
10/04/2013 22:57:38
|
Enable global toolbar for the simple Studio perspective
|
Once we clean up the global toolbar and add the new UI for device profile, we should re-enable global toolbar for the simple perspective.
| 2 |
1,670 |
TISTUD-5473
|
10/04/2013 23:00:51
|
Default to only applying theme to editor
|
A suggestion is to only have the dark theme applied to editor. There is currently a preference to apply theme to all views, so maybe set it to false by default?
| 2 |
1,671 |
TISTUD-5477
|
10/04/2013 23:24:08
|
Re-skin Studio appearance
|
Chris presented a theme/skin that got raves from everyone. We should add it in Studio and make it the default. Once we receive additional feedback, we could tweak the default as needed.
| 8 |
1,672 |
TISTUD-5479
|
10/07/2013 06:36:15
|
Remove the thick dark stroke under global toolbar
|
See screenshot. There is a dark line under the global toolbar that we should try to remove or re-theme as part of TISTUD-5477.
| 5 |
1,673 |
TISTUD-5482
|
10/08/2013 00:35:09
|
Improve the loading time of TiApp editor
|
Currently opening tiapp editor takes a good few seconds, and when it's left open and Studio relaunches, loading it will contribute to the startup time. We should make opening the editor as fast as we could and move the time-consuming operations to the non-UI thread.
| 0 |
1,674 |
TISTUD-5483
|
10/08/2013 01:01:17
|
Profile TiApp editor for expensive operations that should be run on non-UI threads
|
We should run a profile session on opening TiApp editor and locate the bottleneck. Once located, we should move those operations to be run off the UI thread and have some indication to say the tiapp is loading.
| 8 |
1,675 |
TISTUD-5484
|
10/08/2013 01:01:47
|
Investigate and if necessary, improve the loading time of Build Properties section in TiApp
|
Investigate if loading tiapp's Build Properties section needs to be improved, and if so, move the time-consuming task to non-UI thread.
| 8 |
1,676 |
TISTUD-5489
|
10/08/2013 05:16:16
|
Appcelerator studio 3.2.0.201310071837 does not show possible platform run options when clicked on run.
|
h5.Description: 1.Create an app in appc studio 3.2.0.201310071837.Make sure you have all or more than one platforms enabled for the app. 2.Click on run button in studio. h5.Actual result: 1.We see 'run configurations' rather than a list of all possible run options according to the platforms (please refer to the screen shot attached). h5.Expected result: 1.We should see the list of all possible run options for the selected platforms.
| 5 |
1,677 |
TISTUD-5495
|
10/09/2013 04:50:40
|
Views revert back to white/light grey background on redraw when user has editor theme applying to views
|
h5.Description: 1. Verify new eclipse theme "Dashboard" is being used in Preferences > General > Appearance. 2. Turn on option to apply editor theme to views in Preferences > Studio > Theme. 3. Choose a theme with a dark/black background. Click OK. 4. Right click in a view like the Project Explorer. It will revert back to Dashboard theme's white/light grey BG rather than keeping the black bg from editor. h5.Actual Result: 1. View takes on white BG color. h5.Expected Results: 1. View retains the same BG as the editor.
| 5 |
1,678 |
TISTUD-5499
|
10/09/2013 19:10:51
|
Studio:Updates failed to install
|
"Installing Appcelerator Updates" failed during installation of Appcelerator Studio, Nightly build: 3.2.0.201310091613 h5.Test steps 1. Update Studio to Nightly 2. Check for Studio Updates h5.Actual result: Failed to install updates
| 8 |
1,679 |
TISTUD-5501
|
10/10/2013 06:45:28
|
Studio: Studio window cannot be focused at first time after launch
|
A Studio window and a Studio menu cannot be focused at first launch of Studio. h5.To reproduce 1. Launch Studio 2. Try to click anywhere inside of a Studio window or Studio menu(navbar) h5. Actual result A window cannot be focused h5.Expected result A focused Window h5.Work around Click anywhere outside of a Studio window and back inside.
| 5 |
1,680 |
TISTUD-5502
|
10/10/2013 12:23:02
|
Add release notes provider for Studio update
|
Since Studio updates now appear in the Titanium update wizard, it has to provide release notes in the wizard similar to Titanium SDK or other npm packages.
| 8 |
1,681 |
TISTUD-5503
|
10/10/2013 12:24:57
|
Add license text for Studio updates in update wizard
|
As Studio updates will now appear in the Titanium update wizard, users need to accept agreement terms before the Studio updates are installed through the wizard. The wizard already contains the ability to show the license if it is contributed by the release provider.
| 5 |
1,682 |
TISTUD-5504
|
10/10/2013 12:29:04
|
Disable the Studio updates from the Eclipse update popup
|
Eclipse p2 checks for updates during the startup of Studio and then shows a popup toast to allow install all the updates of the features/plugins. Since Studio updates will now appear in the titanium update wizard, the Eclipse update popup should appear for only non-studio related updates. We need to copy the p2 plugins (especially equinox.p2.ui.scheduler and may be, p2.ui.sdk - for modifying code that is invoked through UpdateHandler) and modify the p2 update checker code to filter out the install units containing the appcelerator specific to standalone.
| 5 |
1,683 |
TISTUD-5508
|
10/10/2013 18:50:19
|
Studio Dashboard - Dashboard will display a second view of the tab in the top left corner
|
h5.Description Upon opening titanium and going into the "Learn" tab of the dashboard a second window is placed inside the first window displaying all components on top of each other in the top left corner. Happens inconsistently. h5.Steps To Reproduce 1. Open Studio and wait for dashboard to load. 2. Select "Learn" h5.Result Window is displayed within the tab and the layout is a mess h5.Expected Result Tab should open and display all components in the correct place.
| 8 |
1,684 |
TISTUD-5510
|
10/10/2013 23:13:01
|
Studio Dashboard - Dashboard opens twice
|
h5.Description When Studio is opened, dashboard is opened twice. One displays an error, the other displays correctly. h5.Steps To Reproduce Unknown, occurs inconsistently. h5.Result Dashboard is displayed twice. h5.Expected Result Dashboard to work and only open once.
| 5 |
1,685 |
TISTUD-5513
|
10/11/2013 13:14:15
|
Titanium Studio: Links on Login Splash Screen not working.
|
Links such as "Forgot Password","Privacy Policy" and "terms and services" link on Login Splash Screen are not working. Links are not clikable.
| 5 |
1,686 |
TISTUD-5514
|
10/11/2013 17:17:30
|
Appcelerator Studio: Can not login with corporate HTTP Proxy
|
User can not login into Appcelerator studio behind his corporate proxy Attaching log file
| 8 |
1,687 |
TISTUD-5523
|
10/14/2013 19:16:33
|
Improve look and feel of Tab font in new UI
|
The current tab labels are distracting using a 14px font and black FG color. I originally developed the theme using https://github.com/jeeeyul/eclipse-themes to come up with the CSS. He wrote a custom CTabFolder renderer that supports additional options including the ability to set the color of the tab FG. I tried using the normal CSS route of e4 and it's not working. So we either need to bump down the font size (which also looks bad, IMO) or use a custom renderer (like maybe his, since it's EPL) and color the tab FG as #484850.
| 8 |
1,688 |
TISTUD-5526
|
10/14/2013 21:46:03
|
TiStudio: Alloy - Default Alloy project option does not appear when you want to create a new mobile app project
|
*Details:* Default Alloy project option does not appear when you want to create a new mobile app project. *This is a regression as this does appear on TiStudio 3.1.4.201310112035.* *Steps to reproduce:* 1. Make sure to be on TiStudio build 3.2.X 2. Right-click on the Project Explorer 3. Go to: New > Mobile App Project *Actual:* Alloy template is not an option (see 3.2.0_tistud.png) *Expected:* Alloy template should be an option when you create a new app (see 3.1.4_tistud.png)
| 5 |
1,689 |
TISTUD-5527
|
10/14/2013 23:11:07
|
Studio: Mobile Web Preview in Browser - failure to connect to internal server
|
Unable to preview default classic and alloy projects in browsers. *Regression*, does not occur in 3.1.3 Studio
| 5 |
1,690 |
TISTUD-5529
|
10/15/2013 17:59:51
|
Windows - Automatic updates get the wrong address
|
h5.Description When opening Studio and checking for updates it throws an error saying it cannot connect to the update sites. h5.Steps To Reproduce 1. Open Studio 2. Check for updates 3. Open Preference -> Install/Update 4. Check another update site and try that one h5.Result Cannot connect to update site h5.Expected Result Should connect to the update site and produce a list of updates +Extra Information+ The links to connect to the update site begins as http://preview.appcelerator.com/appcelerator This uses forward slashes "/" After this it uses \studio\standalone\update\/beta This uses back slashes "\" When it connects to the internet it changes the "\" to "%5C" So the final address is: http://preview.appcelerator.com/appcelerator%5Cstudio%5Cstandalone%5Cupdate%5C/beta
| 3 |
1,691 |
TISTUD-5531
|
10/16/2013 01:06:10
|
Console: Console view displays two colour:black and white
|
Test Steps: 1.Create a mobile project. 2.Run the project on emulator/simulator/ local server. 3.Observe the console view .screenshot attached. This ticket is to fix the issue long term (3.2.0 timeframe) with our new skin and old theming system.
| 5 |
1,692 |
TISTUD-5534
|
10/16/2013 21:41:41
|
iOS: Context Menu - In "Run As" and "Debug As" context menu, simulator.shorcut.label appears
|
*Details:* In "Run As" and "Debug As" context menu, %ipad.simulator.shorcut.label and %iphone.simulator.shorcut.label appears instead of the human readable labels. *This is a regression as this does not occur on Titanium Studio, build: 3.1.4.201310152018* *Steps to reproduce:* 1. Create new Titanium project 2. Right-click on the project 3. Go to either "Run As" or "Debug As" *Actual:* %ipad.simulator.shorcut.label and %iphone.simulator.shorcut.label appears instead of the human readable labels (see attachments). *Expected:* "iPad Simulator" and "iPhone Simulator" label should appear in the "Run As" and "Debug As" context menu.
| 2 |
1,693 |
TISTUD-5538
|
10/17/2013 19:08:03
|
TiApp: Deployment Targets - The spinners to the left of the Deployment Targets are frozen
|
*Details:* The spinners to the left of the Deployment Targets in the TiApp Editor do not spin after creating an app. *Steps to reproduce:* 1. Create a new app from Studio 2. Wait for the TiApp Editor to open *Actual:* The spinners to the left of the Deployment Targets do not spin (see no_spin.png) *Expected:* The spinners should spin and show the expected icons (see icons.png) *Note:* The expected icons appear if you switch to a different tab and back to the TiApp Editor tab; reopening the TiApp Editor does not fix the issue.
| 5 |
1,694 |
TISTUD-5539
|
10/17/2013 22:05:00
|
Android: Emulator: Remove Fastdev for 3.2.0+ SDK
|
We are deprecating FastDev in SDK 3.2.0+ Thus, we should remove the option to launch with FastDev enabled
| 3 |
1,695 |
TISTUD-5541
|
10/18/2013 13:57:42
|
Add packaging to new launch mode drop-down UI
|
The new UI has a drop down for mode, but we also wanted to add packaging to it. Technically packaging is not a mode. So we need to find some way to add that on as well.
| 8 |
1,696 |
TISTUD-5542
|
10/18/2013 18:25:14
|
Add e4 Theme picker to our Theme Preference Page
|
Add the e4 theme picker to our pref page (and label clearly one as "Overall" and other as "Editor") - so the user can modify themes/colors from the same place.
| 5 |
1,697 |
TISTUD-5543
|
10/18/2013 18:25:57
|
Create a dark e4 theme (that is similar to our new "Dashboard" theme)
|
We should have a dark e4 theme for users to choose from.
| 5 |
1,698 |
TISTUD-5544
|
10/18/2013 18:26:44
|
Remove the option to apply editor theme to views
|
The old theming hack and the new e4 themes do not play nice together. We should remove the option to apply the old theming outside the editor entirely.
| 8 |
1,699 |
TISTUD-5545
|
10/18/2013 18:27:35
|
Set new e4 and editor theme defaults
|
Set new defaults for e4 and editor themes? dark with dark or light with light. maybe different defaults for TiStud vs AppcStud. Seems like community may prefer dark themes, enterprise light.
| 3 |
1,700 |
TISTUD-5547
|
10/18/2013 20:29:27
|
Mobile Web: Run Configurations doesn't allow to use other browser than the default one
|
When I open Run Configurations, and try to set my Web Browser for a Mobile Web Previewer configuration, Appc will only work if I choose "Default system web browser". If I choose Chrome, IE, or Firefox, I see the following error when I run the app: "Could not launch external web browser for http://127.0.0.1:8020/index.html. Check the Web Browser preferences."
| 5 |
1,701 |
TISTUD-5551
|
10/20/2013 08:16:31
|
NullPointerException trying to run simulator for a project
|
!ENTRY org.eclipse.core.jobs 4 2 2013-10-20 00:14:07.754 !MESSAGE An internal error occurred during: "Launching Appcelerator iPhone Simulator - foobar". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.mobile.cli.IOSCommandsHelper.getIOSTargetDevice(IOSCommandsHelper.java:368) at com.appcelerator.titanium.mobile.cli.nodejs.IOSNodeJSCommandsHelper.runOnSimulator(IOSNodeJSCommandsHelper.java:358) at com.appcelerator.titanium.mobile.cli.nodejs.NodeTitaniumSDKCommandsHandler.run(NodeTitaniumSDKCommandsHandler.java:578) at com.appcelerator.titanium.mobile.ui.iphone.launch.IOSSimulatorLaunchConfigurationDelegate.launch(IOSSimulatorLaunchConfigurationDelegate.java:66) 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)
| 3 |
1,702 |
TISTUD-5552
|
10/21/2013 06:25:10
|
Update Studio themes using the new capability provided in Eclipse 4.x
|
Eclipse 4.x provides CSS styling to theme the visual appearance. We should take advantage of it and incorporate with or replace our existing theming support as necessary. This is the umbrella ticket for the feature.
| 0 |
1,703 |
TISTUD-5556
|
10/21/2013 21:20:01
|
Platform Config Wizard: remove the requirement of having Android 2.3.3 installed
|
The new CLI for Android build no longer requires Android 2.3.3. User would still need it for pre-3.2.0 Titanium SDKs, but we don't need to install 2.3.3 by default in the platform configuration wizard. This is to not have the checkbox selected by default, make it selectable, and remove the info icon next to the version.
| 3 |
1,704 |
TISTUD-5557
|
10/21/2013 22:28:52
|
Error in Studio log on "cannot find templates/release_notes.html"
|
See the following exception when starting up Appcelerator Studio 3.2.0.201310181700: {code} !ENTRY com.appcelerator.titanium.update.core 4 0 2013-10-21 14:20:37.200 !MESSAGE (Build 3.2.0.201310181700) [ERROR] Cannot find templates/release_notes.html !STACK 0 java.io.IOException: Cannot find templates/release_notes.html at org.eclipse.core.internal.runtime.FindSupport.openStream(FindSupport.java:274) at org.eclipse.core.runtime.FileLocator.openStream(FileLocator.java:188) at com.appcelerator.titanium.update.core.DefaultReleaseNotesProvider.getTemplate(DefaultReleaseNotesProvider.java:136) at com.appcelerator.titanium.update.core.DefaultReleaseNotesProvider.applyTemplate(DefaultReleaseNotesProvider.java:117) at com.appcelerator.titanium.update.core.GitHubReleaseNotesProvider.getReleaseNotes(GitHubReleaseNotesProvider.java:88) at com.appcelerator.titanium.update.core.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:99) at com.appcelerator.titanium.update.ui.internal.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:453) at com.appcelerator.titanium.update.ui.internal.TitaniumUpdatePage.createControl(TitaniumUpdatePage.java:518) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) at org.eclipse.jface.window.Window.create(Window.java:432) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) at com.appcelerator.titanium.update.ui.internal.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:66) at com.appcelerator.titanium.update.ui.TitaniumUpdateStartup$1$1$1.openMessageDialog(TitaniumUpdateStartup.java:81) at com.aptana.ui.util.UIUtils$3.runInUIThread(UIUtils.java:498) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) at org.eclipse.swt.widgets.Display.observerProc(Display.java:3566) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4918) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5296) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1101) at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1093) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5556) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2104) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2318) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5620) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5057) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5206) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3648) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) {code}
| 3 |
1,705 |
TISTUD-5559
|
10/22/2013 00:49:13
|
Project explorer: The project cannot be imported from git, Titanium SDK could not be found
|
The git project cannot be imported, if SDK it was built with is not in mobilesdk folder. h5.To reproduce Using project explorer (right click), Import > Appcelerator> Existing Mobile Project h5.Actual result The error Titanium SDK could not be found h5.Expected result Projects should be imported successfully Note: This is *regression*, in Studio 3.1.4 SDK is being updated to the latest build and import is successful
| 5 |
1,706 |
TISTUD-5561
|
10/22/2013 03:17:02
|
Studio finds the globally installed npm packages over the local ones
|
If the npm packages are globally installed through command line, then Studio will recognize the npm packages that are installed globally rather than the local ones (in .npm directory). Since the executable is available in the system PATH, they are found prior to the common locations path.
| 3 |
1,707 |
TISTUD-5562
|
10/22/2013 05:42:55
|
The mode and device dropdowns in Studio global toolbar are not populated until a selection is made in Project Explorer
|
When I updated to the latest 3.2.0 build (Appcelerator Studio, build: 3.2.0.201310181700), the global toolbar does not show any items in the mode and device dropdowns. Only when a project is selected in Project Explorer, both combo-boxes would then get populated.
| 5 |
1,708 |
TISTUD-5563
|
10/22/2013 09:16:01
|
Intermitant issue : Appcelerator Studio gives null pointer exception on Restart
|
I was trying to update Studio by following the below steps when I faced this issue: 1. From the Help menu, select Install New Software... to open an Install pop-up window. 2. In the Work with: text box of the Install window, type the URL http://ec2-50-16-19-245.compute-1.amazonaws.com/appcelerator/appc-studio/standalone/update/nightly/ for the update site, and hit the Enter key. Close the Install window. 3. From the Help menu, select Check for Updates. 4. After successful update Studio prompts for Restart. 5. Restart 6. Observe the attached screen shot for the Null Pointer Exception I encountered on Studio restart Also I faced the same issue when I run a mobile project using iOS simulator and restarted my Studio. Please refer the attached log file and screen shot for further reference.
| 5 |
1,709 |
TISTUD-5566
|
10/22/2013 11:55:21
|
Unable to Profile a Mobile App Project using iOS simulator
|
Steps Followed: 1. Create a Mobile App Project 2. Try to Profile it by Project Context Menu >> Profile as >> iOS(iPhone/iPad simulator) Actual Results: It fails prompting an error message on the screen. Pleaser refer the attached log file and screen shot for further reference.
| 5 |
1,710 |
TISTUD-5567
|
10/22/2013 12:29:00
|
Code Analyzer : Fails with a missing plugin error prompt
|
Steps Followed: 1. Create a Mobile App Project 2. Try to run Code Analysis using any of the options available in the Project Context Menu >> Code Analysis >> iOS(iPhone/iPad)or Multiple or Android Actual Results: It fails prompting an error message on the screen. Pleaser refer the attached log file and screen shot for further reference.
| 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.