issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-958
|
Implement Snippet Drag and Drop
|
Support dragging a snippet from the snippets view and dropping into a source editor. The snippet is inserted at the drop location, and tabstops and cursor locations are honored
| 13 |
train
|
TISTUD-959
|
Implement Snippet Filtering
| null | 13 |
train
|
TISTUD-960
|
Add Studio Listeners to Snippets View
|
Add appropriate listeners so the snippets view displays the appropriate contents A selection listener will listen to cursor location changes, and updates the snippet contents to match the cursor context. If there is a mismatch, the snippet is shown with greyed out colors A Bundle listener will listen to bundle loading/changes, to keep the snippets view contents in sync.
| 13 |
train
|
TISTUD-961
|
Implement Theming and Request Images/Icons for Snippets view
|
Snippets view should honor the theme settings. This applies to theme colors, invasive themes and invasive fonts Snippets view requires two new images - Insert snippet and Navigate to snippet source. These will be provided by our creativity engineer
| 13 |
train
|
TISTUD-971
|
Release Checklist: 1.0.7 Studio
|
Release checklist for 1.0.7 (v2)
| 1 |
train
|
TISTUD-989
|
Manually-installed Android SDKs should be available from Run Configuration dialog without having to restart Studio
|
h3. Expected Behavior All available Android SDKs/APIs should be available when the 'Run Configurations' dialog is opened. h3. Actual Behavior Custom Android APIs copied into the {{\{android-sdk\}/add-ons}} folder from outside Studio are only available after closing and restarting Studio h3. Reproduce # Start Titanium Studio # Copy over a vendor android API addon (available from {{http://developer.motorola.com/docstools/tools/}} or {{http://innovator.samsungmobile.com/down/cnts/toolSDK.list.do?platformId=1}}) # From the app explorer pane, choose 'Run Configurations' from the 'Run' drop down menu. # Your new API is not available. # Restart Studio. # Open 'Run Configurations' # New API is now available.
| 5 |
train
|
TISTUD-1002
|
Warn before launching in simulator/emulator/packager if there are errors in the project
|
If i type bad javascript and compile, it's not always apparent from the logging what the heck is the issue. We show parse errors in the gutter of the editor and in the problems view. If the project has errors, we pop up a dialog as shown (similar to JDT) warning the user of the error and confirming they wish to continue. There also needs to be a way for the user to reset the preference warning (suggest a single button to reset all checkbox preferences, not one per preference)
| 8 |
train
|
TISTUD-1003
|
Debug: Variable View: the last pixel of variables is cut off
|
Steps to reproduce: 1. Create the default Titanium project 2. Add a break point any where in app.js 3. Debug the project as Android Emulator (in V8 or Rhino) 4. In the Debug perspective, navigate to the variables tab Actual: The end of variable names are being cut off. See attachment. Expected: Variable names should not be cut off.
| 13 |
train
|
TISTUD-1006
|
Add Snippet Category Ruble
|
Implement the new SnippetCategoryElement in Rubles: snippet_category 'UI Elements' do |s| s.icon_path = 'snippets/icons/category_ui_elements.png' end Update bundle view to display categories
| 13 |
train
|
TISTUD-1009
|
Rss Reader sample shows as connected to Git
|
# Click on the dashboard > develop tab. # Import the RSS Reader sample # Note that it thinks it's still connected to HEAD, even though it should be disconnected from git
| 8 |
train
|
TISTUD-1015
|
Studio: Attempting to reimport a sample when an older version exists in the workspace (but not project explorer) fails with error
|
Description: I attempted to import a sample (KitchenSink) and got an error. The cause of this turned out to be I already had KS installed, then deleted it, but did not remove it from my workspace. When the folder is deleted from the hard disk, the import completes as expected. Steps to reproduce: 1) Install and launch Studio 1.0.8 2) Import KS sample 3) Delete KS sample but do not check the "remove for hard disk" option 4) Attempt to import KS sample again Result: The sample import will fail with the attached dialog Expected: A prompt stating the sample was there and an option to overcome this situation without having to use the finder to remove the old sample
| 3 |
train
|
TISTUD-1016
|
Studio: Kitchen Sink iPad included with Linux and windows samples
|
Description: The sample Kitchen Sink iPad is available but unusable on Windows and Linux systems. Steps to reproduce: 1) Install Titanium Studio, build: 1.0.8.201201101928 on a linux or windows system 2) Navigate to the samples Result: Kitchen Sink iPad is available but unusable Expected: Only usable templates available on Linux or Windows
| 5 |
train
|
TISTUD-1021
|
Catch browser exception in Git commit dialog
|
Inspired by this ticket: http://developer.appcelerator.com/question/130627/git-commit-doesnt-work-on-titanium-studio We should provide the user with a better error experience if they run into this issue on Linux, where the browser is not configured correctly.
| 5 |
train
|
TISTUD-1274
|
When deleting a project, associated run configurations should be deleted as well
|
I noticed when I previewed a TiMobile web project, that we auto-create a run configuration. When I delete the project; however, the run configuration still remains. I did a quick test in JDT and found that when I deleted a Java Project, the run configurations associated with that project were deleted as well. We should probably do the same
| 5 |
train
|
TISTUD-1023
|
Kernel panic in Titanium Studio
|
From the user: "Today I've been working on my laptop here all day (as usual) with Ti Studio open with several projects (as usual) and several other applications open (as usual). I was last working on a Mail Note... walked away from my laptop for ~5 min and came back with a message indicating I needed to shut down my computer with instructions in several languages. I was unable to access anything, no keyboard key combinations seemed to do anything. The message was "modal" in that it was over the desktop with slightly transparent look so I could see the apps behind it slightly but not access them. This is what I might call a slightly nicer display of a OS crash than a full BSOD (blue screen of death) on a windows machine. When I shutdown and restarted the computer, the system notified me of the crash report and that the core cause of the failure being the Titanium Studio thread. Attached is the crash report." How to read a panic log: http://developer.apple.com/library/mac/#technotes/tn2063/_index.html {code} Interval Since Last Panic Report: 11603879 sec Panics Since Last Report: 1 Anonymous UUID: 6F53AEDA-DEAB-42C9-B86B-75756346052C Sat Jan 14 22:38:45 2012 panic(cpu 1 caller 0x2abf6a): Kernel trap at 0x006ab22a, type 14=page fault, registers: CR0: 0x8001003b, CR2: 0x10004003, CR3: 0x00100000, CR4: 0x00000660 EAX: 0x10004003, EBX: 0x006ab22a, ECX: 0x01000000, EDX: 0x0bc660a8 CR2: 0x10004003, EBP: 0x7e3e3fc8, ESI: 0x09a773f0, EDI: 0x0a045000 EFL: 0x00010206, EIP: 0x006ab22a, CS: 0x00000008, DS: 0x0bc60010 Error code: 0x00000002 Backtrace (CPU 1), Frame : Return Address (4 potential args on stack) 0x7e3e3dc8 : 0x21b837 (0x5dd7fc 0x7e3e3dfc 0x223ce1 0x0) 0x7e3e3e18 : 0x2abf6a (0x59e3d0 0x6ab22a 0xe 0x59e59a) 0x7e3e3ef8 : 0x2a1a78 (0x7e3e3f10 0x18bea2a0 0x7e3e3fc8 0x6ab22a) 0x7e3e3f08 : 0x6ab22a (0xe 0x48 0x7e3e0010 0x210010) 0x7e3e3fc8 : 0x2a179c (0x0 0x1 0x10 0xb7b56c0) BSD process name corresponding to current thread: TitaniumStudio Mac OS version: 10K549 Kernel version: Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 System model name: MacBookPro3,1 (Mac-F4238BC8) System uptime in nanoseconds: 386543916616184 unloaded kexts: com.vmware.kext.vmx86 0053.60.16 (addr 0x7fe54000, size 0x65536) - last unloaded 339536331775578 loaded kexts: com.logmein.hamachi 1.0 com.bresink.driver.BRESINKx86Monitoring 4.0 com.iospirit.driver.rbiokithelper 1.8.0 com.keyspan.iokit.KeyspanNHCI 2.1b4 com.apple.filesystems.afpfs 9.7.1 com.apple.nke.asp_tcp 5.0 com.apple.driver.AppleHWSensor 1.9.3d0 com.apple.filesystems.autofs 2.1.0 com.apple.driver.InternalModemSupport 2.6.2 com.apple.driver.AudioAUUC 1.57 com.apple.driver.AppleTyMCEDriver 1.0.2d2 com.apple.Dont_Steal_Mac_OS_X 7.0.0 com.apple.iokit.CHUDUtils 364 com.apple.driver.AppleIntelYonahProfile 76 com.apple.iokit.CHUDProf 366 com.apple.driver.AppleUpstreamUserClient 3.5.7 com.apple.driver.AppleIntelPenrynProfile 76 com.apple.driver.AppleMCCSControl 1.0.20 com.apple.driver.AppleGraphicsControl 2.10.6 com.apple.driver.AppleIntelNehalemProfile 76 com.apple.driver.AirPort.Atheros 423.19.10 com.apple.driver.AppleHDA 2.0.5f14 com.apple.driver.AudioIPCDriver 1.1.6 com.apple.GeForce 6.3.6 com.apple.driver.AppleBacklight 170.0.46 com.apple.iokit.AppleYukon2 3.2.1b1 com.apple.driver.AppleIntelMeromProfile 76 com.apple.driver.AirPort.Atheros21 425.14.7 com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0a1 com.apple.driver.AppleLPC 1.5.1 com.apple.kext.AppleSMCLMU 1.5.2d10 com.apple.driver.SMCMotionSensor 3.0.1d2 com.apple.driver.AppleUSBTrackpad 201.6 com.apple.driver.AppleUSBTCKeyEventDriver 201.6 com.apple.driver.AppleUSBTCKeyboard 201.6 com.apple.driver.AppleIRController 303.8 com.apple.driver.CSRHIDTransitionDriver 2.4.5f3 com.apple.iokit.SCSITaskUserClient 2.6.8 com.apple.BootCache 31.1 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1 com.apple.driver.AppleFWOHCI 4.7.3 com.apple.driver.AppleIntelPIIXATA 2.5.1 com.apple.iokit.IOAHCIBlockStorage 1.6.4 com.apple.driver.AppleEFINVRAM 1.4.0 com.apple.driver.AppleUSBHub 4.2.4 com.apple.driver.AppleUSBUHCI 4.2.0 com.apple.driver.AppleUSBEHCI 4.2.4 com.apple.driver.AppleAHCIPort 2.1.7 com.apple.driver.AppleHPET 1.5 com.apple.driver.AppleSmartBatteryManager 160.0.0 com.apple.driver.AppleRTC 1.3.1 com.apple.driver.AppleACPIButtons 1.3.6 com.apple.driver.AppleSMBIOS 1.7 com.apple.driver.AppleACPIEC 1.3.6 com.apple.driver.AppleAPIC 1.4 com.apple.driver.AppleIntelCPUPowerManagementClient 142.6.0 com.apple.driver.AppleIntelCPUPowerManagement 142.6.0 com.apple.security.sandbox 1 com.apple.security.quarantine 0 com.apple.nke.applicationfirewall 2.1.14 com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.8 - last loaded 310101164987901 com.apple.iokit.IOUSBMassStorageClass 2.6.7 com.apple.driver.AppleUSBAudio 2.7.6f6 com.apple.driver.AppleHIDKeyboard 141.5 com.apple.driver.AppleBluetoothHIDMouse 162 com.apple.driver.AppleHIDMouse 162 com.apple.driver.IOBluetoothHIDDriver 2.4.5f3 com.apple.driver.AppleProfileReadCounterAction 76 com.apple.driver.AppleProfileTimestampAction 76 com.apple.driver.AppleProfileThreadInfoAction 76 com.apple.driver.AppleProfileRegisterStateAction 76 com.apple.driver.AppleProfileKEventAction 76 com.apple.driver.AppleProfileCallstackAction 76 com.apple.iokit.IOSurface 74.2 com.apple.iokit.IOBluetoothSerialManager 2.4.5f3 com.apple.iokit.IOSerialFamily 10.0.3 com.apple.driver.AppleHDAHardwareConfigDriver 2.0.5f14 com.apple.iokit.CHUDKernLib 365 com.apple.driver.DspFuncLib 2.0.5f14 com.apple.iokit.IOAudioFamily 1.8.3fc2 com.apple.kext.OSvKernDSPLib 1.3 com.apple.driver.AppleBacklightExpert 1.0.1 com.apple.iokit.IOFireWireIP 2.0.3 com.apple.iokit.IO80211Family 320.1 com.apple.iokit.IONetworkingFamily 1.10 com.apple.iokit.AppleProfileFamily 76 com.apple.driver.AppleHDAController 2.0.5f14 com.apple.iokit.IOHDAFamily 2.0.5f14 com.apple.driver.IOPlatformPluginFamily 4.7.0a1 com.apple.driver.AppleSMBusPCI 1.0.10d0 com.apple.nvidia.nv50hal 6.3.6 com.apple.NVDAResman 6.3.6 com.apple.iokit.IONDRVSupport 2.2.1 com.apple.iokit.IOGraphicsFamily 2.2.1 com.apple.driver.AppleSMC 3.1.0d5 com.apple.driver.CSRUSBBluetoothHCIController 2.4.5f3 com.apple.driver.AppleUSBBluetoothHCIController 2.4.5f3 com.apple.iokit.IOBluetoothFamily 2.4.5f3 com.apple.iokit.IOUSBHIDDriver 4.2.0 com.apple.driver.AppleUSBMergeNub 4.2.4 com.apple.driver.AppleUSBComposite 3.9.0 com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.8 com.apple.iokit.IOBDStorageFamily 1.6 com.apple.iokit.IODVDStorageFamily 1.6 com.apple.iokit.IOCDStorageFamily 1.6.1 com.apple.driver.XsanFilter 402.1 com.apple.iokit.IOATAPIProtocolTransport 2.5.1 com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.8 com.apple.driver.AppleFileSystemDriver 2.0 com.apple.iokit.IOFireWireFamily 4.2.6 com.apple.iokit.IOATAFamily 2.5.1 com.apple.iokit.IOUSBUserClient 4.2.4 com.apple.iokit.IOUSBFamily 4.2.4 com.apple.iokit.IOAHCIFamily 2.0.6 com.apple.driver.AppleEFIRuntime 1.4.0 com.apple.iokit.IOHIDFamily 1.6.6 com.apple.iokit.IOSMBusFamily 1.1 com.apple.driver.DiskImages 289 com.apple.iokit.IOStorageFamily 1.6.3 com.apple.security.TMSafetyNet 6 com.apple.kext.AppleMatch 1.0.0d1 com.apple.driver.AppleACPIPlatform 1.3.6 com.apple.iokit.IOPCIFamily 2.6.5 com.apple.iokit.IOACPIFamily 1.3.0 Model: MacBookPro3,1, BootROM MBP31.0070.B07, 2 processors, Intel Core 2 Duo, 2.4 GHz, 6 GB, SMC 1.16f11 Graphics: NVIDIA GeForce 8600M GT, GeForce 8600M GT, PCIe, 256 MB Memory Module: global_name AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), Atheros 5416: 2.1.14.6 Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports Network Service: AirPort, AirPort, en1 PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5 Serial ATA Device: ST95005620AS, 465.76 GB Parallel ATA Device: MATSHITADVD-R UJ-857R USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8502, 0xfd400000 / 2 USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8205, 0x1a100000 / 2 USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x5d100000 / 2 USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x021a, 0x5d200000 / 3 {code}
| 13 |
train
|
TISTUD-1028
|
Studio: Mobile Web should be supported as target for studio templates
|
Description: Currently, Studio templates can't be utilized with mobile web. The templates are coded to produce a dialog stating "Mobile web is not yet supported by this template". This does not occur with the default template. Steps to reproduce: 1) Install Titanium Studio, build: 1.0.8.201201131907 2) Select Mobile Web as a target 3) Create a new project and select one of the templates 4) Attempt to preview in browser Result: A dialog stating the template is not supported Expected: The template launches in the browser
| 8 |
train
|
TISTUD-1032
|
After importing samples from dashboard, some display that they are from [HEAD] and some display nothing, need to be consistent
|
Steps to Reproduce: 1. Launch Dashboard in Studio 2. Click on the Develop tab 3. Click to import Kitchen Sink 4. Click to import Kitchen Sink Nook 5. Click to import Kitchen Sink iPad 6. Click to import Todo List 7. Click to import Geocoder 8. Click to import RSS Reader Actual Result: Some display [HEAD] Expected Result: Should be consistent, they should either all display it or not
| 21 |
train
|
TISTUD-1036
|
TiStudio: Mobile Web - After deleting a packaged Mobile Web project, a noticable performance degradation occurs in TiStudio
|
Steps to reproduce: 1. Package default Titanium project for Mobile Web 2. Select "Create a new project for the Mobile Web app" 3. Open the index.html in the newly created Mobile Web project 4. Press preview button 5. Select all projects in Project Explorer and delete them Actual: * Deleting selected projects takes a long time * After projects are deleted, TiStudio becomes sluggish e.g. opening context menu in project explorer is slow * See attachment for TiStudio's log file Expected: Performance degradation should not occur. Note: Performance degradation does not occur on Mac OS X Lion (10.7.1) or Windows XP
| 8 |
train
|
TISTUD-1037
|
Mobile Web in emulator does not refresh the index.html after it is recompiled
|
Steps to Reproduce: 1. Create a default application for mobile web 2. Run "Mobile Web Preview in Emulator" 3. Make changes to the app.js and save the file 4. Run "Mobile Web Preview in Emulator" again Actual: The index.html file on the emulator is not refreshed Expected: The index.html file should refresh to show the updated content
| 8 |
train
|
TISTUD-1038
|
Openshift: PHP Wizard Account information page should request "Domain" in the "Already have an account" radio
|
This is related to TISTUD-1000. Currently the domain information is only needed during login, so it makes sense to add the domain field to the "Already have an account radio". The default gray text should be something like "Specify domain if desired". If the login fails because the domain isn't satisfied, then the domain field is required.
| 8 |
train
|
TISTUD-1039
|
OpenShift: the creation of ssh key would fail if .ssh directory doesn't exist in user's home directory
|
Follows the steps in https://wiki.appcelerator.org/display/tis/OpenShift+Deployment, and ~/.ssh directory doesn't exist yet, an error status would show when the domain is being created (see screenshot). The log shows the following: {code} !ENTRY com.appcelerator.titanium.deploy.openshift 4 0 2012-01-17 17:54:51.092 !MESSAGE Could not create new rsa key !STACK 0 com.openshift.express.client.OpenShiftException: Could not create new rsa key com.openshift.express.client.SSHKeyPair.create(SSHKeyPair.java:67) com.appcelerator.titanium.deploy.openshift.OpenShiftUserManager.loadSshKey(OpenShiftUserManager.java:405) com.appcelerator.titanium.deploy.openshift.OpenShiftUserManager.createDomain(OpenShiftUserManager.java:167) com.appcelerator.titanium.deploy.openshift.ui.wizard.RedHatSignupWizardPage$8.run(RedHatSignupWizardPage.java:478) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: java.io.FileNotFoundException: /Users/mxia/.ssh/libra_id_rsa.pub (No such file or directory) java.io.FileOutputStream.open(Native Method) java.io.FileOutputStream.<init>(FileOutputStream.java:194) java.io.FileOutputStream.<init>(FileOutputStream.java:84) com.jcraft.jsch.KeyPair.writePublicKey(KeyPair.java:144) com.openshift.express.client.SSHKeyPair.create(SSHKeyPair.java:63) ... 4 more {code}
| 8 |
train
|
TISTUD-1048
|
The ios-sim process is not killed when user re-launches iPhone simulator from Studio without first quitting the previous one
|
Steps to reproduce: 1. Create a Titanium Mobile project; 2. Click on Run > iPhone Simulator in App or Project Explorer toolbar to launch the iPhone simulator; 3. After the simulator successfully appears, click on Run > iPhone Simulator again; 4. The existing simulator will disappear and then re-appear, and that is good; now types "top" in a terminal outside Studio to check the running process. Expected Result: only one "ios-sim" process is running. Actual Result: two "ios-sim" processes are running.
| 5 |
train
|
TISTUD-1051
|
Externalize UI strings in Titanium Desktop ruble
| null | 2 |
train
|
TISTUD-1052
|
Externalize UI strings in Titanium Mobile ruble
| null | 2 |
train
|
TISTUD-1053
|
Test build participant infrastructure
|
This involves taking the current built participant infrastructure, reviewing the test plans and unit tests, and performing the tests. Current wiki: https://wiki.appcelerator.org/display/tp/TiStudio+Build+Participant+Test+Plan Suggested approach: * Review the above test plan. The list of test cases is incomplete. Don't worry about fleshing them out fully. Instead, take Chris's feedback and Thomas's feedback (shown below) to create a set of test scenarios at the top of the file and run through those. We will leave the creation of exhaustive test cases to later when we have more QA resources. * Review the unit tests. See if they exercise the functionality. Run them through Emma to check for code coverage * Run the test scenarios and file any bugs found. To Test: Checkout the "participant" branch of studio3, studio3-ruby and studio3-php Thomas's feedback: * All tests are marked as full. The point of a test plan is to break functionality into smoke, acceptance and full levels of test. If the tester can't figure out these coverage levels, they need to work with dev to figure it out. * Resource requirements are not filled out - now way of knowing from this plan what Os are being tested or targeted * An actual description of what "Build Participant functionality" is would be helpful if the test plan is going to be run by anyone other than the author. There seems to be multiple features in the test cases * No risks or assumptions are filled out * Often missing set up steps - For the PHP and Ruby specific test cases, how do we setup our environment to test those test cases? * Under genericized tests, it says "Applicable to all languages." Which programming languages is being tested: JS, Java, Objective C? * Unclear if it applies to Aptana or Tistudio. * Not seeing links to any dev specs: http://wiki.appcelerator.org/display/tis/Participating+in+the+build+and+reconcile+process Ignore for now: * Overall, the test cases should be more detailed since the test plan seems to be dealing with different programatic syntax and the test plan needs to clearly define what it is testing. (ignore for now) * Not sure of why the tests at the top are repeated from 1012 on with a "syntactically sound" js file. Is there a target for this specific set of tests? * In the "Declarations and documentation" tests, need specific examples for the programatic syntax (e.g. Document a class, declare a class, declare a function etc.) * 1112 - 1115 refer to Aptana Studio. Also the location is Mac-only for the preferences. Unless the testing is Mac only either leave out the menu path or put Linux and Win info too.
| 21 |
train
|
TISTUD-1055
|
Create test plan for Snippets view
| null | 8 |
train
|
TISTUD-1058
|
Titanium Studio: Improved error reporting in preferences window for invalid Android SDK
|
I had a bad Titanium SDK install. Not entirely sure how it happened, but the end result was some files were missing or corrupt. The end result was that, in the Titanium Preferences, I was getting an error saying that no Android SDK was found at my android sdk path. Upon much hand-wringing, eventually I was told to look at the Titanium log, which had an error "!MESSAGE (Build 1.0.0.1326828513) [ERROR] /usr/bin/python: can't open file '/Users/shan/Library/Application Support/Titanium/mobilesdk/osx/1.8.1.v20120123161633/android/avd.py': [Errno 2] No such file or directory", which made the problem pretty obvious. It would be great if: 1. Titanium Studio would have alerted me that there was an error, instead of saying that my Android SDK could not be found. 2. If that can't easily be accomplished, the error text displayed on the Preferences screen should have "Check the Titanium Studio log for more information." appended to it.
| 13 |
train
|
TISTUD-1067
|
Interpret kernel panic log file
|
From the parent ticket, it's yet unknown how long it will take to fix this issue, since we have yet to determine the root cause. This ticket is just to read the attached kernel panic log file to decipher what the stack trace entails.
| 5 |
train
|
TISTUD-1068
|
Allow snippets to be scoped by project type
|
Have this code in a JS file: {code} function Coffee (type,roast) { this.type = type; this.roast = roast; } Coffee.prototype.describe = function() { return this.roast + ' ' + this.type + ' coffee'; }; var sumatra = Coffee("Sumatra", "Light"); sumatra.d| <<< Content Assist here {code} The result of this CA is: {code} sumatra.Ti.API.debug(}) {code} In this case, the Titanium Mobile ruble is contributing a snippet which does not apply inside a regular JS project. Suggest is we have some way to allow snippets to be scoped based on project natures (i.e. titanium mobile), or perhaps a more generic mechanism (i.e. jquery snippets enabled in a "jquery" project, where there is no corresponding nature) Suggestion is to add a meta scope of: meta.project.<nature>
| 20 |
train
|
TISTUD-1073
|
Improve performance when the Snippets view is initially loaded
|
I profiled the performance issue. The root cause is creation of all the snippets when the view is loaded. A solution would be to lazy load the creation of the snippets until they are shown. This requires an introduction of a UI model for the snippet element, which would store the state of the snippet (visually disabled/enabled and filtered). The UI model is taken into account when the Snippet UI is actually created
| 8 |
train
|
TISTUD-1076
|
Need to pass in "mobileweb" to project.py when creating new projects
|
When Studio creates a new project, it runs a python script called "project.py" where the arguments may contain "iphone", "android", and "mobileweb". The call should like this: {code} "/usr/bin/python" "/Library/Application Support/Titanium/mobilesdk/osx/1.9.0/project.py" "MyProject" "com.appcelerator.myproject" "~/workspace" "iphone" "android" "mobileweb" "~/android-sdk-mac_x86" {code} You can pass in "iphone", "android", and "mobileweb" in any order. Just need to make sure "mobileweb" is added to the call if the mobile web checkbox is checked. Side effects of not specifying this argument today is that the mobileweb resources folder will not get copied into the project's resources folder and then the appicon, favicon, apple touch icons, and apple startup images won't be displayed in the app. Undoubtedly there will be more logic performed during project creation in the future, so we need to have this argument added.
| 8 |
train
|
TISTUD-1077
|
Indicates the outline is out of date when there is syntax error in the code
|
Please see capture at http://www.screencast.com/t/qOsLUmhehKA. The JSON Outline does not clear if you replace all current content by pasting in syntactically erroneous content. Steps to Replicate : 1) Open Aptana Studio 2) Open JSON file 3) Add content that will register in the Outline 4) Select the entire file and paste in syntactically erroneous content Actual Results : The Outline freezes in its initial state. Expected Results : The Outline should clear when this happens. Proposed solution: Display a message (similar to a status message) inside the outline view with the message "The outline view is out-of-date due to syntax errors in the document". suggestion is that the message is noticeable, but not obtrusive, as it may appear during normal editing.
| 13 |
train
|
TISTUD-1078
|
OpenShift: allow user to be able to delete an OpenShift app from Studio
|
Currently there isn't an way to delete an OpenShift app from within Studio once it is created, and if user runs into issues with creating a new app, e.g. exceeding the limit for the number of apps per namespace or trying to create one with one that already exists, and would need to delete an app, they would have to go back to command line with gem to resolve it. * If a user creates a new project, add right-click menu to delete * Perhaps add a command (using Rubles) for OpenShift to delete an app (by typing in the app name)
| 20 |
train
|
TISTUD-1079
|
Exclude build folder from text search made in AppExplorer
| null | 8 |
train
|
TISTUD-1091
|
TiStudio: Samples - Project clean does not recognize Geocoder, RSS Reader, and Todo List samples
|
Steps to reproduce: 1. In the Samples pane, import Geocoder or RSS Reader or Todo List 2. Go to Project > Clean Actual: Clean option does not recognize these samples. The clean option recognizes only the Kitchen Sink samples (iPad and Nook) and other projects created by the user. Expected: Clean option should recognize all projects.
| 13 |
train
|
TISTUD-1093
|
Titanium Studio: mobileweb is selected as a deployment target when a new project without mobileweb support is imported into studio after being generated by titanium.py create
|
When an iOS or Android project is created using 'titanium.py create', and imported into studio, mobileweb is always selected as a deployment target. Steps to Reproduce: 1. Generate a new project using titanium.py create, such as: {code:title=OSX Terminal} dhydeMBPLion:~ dhyde$ /Users/dhyde/Library/Application\ Support/Titanium/mobilesdk/osx/1.8.1.v20120123161633/titanium.py create --platform=iphone --type=project --dir=/Users/dhyde/Downloads --name=iPhoneProject --id=com.appcelerator.iphoneproject {code} . . .Project will be created, and there will be no deployment target tags in tiapp.xml, as expected. 2. Import the project into studio. 3. Look at tiapp.xml. Expected Result: Only iPhone (and iPad, incidentally) should be selected as a deployment target. Actual Result: MobileWeb is additionally set as a deployment target.
| 13 |
train
|
TISTUD-1094
|
Inconsistent mobile project name passed to iOS builder.py scripts
|
1. Import KS from Samples 2. Compile to device 3. Without cleaning compile to iphone simulator We semi-solved this with TISTUD-697, but we missed a case.
| 5 |
train
|
TISTUD-1105
|
The project builders get overwritten when importing a sample from a remote url that already contains .project file
|
The issue is discovered while debugging TISTUD-1091. What we saw is that when importing a sample from a git repo that already has .project file defined, we would end up overwriting the .profile after the project is created. For example, the original .project file in the remote repo is this: {code} <?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>Sample.RSS</name> <comment></comment> <projects> </projects> <buildSpec> <buildCommand> <name>com.appcelerator.titanium.core.builder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>com.aptana.ide.core.unifiedBuilder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>com.appcelerator.titanium.mobile.nature</nature> <nature>com.aptana.projects.webnature</nature> </natures> </projectDescription> {code} and afterward, it becomes the following: {code} <?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>Sample.RSS</name> <comment></comment> <projects> </projects> <buildSpec> </buildSpec> <natures> <nature>com.appcelerator.titanium.mobile.nature</nature> <nature>com.aptana.projects.webnature</nature> </natures> </projectDescription> {code}
| 8 |
train
|
TISTUD-1107
|
Update Titanium Mobile Snippets contributions to provide more context and improve discoverability
|
With the introduction of the Snippets View (https://wiki.appcelerator.org/display/tools/Snippets+View), we need update the existing snippets to add more context and improve discoverability. This is accomplished by adding the following fields to Snippets (https://wiki.appcelerator.org/display/tis/Snippets): * description: A descriptive text about the snippet. Optional * category: A name of a category used to group the snippet with other similar snippets. Optional * icon_path: the path to an icon that represents the snippet. Optional * tags: keywords that describe the snippet. Used as means to easily filter snippets. Optional Example: {code} snippet "My create map Snippet" do |snip| snip.trigger = "foo" snip.expansion = "my_map_snippet" snip.description = "Creates a map object and adds the following annotations: current location, paris, and ontario" snip.tags = ['UI','map','annotation'] snip.category = "Maps and Annotations" snip.icon_path = "icons/my_map_icon.png" end {code} In addition is the snippet_category entry that defines a grouping for snippets: {code} snippet_category "my_category" do |category| category.icon_path = "icons/my_category.png" end {code} These additions will make working with snippets much easier for user via the Snippets view The changes are also outlined here (towards the bottom): https://wiki.appcelerator.org/display/tis/Creating+a+New+Snippet
| 13 |
train
|
TISTUD-1108
|
Studio: Sort project list using natural rather than alphabetical sorting
|
Expected: the list of projects in App Explorer view would be sorted naturally -- project1, Project2, project3, Project4, etc. Actual: projects are sorted alphabetically (all the capitalized project names sort higher than lower-case names: Project2, Project4, project1, project3) See the attached screen shot. This would be better sorted naturally, as is done in the Project Explorer view. A quick google shows that this is perhaps easier said than done. There are a couple of how-tos linked to from this article in case they help: http://www.codinghorror.com/blog/2007/12/sorting-for-humans-natural-sort-order.html
| 3 |
train
|
TISTUD-1114
|
Titanium Studio: Projects: new project with same name overwrites existing files
|
Creating a new project overwrites existing files. OSX: If a new project is created with the same name as an existing project in the workspace, all default files are overwritten. OSX-specific: If a new project is created with the same name, but different capitalization, the original files are all overwritten, but the project folder retains the original capitalization, and the studio interface shows the new project name as it was overwritten in the new project settings file. Linux: If a new project is created with the same name as an existing project in the workspace, all default files are overwritten. Steps to Reproduce: 1. Create a new project called MyProject. 2. Edit the app.js file to make a meaningful change. 2. Delete the project from studio without removing it from disk. 3. Create a new project called MyProject. Expected Result: Studio should show an error message indicating the project already exists. Actual Result: The new project is created and any default files are overwritten. An OSX-specific issue occurs when the new project has the same name with different capitalization. When the new project is created, the original files are overwritten and the original folder keeps it's old capitalization, but the studio ui representation of the project shows the new capitalization.
| 8 |
train
|
TISTUD-1115
|
Studio: Android SDK detection relies on script in latest Titanium SDK in mobilesdk folder, giving misleading info during failure
|
Description: To determine if the Android SDK is properly configured, Studio relies on a script (avd.py I believe) in the latest Titanium SDK in the Titanium SDK folder. This is problematic in some circumstances including when a developer installs a development Titanium SDK. Studio will automatically defer to this new version for verification of the correct configuration of the Android SDK. If there is an issue with the script or some other problem with the folder structure of the development Titanium SDK, it will disable the ability of Studio to use Android projects. Since it is not possible for QE to verify every development release has the correct structure and that the and.py script is present and functional, this is a potential risk area. Steps to reproduce: 1) Configure studio to have 1.8.0.1 GA as the latest SDK 2) Install an SDK from master branch (1.9.0) 3) navigate to the folder for the 1.9.0 SDK and remove SDK FOLDER/android/avd.py 4) In studio, select the titanium preference pane or click "configure..." from the TIapp.xml overview Result: Android preference states "Could not locate the Android SDK at the given path" Expected: Android SDK configuration verification based on method that is independent of Titanium SDK
| 13 |
train
|
TISTUD-1116
|
Titanium Studio: Editor: closing or deleting project intermittently fails to close all open related project files
|
When a project is deleted from disk in studio, all open related project files intermittently fail to close. The file tab reads: Could not open the editor: An unexpected exception was thrown. Steps to Reproduce: 1. Create a new project. 2. Delete the project, removing from disk. Expected Result: All open associated project files in studio should close. Actual Results: Files stay open and an error message is generated.
| 5 |
train
|
TISTUD-1118
|
JavaScript validation continues to report a syntax error, even after error is corrected
|
The JavaScript parser will report a syntax error in code that functions properly. Steps to Replicate : 1) Open Titanium Studio 2) Open an empty HTML file and add the content : {noformat} <html> <head> <script type="text/javascript"> function alertMsg{alert("Popup");} </script> </head> <body> <form> <input type="button" value="Show alert box" onclick="alertMsg()" /> </form> </body> </html> {noformat} 3) Note the syntax error on line 4 and add parameter parentheses after "alertMsg" to correct the error 4) Note the editor continues to report a syntax error, save and preview the file Actual Results : The code functions successfully however is marked as syntactically erroneous. Expected Results : The editor should not report errors in valid code.
| 13 |
train
|
TISTUD-1125
|
Error in log file: "Was unable to add folding position"
|
The JSON editor writes warnings to the log upon deleting then backspacing the contents of a file. Steps to Replicate : 1) Open Titanium Studio 2) Open a saved empty JSON file and add the content : {noformat} { "firstName": "John", "lastName": "Smith", "age": 25, "address": { "streetAddress": "21 2nd Street", "city": "New York", "state": "NY", "postalCode": "10021" }, "phoneNumber": [ { "type": "home", "number": "212 555-1234" }, { "type": "fax", "number": "646 555-4567" } ] } {noformat} 3) Erase approximately the first half of the file with the delete key 4) Place the caret at the end of the file and erase the rest with the backspace key Actual Results : Studio will write this to the log : !ENTRY com.aptana.editor.common 2 0 2012-01-25 20:41:57.730 !MESSAGE (Build 3.0.3.1325798464) [WARNING] Was unable to add folding position. Start: 253, end: 206 !ENTRY com.aptana.editor.common 2 0 2012-01-25 20:41:57.730 !MESSAGE (Build 3.0.3.1325798464) [WARNING] Was unable to add folding position. Start: 264, end: 206 !ENTRY com.aptana.editor.common 2 0 2012-01-25 20:41:57.730 !MESSAGE (Build 3.0.3.1325798464) [WARNING] Was unable to add folding position. Start: 350, end: 206 Expected Results : These keys are expected to function with no errors or warnings.
| 5 |
train
|
TISTUD-1133
|
CSS "Add Color" Command places the caret before, not after the inserted color
|
Please see capture at : http://www.screencast.com/t/p8PMAm0sC. Upon invoking the CSS Add Color command, the editor places the caret after the new color code. Steps to Replicate : 1) Open Titanium Studio 2) Open a CSS file 3) Select Color > CSS > Add Color Actual Results : The caret precedes the new color. Expected Results : The caret should be after the new color.
| 3 |
train
|
TISTUD-1134
|
HTML Template Indentation
|
Please see capture at http://www.screencast.com/t/3eloNGUR. The File menu and Project Explorer menu have differing template indentation. Steps to Replicate : 1) Open Titanium Studio 2) Select an HTML project with the default formatter profile selected 3) From the context menu select New From Template > HTML > HTML 5 Template 4) Select File > New From Template > HTML > HTML 5 Actual Results : The templates have differing indentation. Expected Results : The templates should have the same indentation.
| 8 |
train
|
TISTUD-1136
|
FileNotFoundException: .../manifest
|
Minor issue, but completely filling up the log files: {code} !ENTRY com.appcelerator.titanium.core 4 0 2012-02-01 12:51:54.982 !MESSAGE (Build 1.0.7.1327097522) [ERROR] /Users/fusion94/Documents/Titanium Studio Workspace/zzzzz/manifest (No such file or directory) !STACK 0 java.io.FileNotFoundException: /Users/fusion94/Documents/Titanium Studio Workspace/zzzzz/manifest (No such file or directory) java.io.FileInputStream.open(Native Method) java.io.FileInputStream.<init>(FileInputStream.java:120) com.appcelerator.titanium.core.tiapp.TiManifestModel.<init>(TiManifestModel.java:181) com.appcelerator.titanium.core.TiModelFactory.createTiManifestModel(TiModelFactory.java:92) com.appcelerator.titanium.core.TitaniumProject.loadManifest(TitaniumProject.java:248) com.appcelerator.titanium.core.TitaniumProject.lazyLoad(TitaniumProject.java:232) com.appcelerator.titanium.core.TitaniumProject.isIPadDeployTarget(TitaniumProject.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) com.appcelerator.titanium.core.TitaniumProjectPropertyTester.test(TitaniumProjectPropertyTester.java:27) org.eclipse.core.internal.expressions.Property.test(Property.java:58) org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:189) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) org.eclipse.core.internal.expressions.ReferenceExpression.evaluate(ReferenceExpression.java:70) org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68) org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:21) org.eclipse.ui.internal.services.EvaluationResultCache.evaluate(EvaluationResultCache.java:74) org.eclipse.ui.internal.WorkbenchWindow.liftRestrictions(WorkbenchWindow.java:3062) org.eclipse.ui.internal.WorkbenchWindow$28.shellActivated(WorkbenchWindow.java:3112) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:88) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:3783) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1398) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1379) org.eclipse.swt.widgets.Shell.windowDidBecomeKey(Shell.java:1892) org.eclipse.swt.widgets.Display.windowProc(Display.java:5031) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:213) org.eclipse.swt.widgets.Widget.becomeKeyWindow(Widget.java:324) org.eclipse.swt.widgets.Shell.becomeKeyWindow(Shell.java:478) org.eclipse.swt.widgets.Display.windowProc(Display.java:4863) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSWindow.becomeKeyWindow(NSWindow.java:40) org.eclipse.swt.widgets.Control.fixFocus(Control.java:1246) org.eclipse.swt.widgets.Control.setEnabled(Control.java:3319) org.eclipse.swt.widgets.Shell.setEnabled(Shell.java:1452) org.eclipse.ui.internal.progress.ProgressManager.setUserInterfaceActive(ProgressManager.java:1265) org.eclipse.ui.internal.progress.ProgressManager.access$4(ProgressManager.java:1252) org.eclipse.ui.internal.progress.ProgressManager$5.run(ProgressManager.java:959) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:995) org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:970) org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.checkInitialConditions(RefactoringWizardOpenOperation.java:205) org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.access$0(RefactoringWizardOpenOperation.java:200) org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:163) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:192) org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:115) org.eclipse.ltk.internal.ui.refactoring.actions.DeleteResourcesHandler.execute(DeleteResourcesHandler.java:40) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommandInContext(HandlerService.java:270) org.eclipse.ui.internal.ide.actions.LTKLauncher.runCommand(LTKLauncher.java:95) org.eclipse.ui.internal.ide.actions.LTKLauncher.openDeleteWizard(LTKLauncher.java:47) org.eclipse.ui.actions.DeleteResourceAction.run(DeleteResourceAction.java:481) org.python.pydev.navigator.actions.PyDeleteResourceAction.run(PyDeleteResourceAction.java:101) org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:3783) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1398) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1383) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1195) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3629) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3284) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) org.eclipse.equinox.launcher.Main.run(Main.java:1408) {code}
| 3 |
train
|
TISTUD-1137
|
Console: High water mark must be greater than low water mark
|
Found in a log file: {code} !ENTRY org.eclipse.ui.console 4 120 2012-01-23 14:10:15.147 !MESSAGE An exception occurred during console notification !STACK 0 java.lang.IllegalArgumentException: High water mark must be greater than low water mark org.eclipse.ui.console.IOConsole.setWaterMarks(IOConsole.java:204) org.eclipse.debug.internal.ui.views.console.ProcessConsole.init(ProcessConsole.java:416) org.eclipse.ui.console.AbstractConsole.initialize(AbstractConsole.java:258) org.eclipse.ui.console.AbstractConsole$Lifecycle.consolesAdded(AbstractConsole.java:64) org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.run(ConsoleManager.java:152) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.notify(ConsoleManager.java:175) org.eclipse.ui.internal.console.ConsoleManager.fireUpdate(ConsoleManager.java:269) org.eclipse.ui.internal.console.ConsoleManager.addConsoles(ConsoleManager.java:231) org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.launchChanged(ProcessConsoleManager.java:149) org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:447) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:428) org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:990) org.eclipse.debug.core.Launch.fireChanged(Launch.java:388) org.eclipse.debug.core.Launch.addProcess(Launch.java:351) org.eclipse.debug.core.model.RuntimeProcess.<init>(RuntimeProcess.java:125) com.aptana.console.process.TTYConsoleProcess.<init>(TTYConsoleProcess.java:33) com.aptana.console.process.ConsoleProcessFactory.newProcess(ConsoleProcessFactory.java:32) org.eclipse.debug.core.DebugPlugin.newProcess(DebugPlugin.java:750) com.aptana.git.internal.core.launching.GitLaunchDelegate.launch(GitLaunchDelegate.java:66) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696) com.aptana.git.ui.internal.Launcher.launch(Launcher.java:59) com.aptana.git.ui.internal.actions.AbstractSimpleGitCommandHandler$1.run(AbstractSimpleGitCommandHandler.java:81) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 8 |
train
|
TISTUD-1139
|
Should check and load the existing .project file before setting our required natures/builders when creating or importing a project we support
|
Currently in our project creation or import wizards, we always create a new project description using IWorkspace.newProjectDescription() and then set nature ids and builders on it, but there is a possibility that the directory we're creating the project in or importing from already has a .project file. The correct way would be: 1. Check if a .project file exists in the specified directory; 2. Load project description from the .project file using IWorkspace.loadProjectDescription(); 3. Check if the project description already contains the natures and builders that we need and only add the missing ones; 4. If the project description isn't modified because it already includes the natures and builders we need, there will not be a need to call IProject.setDescription(); otherwise, call the method to update the .project file. We should be able to capture most of the steps in an utility method.
| 13 |
train
|
TISTUD-1152
|
Add XSD-based Validation for tiapp.xml and timodule.xml editors
|
Once we have a XSD for tiapp.xml, we need to validate against it. Doing so requires: * XSD * build participant to wrap calling the XSD
| 8 |
train
|
TISTUD-1156
|
Project creation needs to check for app id segments that start with a number
|
Android requires that all namespaces in a package not start with a number, but studio only checks the first namespace currently. Example invalid package name: com.test.123
| 5 |
train
|
TISTUD-1158
|
Multiple instances of the same process showing up in the console view
|
# Clone the Kitchen Sink sample into your workspace # Clear all terminated launches in the Studio console # Run the Kitchen Sink sample in the Android emulator Note the duplication of launch processes, in particular, FastDev and the Android Emulator Process
| 13 |
train
|
TISTUD-1162
|
Research support ScriptDoc'ing of CommonJS Modules
|
Research what changes will be needed in the JS inferencing, indexing, and content assist to add support for CommonJS modules to JS content assist
| 13 |
train
|
TISTUD-1163
|
Make IOS Package/Run on Device launch configuration public
|
Refactor the existing wizard page contents so they can be re-used in the Launch configuration tabs. Expose the Launch configurations so they are public. Launch the "full" wizard if the launch configuration is initiated for the first time
| 20 |
train
|
TISTUD-1164
|
Make Android Package launch configuration visible to users
|
Refactor the Android wizard page contents so it can be reused in the Launch configuration tab. Add a launch configuration for "Install on Android Device", which allows users to specify a android sdk
| 20 |
train
|
TISTUD-1165
|
Add MobileWeb Distribute operation as a Launch configuration
|
Refactor the wizard page contents so it can be re-used in a new Mobile Web Launch configuration
| 20 |
train
|
TISTUD-1167
|
Investigate ability to auto-scroll lock the console
| null | 8 |
train
|
TISTUD-1168
|
Add Common Interface for consolidating UI errors and notifying listeners when status changes
| null | 5 |
train
|
TISTUD-1169
|
Write a document on Ruble localization
|
We now allow Rubles to be localized. Add a document to the Wiki covering the following topics (might be two, depending on the amount of content): * How the architecture works * How to externalize strings * How to contribute a new localization The document should have a few short examples to illustrate the concepts.
| 3 |
train
|
TISTUD-1171
|
Upgrade Run/Debug/Deploy icons
|
We have a a few icons (as detailed in the attached document) that need upgrading as they are not in keeping with they rest of the Studio UI. In general, they should be a bit more three-dimensional and colorful. * Run icon * Debug Icon * Distribute/Deploy icon
| 5 |
train
|
TISTUD-1175
|
JavaScript externalizations are not evident in commands menu
|
Please see capture at http://www.screencast.com/t/ZGzGqfaZfq0w. The string externalizations in the JavaScript ruble are not evident in the Commands menu. Furthermore, the list of keys in the en.yml do not match the drop down menu list. Steps to Replicate : 1) Open Titanium Studio 2) Clone the JavaScript ruble and select the development branch 3) Edit the en.yml file, save and cycle Studio Actual Results : The cache.en_US.yml file contains the edited values, however the JavaScript drop down menu has not changed. Expected Results : The commands menu should contain the new values.
| 8 |
train
|
TISTUD-1179
|
Titanium Studio: titanium.py create: iphone project imported into studio does not include ipad as a selected target
|
When an iphone project is created using 'titanium.py create', and imported into studio, ipad is not selected as a deployment target. This is relevant because projects imported into studio after being created by 'titanium.py create' do not initially contain tiapp.xml deployment target tags. The tags are created on import based on the presence of a respective platform folder (i.e., NewProject/iphone). Because iPad and iPhone use the same folder, they should both be selected as targets when imported to studio for the first time. Steps to Reproduce: 1. Generate a new iphone project using titanium.py create, such as: {code:title=} // dhydeMBPLion:~ dhyde$ /Users/dhyde/Library/Application\ Support/Titanium/mobilesdk/osx/1.8.1/titanium.py create --platform=iphone --type=project --dir=/Users/dhyde/Downloads --name=NewProject --id=com.appcelerator.project // {code} 2. Import the project into studio. 3. Open tiapp.xml and observe the deployment targets. Expected Result: iPhone and iPad should be selected as targets. Actual Result: Only iPhone is selected.
| 8 |
train
|
TISTUD-1180
|
MobileWeb : Selecting to clean a mobile web project does not remove the contents of the build folder
|
Steps to reproduce: 1. Create a default Titanium project and be sure to have mobile web selected as a target 2. Run the project as a preview in the browser 3. In Ti Studio select Project > Clean... Actual result: The contents of the build folder persist Expected result: The contents of the build folder are removed
| 5 |
train
|
TISTUD-1182
|
Create ACS Overview Page
|
When a user wishes to learn more about Appcelerator Cloud Services from inside Studio, they are directed to this page here: https://wiki.appcelerator.org/display/tis/Appcelerator+Cloud+Services It needs to be filled with appropriate content. Some of that will be instructions on how to use the functionality, and some of it how to enable it inside Studio. I would imagine this top-level page could be a landing area, and specific sub-pages could be created as necessary.
| 8 |
train
|
TISTUD-1183
|
Add "release notes" overview to Titanium SDK update dialogs
|
As in Studio 1.5, we previously prompted for user updates with a custom dialog box containing a browser pointing to a remote URL containing the latest set of release notes, similar to this: http://developer.appcelerator.com/apidoc/mobile/1.8.1/changelog.html, but formatted differently. I've attached a screenshot of how 1Password does it, which seems fine. Ideally, this dialog would _follow_ clicking on the yellow toast (though note the case where we had both a SDK and a Studio simultaneous update--we should handle that gracefully) The SDK and Studio dialogs will be identical, save the URL in the middle. However, we only do the SDK update dialog right now, as we completely control that process.
| 20 |
train
|
TISTUD-1184
|
MobileWeb : Remove the "Beta" tag from mobile web for Ti Studio 2.0 release
|
As per Ingo, this ticket is for ensuring the removal of the beta tag in Ti Studio 2.0 There are two main places this needs to occur: 1. In tiapp.xml overview view 2. In the new project wizard
| 2 |
train
|
TISTUD-1185
|
Only check ACS checkbox if cloud services will actually be added
|
In the attached image, I am not using an ACS-compatible SDK version, so the control is greyed out. However, the checkbox is still checked, making me think that it _will_ use cloud services, even though I can't change that option. Instead, in this case, the checkbox should be unchecked.
| 3 |
train
|
TISTUD-1186
|
Add Label for "More Info" to ACS cloud area
|
From the demo, Jo ann had asked for the Info (?) link to be brought back even after a user has selected to enable cloud services.
| 5 |
train
|
TISTUD-1187
|
Move SDK check for cloud services back to 2.0
|
We moved the SDK check to 1.9 for demo purposes. Revert this back to 2.0 by Titanium Studio GA
| 1 |
train
|
TISTUD-1188
|
Dashboard : After logging into Ti Studio for the first time an error is presented and dashboard content fails to load until one refreshes the page
|
Steps to reproduce: 1. Make sure you are not currently logged in to Ti Studio 2. Login to Ti Studio and wait for the dashboard pane to appear Expected result: The dashboard page loads without error Actual result: An error dialog is presented *see attached screenshots* and dashboard content doesn't load *Note a workaround is to just reload/refresh the page, however if one closes the dashboard the same issue persists*
| 8 |
train
|
TISTUD-1193
|
"window" hover has description twice
|
# Open a new .JS document # Type "window" (no quotes) # Hover over the item. Note it says "Reference to the current Window. Reference to the current Window."
| 5 |
train
|
TISTUD-1194
|
Type names missing from JavaScript hover
|
# Create a new Titanium Mobile project # Open up app.js # Hover over a call to "createWindow" # Note the incomplete text: "Create and return an instance of ." Looking at the JSCA file, the type is denoted by <>: "description": "<p>(Optional) A dictionary object with properties as defined in <Titanium.UI.Window>.</p>" Ideally, we pre-process those tags so that we might create a link to the remote type that users can click on. Alternately, we could have the JSCA file generated with a proper enclosing tag (but links might be very difficult)
| 8 |
train
|
TISTUD-1196
|
Add support for new Xcode 4.3 install location
|
It appears Xcode 4.3 has changed the location of developer tools. In particularly, it's packaged as a single application, with the platforms and command-line tools installed underneath. Homebrew has a function that finds the proper path prefix: https://github.com/mxcl/homebrew/blob/master/Library/Homebrew/utils.rb Note...xcode-select no longer seems to be installed by default, so note that we have to have a fallback here * Check /usr/bin/xcode-select -print-path to see if it exists and is an absolute path. if so, use that * Else check if /Developer exists. If so, use that. * Else check if /Applications/Xcode.app/Contents/Developer exists. If so, use that. * Else ask spotlight where Xcode is (mdfind "kMDItemDisplayName==Xcode&&kMDItemKind==Application). if that succeeds, append /Contents/Developer to that location
| 5 |
train
|
TISTUD-1198
|
Merge multiple update dialogs into a single dialog
|
If there are multiple product updates (i.e. Studio and a SDK), we should pop up a single yellow toast, and a "release notes" dialog that allows you to switch between the currently active product release notes. Suggestion is we do something similar to apple...we have a set of checkboxes at the top for all products being updated, and then clicking on a product shows the release notes below
| 13 |
train
|
TISTUD-1199
|
Use pre-configured web servers to launch Mobile Web preview
|
The Mobile Web "browser preview" launch configuration uses some separate settings for determining which browser to launch. Instead, we should have a drop down respecting the current browser settings in preferences: * Have a radio button for "Global settings" or "Specific choose:". * If user selects to specifically choose a different option than the global settings, have a drop down with the following options: ** Internal browser ** System browser ** Browser 1 ** Browser 2 * Have a link to open the preference page for users to manage the settings. If any launch configuration fails because a browser setting has been removed, fall back to an external browser using the system default.
| 13 |
train
|
TISTUD-1200
|
Exclude derived resources from validation
|
# Create a new Mobile Web project # Run a browser preview # Note the litany of errors in /build/mobileweb. All of those are derived resources, and as such, should not show errors.
| 5 |
train
|
TISTUD-1204
|
Create test plan for tiapp.xml module additions
|
The new additions to the tiapp.xml need formal testing. We need a test plan.
| 13 |
train
|
TISTUD-1217
|
Use "TestFlight" logo on relevant dialogs and wizards
|
Add the TestFlight logo to at least the following screens: # Register existing # Publish wizard
| 8 |
train
|
TISTUD-1218
|
Add a "TestFlight" description to Register Existing and Publish screens
|
At the top of the "Register Existing" and right below the "Publish" screen dropdown, add the following text: "TestFlight allows developers to publish beta builds of applications to a group of users organized into a team." This might need to be contributed as part of an extension point or interface.
| 2 |
train
|
TISTUD-1219
|
Minor tweaks of "Publish" screen and menu
|
*Menu* # The menu item seems to be writing out the name improperly (see image) *Publish Screen* # Rename the wizard to "Publish _AppName_ to _TeamAlias_" # The Manage... button needs to go to the Studio TestFlight preferences # Don't show the error message if there are no registered teams on dialog open. Instead, add a description of "Choose the platform to which you wish to publish, and the publication target" # Add a label below the platform choice with "Platform choice is determined by the platforms this provider supports and the deployment targets for this project." # Add a label below the dropdown as shown in TISTUD-1218. # Disable the dropdown until is has something to select # If choosing "Publish...", auto-select the first item in the list if there is one
| 8 |
train
|
TISTUD-1221
|
OpenShift: surface the root cause to the error dialog when creating an application failed
|
Currently, when creating an OpenShift application failed, the project creation wizard will show an error dialog as attached, but it doesn't contain the actual root cause that made the creation fail. User would have to go to Help > Titanium Studio > View Log File... to see the full response. We should change the behavior to surface the cause in the details section of the error dialog.
| 5 |
train
|
TISTUD-1222
|
Parameter content assist showing HTML tags
|
# Create a new Titanium Mobile project # Open the app.js file, if it is not open already # Type the following on an empty line in that file: Ti.UI.createWindow( # If you do not get context information after typing the open parenthesis, type ctrl-shift-space h3. Expected behavior: No tags should appear in the parameter description and types indicated via < and > should appear in the text with the brackets stripped. h3. Actual behavior: The <p> tag appears in the description.
| 5 |
train
|
TISTUD-1223
|
OpenShift: creating an OpenShift PHP project failed
|
Followed the steps at https://wiki.appcelerator.org/display/tis/OpenShift+Deployment to create an OpenShift PHP project, and when the wizard finishes, an error is generated as shown in the attached screenshot. Then when checking Help > Titanium Studio > Run Diagnostic Log..., I do see the new OpenShift app, so it looks like it's a problem with cloning the repo.
| 5 |
train
|
TISTUD-1224
|
Add ACS module XML to tiapp.xml when cloud-enabling a project
|
Both when creating a new project with cloud enablement, and upgrading an existing one, we need to add the ID for the cloud module into the tiapp.xml The module id is "ti.cloud"
| 5 |
train
|
TISTUD-1226
|
Create test plan for TestFlight integration
|
A test plan needs to be created for TestFlight integration.
| 13 |
train
|
TISTUD-1227
|
Incorrect JSCA file selected for content assist when creating new Titanium Mobile project
|
1. Create new Titanium Mobile Project 2. Choose an SDK, but _not_ the latest one (i.e. choose 1.8.1 when 1.9 is installed) 3. See 1.8.1 selected in the tiapp.xml, but right-click on the project > build path, and notice the latest JSCA file (i.e. 1.9) is selected
| 8 |
train
|
TISTUD-1229
|
"Mobile Web" action icons should use HTML5 icon, not the "server" one
|
The icons in "preview" and "package" should be the HTML5 icon used for content assist, not the server icon
| 3 |
train
|
TISTUD-1230
|
Update project-specific run/debug/package menus with favorites and recent history
|
Similar to the global run/debug menus, add run/debug/package history to bottom of App Explorer and Project Explorer menus (perhaps show favorites, then separator, then last five, per project) * Run ** Emulator/Simulator options ** -------------------------- ** Device options ** -------------------------- ** Favorite configuration 1 ** -------------------------- ** Recent configuration 1 ** Recent configuration 2
| 20 |
train
|
TISTUD-1231
|
Add MobileWeb platform to SDK dashboard configuration screen
|
# Add a new platform to the dashboard (add an icon with and without a questionmark) # Mobile web will show a question mark on first launch, or first time it appears # Clicking on the question mark will show the information in the following panels (based on # There will be a link which opens Preferences > General > Web Browser, and another link which opens https://wiki.appcelerator.org/display/tis/Mobile+Web+Support {panel} Mobile Web previewing works best in modern HTML 5-compliant browsers. We recommend you configure your Studio browsers before working on mobile web projects: 1) Click [here] to open browser preferences. 2) Add one or more entries for <OS-X specific choice here>. Alternately, if your default system browser meets one these requirements, you can leave the preference alone. 3) Save and close the preference. {panel} Text to replace for *<OS-X specific choice here>*: * OS X: Safari 5+, Chrome 10+, or Firefox 10+ * Windows: Chrome 10+, Firefox 10+, or IE 10 * Linux: Chrome 10+ or Firefox 10+
| 20 |
train
|
TISTUD-1236
|
Show text hovers on variable/identifiers in declaration statements
|
When hovering over the name of the identifier/variable in an assignment/declaration we don't get hovers as we do when hovering over the exact same variable in a reference.
| 3 |
train
|
TISTUD-1237
|
Text hovers not showing on rhs of variable assignments
|
If we hover over the rhs of an assignment where it is a function call, we don't get hovers for the method we're invoking.
| 5 |
train
|
TISTUD-1257
|
Kitchen Sink : Importing Kitchen Sink from the samples area sometimes produces an error and doesn't allow the sample to be imported
|
Steps to reproduce: 1. Launch Studio 2. Ensure you do not have Kitchen Sink as a project in Studio or your workspace 3. Import Kitchen Sink from the Studio samples Actual result: An error dialog is displayed and Kitchen Sink is not imported Expected result: Kitchen Sink is imported without error *Note since this error does not occur every time I was unable to capture the error dialog, but I attached the log*
| 8 |
train
|
TISTUD-1259
|
Studio installer for Windows: Install screen has rendering and refresh issues during install
|
Description: While testing the installer for Windows, we noted that the border around the detail field, and the border around the progress bar were not initially drawn. When another window is placed over the installer window and then closed, the borders appear. Please see screenshots for more information Steps to reproduce: 1) If studio is installed, uninstall it 2) Download the installer from my.appcelerator.com 3) Run the installer and examine the window 4) Open the detail view 5) PLace a window over the installer window and then close it Results: The borders around the detail field and the progress bar are not drawn, placing a window over the installer window then closing it causes them to appear. Expected: No rendering issues on the installation window. Note: We also saw text overwriting itself in the detail field on one out of three attempts, but have been unable to reproduce it thus far.Image "badRefresh" shows this behavior.
| 5 |
train
|
TISTUD-1260
|
Titanium Studio: MobileWeb: Preferences need MobileWeb default run configuration menu
|
The Titanium preferences menu needs a default run configurations sub-menu for MobileWeb. Android has a default run configuration menu. Parity issue and basic functionality. The MobileWeb sub-menu (default browser, etc.) would be in the preferences menu below the Android default configuration settings. Screenshots attached.
| 8 |
train
|
TISTUD-1261
|
Snippets view color scheme on Windows is not consistent with other views
|
Currently the color scheme for the snippets view on Windows (tested on XP specifically) is not consistent with the other Studio views. See attached screenshots Background colors need updating Disabled tag buttons are not painted properly Hover over the tag buttons has an outline Snippet popup toolbar bg color has incorrect border colors
| 13 |
train
|
TISTUD-1266
|
TiStudio: Projects - Cannot import a project when project is copied from a GitHub repository folder
|
Steps to reproduce: 1. Import a project from a GitHub repository folder 2. Delete project from Studio; do not select *Delete project contents on disk* 3. Copy project from GitHub repository folder into workspace folder 4. Import project from workspace Actual: Get a *Invalid project description* error. See attachment. Expected: Should be able to import copied projects Note: No logs were generated.
| 8 |
train
|
TISTUD-1268
|
Titanium Studio: Content Assist: assist menu intermittently fails to close at all
|
In addition to being persistent as a stand-alone window when focused (related issue), the content assist menu intermittently fails to close at all until studio closes. Pressing escape, clicking away, etc. do not close the content assist menu. Steps to Reproduce: 1. Create a default project. 2. Open content assist within the app.js editor. 3. Click the content assist menu to give it focus. 4. Close the content assist menu (e.g., 'escape', click away, etc.). Expected Result: Content Assist menu should close. Actual Result: Content Assist menu intermittently does not close at all until studio is closed.
| 8 |
train
|
TISTUD-1269
|
Titanium Studio: Content Assist: content assist results in no proposals if code file contains syntax error warnings
|
If a code file contains syntax error warnings, and content assist is called, no proposals will be generated. This interferes with development. Steps to Reproduce: 1. Create a new project. 2. Insert the following code: {code:title=app.js} switch() { case Ti. } {code} 3. Move the cursor to the right of "Ti.". 4. Active content assist (cntrl + space). Expected Result: Content Assist should be invoked with proposals. Actual Result: No proposals.
| 8 |
train
|
TISTUD-1271
|
iOS: Xcode 4.3 - Dashboard link to install Xcode fails
|
Description: While testing the Xcode 4.3 capabilities, I started with a clean system and installed studio. On the dashboard an option is given to install Xcode. When clicking on this link, the Appstore opens, but reports a failure. See attached image for details. Steps to reproduce: 1) Install Studio 1.0.9 2) Launch studio and on the dashboard, select "let's get started" 3) Select the iOS SDK button and the install link Result: The Mac app store opens but the request fails Expected: The Mac app store opens to a supported Xcode version page
| 8 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.