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
|
|---|---|---|---|---|---|
511 |
TISTUD-1884
|
07/09/2012 18:34:28
|
Add CLI support to check for available SDK commands
|
V2 (Node.js) CLI will support querying for command availability. This would be a check we can do against a SDK to see if a new command is supported by a particular version. For example, rather than doing a version check, we can query the SDK to see if the command "clean" is available. {code} titanium available [--command|--feature|--platform] [--version] [--sdk=sdk-version] name {code} _Note:_ We may want to consider how we define the versioning of the CLI. Will it have a different version, or will it map to an SDK version. _V1 CLI does not support this feature._
| 8 |
512 |
TISTUD-1886
|
07/09/2012 18:39:38
|
Add CLI command support for building a mobileweb project
|
This one is only for V2 (Node.js). The Python implementation in V1 does not support a building command. We should try call "build" again when we've cleaned all our projects and build automatically is checked. The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed. {code} titanium build --platform [iphone,ipad,ios,android,blackberry,mobileweb,etc.] --sdk <value> [--build-type [production | development | test]] [--log-level [trace | debug | info | warn | error]] --dir <project-path> {code}
| 8 |
513 |
TISTUD-1888
|
07/09/2012 18:45:32
|
Add CLI command support for cleaning a project
|
Add "clean" support via the CLI commands extension. V1 (Python): {code} sdk-version/titanium.py clean Working directory: [project-dir] {code} V2 (Node.js): {code} titanium clean [project-dir] {code}
| 8 |
514 |
TISTUD-1890
|
07/09/2012 18:52:05
|
Add CLI command support to run a pre-requisite check
|
On V1 CLI support there are scripts that check for prerequisites. Android V1: {code} Process: android.sdk/android list targets Working directory: android.sdk {code} iOS V1: {code} sdk-version/iphone/prereq.py package Environment: DEVELOPER_DIR=ios.tools {code} There does not yet appear to be an analogue of these commands in V2 of the CLI. It's unclear how multiple commands that gather information like this would be structured.
| 13 |
515 |
TISTUD-1891
|
07/09/2012 19:01:02
|
Add CLI command support to run an Android project
|
We should support that for all platforms. h3. Run Android V1: {code:title=V1|borderStyle=solid} sdk-version/android/builder.py emulator name [android.sdk] [project-dir] id 6 HVGA sdk-version/android/fastdev.py start [project-dir] {code} V2: {code:title=V2|borderStyle=solid} titanium build --platform=[platform] --emulator=[emulator.name] [project-dir] titanium run --platform=[platform] --emulator=[emulator.name] [project-dir] {code}
| 8 |
516 |
TISTUD-1892
|
07/09/2012 19:09:31
|
Add CLI command support an Android debug launch
|
h3. Debug Android V1: {code} sdk-version/android/builder.py emulator [name] [android.sdk] [project-dir] [id] 6 HVGA sdk-version/android/fastdev.py start [project-dir] sdk-version/android/builder.py simulator [name] [android.sdk] [project-dir] [id] 6 HVGA /127.0.0.1:55040 {code} V2: {code} titanium build --platform=android --emulator=[emulator.name] [project.dir] titanium run --platform=android --emulator=[emulator.name] --debug [project.dir] {code} h3. Notes # We need to make sure that FastDev is supported by the new CLI
| 8 |
517 |
TISTUD-1893
|
07/09/2012 19:18:30
|
Add CLI command support for packaging Android applications
|
Add support for the packaging command via the CLI extension. V2: {code} titanium build --package --platform=[platform] [project.dir] {code} +create the V1 (need to investigate what it is)
| 8 |
518 |
TISTUD-1894
|
07/09/2012 19:20:51
|
Add CLI command support for packaging iOS applications
|
Add support for the packaging command via the CLI extension. V1: {code} sdk-version/iphone/prereq.py package Environment: DEVELOPER_DIR=ios.tools sdk-version/iphone/prereq.py package Environment: DEVELOPER_DIR=ios.tools sdk-version/iphone/builder.py distribute [ios.version] [project-dir] [id] [name] "C694789B-BEF5-49BE-800C-A5F4C8EADF5F" "Roland Muschenetz" "" "universal" Environment: DEVELOPER_DIR=ios.tools {code} V2. {code} titanium build --package --platform=ios sample {code}
| 8 |
519 |
TISTUD-1895
|
07/09/2012 19:23:01
|
Add CLI command support for packaging MobileWeb applications
|
Add support for the packaging command via the CLI extension. V1. {code} sdk-version/mobileweb/builder.py [project-dir] production Working directory: [project-dir] {code} V2. {code} titanium build --package --platform=mobileweb [project-dir] {code}
| 8 |
520 |
TISTUD-1897
|
07/09/2012 19:36:27
|
Add support for log-in and log-out for the V2 CLI
|
The V2 CLI requires log-in before execution. The implementation should probably log-in once per session with the credentials the user already provided for the studio. We'll need to make sure we log-out in case the user clicked the log-out. The Studio support a limited time of offline work, and we need to make sure that the platforms supports it as well.
| 8 |
521 |
TISTUD-1903
|
07/10/2012 09:18:59
|
Rebrand Node.js functionality as Appcelerator Custom Cloud Services
|
Existing Node.js functionality is labelled as a "Node.js" project. We need to replace that name with a new name in wizards, project descriptions and preferences (as appropriate)
| 8 |
522 |
TISTUD-1905
|
07/10/2012 09:25:50
|
Install nettle command-line package
|
Once a user has Node.js installed, we need to install the nettle package for ACS/Node.js deployment: * We need to check to see if the package is installed * If not, install it. {code} [sudo] npm install nettle -g {code} Suggestion is that we don't really know if we need to sun under sudo. We should try without, and then prompt the user if we fail in that case.
| 8 |
523 |
TISTUD-1934
|
07/10/2012 12:05:29
|
Add CLI command support for creating a module
|
h2. Module Creation V1: {code} sdk-version/titanium.py create --type=[module] --id=[id] --name=[name] --dir=[project-parent-dir] --platform=[iphone] Environment: ANDROID_SDK=[android.sdk], DEVELOPER_DIR=[ios.tools] {code} V2: {code} titanium create --platforms=[iphone,ipad,ios,android,blackberry,mobileweb,etc.] [--type=[module]] [--id=string] [--sdk=sdk-version] [--verbose|-v [0-5]] [--template=name] [--[no-]cloud] [--dir=dir] name {code} Reference: https://wiki.appcelerator.org/display/tools/Studio+support+for+new+Module+structure+and+CLI
| 0 |
524 |
TISTUD-1935
|
07/10/2012 12:30:43
|
Titanium Studio: Themes: unhandled event loop exception when changing theme
|
unhandled event loop exception when changing theme. log attached. I could not reproduce this issue, it is intermittent. Unknown if this is a regression. In this particular case, I was changing from the Aptana Studio theme to the Aptana Studio 2.x theme. Steps to Reproduce: 1. Open Preferences > Titanium Studio > Themes. 2. Change the theme using the drop-down menu. Actual Result: unhandled event loop exception in studio log. Expected Result: No errors in studio log.
| 3 |
525 |
TISTUD-1937
|
07/10/2012 12:31:54
|
Rework Template selection page UI
|
The first page of the new project wizard should prompt the user to select a template. the second page is the page that the users enters the app info (exists today) In the first page, add the ability to: * List all available Alloy templates (TISTUD-2057) * User should be able to select only one template * There should be an empty template. this template will create non Alloy apps (TISTUD-2070)
| 0 |
526 |
TISTUD-1939
|
07/10/2012 15:41:33
|
Add CLI command support to run an iOS project
|
We should support that for iOS. h3. Run iOS V1: {code:title=V1|borderStyle=solid} /usr/bin/killall" -2 "iPhone Simulator" /usr/bin/killall" -2 iphonesim /usr/bin/killall" -2 ios-sim sdk-version/iphone/builder.py simulator [ios.version] [project-dir] [id] Environment: DEVELOPER_DIR=ios.tools {code} V2: {code:title=V2|borderStyle=solid} titanium build --platform=ios --simulator=[ios.version] sample titanium run --platform=ios --simulator=[ios.version] --debug sample {code}
| 8 |
527 |
TISTUD-1940
|
07/10/2012 15:52:39
|
Add CLI command support an iOS debug launch
|
h3. Debug iOS V1: {code} /usr/bin/killall -2 "iPhone Simulator" /usr/bin/killall -2 "iphonesim" /usr/bin/killall -2 "ios-sim" sdk-version/iphone/builder.py simulator [ios.version] [project-dir] [id] [name] universal ipad 192.168.0.101:55205 Environment: DEVELOPER_DIR=ios.tools {code} V2: {code} titanium build --platform=ios --simulator=[ios.version] [project-name] {code} h3. Notes # For iOS, we may still need to call the _'killall'_ before the command.
| 8 |
528 |
TISTUD-1941
|
07/10/2012 15:57:36
|
Add CLI command support to run a MobileWeb project
|
We should support that for MobileWeb. h3. Run MobileWeb V1: {code:title=V1 (Browser)|borderStyle=solid} "sdk-version/mobileweb/builder.py" [project-dir] "development" Working directory: /Users/ingo/Documents/Aptana Studio 3 Workspace/MobileProject {code} V1: {code:title=V1 (Android Emulator)|borderStyle=solid} sdk-version/android/builder.py emulator [name] [android.sdk] [project-dir] [id] "6" "HVGA" sdk-version/android/wait_for_device.py [android.sdk] android.sdk/platform-tools/adb -e shell "rm /data/data/com.android.browser/cache/webviewCache/*" android.sdk/platform-tools/adb -e shell am start -a android.intent.action.VIEW -d 'http://10.0.2.2:8020/index.html' {code} V2: {code:title=V2|borderStyle=solid} Switch calling builder.py to the new CLI build command (related to TISTUD-1886); everything else stays the same (? may need to confirm with the CLI team) {code}
| 8 |
529 |
TISTUD-1944
|
07/10/2012 22:37:14
|
Replace Node.js images
|
We need to replace the current Node.js branding with new branding. * Project wizards * Icons * Project nature
| 8 |
530 |
TISTUD-1947
|
07/11/2012 14:30:08
|
Titanium Studio: Dashboard: Configure: Android Update: Cancel button does not cancel android update process
|
When the Android Configure utility is run from the dashboard, and the Android SDK is already installed, the Android-controlled update menu will not close when the Cancel button is pressed in Studio. This is not a regression. This is a usability issue. Screenshot and stack trace attached. Steps to Reproduce: 1. Open Titanium Studio. 2. Set the Android SDK in the Preferences if not set already. 3. Go to the Dashboard > Configure > Android > Update. 4. Press the Cancel button in the Studio process pop-up. Actual Result: The Android update menu launches and runs without interruption. Expected Result: Cancel should close the Android process, or prevent it from running.
| 5 |
531 |
TISTUD-1948
|
07/11/2012 15:25:06
|
Implement sign up process through Studio
|
implement sign up process through Studio. Flow should be: * option for selecting "new User" or "Existing user" * if New User show sign up form with fields: ** First, Last, email ,password, verify password, Agree to EULA, Submit or Cancel (Cancel takes you back to the first screen) ** Once submit show some visual indicator that there is progress * If existing user, then follow current flow (username / password) ** If new user sign up success, then auto login in Studio and launch dashboard (configuration wizard). Also show toaster, asking user to activate his account
| 13 |
532 |
TISTUD-1949
|
07/12/2012 07:57:19
|
Studio: Jira Username field looks cramped in Windows 7
|
When viewing the Submit a ticket window in Windows 7, the username and log out button seem to be squished with little or no white space between them. This does not happen on Mac OS. This is not a regression. Steps to reproduce: 1. Open the ticket submission form (Help > Titanium Studio > Submit a Ticket) Expected result: The Username portion should be correctly spaced out and be pleasing to look at. Actual result: On windows it looks cramped, seeming to be missing the white space found on the mac version.
| 3 |
533 |
TISTUD-1950
|
07/12/2012 09:45:32
|
Replace Message dialog notifying background job complete with toast popup
|
This is related to TISTUD-1817, where we tracked down the locations that opened up a Message dialog from a background thread. A more elegant method of displaying the notification is to use a popup toast to notify the user. The popup should only be used for INFO messages, for Question and Error we should still use the Message dialog Locations that this affects: -iOS/Android/MobileWeb project packaging -iOS/Android/MobileWeb module packaging (normal and deploy to project with changes) -Titanium SDK update -Publish -Android SDK update (dashboard)
| 8 |
534 |
TISTUD-1951
|
07/12/2012 16:06:28
|
Dashboard: Configure: Android: Improve OS Global Environment Variable detection
|
If the Dashboard Android Configuration Wizard is run without having the JAVA_HOME variable set, Studio provides no indication it needs to be set. There is only a pop-up indicating Android was downloaded successfully. Note that studio automatically detects JDK to run, but it does not forward this information to the Android SDK tools. There is no log info. This is not a regression. This is a usability issue. Steps to Reproduce: 1. Make sure JDK is installed. 2. Remove JAVA_HOME from the Global Environment Variables. 3. Make sure JAVA_HOME is no longer active (i.e., echo %JAVA_HOME%, echo $JAVA_HOME from the console). 4. Run Titanium Studio. 5. Make sure the Android SDK path is set in the Titanium Studio Preferences. 5. Run Dashboard > Configure > Android > Install/Update. Actual Result: A pop-up appears indicating Android was downloaded successfully every time Update is run. Expected Result: Either the Android SDK Update utility should run, Titanium Studio should set JAVA_HOME, or Titanium Studio should prompt the user to set JAVA_HOME.
| 8 |
535 |
TISTUD-1953
|
07/13/2012 16:13:20
|
Change AppID validation to only allow upper and lower letters (A-Z, a-z), digits (0-9), and period '.'
|
Steps to reproduce: 1. Create default TiMobile app 2. During creation of default app, include an underscore in the application id name e.g.: com.appcelerator.test_1 3. Install app to device Actual: In the console, will get CFBundleIdentifier error. See attachment. Expected: Replace underscores with dashes in the app ID. Note: * You can launch app to iOS simulator without any issues * You can install to Android device without any issues A similar issue happens if you have a '-' in the app id. In order to have the widest cross-platform appIDs, we can only allow upper and lower letters (A-Z, a-z), digits (0-9), and periods '.'
| 5 |
536 |
TISTUD-1954
|
07/13/2012 18:18:07
|
The order of deployment targets is inconsistent between the new project wizard and tiapp.xml editor
|
See the screenshots; the order of iPhone and iPad is reversed between the two. If we are listing them alphabetically, then the one in project creation wizard should be used.
| 2 |
537 |
TISTUD-1959
|
07/16/2012 11:59:27
|
PATH environment variable incorrect in python compiler plugins
|
h2. Problem When attempting to get the PATH environment variable while executing a python compiler plugin, the PATH is incorrect. It does not include the user's current PATH, it only shows the following: {code}/usr/bin:/bin:/usr/sbin:/sbin{code} This makes it difficult for the compiler plugin to execute programs that are on the developer's PATH. h2. Test Case *plugins/path.test/plugin.py* {code:python} import os def compile(config): print os.environ['PATH'] {code} *tiapp.xml* {code:xml} <plugins> <plugin version="1.0">path.test</plugin> </plugins> {code} The output of the above can be found in the console log. Every time I run it, I get the same result, which does not reflect my full PATH variable: {code} [INFO] Detected compiler plugin: path.test/1.0 /usr/bin:/bin:/usr/sbin:/sbin {code} h2. Expected Behavior The above should output my current full PATH variable contents
| 8 |
538 |
TISTUD-1963
|
07/17/2012 16:11:40
|
Set "JS Editor" as default editor for *.tss files
|
The style files used in Alloy are a JSON derivative. For this reason we changed their extension from "json" to "tss". "tss" is short for "Titanium Stylesheet". While there are some improvements that can be made to syntax highlighting for "tss" files, the default "JSON Source Editor" editor works very well on them as is. For this reason, it would be good to have that editor be the default editor for all "tss" files opened in TiStudio.
| 2 |
539 |
TISTUD-1970
|
07/19/2012 11:34:00
|
Split "Nettle" feature into separate plugins
|
We've bundled together the node.js code and the nettle code in a single plugin. Instead, we should create: * com.appcelerator.titanium.acs.core * com.appcelerator.titanium.acs.ui and make those depend on the existing nodejs plugins.
| 5 |
540 |
TISTUD-1973
|
07/19/2012 17:43:02
|
Titanium Studio: SDK Updates: canceling extraction does not produce a warning
|
During an SDK update, if the extraction process is canceled, there is no longer an error message generated. This is a regression. This worked in 2.1.0. It is worth noting (not part of the regression) that the partially extracted SDK remains in the SDK folder, resulting in an invalid SDK. When the SDK is in this invalid state: It is still selectable by titanium projects, and if it is a stable release, it will not be recognized as needing an update. Steps to Reproduce: 1. Download any version of the SDK using a method such as: Help > Check for Titanium SDK Updates or Help > Install Specific Titanium SDK... 2. During the extraction process (which occurs after the downloading/fetching process), press 'Cancel'. Actual Result: No error dialog, no error logs. Expected Result: Error dialog pop-up and error logs, with a button allowing the user to open an explorer/finder window to the extracted location on disk (if they wish to remove it themselves)
| 8 |
541 |
TISTUD-1984
|
07/20/2012 16:53:21
|
Pass in JAVA_HOME to Python scripts
|
While testing "Build Acceptance TIMOB-7472-A Android Only", I attempted to build a default Titanium Mobile app (just the standard template) and I encounter the following problem: {noformat} [DEBUG] /home/qatester/.titanium/mobilesdk/linux/2.1.0.GA/android/titanium_prep.linux64 com.shastaqa.fresh1 /home/qatester/Titanium_Studio_Workspace/fresh1/build/android/bin/assets/Resources ui/common/ApplicationTabGroup.js ui/handheld/ApplicationWindow.js app.js ui/tablet/ApplicationWindow.js [ERROR] Program launch failed. Unable to locate Java VM. Please set JAVA_HOME environment variable. [ERROR] Unabled to prepare JavaScript for packaging. Error code 4. {noformat} I check and the $JAVA_HOME is set, but was not available to the Python script. Studio should check for the JAVA_HOME before beginning a build, check if it is correctly set, and if it is missing or incorrect pass in a correct version into the build. This issue is a not a regression since the bug is due to a user mis-configuration of JAVA_HOME. Steps used to reproduce: 1. Ensure that the $JAVA_HOME global variable is set ( ls -R $JAVA_HOME ). 2. Create a new Titanium Mobile Project. 3. Create a signing key. 4. Package for Distribution (Package > Distribute - Android App Store) Expected result: Android correctly packages and a package file is created in the specified place. Actual result: The packager gets to titanium_prep.linux64 where it can not find java as $JAVA_HOME isn't available to it. Tested by multiple sources on Titanium Studio build 2.1.1, 2.1.0, and 2.0.2 on both Ubuntu 12.04 and 10.04, using SDK 2.1.0GA replicated the same failure. Switching back to SDK 2.0.2GA fixes the issue in all studio platforms, as 2.1.0 is the first version to use JAVA_HOME in the packaging scripts. Suggested solution: * See if JAVA_HOME is set in such a way that the scripts can read it * If it is, check if the JAVA_HOME variable is correct by checking for /lib/tools.jar at that path * If it is incorrectly set, or not set, infer the JAVA_HOME location by using values from Studio's environment.
| 13 |
542 |
TISTUD-1980
|
07/23/2012 12:39:38
|
Package Node.js installer with Titanium Studio Windows installer
|
Similar to TISTUD-1825, we need to check and see if node.js is installed during the initial Studio install, and if not, run the node.js installer. Once we've updated TISTUD-2001, we just need to alter the installer to actually include the check. See the parent ticket for the URL from which to download the installer.
| 8 |
543 |
TISTUD-1982
|
07/23/2012 14:00:22
|
Titanium Studio: Progress View: 'Remove All Finished Operations' fails to remove operations, adds them back if they are gone
|
In the progress view, pressing the double x ('Remove All Finished Operations') will not remove the operations. If the operations are removed one-by-one, then the double x is pressed, they will re-appear. This is a regression. Works as expected in Ti.Studio 2.0.2 Steps to reproduce: 1. Create Multiple Ti.Mobile Projects 2. Open Progress window in Ti.Studio 3. Run the projects in Emulator or Simulator and close the emulator/simulator. 4. List of completed process is generated in "Progress" Window 5. Click on "XX" (Remove All Finished Project) 6. See Expected Result # 6. 7. Close progress view processes one by one by pressing cross "x" (Remove From View) icon on right 8. The processes should remove properly 9. Press "XX" (Remove All Finished Project) 10. See Expected Result # 10. Actual Result: 6."XX" (Remove All Finished Project) does nothing. 10. "XX" (Remove All Finished Project) brings back all processes that were removed previously. Expected Result: 6. Pressing "XX" (Remove All Finished Project) should remove all processes from the progress view. 10. There should be no list of project in the "Progress" view area.
| 8 |
544 |
TISTUD-1985
|
07/23/2012 16:15:09
|
Android Emulator: run config console level ignored on subsequent deployments
|
Android Emulator console log level is always set to the run config setting used to first launch the console process. Steps to Reproduce: 1. Create and run an android project in the emulator with the run configuration log level set to TRACE using code: {code} alert('SESSION ID: ' + Ti.App.sessionId); Ti.API.error('SESSION ID: ' + Ti.App.sessionId); Ti.API.trace('TRACE'); Ti.API.log('TRACE', 'TRACE'); Ti.API.debug('DEBUG'); Ti.API.log('DEBUG', 'DEBUG'); Ti.API.info('INFO'); Ti.API.log('INFO', 'INFO'); Ti.API.warn('WARN'); Ti.API.log('WARN', 'WARN'); Ti.API.error('ERROR'); Ti.API.log('ERROR', 'ERROR'); Ti.API.log('FREEFORM', 'FREEFORM'); {code} 2. Edit run configuration to log level ERROR and redeploy project. Actual Result: TRACE+ levels log to console. Expected Result: ERROR level should log to console, as per the current run configuration.
| 5 |
545 |
TISTUD-1986
|
07/23/2012 16:49:14
|
Ability to sort the certificates and provisioning profiles in Titanium Studio Preferences->Titanium->iOS platform
|
When, there are many certificates or multiple provisioning profiles, its really difficult to sort them. Please add sorting by clicking on the column name.
| 5 |
546 |
TISTUD-1990
|
07/23/2012 19:33:38
|
Titanium Studio: Console View: Log Level icon should respond to click events
|
In the console view, the log level icon does not respond to click events, only the small arrow to the right. This is a usability issue. Test Steps: 1. Run titanium project in iOS simulator. 2. Click log level icon in the console view. Actual Result: Nothing happens. Expected Result: Log level drop-down should appear.
| 5 |
547 |
TISTUD-1991
|
07/23/2012 20:09:02
|
Titanium Studio: Console View: iOS Custom Info Log Level does not display
|
Ti.API.log() calls with custom log levels no longer display in the studio console. For example: Ti.API.log('CUSTOM', 'CUSTOM'); This is a regression introduced in Studio 2.1.0. This did not affect Studio 2.0.2. Steps to Reproduce: 1. Run code in iOS Simulator: {code} alert('SESSION ID: ' + Ti.App.sessionId); Ti.API.error('SESSION ID: ' + Ti.App.sessionId); Ti.API.trace('1A. TRACE'); Ti.API.log('TRACE', '1B. TRACE'); Ti.API.debug('2A. DEBUG'); Ti.API.log('DEBUG', '2B. DEBUG'); Ti.API.info('3A. INFO'); Ti.API.log('INFO', '3B. INFO'); Ti.API.warn('4A. WARN'); Ti.API.log('WARN', '4B. WARN'); Ti.API.error('5A. ERROR'); Ti.API.log('ERROR', '5B. ERROR'); Ti.API.log('CUSTOM', 'CUSTOM'); {code} Actual Result: Custom log does not display. Expected Result: Custom log should display as [INFO] [CUSTOM] CUSTOM Note: The Android log levels display correctly.
| 8 |
548 |
TISTUD-2000
|
07/24/2012 09:41:34
|
Migration to Cascades R6: Update the condition for checking the content of the bbndk folder
|
The folder structure of the bbndk top folder has changed in R6, yielding the following message when trying to configure Studio with the path to the new ndk. "[BlackBerry NDK Home] Could not locate a required directory 'host' under the specified BlackBerry NDK root path '/Applications/bbndk'" The content of the top folder in the latest ndk is as follows and judging by the names, also subject to change before the official release: ll /Applications/bbndk/ total 24 drwxrwxr-x 10 jpl admin 340 20 Jul 12:35 . drwxrwxr-x+ 54 root admin 1836 20 Jul 13:27 .. -rwxr-xr-x 1 jpl admin 690 20 Jul 12:35 bbndk-env.sh -rwxr-xr-x 1 jpl admin 110 20 Jul 12:35 bbndk.command -rwxr-xr-x 1 jpl admin 210 20 Jul 12:35 bbndk_admin.command drwxr-xr-x 3 jpl admin 102 13 Jul 01:23 host_10_0_6_1 drwxr-xr-x 3 jpl admin 102 13 Jul 01:23 ide drwxrwxr-x 8 jpl admin 272 20 Jul 12:35 install drwxrwxr-x 4 jpl admin 136 20 Jul 12:35 licenses drwxr-xr-x 6 jpl admin 204 13 Jul 01:14 target_10_0_6_384
| 2 |
549 |
TISTUD-2004
|
07/24/2012 16:00:55
|
Studio: Startup: Error "Bad Padding" and "Failed to load Jira user credentials"
|
At startup in Ubuntu 12.04, my user name and password are not retained for future logins. This results in the user being forced to log-in every time the program restarts. The following is found in the log file: {noformat} !ENTRY com.aptana.ide.security.linux 4 0 2012-07-24 14:07:46.459 !MESSAGE Bad padding !STACK 0 javax.crypto.BadPaddingException: Given final block not properly padded at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811) at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676) at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:317) at javax.crypto.Cipher.doFinal(Cipher.java:1813) at com.aptana.ide.security.internal.linux.PasswordProvider.decrypt(PasswordProvider.java:251) at com.aptana.ide.security.internal.linux.PasswordProvider.getPassword(PasswordProvider.java:136) at com.aptana.ide.security.internal.linux.PasswordProvider.getPassword(PasswordProvider.java:67) at org.eclipse.equinox.internal.security.storage.PasswordProviderModuleExt.getPassword(PasswordProviderModuleExt.java:35) at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:259) at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224) at org.eclipse.equinox.internal.security.storage.SecurePreferences.get(SecurePreferences.java:262) at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.get(SecurePreferencesWrapper.java:106) at com.aptana.jira.core.JiraManager.loadCredentials(JiraManager.java:284) at com.aptana.jira.core.JiraManager.<init>(JiraManager.java:85) at com.aptana.jira.core.JiraCorePlugin.getJiraManager(JiraCorePlugin.java:63) at com.aptana.jira.ui.preferences.JiraPreferencePageProvider.getJiraManager(JiraPreferencePageProvider.java:218) at com.aptana.jira.ui.preferences.JiraPreferencePageProvider.isLoggedOut(JiraPreferencePageProvider.java:223) at com.aptana.jira.ui.preferences.JiraPreferencePageProvider.createContents(JiraPreferencePageProvider.java:83) at com.aptana.jira.ui.internal.SubmitTicketDialog.createDialogArea(SubmitTicketDialog.java:174) at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:155) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at com.aptana.jira.ui.handlers.SubmitTicketHandler.execute(SubmitTicketHandler.java:51) 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.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) !ENTRY com.aptana.jira.core 4 0 2012-07-24 14:07:46.460 !MESSAGE (Build 2.1.1.201207171343) [ERROR] Failed to load Jira user credentials !STACK 0 org.eclipse.equinox.security.storage.StorageException: No password provided. at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:304) at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224) at org.eclipse.equinox.internal.security.storage.SecurePreferences.get(SecurePreferences.java:262) at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.get(SecurePreferencesWrapper.java:106) at com.aptana.jira.core.JiraManager.loadCredentials(JiraManager.java:284) at com.aptana.jira.core.JiraManager.<init>(JiraManager.java:85) at com.aptana.jira.core.JiraCorePlugin.getJiraManager(JiraCorePlugin.java:63) at com.aptana.jira.ui.preferences.JiraPreferencePageProvider.getJiraManager(JiraPreferencePageProvider.java:218) at com.aptana.jira.ui.preferences.JiraPreferencePageProvider.isLoggedOut(JiraPreferencePageProvider.java:223) at com.aptana.jira.ui.preferences.JiraPreferencePageProvider.createContents(JiraPreferencePageProvider.java:83) at com.aptana.jira.ui.internal.SubmitTicketDialog.createDialogArea(SubmitTicketDialog.java:174) at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:155) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at com.aptana.jira.ui.handlers.SubmitTicketHandler.execute(SubmitTicketHandler.java:51) 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.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {noformat} Steps to reproduce: 1. Open Titanium Studio. 2. Log in to Titanium Studio. 3. Close (but do not log out of) Titanium Studio 4. Open Titanium Studio. This is a regression issue.
| 8 |
550 |
TISTUD-2007
|
07/25/2012 13:44:58
|
OpenShift: Domain 'null' is not found for user
|
# Signed in as an existing user, but did not specify a domain # Tried to create a project # Got the attached error (project was not created)
| 5 |
551 |
TISTUD-2029
|
07/26/2012 00:17:00
|
Unable to edit proxy schema in splash screen "Proxy Setup..."
|
Steps to reproduce: [As per setup instructions|http://docs.appcelerator.com/titanium/2.1/index.html#!/guide/Setting_up_Titanium_Studio-section-30086257_SettingupTitaniumStudio-LaunchingTitaniumStudio] 1. Clean TiStudio install with clean workspace/configuration. 2. Launch TiStudio 3. On the splash screen click "Proxy setup..." 4. Change Schema from HTTPS to HTTP Expected results: Text will be editable Actual results: Text is read-only Suggested fix: Provide a dropdown box of supported schema (HTTPS, HTTP, SOCKS) or inform user that HTTPS is the only supported schema (if this is the case).
| 8 |
552 |
TISTUD-2011
|
07/26/2012 16:40:10
|
Sign-Up Splash: make cursor change to hover on mouseover of hyperlinks
|
Currently the hyperlinks are active but appear as colored text. Add a hover to the items so the cursor changes to a "hand" to highlight the link nature. See main bug TISTUD-1948 for screenshots. We decided against underlines as they look busy in context.
| 5 |
553 |
TISTUD-2013
|
07/27/2012 10:15:29
|
Remove redundant Kitchen Sink sample(s) from Titanium Mobile ruble
|
The new Kitchen Sink version is designed to replace the 3 existing versions. Remove the Kitchen Sink iPad version, and if possible, also remove the Kitchen Sink Nook version. You will need to confirm with eric Merriman about whether or not we can leave the Kitchen Sink Nook version in.
| 3 |
554 |
TISTUD-2014
|
07/27/2012 10:25:56
|
Sign-Up Splash: Text unreadable in Windows 7
|
In windows the default text color is black which is hard to read on the blue background. See image for detailed view. Steps to reproduce: 1. While not logged in start Titanium Studio. Expected result: Text on the splash screen should be readable. Actual result: The default color makes the text hard to read.
| 5 |
555 |
TISTUD-2015
|
07/27/2012 12:26:55
|
Toolbar: Dashboard icon is not functional in new Titanium Studio window instance
|
Window > New Window new Titanium Studio window instance cannot open the dashboard. This is not a regression. There are no log messages. Steps to reproduce: # Titanium Studio > Window > New Window # Navigate on ToolBar in New window and Tap on "Dashboard" button ("Appcelerator" logo), or Help > Titanium Studio > Open Dashboard to open the dashboard. Actual result: Dashboard does not open. Expected Result: Dashboard should open.
| 5 |
556 |
TISTUD-2017
|
07/27/2012 15:39:44
|
Build: Android: Error while building Android application
|
While building for Android I setup my SDK, create a template project, select to build for Android, input a key file I generate using these instructions (link:http://developer.android.com/tools/publishing/app-signing.html#cert). Everything seems to be doing fine till it tries to sign the app. I get the following error: {noformat} [DEBUG] jarsigner -sigalg MD5withRSA -digestalg SHA1 -storepass qatesting -keystore /Users/shastaqa/my-release-key.keystore -signedjar "/Users/shastaqa/Documents/Test Project 1.apk" "/Users/shastaqa/Documents/Titanium_Studio_Workspace/Test Project 1/build/android/bin/app-unsigned.apk" "" [ERROR] Certificate chain not found for: . must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain. {noformat} Steps to reproduce: 1. Setup Android. 2. Create the key file (http://developer.android.com/tools/publishing/app-signing.html#cert) 3. Click Publish > Distribute -- Android App Store 4. Fill out the form using the correct information and supply the key generated in step 2. 5. Click publish. Expected results: Titanium Studio should build the app for distribution without error. Actual results: The above error and no file created.
| 5 |
557 |
TISTUD-2022
|
07/30/2012 15:13:39
|
Add Titanium Studio updates to the updates dialog
|
Currently, the Titanium Update dialog only checks for SDK and modules updates. It should also check for Studio updates and allow for installing via the dialog Tasks: * Remove the current separate Studio update check * Perform the Studio update check at the same time as the SDK/module update check * Display any plugins that need to be updated as part of the update dialog. * For any Studio plugins, send the user through the normal plugin update process (with license acceptance screen)
| 0 |
558 |
TISTUD-2023
|
07/30/2012 15:38:39
|
Replace images in Open Shift feature with new branding
|
Open Shift has new images and logos. Replace the branding in the project wizards with new images. * Create new project dialog (16px icon) * Wizard banners during project creation (48px image) * Deploy wizards (16px images)
| 5 |
559 |
TISTUD-2024
|
07/30/2012 16:04:17
|
OpenShift: the ssh private key is created with 644 permisson and it causes an error when creating a project
|
1. Make sure libra_id_rsa* files don't exist in the ~/.ssh directory; 2. Follow the steps in https://wiki.appcelerator.org/display/tis/OpenShift+Deployment as a new OpenShift user to sign up and then create an OpenShift PHP project. Expected result: the project is created successfully. Actual result: an error dialog appears saying the permissions for the ssh private key is 0644 and too loose, thus the key will be ignored. Workaround: change the permission for ~/.ssh/libra_id_rsa to 0600 from the command line; then creating the project will work.
| 5 |
560 |
TISTUD-2026
|
07/30/2012 20:37:38
|
Widget is disposed in WizardNewRedHatProjectCreationPage.getProjectName()
|
Edge case, but I believe it happened because I had an indexing job running in the background as I was trying to create a project. I kept pressing the "Finish" button but nothing would happen. {code} !ENTRY org.eclipse.ui 4 0 2012-07-30 19:35:15.883 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.widgets.Widget.error(Widget.java:774) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:568) at org.eclipse.swt.widgets.Text.getText(Text.java:1113) at com.appcelerator.titanium.openshift.wizard.WizardNewRedHatProjectCreationPage.getProjectName(WizardNewRedHatProjectCreationPage.java:443) at com.appcelerator.titanium.openshift.wizard.WizardNewRedHatProjectCreationPage.getProjectRemoteURL(WizardNewRedHatProjectCreationPage.java:430) at com.appcelerator.titanium.openshift.wizard.AbstractNewRedHatProjectWizard.performFinish(AbstractNewRedHatProjectWizard.java:214) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.ui.internal.dialogs.EventLoopProgressMonitor.runEventLoop(EventLoopProgressMonitor.java:123) at org.eclipse.ui.internal.dialogs.EventLoopProgressMonitor.isCanceled(EventLoopProgressMonitor.java:97) at org.eclipse.core.internal.jobs.ThreadJob.isCanceled(ThreadJob.java:146) at org.eclipse.core.internal.jobs.ThreadJob.waitForRun(ThreadJob.java:235) at org.eclipse.core.internal.jobs.ThreadJob.joinRun(ThreadJob.java:199) at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:92) at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:286) at org.eclipse.team.core.RepositoryProvider.map(RepositoryProvider.java:94) at com.aptana.git.core.model.GitRepositoryManager.attachExisting(GitRepositoryManager.java:211) at com.aptana.git.core.model.GitRepositoryManager.createOrAttach(GitRepositoryManager.java:314) at com.appcelerator.titanium.openshift.wizard.AbstractNewRedHatProjectWizard.performFinish(AbstractNewRedHatProjectWizard.java:196) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:117) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code}
| 3 |
561 |
TISTUD-2028
|
07/31/2012 14:53:47
|
Dashboard: Learn > Developer Reference: Titanium Guides and Titanium Studio Guide need to point to latest
|
Dashboard > Learn > Developer Reference > Titanium Guides and Titanium Studio Guide need to point to 'latest'. Currently the API Docs link correctly points to 'latest'. Steps to Reproduce: 1. Go to Dashboard > Learn > Developer Reference > Titanium Guides and Titanium Studio Guide and click links. Actual Result: Links to 2.0 documentation. Expected Result: Should point to latest and get redirected to 2.1.1 docs.
| 3 |
562 |
TISTUD-2034
|
08/01/2012 12:45:36
|
Move Zero-to-App links to new locations on Vimeo
|
The videos in (https://github.com/appcelerator/titanium_studio_dashboard/blob/master/data/videoCategories.json): {code} { "id": "zero-to-app", "title": "Zero-to-App", "videos": [ { "id": 1, "title": "Preparing for Mobile Development", "isFeatured": true, "length": "6:24", "description": "Learn how to configure your computer with the software necessary to develop Titanium Mobile applications. We will also look at some TODO items for development teams looking to publish applications to the Apple App Store and Android Market.", "thumbnail": "img/mock_video.png", "href": "http://training.appcelerator.com/zero-to-app#102" }, { "id": 2, "title": "Getting Started and the Development Workflow", "length": "6:40", "description": "Learn the basics of building, testing and deploying mobile apps with Titanium. This video introduces you to the Titanium Studio IDE and development workflow. We'll step through creating and importing projects, editing source code, launching mobile emulators and debugging your Titanium applications.", "thumbnail": "img/mock_video.png", "href": "http://training.appcelerator.com/zero-to-app#103" }, { "id": 3, "title": "Importing Sample Projects", "length": "4:30", "description": "Use the project import capabilities of Titanium Studio to import sample applications like the Kitchen Sink, Tweetanium, or ARTi to explore the capabilities of Titanium.", "thumbnail": "img/mock_video.png", "href": "http://training.appcelerator.com/zero-to-app#104" } ] }, {code} need to be switched to: http://vimeopro.com/appcelerator/zero-to-app/video/24896537 - Preparing for mobile development' http://vimeopro.com/appcelerator/zero-to-app/video/24896600 - Getting Stated with Development Workflow http://vimeopro.com/appcelerator/zero-to-app/video/25102426 - importing sample projects
| 3 |
563 |
TISTUD-2035
|
08/01/2012 13:12:26
|
Dashboard: Search Option: Change endpoint of search to https://www.appcelerator.com/search
|
The search option in Dashboard needs to point to the new https://www.appcelerator.com/search endpoint. An example query is http://www.appcelerator.com/search/devblog?qry=wiki
| 3 |
564 |
TISTUD-2038
|
08/01/2012 16:38:23
|
Add XSD-based Validation for the TiApp editor parts that can support it
|
Once we have a XSD for tiapp.xml, we need to validate the UI elements in the TiApp editor against it. Doing so requires: * Investigate how to link the UI elements in the editor with the XSD errors. * replacing whatever possible for the current validation scheme in the TiApp editor with the XSD validation.
| 8 |
565 |
TISTUD-2040
|
08/01/2012 18:38:45
|
The iOS Platform preference page should load the certificates in background
|
I have quite a few certificates, and when Titanium Studio > Titanium > iOS Platform is selected, the UI will freeze for a while before showing the page. We should improve it to load the certificates in the background so that the page would appear right away, and then fill the table after it's done. We should also not freeze the UI when Refresh is clicked to reload the certificates.
| 8 |
566 |
TISTUD-2041
|
08/02/2012 10:38:19
|
Git tag Titanium Studio builds on push to stable
|
As part of the http://hudson-master.hdqt.appcelerator.com/hudson/job/push-titanium-stable/ build, (before the push): * Find the version # in the version.txt file * See if that git tag has not already been created. If not, create a new tag of the form "vX.X.X.XXXXX" (note the additional "v" at the front) * Push the tag to the following repos: ** titanium_studio ** titanium_studio_rcp ** appcelerator/*.ruble And on Aptana: ** studio3 ** studio3-php ** studio3-ruby ** Pydev ** libraries_com ** swt-webkit ** aptana/*.ruble
| 8 |
567 |
TISTUD-2042
|
08/02/2012 10:44:01
|
Create "push-titanium-rubles-stable" Jenkins build
|
This makes the latest version of Rubles available to all Studio users * Merge the appcelerator/*.ruble projects from the master to the stable branch * Push the results back to Github
| 5 |
568 |
TISTUD-2044
|
08/02/2012 15:16:08
|
Projects: new android sdk path not recognized by tiapp until xml reopen
|
Creating the iOS project without Android SDK setup, restrict the user to update Android as a development target in Tiapp.xml after locate the android SDK locations. Step to reproduce: 1. Open Titanium Studio 2. Select Preference> Titanium Studio> Titanium and delete the Android SDK locations 3. Create new iOS project 4. Select Preference> Titanium STudio> Titanium and Browse and setup Android SDK locations 5. Try to select Android as a deployment target from Tiapp.xml overview Expected Result: User should able to select the Android as a deployment target. Actual Result: User have to close the Tiapp.xml window and reopen it to select the "Android" as a deployment target.
| 5 |
569 |
TISTUD-2045
|
08/02/2012 16:25:32
|
MobileWeb Packaging: dirty project not prompted for save
|
Publishing the dirty project, not prompting any error message and publishing the project successfully. Step to reproduce: 1. Create an Ti.Mobile Project 2. Edit the app.js (Don't save the file) 3. Publish the Ti.Mobile Project Expected Result: User should prompted with error message to save the app.js file. Actual Result: Project published successfully.
| 5 |
570 |
TISTUD-2047
|
08/03/2012 15:23:59
|
Create proxy to retrieve authenticated module list
|
There needs to be some way to retrieve the authenticated list of modules (currently hidden behind OpenID authentication)
| 8 |
571 |
TISTUD-2052
|
08/03/2012 15:51:46
|
Module installation should not allow modules to be corrupt
|
When installing modules, cancelling the installation should not result in a corrupt module. Steps: 1. Use Help > Install Titanium Module... 2. Specify a module url. 3. Select output location: Titanium SDK 4. During the extaction phase, cancel the job Expected results: The operation is canceled and does not corrupt modules/sdk Actual results: The module is part-way installed To accomplish this, the module installation should be split into three parts: 1. Download 2. Extraction of zip in temp location 3. Copy temp location to target location The shortest step (3) should not be cancelable. Other steps should be cancelable
| 8 |
572 |
TISTUD-2054
|
08/06/2012 13:01:53
|
Web Browser : Viewing the analytics in the studio browser window crashes the studio after closing the window.
|
Steps to reproduce: 1.Launch the studio. 2.Create a 'Titanium Mobile project'. 3.Right click on the project & click 'Show analytics'. 4.You will see the analytics window in the studio. 5.Now go to 'my apps' from the drop down below your login name. 6.Select any app which has 'view analytics' available. 7.Click on 'view analytics'. 8.You will see a new internal studio browser window open outside of the studio. 9.Now make sure you are able to see the analytics events. 10.Close the window. 11.You will see that the studio crashes. Actual: Viewing the analytics in the studio browser crashes the studio after closing the window. Expected: Viewing the analytics in the studio browser should not crash the studio. NOTE:If the analytics window opens up in browser like chrome etc rather than the studio web browser window,might solve the issue. Attached are the logs.
| 8 |
573 |
TISTUD-2055
|
08/06/2012 14:20:09
|
Dashboard: Configure: Android: update default android sdk to 20.0.1
|
Update default dashboard config android sdk to Android SDK: r20.0.1 Test Steps: 1. Dashboard > Configure > Android. Expected Result: Android SDK: r20.0.1 is downloaded.
| 3 |
574 |
TISTUD-2057
|
08/06/2012 15:40:11
|
Add custom Alloy project templates to project wizard
|
Alloy templates are similar to rails templates--less preset set of files, more a set of commands to run to generate a scaffold. We need to present Alloy templates alongside traditional templates as part of the new project wizard. * Need metadata format for Alloy templates and location on disk where they are stored (or how we will grab them) * Alloy templates need to specify "Alloy" in the tags
| 8 |
575 |
TISTUD-2059
|
08/06/2012 17:59:19
|
Dashboard: Configure: Android: Linux: android sdk only partially downloads then fails to run
|
Unable to run Android update. Step to reproduce: 1. Open Preferences from "Window" menu bar 2. Titanium Studio> Titanium, delete the "Android SDK Home:" location and Save the changes 3. Open "Dashboard" Window and Click "Configure" tab option 4. Click on "Android" and then "Update Android SDK" Expected Result: Android SDK update should run successfully. Actual Result: Error Message.(log file and image is attached)
| 13 |
576 |
TISTUD-2063
|
08/07/2012 18:28:49
|
Dashboard: Text in search box become invisible when focus changes
|
Description: Text in search box disappeared after searching. Steps to reproduce: Dashboard > type some text in search box > enter Actual Result: Text in search box become invisible. Expected result: Text should be visible.
| 5 |
577 |
TISTUD-2064
|
08/07/2012 18:31:33
|
Keep system default associated file types when titanium studio is run
|
JavaScript files become associated with Titanium Studio as a default without user notification. Steps to Reproduce: 1. Launch Titanium Studio. 2. Create a .js file on the desktop. 3. Context click the .js file and Open With... Actual Result: Titanium Studio is the default associated program for opening javascript files. Expected Result: TextEdit (or whatever it was before) should be the default program.
| 0 |
578 |
TISTUD-2065
|
08/07/2012 19:29:20
|
Linux: Help > Install Specific Titanium SDK > Install from Update Stream lists duplicates of every sdk
|
Help > Install Specific Titanium SDK > Install from Update Stream > release lists duplicates of every sdk. Screenshot attached. This is linux-specific. This is not a regression. Steps to Reproduce: 1. Go to Help > Install Specific Titanium SDK > Install from Update Stream > release Actual Result: Every SDK is listed twice, but there is only one instance of each sdk installed (correct). Expected Result: Every sdk should be listed once.
| 5 |
579 |
TISTUD-2067
|
08/08/2012 10:00:32
|
Links in Dashboard should honor Eclipse browser settings
|
When links are clicked in the browser, they are opened in an external browser. The links should be opened using the eclipse preference (either internally or externally in either a specified or default browser). The following tasks are required: -Add a portal action that opens a url in the prefered browser - "openUrl" -Update the portal core.js to use the new action
| 8 |
580 |
TISTUD-2068
|
08/08/2012 13:30:15
|
SWTException: Invalid thread access when pressing "Cancel" in login screen
|
# Open up the login screen # Press "I have an account" # Press "Cancel" # Note the following in the log file: {code} Exception in thread "Thread-2" org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.widgets.Widget.error(Widget.java:774) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:661) at org.eclipse.swt.widgets.Shell.closeWidget(Shell.java:610) at org.eclipse.swt.widgets.Shell.windowWillClose(Shell.java:2264) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5442) at org.eclipse.equinox.launcher.JNIBridge._takedown_splash(Native Method) at org.eclipse.equinox.launcher.JNIBridge.takeDownSplash(JNIBridge.java:167) at org.eclipse.equinox.launcher.Main.takeDownSplash(Main.java:2050) at org.eclipse.equinox.launcher.Main$SplashHandler.run(Main.java:111) {code}
| 5 |
581 |
TISTUD-2069
|
08/08/2012 13:36:39
|
OS X: Order of Next/Cancel buttons reversed in login screen
|
According to http://www.useit.com/alertbox/ok-cancel.html, the buttons should be: * Windows puts OK first * Apple puts OK last * KDE uses Windows button ordering, and GNOME desktop uses Mac button ordering. We need to swap the ordering of Next/Cancel for OS X.
| 5 |
582 |
TISTUD-2070
|
08/08/2012 14:02:37
|
Replace checkbox in template creation page with "Default" entry
|
Now that the template selection page is first, it's somewhat confusing if you _don't_ want to use a template. Similar to what was done for Alloy, remove the checkbox for "Create the project using one of the templates" and instead replace it with an entry in the template list. # Named "Default Project" # Icon is the default icon # Description is "A default [Wizard Type] project without a template"
| 5 |
583 |
TISTUD-2071
|
08/08/2012 14:05:41
|
Replace Geolocation client/server icons with new versions
|
The icons for the RedHat Open Shift client/server are not in keeping with rest of the icon templates. They need to be upgraded.
| 2 |
584 |
TISTUD-2072
|
08/08/2012 14:12:06
|
%wizard.nodejsproject.name in "Create Project' wizard
|
# File > New > Project # Note %wizard.nodejsproject.name near the top. Looks like a missed refactoring. Should be something like "New Node.js Project"
| 2 |
585 |
TISTUD-2073
|
08/09/2012 10:38:01
|
Direct user to Node.JS troubleshooting document if NPM is not installed, or package fails to install
|
When a user attempts to install a NPM package and NPM is not installed, or NPM is installed and the package fails, we should direct the user to a troubleshooting document as part of displaying the error. http://go.aptana.com/Installing+Node.js
| 5 |
586 |
TISTUD-2074
|
08/09/2012 11:40:36
|
Assign key-bindings for the Alloy generation wizards
|
Add keyboard shortcut for opening dialog and generating Alloy resources (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard) This includes key-bindings for: # Widget # Migration # Controller # Model
| 5 |
587 |
TISTUD-2076
|
08/09/2012 12:27:35
|
Add Support for debugging on iOS devices (wifi)
|
We have the following issue open for iOS to add debugging support for device Enhancement request - Add Support for debugging on device http://jira.appcelerator.org/browse/TIMOB-4625 Once it is addressed, Studio would need to add UI to support the feature.
| 0 |
588 |
TISTUD-2077
|
08/09/2012 22:50:44
|
New Project Wizard: Templates: template icons are solid red if offline
|
If offline, template icons in the new project wizard are solid red. This is not a regression. There is no log info. Steps to Reproduce: 1. Turn off the internet. 2. Create a new Titanium Mobile project to bring up the new project wizard. Actual Result: Template icons are solid red. Expected Result: Each template icon should have unique pixel art.
| 5 |
589 |
TISTUD-2078
|
08/10/2012 10:39:40
|
For Mobile project wizard, double-click on a template should proceed to next page
|
Steps: 1. Right click in Project explorer > New Titanium Mobile Project 2. On the Template page, double-click on the Single Tab Template Expected result: The next page is shown and the template is selected Actual result: The template is selected
| 5 |
590 |
TISTUD-2079
|
08/10/2012 12:42:19
|
Android Packaging Wizard: allow user to manually enter new directory in distribution path
|
When packaging an android project, the user must select an existing directory. If the user manually enters a previously non-existent directory, there is an error. The directory should be created based on the entered path if it did not exist before. Test Steps: 1. Create an android project. 2. Package to bring up package wizard. 3. Enter an otherwise valid directory that does not exist (e.g., Downloads/newdirectory). Expected Result: Manually entered valid directory should not generate error and should be created when packaging is run.
| 5 |
591 |
TISTUD-2086
|
08/13/2012 16:11:54
|
"Right click > Open in New window" in Dashboard should honor Eclipse browser settings
|
This was found in the course of testing TISTUD-1527. Steps: 1. Open dashboard 2. Right click (on a link) > Open in new window Expected Link is opened in a browser based on the Eclipse/Studio settings Actual Link is opened in a new external generic browser with no navigation controls This is currently only occurring on Windows, but an implementation change will affect osx/linux as well
| 8 |
592 |
TISTUD-2088
|
08/13/2012 17:21:44
|
Review Debug on Device platform code contributions
|
Ensure code fits our conventions and standards.
| 8 |
593 |
TISTUD-2089
|
08/13/2012 17:22:36
|
Restrict debugging on device to SDK 2.2+
|
The menu options for debugging should be disabled in < SDK 2.2. There may be other locations we need to check as well, like validating the launch configuration.
| 5 |
594 |
TISTUD-2090
|
08/13/2012 17:24:25
|
Display a set of instructions when launching iOS "Debug on Device"
|
Debugging on Device is a multi-step process, and we should guide the user through the steps. Once the user presses the "debug on device" command, pop up a dialog that shows the four steps: * Build application * Sync to device (iTunes) * Launch app on device (waiting for connection) * Connected Suggest having a wizard page that appears when launching. The page will describe the four steps (1-4), and can help to resolve any setup issues.
| 13 |
595 |
TISTUD-2091
|
08/13/2012 18:22:54
|
Prompt user to choose a device for debugging when multiple devices with the same application are discovered on a local network
|
If multiple devices all present themselves with the same launched app and same security key, we need to allow the user to select between them * Pop a dialog with the names of all the devices in question * Add a small 16px icon next to the device to identify it (iOS/Android, but could eventually be something like iPhone/iPad) * Okay/Cancel to select a device. Double-clicking on the device also performs an "OK"
| 8 |
596 |
TISTUD-2092
|
08/13/2012 18:23:12
|
Modify code to auto-generate a security key on app packaging
|
See RunOnDeviceIOSConfigurator.java for more information
| 8 |
597 |
TISTUD-2093
|
08/13/2012 18:25:59
|
Templates: Error Enabling Cloud Services during HTML project creation.
|
Description: Creating a new HTML template from Titanium Studio causes an Error Enabling Cloud Services. ACS can be enabled from tiapp overview. See an attached screenshot. Steps to reproduce: 1. Click on HTML-based Application from Titanium Studio Dashboard > Develop Actual result: ACS Error Expected result: No Error
| 8 |
598 |
TISTUD-2105
|
08/14/2012 11:06:37
|
Templates: Error unzipping HTML project creation.
|
Description: Creating a new HTML template from Titanium Studio causes an unzipping error. Steps to reproduce: 1. Click on HTML-based Application from Titanium Studio Dashboard > Develop Actual result: Error Expected result: No Error
| 5 |
599 |
TISTUD-2111
|
08/15/2012 12:38:02
|
Reduce required supported node version to 0.6.0
|
Currently, we require node.js to be version 0.8.0 or higher. This can be reduced to 0.6.0.
| 2 |
600 |
TISTUD-2112
|
08/15/2012 12:52:53
|
Python not on the list in commands menu
|
Python is not on the list in Commands menu. This is not regression. h3. Step to reproduce: # Open a Python file: File > New From Template > Python > Blank File # Run a command from the Python Commands Menu (Commands>Python>*) h3. Actual result: Python is not on the list in Commands Menu. h3. Expected result Should exist Python commands in Commands Menu.
| 8 |
601 |
TISTUD-2118
|
08/15/2012 17:35:18
|
If Node.js version is out of date, offer to re-run installer for new version
|
If you have an older version of node.js, you can just install a newer version over the top. Currently we direct the user to a troubleshooting page, but we can improve that process. If the version of node.js is out of date: # Pop up a dialog (currently implemented) letting the user know the version is out of date # Offer to install a newer version for the user (mac and windows). Follow the same steps as the normal installation # If that fails, or on Linux, direct the user to the previous troubleshooting page.
| 5 |
602 |
TISTUD-2127
|
08/16/2012 17:14:58
|
Give descriptive name to Titanium Studio inside VisualVM app
|
For debugging, it's nice to give our app a better name than "Unknown Process". This is relatively straightforward as detailed here: http://stackoverflow.com/questions/4433979/how-do-i-give-a-name-to-a-visualvm-unknown-application {code} -Dvisualvm.display.name=FooBar {code}
| 3 |
603 |
TISTUD-2133
|
08/22/2012 17:48:03
|
A new launch configurations is added on every iOS debug-on-device launch
|
When launching an iOS debug on device (via the Project Explorer debug dropdown), a couple of two new launch configurations is added to the dropdown list. The list is growing on every launch, and there is no way to remove those items, even from the launch configuration dialog (those launches are probably defined as private). Expected behavior: A previous launch should be added to the list, only if it's a new one for the project. Also, only one item should be added, and be named as 'iOS Device - xxx'. Clicking that item should just launch the debug on device, just like clicking the project-explorer "iOS Device" debug action.
| 13 |
604 |
TISTUD-2136
|
08/23/2012 13:18:41
|
Unable to distribute iPhone app due to NPE in loading local provisioning profile
|
When trying to build for distribution, the distribute window never opens and the user cannot distribute their app. An error ops up with a NullPointer Exception. Here is the provisioning profile info: {"wwdr": true, "iphone_dist_name": ["*****"], "sdks": [], "iphone_dev_name": [*****], "iphone_dist_message": null, "wwdr_message": null, "itunes_message": null, "itunes": true, "iphone_dev_message": null, "iphone_dev": true, "iphone_dist": true, "ipad": false, "itunes_version": "10.0"} The error log is below: !ENTRY org.eclipse.jface 4 2 2012-08-23 14:35:53.615 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfile(IOSConfigurationHelper.java:276) at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfiles(IOSConfigurationHelper.java:179) at com.appcelerator.titanium.mobile.iphone.IOSConfiguration.loadLocalProvisioningProfiles(IOSConfiguration.java:507) at com.appcelerator.titanium.mobile.ui.iphone.wizard.SimpleiPhonePackagingComponent.refreshProfiles(SimpleiPhonePackagingComponent.java:511) at com.appcelerator.titanium.mobile.ui.iphone.wizard.SimpleiPhonePackagingComponent.createPageContents(SimpleiPhonePackagingComponent.java:99) at com.appcelerator.titanium.mobile.ui.iphone.wizard.AbstractiPhonePackagingComponent.createContents(AbstractiPhonePackagingComponent.java:61) at com.appcelerator.titanium.mobile.ui.iphone.launch.BaseIOSLaunchConfigurationTab.createPlatformControl(BaseIOSLaunchConfigurationTab.java:70) at com.appcelerator.titanium.ui.launching.BaseTitaniumLaunchConfigurationTab.createControl(BaseTitaniumLaunchConfigurationTab.java:74) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:803) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:735) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:623) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:640) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:602) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:578) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:941) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:560) 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.setSelection(StructuredViewer.java:1726) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.handleConfigurationAdded(LaunchConfigurationView.java:283) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.access$1(LaunchConfigurationView.java:272) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView$2.run(LaunchConfigurationView.java:261) 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.readAndDispatch(Display.java:3615) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1132) at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:579) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:587) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:521) at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:81) at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.runWithEvent(OpenLaunchDialogAction.java:89) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:241) at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !SESSION 2012-08-23 14:38:05.046 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_33 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/mark_allen/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86 -keyring /Users/mark_allen/.eclipse_keyring -consoleLog -showlocation !ENTRY org.eclipse.core.net 1 0 2012-08-23 14:38:19.204 !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.ui 4 0 2012-08-23 14:39:29.166 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfile(IOSConfigurationHelper.java:276) at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfiles(IOSConfigurationHelper.java:179) at com.appcelerator.titanium.mobile.iphone.IOSConfiguration.loadLocalProvisioningProfiles(IOSConfiguration.java:507) at com.appcelerator.titanium.mobile.ui.iphone.wizard.IOSProvisioningComponent.createPageContents(IOSProvisioningComponent.java:62) at com.appcelerator.titanium.mobile.ui.iphone.wizard.AbstractiPhonePackagingComponent.createContents(AbstractiPhonePackagingComponent.java:61) at com.appcelerator.titanium.mobile.ui.iphone.wizard.AbstractiPhonePackagingPage.createControl(AbstractiPhonePackagingPage.java:62) at com.appcelerator.titanium.mobile.ui.iphone.wizard.IOSProvisioningPage.createControl(IOSProvisioningPage.java:38) 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:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at com.appcelerator.titanium.mobile.ui.iphone.wizard.PackageHandler.execute(PackageHandler.java:43) 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.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) !ENTRY org.eclipse.ui 4 0 2012-08-23 14:39:55.355 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfile(IOSConfigurationHelper.java:276) at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfiles(IOSConfigurationHelper.java:179) at com.appcelerator.titanium.mobile.iphone.IOSConfiguration.loadLocalProvisioningProfiles(IOSConfiguration.java:507) at com.appcelerator.titanium.mobile.ui.iphone.wizard.IOSProvisioningComponent.createPageContents(IOSProvisioningComponent.java:62) at com.appcelerator.titanium.mobile.ui.iphone.wizard.AbstractiPhonePackagingComponent.createContents(AbstractiPhonePackagingComponent.java:61) at com.appcelerator.titanium.mobile.ui.iphone.wizard.AbstractiPhonePackagingPage.createControl(AbstractiPhonePackagingPage.java:62) at com.appcelerator.titanium.mobile.ui.iphone.wizard.IOSProvisioningPage.createControl(IOSProvisioningPage.java:38) 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:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at com.appcelerator.titanium.mobile.ui.iphone.wizard.PackageHandler.execute(PackageHandler.java:43) 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.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)
| 5 |
605 |
TISTUD-2138
|
08/23/2012 16:42:10
|
Dashboard: Update Android SDK to 20.0.3 on Staging
|
Dashboard: Update Android SDK to 20.0.3 on Staging
| 3 |
606 |
TISTUD-2139
|
08/23/2012 16:56:20
|
Exception in the log during acs.core plugin loading
|
{code} !ENTRY org.eclipse.osgi 2 0 2012-08-23 14:46:05.930 !MESSAGE While loading class "com.appcelerator.titanium.acs.core.ACSCorePlugin$TiAppChangeListener", thread "Thread[Worker-15,5,main]" timed out waiting (5044ms) for thread "Thread[Worker-8,5,main]" to finish starting bundle "com.appcelerator.titanium.acs.core_1.0.0.qualifier [4]". To avoid deadlock, thread "Thread[Worker-15,5,main]" is proceeding but "com.appcelerator.titanium.acs.core.ACSCorePlugin$TiAppChangeListener" may not be fully initialized. !STACK 0 org.osgi.framework.BundleException: State change in progress for bundle "reference:file:/Users/mxia/git-workspaces/master/titanium_studio/plugins/com.appcelerator.titanium.acs.core/" by thread "Worker-8". at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at com.appcelerator.titanium.acs.core.ACSCorePlugin$1.run(ACSCorePlugin.java:199) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException ... 15 more Root exception: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at com.appcelerator.titanium.acs.core.ACSCorePlugin$1.run(ACSCorePlugin.java:199) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 8 |
607 |
TISTUD-2140
|
08/23/2012 17:36:28
|
Create a wiki page on how to debug on iOS device from Studio
|
We should create a wiki page that lists out the requirements needed as well as the detailed steps to successfully debug on iOS device. We should also add a link that points to the wiki page to the wizard when it is launched in debug mode.
| 8 |
608 |
TISTUD-2142
|
08/23/2012 17:48:12
|
Make the progress monitor for the debug process display more detailed message
|
Debuggin on iOS device is a multi-step process (listed in TISTUD-2090), and before we implement the wizard idea, we should improve the message we show to the user after we started step 2 and are waiting for user to complete step 3 once iTunes finishes syncing. The suggest message is "Waiting for device... (the app is being installed to iTunes; when iTunes finishes syncing, please launch the app on device for the debugger to connect)."
| 5 |
609 |
TISTUD-2143
|
08/23/2012 18:27:22
|
Macbook Pro Retina: display text needs adjustment
|
The tab header text needs to be adjusted to appear more desirable.
| 8 |
610 |
TISTUD-2145
|
08/24/2012 12:10:21
|
Highlight and warn about usage of deprecated API
|
Currently, although there is a "deprecated" flag defined in the JSCA format, it is not displayed in Studio. For example, Ti.Network.INADDR_ANY is deprecated: http://docs.appcelerator.com/titanium/2.1/index.html#!/api/Titanium.Network-property-INADDR_ANY But if you attempt to use it in code: var foo = Ti.Network.INADDR_ANY; Studio will prompt you with a description and not show it as deprecated, or issue any kind of warning. We can now include a deprecation message along with the version number in the YML docs, and it would be good if we could convey that through JSCA. We actually have three keys in the YAML: {code} deprecated: since: <version> notes: Text string, generally involving a link to the new API. removed: <version> {code} Obviously, we shouldn't prompt for APIs that have been removed. We could omit these from the JSCA, or add a new annotation to the JSCA so you can post an appropriate message. Ingo said we'd need to rev the JSCA version number to change deprecated from a boolean to dict to accomplish this. When a new version is available, we can update the JSCA generator. * Create version 1.1 of the JSCA format that supports an expanded deprecated flag. It may be that we can also creatively update the existing fields, i.e. place the deprecation notes in the main description, and just add a "removed" field, like the "since" we already have. * If an item is deprecated in the JSCA, we should display an appropriate warning in content assist. It may also be that we have a flag _not_ to show deprecated items by default * Deprecated items should prompt a warning in both the editor gutter and the problems view, ideally with a note indicating what the replacement is. This implies some sort of reconcile and build participant.
| 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.