issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-358
|
Code-assist icons should not be IE and Firefox on mobile projects (or at all)
|
The code-assist show icons that are active or grayed in order to inform the developer if a property (or function) is supported on a specific browser. While this is useful when developing web pages, it has no added value on mobile applications. There are however android and iPhone (which is very ugly by the way) icons. But those must be activated in the *Editors* Preference window. (see screenshot) * The default setting should be (Android and iPhone) for Mobile projects. * And no icons for Desktop projects.
| 1 |
train
|
TISTUD-373
|
Label adjustment for deploy targets in new mobile project wizard
|
I'm not sure how this looks on other platforms, but on Ubuntu 9.10, the "Deployment Targets" label is centered vertically with all of the deploy targets. This makes the first item look like it is associated with the previous item in the dialog (see attached). Older screenshots show the deploy targets running horizontally. If these are supposed to be vertical, then I would justify the label to the top instead of centering it.
| 1 |
train
|
TISTUD-380
|
Request for "Install Titanium SDK from URL" to install Continuous Builds under directories reflecting their dates, to distinguish them from major releases in the TiApp editor
|
When testing Continuous Builds, it is very useful to be able to easily differentiate between each day's release, and also the official releases. Currently, however, only one version of each SDK can exist for TiStudio at one time using the "Install Titanium SDK from URL" feature. The workaround is to download and extract the packages to the SDK directory manually. The suggestion is to append the date to the end of the SDK version number (most likely by simply naming the SDK directory to reflect this format). Thus, the package: http://builds.appcelerator.com.s3.amazonaws.com/mobile/1_6_X/mobilesdk-1.6.3-20110418162355-linux.zip would be shown in the TiApp editor as: 1.6.3-20110418 To add weight to the argument for this feature, Marshall has also agreed that it would be extremely useful.
| 1 |
train
|
TISTUD-383
|
Help menu not showing in Ubuntu 11.04
|
Only the "Window"-menu is available, the "Help"-menu is not showing, which makes it impossible to update to a newer SDK.
| 8 |
train
|
TISTUD-415
|
App ID with dash/hyphen - Malformed App Id error
|
If I try to create a new project and the App ID contains a dash character like this: {{net.example.project-hd}} ... Titanium Studio RC1 reports an error: {color:red}Malformed App Id (example: com.companyname.appname){color} But the dash character *is allowed* in the App ID. It works also in previous versions of Titanium Developer and Apple accepts apps with this App IDs. This is an big show stopper because I'm not able to import my old projects with dash characters in the App ID.
| 3 |
train
|
TISTUD-400
|
Color code console output for Ti.API.info, debug, warn and console filtering
|
In Titanium Developer the console output color codes the info, debug, and warn logging functions. It's very handy when scrolling through to see what is what. You can also filter out the 3 types of logging if you just want to see, info, or info + debug, or info + warn.
| 1 |
train
|
TISTUD-406
|
Use mobile project's active SDK api.jsca file
|
When creating and importing a titanium mobile project, we should copy the api.jsca file for the SDK being used by that project. If the api.jsca file does not exist, then we should fall back to the api.jsca in the timobile plugin. Also, if the SDK version is changed while editing a tiapp.xml file, we should update the api.jsca, if necessary, when the tiapp.xml file is saved.
| 1 |
train
|
TISTUD-407
|
Confirm TiStudio default update set is set to "stable" not "beta"
| null | 1 |
train
|
TISTUD-421
|
Hide user email address at bottom right hand corner of IDE
|
Note: discussed with Ingo today by email. Currently, TiStudio shows the user's email address in the bottom right hand corner of the IDE. This may not be good for users wishing to publish public demo or training videos, as it reveals their email address to everyone. Consider either replacing this with their devcenter display name (this may be desirable, as it links the video to their devcenter identity, which will possibly be useful later on when the developer marketplace goes live), or replacing it with a "logged in" or "logged out" message/indicator.
| 1 |
train
|
TISTUD-428
|
Allow a ruble to contribute the image for a template
|
allow a ruble to contributing the image for a template see attached picture
| 1 |
train
|
TISTUD-434
|
Support specifying the density of the emulator
|
h1. Feature Support specifying the "Abstracted LCD density" of an Android Virtual Device in the "Debug Configuration" in Titanium Studio. Also add the field to the Titanium preference page to support a default value. Right now, only the API, Screen, and Log level can be changed. By adding this additional field, it would be easier for developers to test multiple densities. h2. Associated Helpdesk Ticket http://appc.me/c/APP-692888
| 13 |
train
|
TISTUD-448
|
Allow users to add new platform targets after project creation
|
Description: While testing studio, it was noted that new deployment targets could not be added to an existing project. For example, a project created for an Android deployment had the iOS targets grayed out. It is possible to manually edit TiApp.xml to set targets to true. This enables the "run on simulator" for iOS, and in my test was able to launch the project in the simulator. Steps to reproduce: 1) Create a new Titanium Mobile project in Studio 2) Select "Android" as the only deployment target 3) When the project is created, open TiApp.xml and note that only Android is available to select/deselect 4) Open the pure xml tab of TiApp.xml and set deploy target for iOS to "true" Result: Your project can be launched in the simulator, but installed on device will launch then quit and has no icon. Expected: Either no ability to add or remove targets after project creation or the ability to add with the same default structure as during project creation. Suggested solution: * user checks platform option in tiapp.xml * Call platform script to initialize new platform. This would (most likely) add another build folder, and copy several resources into a specific location * Update tiapp.xml with reference to new platform * Validate project specifics as per what we would do in the new project wizard * Suggest we don't _remove_ platform support...alerting the user we can't remove platform support for a project if they try to uncheck a box.
| 13 |
train
|
TISTUD-454
|
We want interface Builder integrated with the Titanium studio next release.
|
We want interface Builder integrated with the Titanium studio next release.
| 1 |
train
|
TISTUD-474
|
Add unit tests for TiAppModel and TiManifestModel
|
Add unit tests for both classes.
| 1 |
train
|
TISTUD-475
|
Add unit tests for TiAppModelUtil
| null | 1 |
train
|
TISTUD-476
|
Add unit tests for TitaniumUpdaterUtil
| null | 1 |
train
|
TISTUD-477
|
Add unit tests for MobileUsageUtil
| null | 1 |
train
|
TISTUD-478
|
Add unit tests for DesktopUsageUtil
| null | 1 |
train
|
TISTUD-479
|
Add unit tests for SDKLocator, SDKManager, SDKEntity classes
| null | 1 |
train
|
TISTUD-480
|
Add unit tests for login/logout logic
|
This might also test Studio capabilities (i.e. debugging on/off)
| 1 |
train
|
TISTUD-481
|
Rename "*Utils" classes to "*Util"
|
In order to be consistent across products, we should rename instances of *Utils classes to drop the 's,' i.e. MobileUsageUtils -> MobileUsageUtil
| 1 |
train
|
TISTUD-483
|
Linux: Adding new expresssions name is not readable, the background and text color is too similar
|
Steps to Reproduce: 1. Create a new application on tiStudio 2. Go to the Expressions Pane and add new expressions 3. Type anything in for the name Actual Result: Text color and background color too similar hard to read Expected Result: Should be readable Note: Duplicate of bug Ti-Stud 426 that was against the Win platform
| 8 |
train
|
TISTUD-486
|
Cannot right-click on a folder in project explorer
|
Steps to Reproduce: 1. Launch Ti Studio 2. Select the Project Explorer tab 3. Click the triangle to expand the project 4. Right click on the Resources folder Actual Result: Nothing happens Expected Result: Should display the context menu Note: It is the area that makes item not selectable, if there are two projects and both not expanded, the 2nd project will not have a context menu
| 8 |
train
|
TISTUD-492
|
Create feature and builder for TiStudio unit tests
| null | 1 |
train
|
TISTUD-499
|
Increment Titanium Studio Master version # to 1.0.2
|
Details on attached wiki page: http://wiki.appcelerator.org/display/tools/Update+Studio+Versions
| 1 |
train
|
TISTUD-501
|
Add Support for debugging on Android devices (tethered)
|
we have the following issues open for ios and android to add debugging support for device Enhancement request - Add Support for debugging on device http://jira.appcelerator.org/browse/TIMOB-4626 http://jira.appcelerator.org/browse/TIMOB-4625 once these are addressed studio would need to add UI to support the features. This ticket is only for the Android side of the equation. The task here is to agree on a discovery mechanism with platform. It might be that we pass the IP address Studio is listening on to the device, or we might have the device broadcast and Studio would listen. After that, the rest of the process is identical to the current mechanism. Additional ADB info: http://developer.android.com/tools/help/adb.html
| 13 |
train
|
TISTUD-504
|
Convert Aptana And Titanium Studio plugins to use ISO 8601 format for build qualifier
|
Currently, the build uses Unix timestamps for most features and plugins, i.e.: com.appcelerator.titanium.aptana.ui.override_1.0.0.1306280624.jar A much nicer presentation would be: com.appcelerator.titanium.aptana.ui.override_1.0.0.20110524_234344.jar YYYYMMDD_HHMMSS It may be that we can do this incrementally, as the build qualifier I believe is an alphabetical sort, and 2 > 1, so any renumbered plugins would show as newer.
| 8 |
train
|
TISTUD-505
|
Add build qualifier to *.override plugins
|
Plugins: com.appcelerator.titanium.aptana.editor.findbar.override_1.0.0.jar com.appcelerator.titanium.aptana.git.ui.override_1.0.0.jar com.appcelerator.titanium.aptana.scripting.ui.override_1.0.0.jar All are missing the build qualifier (the segment after the point version).
| 1 |
train
|
TISTUD-506
|
Path to BlackBerry sdk directory does not fill with correct location
|
When you download the BlackBerry SDK by clicking on the link "Update SDK..." it automatically changes the "BlackBerry SDK Directory" path to "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Appcelerator" and not the location of the newly installed BBsdk.
| 1 |
train
|
TISTUD-509
|
Revamp error messages when user is unable to log in
|
Currently, we default to "incorrect user name or password" as the most common error message. This appears to be causing confusion with some users. In this situation: # If server is completely offline or unreachable, indicate "The login server is currently unreachable. Please try again in a few minutes" # If server returns specifically an error with username or password, indicate "The specified username and/or password is incorrect. Please try again" # In all other cases (assuming server error, malformed request, etc), indicate the server returned an error, and direct the user to consult the web page at: http://aptana.com/r/titrouble (but obfuscate the URL so as to reduce confusion about the redirect)
| 8 |
train
|
TISTUD-1166
|
Setting Log Level in Console view has no effect on the console log
|
There is no way to filter the console log based on event type such as "debug", "info", "error", etc. Changing the Log Level has not affect. This is the same for both iOS and Android. Is there another way to filter the log based on the level of the event? Step 1: run the example app below Step 2: Open "Run Configurations..." Step 3: Change "Log Level" Step 4: Test the log levels with the the app. {code:title=app.js} var win = Titanium.UI.createWindow({ title : 'Test', backgroundColor : '#fff', layout : 'vertical' }); var errorButton = Titanium.UI.createButton({ top : 20, left : 10, right : 10, height : 35, title : 'error' }); win.add(errorButton); var warnButton = Titanium.UI.createButton({ top : 20, left : 10, right : 10, height : 35, title : 'warn' }); win.add(warnButton); var infoButton = Titanium.UI.createButton({ top : 20, left : 10, right : 10, height : 35, title : 'info' }); win.add(infoButton); var debugButton = Titanium.UI.createButton({ top : 20, left : 10, right : 10, height : 35, title : 'debug' }); win.add(debugButton); var traceButton = Titanium.UI.createButton({ top : 20, left : 10, right : 10, height : 35, title : 'trace' }); win.add(traceButton); errorButton.addEventListener('click', function() { Ti.API.error('##### ERROR !!!'); }); warnButton.addEventListener('click', function() { Ti.API.warn('##### WARN !!!'); }); infoButton.addEventListener('click', function() { Ti.API.info('##### INFO !!!'); }); debugButton.addEventListener('click', function() { Ti.API.debug('##### DEBUG !!!'); }); traceButton.addEventListener('click', function() { Ti.API.trace('##### TRACE !!!'); }); win.open(); {code} h3. Associated Helpdesk Ticket http://appc.me/c/APP-192448
| 13 |
train
|
TISTUD-518
|
Look into adding unit tests for packaging
| null | 1 |
train
|
TISTUD-537
|
Increment Titanium Studio to 1.0.4
|
Update the version # to 1.0.4
| 1 |
train
|
TISTUD-564
|
Chromium: Ctrl+Shift+W does not close other open editors when focus is on the embedded browser
|
Pressing Ctrl+W does not close Dashboard pane. Ctrl+W will close other panes. If there are multiple panes open, Ctrl+Shift+W does not close any windows when focus is on the Dashboard pane. If the focus is not on the Dashboard pane, Ctrl+Shift+W will work as expected and close all panes.
| 3 |
train
|
TISTUD-570
|
Create initial configuration process
|
When first starting Titanium Studio a user may not have properly configured their SDKs Individual processes should be allowed to contribute to the configuration screen. Some may be automatic processes (i.e. they need no user interaction, but need to alert the user), and some require user feedback or choice. Current processes: * iOS SDK installation * Android SDK installation * BlackBerry SDK installation * Firefox Browser location * Git install (windows only): Choose Portable Git? * Python: Auto-configure interpreters
| 1 |
train
|
TISTUD-572
|
Enable creation of module projects
|
Allow for the creation of mobile module projects. This is an umbrella ticket to be split into smaller tasks. * Android steps: http://wiki.appcelerator.org/display/guides/Module+Developer+Guide+for+Android#ModuleDeveloperGuideforAndroid-Creatingamodule * iOS Steps: http://wiki.appcelerator.org/display/guides/Module+Developer+Guide+for+iOS#ModuleDeveloperGuideforiOS-Step1%3ACreatingyourFirstModule We need the following: # New Titanium Module wizard (allowing user to choose iOS/Android or both) # Import an existing module project # During wizard, ask user if they wish to create a shell test project to act as a test harness for testing the module # Steps/Launchers to compile the module and deploy it (this would mean deploying it to the root titanium install directory on disk so that other apps can use it) # Ability in other tiapp.xml editors to include modules in your project (these could be already installed ones, or ones from your workspace) # Create documentation for module (tidocs to JSCA file) # Upload finished module project to marketplace
| 1 |
train
|
TISTUD-582
|
Windows: Pressing Cancel on installer does not stop installation process
|
1) Launch installer 2) Press Cancel Results: Prompt appears - "You are about to quit setup. If you quit now, Titanium Studio will not be installed. Do you want to continue?" 3) Press Yes Expected: Installer quits. Actual: Installation proceeds to the "Choose File Associations" page. Notes: Pressing Next will lead to the "Installation Incomplete" page. Pressing Cancel then Yes on a second time (on the "Choose File Associations" page) will go to "Installation Incomplete" page.
| 5 |
train
|
TISTUD-584
|
Importing project causes a "'Building workspace' has encountered a problem" error
|
1) Copy uatest2 to you Titanium Studio Workspace (uatest2 is attached) 2) Import project into TiStudio Results: A "Problem Occurred" error message appears (see screenshot and attached log files)
| 21 |
train
|
TISTUD-589
|
new mobile projects can't find appicon.jpg resulting in "1 error detected" shown on TiApp pane
|
Description: When creating a new Studio Mobile project, the TiApp.xml editor is shown. On this pane, the default app icon field contains appicon.jpg. For new mobile projects, the field is marked with a red "x" and "1 error detected" is shown at the top of the window. This does not occur on Win7 or any other system tested. (Mac OS X 10.7 and 10.6.8, Ubuntu 10.04) Note: Navigating to the .jpg file does not remove the error flag. Steps to reproduce: 1) Install Titanium Studio, build: 1.0.4.201108101535 on windows XP 2) Create a new mobile project 3) Examine TiApp.xml Result: appicon.jpg in the field, but red x and error shown. Expected: No problem with appicon
| 8 |
train
|
TISTUD-592
|
Titanium Studio should support the -n flag to tibuild.py
|
When packaging, the -n will not show the install splash screen by putting a .installed file in the Contents directory. When this file exists, Titanium Desktop Apps will not show the install splash screen the first time the app runs. A customer was asking for this on developer.appcelerator.com: http://developer.appcelerator.com/question/124142/how-to-test-titanium-desktop-app-how-to-get-rid-of-titanium-installer-screen
| 1 |
train
|
TISTUD-600
|
Add preference for default settings on android run/debug configurations (API & Screen size)
|
h5.Feature Request Enable Studio to change the default settings used when it creates an Android Run or Debug Configuration for the first time on a project. E.g. Currently, Studio installation creates new Android configurations using API: 2.3.1 and Screen: WVGA854. This is an inconvenient that emulator screen size is too big for laptop screens, taking up over half the display, so this change the default to something smaller. Also be able to control which API is used by default. h5.Additional info To customize device resolution / density from command line: >emulator -avd HVGA800 -scale 96dpi -dpi-device 160 http://developer.android.com/guide/developing/devices/managing-avds-cmdline.html Further info can be found here as well: http://developer.android.com/guide/developing/tools/emulator.html http://developer.android.com/guide/developing/devices/emulator.html Suggest creating a child page of the titanium preference page to hold that information and allow the user to set it.
| 13 |
train
|
TISTUD-623
|
Need to be able to pass additional emulator arguments from run/debug configurations
|
When a run/debug configuration is created, we need the ability to pass additional command-line arguments to the android emulator. As an example, the -scale argument in order to use skins whose full scale causes them to be larger than the screen you are running on. For example, I am using the Motorola MD860 skin for the Atrix 4G whose screen is 960 pixels high. The resulting emulator window is some 1200 pixels high but my screen is only 900 pixels high. If you run the AVD from the AVD Manager, it offers the option to run with a particular screen size which uses the -scale argument. We need the capability to do this in Studio. I would recommend simply adding an extensible option to specify any additional command line arguments. The standard Eclipse launch configurator allows this on the configuration's Target tab but that appears to be disabled in Studio. Please re-add the tab and allow those arguments to be passed to the emulator. Note: This can only be allowed on SDK versions that support the feature...i.e this won't work on 1.8, but should work on 2.0
| 8 |
train
|
TISTUD-605
|
Epsilon (Show Match Count) option from the search tab does not update on a new search, need to retoggle to check to get the updated value
|
Steps to Reproduce 1. Menu Edit -> Find 2. Type something that can be found in the .js file 3. Check the Epsilon sign 4. Create a new search Actual: The epsilon value is not updated Expected: The value to be updated with the new search result Workaround: Toggle the check mark to get the new value
| 5 |
train
|
TISTUD-651
|
Add Browse button to Save As dialog box
|
See the attached screen...request is to add a Browse button so that you can select the path in which to save the file rather than having to type the path.
| 1 |
train
|
TISTUD-656
|
Change the Log File Location
|
h3. Problem The log file created by Titanium is being saved in the Documents folder of the app. The main problem is that the Documents folder gets backed up by iCloud, and it would be better not to include logs in the user backups. h3. Expected behavior Customer wants to change the location of the logs in somewhere else like in the Application Support/Logs. h3. Additional Information: http://www.apple.com/icloud/what-is.html h3. Associated HD Ticket: http://appc.me/c/APP-525161
| 1 |
train
|
TISTUD-675
|
Add snippets based on Kitchen Sink API examples
|
Inspired by Motorola's Motodev, let's add a set of snippets of drag&drop code to Studio. We could add such snippets for common functions. Or, as Tony G suggested, this could be the evolution of Kitchen Sink. We'd rip out all its API demo code and make each a snippet that could be dropped into a project. See http://developer.motorola.com/docstools/motodevstudio/images/feature_snippets_lg.jpg/ for their UI. We should use a similar categorized arrangement of snippets, but one based on common use cases within our APIs. Prof Support, Dev Relations, and Training could collaborate to create the snippets to be added.
| 1 |
train
|
TISTUD-687
|
Open timodule.xml file in editor for user after generating mobile module project
|
We should be opening the timobile.xml file after we generate a mobile module project, as a means of getting users started more easily.
| 5 |
train
|
TISTUD-713
|
Windows 7 Installer "Choose Install Location" defaults to Administrator's profile
|
If the TiStudio installer is executed while logged in as a non-administrative user, just as when any new software is installed, the user is prompted to provide the administrator's password. At the "Choose Install Location" stage, a path within the administrator's profile, of {{C:\Users\Administrator\AppData\Local\Titanium Studio}}, is populated by default: !http://img812.imageshack.us/img812/50/screenshot356c.png! Obviously standard users do not have write-access to this directory. We should populate this field with a directory under the user's profile, rather than the administrator's.
| 13 |
train
|
TISTUD-990
|
Console: Norwegian characters not correctly displayed
|
h2. Problem Console doesn't display Norwegian characters correctly. h2. Test case {{Ti.API.log('Jeg kan løpe')}} produces a console output in unicode "Jeg kan l\U00f8pe"
| 8 |
train
|
TISTUD-714
|
Add support for listing and importing sample projects through the Dashboard
|
Add a controller-action that will return a list of available sample projects. That list should contain the following information for each sample: * Sample name * Sample ID * Description * Screenshot-image path (can be empty, for now) The Dashboard will create sample-items using this information and will trigger the Samples import handler when a specific sample is clicked on.
| 1 |
train
|
TISTUD-715
|
Compute the status of the installed SDK asynchronously
|
At the moment, the call to compute the installed SDKs status is done synchronously, which causes for delays when the Dashboard loads. We need to change that call to start an asynchronous job and report with an event when the results are ready to be rendered.
| 1 |
train
|
TISTUD-718
|
Create a controller-action that returns the logged-in Titanium user information
|
The action should return, at least, the logged-in user name (email) and the MD5 hash of his/her email.
| 1 |
train
|
TISTUD-734
|
Change "Deploy" tool tip to "Publish"
|
For clarity of terminology, please change the tool tip for the "deploy" menu to be "publish". This better fits with the current usage of that menu and the items inside. * Update root label in App/Project Explorer * Correct references to "Deploy" in wiki documentation
| 5 |
train
|
TISTUD-744
|
Sometimes git managed projects can open with no deployment targets in Tiapp.xml detail but the Overview shows targets selected.
|
Description: While evaluating the impact of using git-managed projects in Studio, I encountered a situation where the git project's Tiapp.xml was missing the deployment targets in the xml view. The targets were checked in the "overview" view however. A quit and relaunch of studio then populated the deployment targets in the xml view, and removed the checkmarks in the "overview" view. Before studio quit and relaunch: {code} <?xml version="1.0" encoding="UTF-8"?> <ti:app xmlns:ti="http://ti.appcelerator.org"> <id>com.nolanwright.kitchensinkipad</id> <name>KitchenSink-iPad</name> <version>1.0</version> <publisher>nwright</publisher> <url>appcelerator.com</url> <description>No description provided</description> <copyright>2010 by nwright</copyright> <icon>default_app_logo.png</icon> <persistent-wifi>false</persistent-wifi> <prerendered-icon>false</prerendered-icon> <statusbar-style>default</statusbar-style> <statusbar-hidden>false</statusbar-hidden> <fullscreen>false</fullscreen> <navbar-hidden>false</navbar-hidden> <analytics>true</analytics> <guid>1000da51-9909-4a9e-a82f-52de59746d37</guid> </ti:app> {code} After relaunch: {code} <?xml version="1.0" encoding="UTF-8"?> <ti:app xmlns:ti="http://ti.appcelerator.org"> <deployment-targets> <target device="mobileweb">true</target> <target device="iphone">true</target> <target device="ipad">true</target> <target device="blackberry">false</target> <target device="android">false</target> </deployment-targets> <id>com.nolanwright.kitchensinkipad</id> <name>KitchenSink-iPad</name> <version>1.0</version> <publisher>nwright</publisher> <url>appcelerator.com</url> <description>No description provided</description> <copyright>2010 by nwright</copyright> <icon>default_app_logo.png</icon> <persistent-wifi>false</persistent-wifi> <prerendered-icon>false</prerendered-icon> <statusbar-style>default</statusbar-style> <statusbar-hidden>false</statusbar-hidden> <fullscreen>false</fullscreen> <navbar-hidden>false</navbar-hidden> <analytics>true</analytics> <guid>1000da51-9909-4a9e-a82f-52de59746d37</guid> </ti:app> {code} Steps to reproduce: 1) Import KS-iPad from titanium_mobile 1.7.X 2) Build from device to populate build folder 3) In terminal, switch branches to master with git checkout -f master 4) Switch back to 1.7.X with "git checkout 1_7_X" 5) Examine TiApp.xml Result: The Tiapp.xml does not have the <deployment-targets></deployment-targets> Expected: TiApp.xml overview matches xml detail and deployment targets are selected and "true"
| 8 |
train
|
TISTUD-746
|
Add GIT configuration to the Dashboard
|
Add dashboard support for checking GIT (windows only). Configuring GIT should be allowed on a Windows OS through the installation of Portable GIT. * Remove current dialog popup on startup * Add check for git configuration to current dashboard check * If check fails, add button that pops up the same dialog as shown now (which ultimately does the installation) Note that for Aptana Studio, this would require us implementing a similar dashboard as Titanium Studio so that we may perform the same checks there.
| 40 |
train
|
TISTUD-747
|
Add Python configuration through the Dashboard
|
Currently, when Studio first runs, a "configuring python interpreters" dialog comes up. Instead, we should integrate this dialog withe the current dashboard configuration process. It would allow for checking and configuring Python interpreters through the Dashboard configuration actions. * Remove current dialog popup on startup * Add check for python configuration to current dashboard check * If check fails, add button that pops up the same dialog as shown now. Note that for Aptana Studio, this would require us implementing a similar dashboard as Titanium Studio so that we may perform the same checks there.
| 20 |
train
|
TISTUD-754
|
Manage the 'modules' for a specific Mobile project through the TiApp editor
|
Create a section in the TiApp editor for manipulating the modules in the tiapp.xml for a Mobile project.
| 1 |
train
|
TISTUD-755
|
Allow "pre-selection" of template in project wizards
|
Apologies for the last minute note on this, but it appears we need a new feature for the dashboard implementation. Basically, we need to be able to "pre-select" a template on popping up the new project wizard. The rationale is that we will have a number of buttons to invoke "New From Template" in the dashboard, but our current project wizard does not support this. Suggest having a short description or preview of the selected template at the bottom to indicate which one was selected. If you choose "finish" it uses that template, otherwise, you could choose a different template if you went to the next screen (though the pre-selected template should show as the chosen item). It's likely we will want to reconfigure the presentation of platform options in the Titanium wizards to create some extra space. There may need to be a little dashboard work done to enable a button to make this happen. If so, please create a subtask and work with Shalom on this.
| 1 |
train
|
TISTUD-757
|
Comment the com.appcelerator.titanium.core.user package
|
This package is sparse on comments. Please add comments to elucidate the classes and methods.
| 1 |
train
|
TISTUD-760
|
Add launch configuration option to run iPhone/iPad simulator with retina display
|
Steps To Reproduce: 1. Create a titanium mobile project 2. Run as only gives the user ipad/iphone simulator 3. Select any one and go to Hardware menu under iOS Simulator 4. See iPhone (Retina) Actual: Cannot set studio to run in retina Expected: To give the user the option to simulate on retina display
| 8 |
train
|
TISTUD-761
|
Titanium Studio: Android reserved namespace is not resulting in a malformed app id error
|
When creating a new project in Titanium Studio (or editing the tiapp.xml), Application ID tokens (tok1.tok2.tok3) containing invalid java namespace identifiers do not generate an error. Steps to Reproduce: 1. Open Titanium Studio. 2. Create a new project. Make sure the project supports Android. 3. Make one of the tokens in the Application ID an invalid java identifier (see below). Expected Result: An error message should appear and the project can't be created or an error message remains (if editing tiapp.xml). Actual Result: No error message appears. The project can be created. tiapp.xml shows no errors when viewed in the editor. The project can build to iOS, but the Android build fails with an error such as: [ERROR] Error(s) compiling generated Java code [ERROR] /Users/dhyde/Documents/Titanium Studio Workspace/helloworld/build/android/gen/com/appcelerator/123/ApplicationStylesheet.java:5: ';' expected package com.appcelerator.123; ^ Note: Below is the Java documentation regarding valid identifiers. Java Documentation (excerpt follows): http://java.sun.com/docs/books/jls/second_edition/html/lexical.doc.html#40625 Excerpt: An identifier is an unlimited-length sequence of Java letters and Java digits, the first of which must be a Java letter. An identifier cannot have the same spelling (Unicode character sequence) as a keyword (§3.9), boolean literal (§3.10.3), or the null literal (§3.10.7). Keywords: abstract default if private this boolean do implements protected throw break double import public throws byte else instanceof return transient case extends int short try catch final interface static void char finally long strictfp volatile class float native super while const for new switch continue goto package synchronized Boolean Literals: true false Null Literal: null
| 5 |
train
|
TISTUD-764
|
Create a dropdown in the tiapp.xml form editor to select an Android runtime
|
We need to support switching Javascript runtimes with a dropdown in the tiapp.xml form editor for Android apps. This is controlled via a simple property: <property name="ti.android.runtime">v8</property> Valid values are "rhino" and "v8"
| 1 |
train
|
TISTUD-766
|
Rework info message for 'native' and 'implements' from Mozilla JS validator
|
In my JavaScript source code when editing in Titanium Studio, if you use the words 'native' and 'implements' as function names, it gives me a warning of a syntax error in the syntax highlighting, but everything compiles and runs fine. This is because those items are future reserved words. We should rework the messages as [INFO], and say something like "Native is a future JavaScript reserved word. Its usage may not be compatible with all JavaScript runtimes"
| 5 |
train
|
TISTUD-769
|
Automatically scan for i18n files
|
We had a neat script created in the community to automate the finding and creating of strings.xml entries: https://gist.github.com/1341925 Would be good to get this translated into a ruble and integrated into Titanium Studio. Or configured to be a compiler plugin, which already has Python hooks. Original author has been contacted and is supportive of the effort.
| 13 |
train
|
TISTUD-775
|
Disable the V8 option in the TiApp editor when the Android SDK version is incompatible
| null | 1 |
train
|
TISTUD-787
|
As a Titanium Developer, I want to view and inspect all available snippets, to determine which snippets I want to insert into my source
|
Inspired by Motorola's Motodev, let's add a set of snippets of drag&drop code to Studio. We could add such snippets for common functions. Or, as Tony G suggested, this could be the evolution of Kitchen Sink. We'd rip out all its API demo code and make each a snippet that could be dropped into a project. See http://developer.motorola.com/docstools/motodevstudio/images/feature_snippets_lg.jpg/ for their UI. We should use a similar categorized arrangement of snippets, but one based on common use cases within our APIs. Prof Support, Dev Relations, and Training could collaborate to create the snippets to be added.
| 34 |
train
|
TISTUD-788
|
Studio: Lion - When first launching studio, it is not possible to expand the contents of the last project in project explorer
|
Description: When you first launch Studio and then attempt to expand the disclosure triangle for the last project in project explorer, nothing happens. The triangle rotates, but no project content is displayed below the project name, and the scroll bar does not adjust for the new content. Since this is on Mac, it is possible to pull the project explorer window content up enough to see that there is indeed nothing there. Please see attached image with the window pulled up to show the lack of content. This does not occur on 10.6.8. Steps to reproduce: 1) Quit studio if it is open 2) Relaunch studio (be sure you have enough projects to fill your project explorer) 3) Open project explorer if it is not already 4) Scroll to the last project in the list 5) Click the disclosure triangle Result: The triangle rotates, but no content is displayed. Expected result: The triangle rotates, project content is displayed, scrollbar is adjusted to match new window size
| 8 |
train
|
TISTUD-791
|
Content assist - context info popup does not appear in parameters if there are values present in the parameters.
|
1. Create a new project 2. Create a new JS file in the project 3. Place the following content into the JS file {code} /** * @param {String} a * This is the first parameter * @param {Object} b * The second parameter * @param {Number} c * Last one */ function testing(a, b, c) {} {code} 4. Type testing( Results: context info popup appears and that it displays all three parameters with their names and their descriptions 5. Place the cursor between the parenthesis and force the context info popup to appear using shift-ctrl-space Results: context info popup appears and that it displays all three parameters with their names and their descriptions 6. Change testing() to testing(10, 20, 30) 7. Place the cursor between the parenthesis and force the context info popup to appear using shift-ctrl-space Expected results: context info popup appears and that it displays all three parameters with their names and their descriptions Actual results: Nothing appears
| 3 |
train
|
TISTUD-794
|
Auto-lock the console if you scroll away from the bottom - like the terminal
|
Requesting the ability to auto-lock the console if you scroll away from the bottom and then unlock when you scroll back to the bottom. Would like it to function like the terminal does. I have attached a screencast to demonstrate the difference in behavior between the Studio Console and the Terminal. (Terminal on the left, Studio Console on the right). http://screencast.com/t/plTURcRFB
| 20 |
train
|
TISTUD-804
|
Add current locale to Dashboard URL
|
We need to send the user's currently requested Java locale on the query string so that we can send back localized versions of the Dashboard in the future. Suggested URL is &nl=ISOCode, as passed in to the Java executable.
| 1 |
train
|
TISTUD-806
|
Show Indicator during Run on Emulator that tells the user that the app is still loading
|
When running an app on an emulator, there is no indication that an app is finished loading. This indication will tell the user that they can now mess around with the emulator. We can show a progress dialog/bar during the Loading process, which finishes when the loading process is complete.
| 8 |
train
|
TISTUD-809
|
Titanium Studio: Installer - Titanium Studio needs a shortcut to the uninstaller in the Windows start menu folder
|
There is no explicit uninstaller for Titanium Studio in both Windows 7 and Windows XP. Currently uninstallation must be done through Control Panel > Programs > Uninstall. Current wiki entry on uninstallation (excerpt below): http://wiki.appcelerator.org/display/tis/Uninstalling+Studio Windows Using the Add or Remove Programs applet on Control Panel to uninstall Studio. If Studio is not listed in your "Add or Remove Programs", it may be because you chose to install Studio with a zip. You will have to determine where you installed it (hopefully in your Program Files) and manually delete it. Delete the remaining application folder off the hard drive (we do not automatically delete this as some users have complained). If you did not change your installation location on disj=k during the install, it is likely in: Windows Vista/7: C:\Users\username\AppData\Local\Aptana Studio or Titanium Studio) Windows XP: C:\Program Files\Aptana Studio or Titanium Studio
| 1 |
train
|
TISTUD-810
|
Remove html5 references inside mobile web platform
|
Links and references to the "html5" naming for mobile web can be removed.
| 1 |
train
|
TISTUD-811
|
Create XSD for tiapp.xml and timodule.xml files to provide validation
|
In order to create a better validation experience for tiapp.xml and timodule.xml files suggestion is to create a XSD for them. Note that tiapp.xml spans both mobile and desktop applications. I don't know if it's feasible to create a XSD that spans both cases, or if it should be split into two.
| 13 |
train
|
TISTUD-818
|
Studio: Dashboard - clicking navigation items ("configure" "learn" etc) repositions the window
|
1.open dashboard if need 2.scroll down a bit 3.click "configure" "learn" etc results: window repositions itself expected: no such repositioning. see screen vid cap
| 8 |
train
|
TISTUD-820
|
Titanium Studio: Validation - TiApp Editor allows invalid android runtime to be selected with incompatible SDKs
|
TiApp Editor allows invalid android runtime to be selected with pre-1.8.0 SDKs. Steps to Reproduce: 1. Create a new project using 1.8.0.1. 2. Open tiapp.xml in the TiApp Editor. 3. Change the runtime to Rhino (this creates an entry in the xml where there was none before: <property name="ti.android.runtime">rhino</property>). 4. Change the runtime to V8 (this changes the contents of the xml property line). 5. Change the SDK version (in TiApp Editor) to pre-1.8.0.1 (e.g., 1.7.5). Expected Result: Rhino should be the default runtime. Actual Result: V8 is the default runtime (invalid). Note: If you select a pre-1.8.0.1 SDK without first selecting a different runtime (thus adding the property line to the xml), the default runtime is correctly changed to Rhino in the TiApp Editor.
| 8 |
train
|
TISTUD-822
|
Add message for pre-1.0.7 dashboard users that they must update to 1.0.7 to get Mobile SDK 1.8.0
|
1.0.7 users will get the new dashboard, whereas pre-1.0.7 users will get the old dashboard. Add messaging to the existing dashboard to indicate that they must upgrade to 1.0.7 to get the new 1.8.0 mobile SDK.
| 1 |
train
|
TISTUD-835
|
Shortcut created for Install to Android Device does not work when focusing on the editor
|
See attached picture for shortcut config. Step 1: hit command+shift+L 2x to bring up the shortcut preferences Step 2: search for android Step 3: set 'Install to Android Device' to work with command+shift+f9 and when = In Window Step 4: hit ok Step 5: open a .js file Step 6: click on the editor Step 7: hit command+shift+f9 Step 8: notice that 'Install to Android Device' does not run. Step 9: click in App Explorer and hit the shortcut and it will work fine. Step 9: repeat the same steps but set the shortcut to open About and it will work fine in the editor.
| 8 |
train
|
TISTUD-993
|
Unicode Code Points from the SMP are encoded according to CESU-8 rather than the expected UTF-8
|
h2. Problem Titanium Studio doesn't convert to UTF-8 correctly in case of Unicode code points starting at U+10000. When I copy-and-paste a symbol located in the SMP (supplementary multilingual plane) from Safari/Chrome into Titanium Studio and try to save the file, the output is not UTF-8, but CESU-8. h2. Steps to reproduce {code} Code Point: U+1D6FB Unichar: (Due to TC-421, I cannot paste the character here. Please take it from: http://www.unicode.org/charts/PDF/U1D400.pdf) UTF-8: 0xF0 0x9D 0x9B 0xBB Name: MATHEMATICAL ITALIC NABLA UTF-16: 0xD835 0xDEFB CESU-8: 0xED 0xA0 0xB5 0xED 0xBB 0xBB {code} http://www.decodeunicode.org/de/u+1d6fb/properties http://www.decodeunicode.org/de/u+d835/properties http://www.decodeunicode.org/de/u+defb/properties You can read the output file like this in the terminal: {code} hexdump -C <file> {code} You will see two byte sequences (representing the high and low surrogate from UTF-16, Java's native character format) consisting of three bytes, that are encoded according to UTF-8. However, expected output is one four-byte sequence.
| 8 |
train
|
TISTUD-844
|
New Project Wizard: auto-generate app id based on company id and project name
|
An auto-generated company id prefix during project creation (i.e., Xcode) would be helpful. Xcode has this feature. Titanium and Eclipse do not. As of now, I do not believe there is a conflict of interest. Screenshot attached comparing Titanium, Eclipse and Xcode, highlighting the auto company-prefix feature.
| 8 |
train
|
TISTUD-869
|
Run git clean on build subfolders during project clean
|
Anytime you do a *clean* on a Titanium mobile project, the *build/android* and *build/iphone* directories have any existing *.gitignore* files deleted. This is bothersome when those files are the easiest way to ensure that the *build/iphone* and *build/android* paths exist when storing a project on git. If they don't exist, a user attempting to build the project will get an error on their first attempt. It would be ideal if, when a *clean* is performed on a project, that any existing *.gitignore* files were left untouched in those directories. Running a git clean should restore the project to the state it was check in with.
| 8 |
train
|
TISTUD-875
|
TiApp Editor: add Edit > Undo and Redo functionality
|
Edit > Undo and Redo are not selectable when using the TiApp editor, nor do the Undo/Redo keyboard shortcuts work. As an outlier, the Undo (cntrl + z) keyboard shortcut happens to work in Windows 7. Steps to Reproduce: 1. Create a new project. 2. Open tiapp.xml in the TiApp Editor. 3. Change text in a field (such as Application ID). 4. Try the following commands: Edit > Undo. Edit > Redo. Undo Keyboard Shortcut: (OS X: cmd + z), (Windows 7: cntrl + z). Redo Keyboard Shortcut: (OS X: shift + cmd + z), (Windows 7: cntrl + y). Expected Result: Menu options should be selectable and work. Keyboard shortcuts should work. Actual Result: Undo/Redo menu options and keyboard shortcuts do not work, with the exception of the Undo keyboard shortcut in Windows 7.
| 8 |
train
|
TISTUD-878
|
Show error in problems view if a project has an incorrect configuration
|
# Create a new Ruby project # Assign the Titanium Mobile nature to the project # View your log file, note a number of errors, but nothing the user would ever see (unless they went looking) In this case, we should show an error in the problems view (and also an X on the project) to indicate that something is wrong (in this case, that the project is missing a tiapp.xml file and a manifest and that users should check their project settings)
| 13 |
train
|
TISTUD-882
|
Rename installation packages so that filenames no longer contain spaces
|
As demonstrated in [this twitter conversation|http://www.exquisitetweets.com/tweets?eids=kHGGcM2MyP.kHIZakiQH6.kHJrXixufs.kHJUriL39N.kHLycersB2], for some reason some browsers, in certain circumstances, will not download files with filenames that contain spaces. Please consider renaming the Windows and OSX install packages in [resources|https://my.appcelerator.com/resources] to *TitaniumStudio + extension* * Fix the installer process to generate the new names for Titanium Studio on OS X and Windows * Update preview.appcelerator.com to respect the new names
| 8 |
train
|
TISTUD-886
|
invalid button name in "uninstall studio" dialog
|
# Have Studio installed # download newer version # Install new version # it asks to uninstall previously installed version # dialog says "click Next" when button is called "Uninstall"
| 2 |
train
|
TISTUD-887
|
display background from PSD file
| null | 1 |
train
|
TISTUD-891
|
Titanium Studio: Projects - File > New > <project type> list is not alphabetically sorted
|
File > New > <project type> list is not alphabetically sorted. The context menu version of this list is sorted. Screenshot attached. Steps to Reproduce: 1. Open Titanium Studio. 2. Click File > New. Expected Result: Project types should be alphabetically sorted in ascending order. Actual Result: Project types are not alphabetically sorted (included in screenshot). Note: Project Explorer > context click > New is sorted in alphabetical ascending order (included in screenshot).
| 8 |
train
|
TISTUD-894
|
V8 Proxy: Filter stack variables by regular expression from the Mobile SDK
|
The format we chose was a file with a variable regular expressions delimited by newlines. Verify that filtered variables from <tisdk>/android/variable_filters.txt (per TIMOB-6549) are not displayed in Variables view.
| 1 |
train
|
TISTUD-905
|
Add right-click option to open analytics for a specific application
|
In project explorer (not sure where to put this in App Explorer--might be a custom button off by default that can get added to the menu bar in Customize View) we have a button that launches the analytics page for that application.
| 8 |
train
|
TISTUD-907
|
Modules UI - Restrict the modules to an API-Level
|
We need to restrict the modules selection in the TiApp UI to an API-Level that is enforced on a module. The platform team adds an api-level value into the module's manifest, and will add a modules-api-level into the 'version.txt' file of the Titanium SDK. We'll need to read both to find an API level match, and do whatever needs to be done in the UI in order to allow selecting only valid modules, and display warnings when incompatible modules exist in the tiapp. To test: # Create a new Titanium Mobile project # Open up tiapp.xml and add a module to the project using the modules panel (I used ti.greystripe). Note the module appears active # Edit the module manifest file to raise the apiversion to something like "3" (current maximum version is 2 for 1.8/2.0) # Save tapp.xml and restart Studio. Note that the module now appears still available, but should appear greyed out Note that this change is only relevant to Android. iOS does not care about apiversions
| 13 |
train
|
TISTUD-909
|
Android: V8: evaluate Ti.API.terminate() to signal application to terminate immediately.
|
Send an evaluation request to call "Ti.API.terminate()". This will cause the application to terminate immediately.
| 1 |
train
|
TISTUD-913
|
Titanium Studio: Content Assist - content assist menu persistent in the OS if it has focus
|
Content Assist menu is persistent in the OS if the assist menu has focus (i.e., by clicking on it). Other OS program windows are now obfuscated by the content assist menu until the focus is shifted back to Titanium Studio proper. Screenshot attached. Steps to Reproduce: 1. Open Studio and create a new project (or open an existing project). 2. Click in the text editor of app.js (or any .js file). 3. Press control + space to bring up the content assist menu. 4. Select any item from the suggestion list by clicking on it (the menu as-is will not exhibit this behavior). 5. Open any other program (such as Chrome) and move the other program window over the content assist menu. Expected Result: The content assist menu should disappear behind the other program window, as it should have the same OS hierarchy as Titanium Studio. Actual Result: The content assist menu persists and obfuscates the other program window until the focus shifts back to Studio.
| 8 |
train
|
TISTUD-919
|
Add mobileweb user agent for content assist
|
When a user uses content assist, we need to include "mobile web" as a platform choice. # Add a mobile web user agent (key 'mobileweb') # Add it to the default list of user agents selected for the mobile nature Icons are attached.
| 1 |
train
|
TISTUD-946
|
Entering PHP variables in multi-line string causes titanium studio to completely hang
|
Open the test.php file in Titanium Studio. The crash can be reproduced by typing: $url on line 11 of test.php. I have to alt-option-esc to get out of Titanium. I've included the crash log. {code:title=crash log} Date/Time: 2011-12-14 10:54:59 -0800 OS Version: 10.6.8 (Build 10K549) Architecture: x86_64 Report Version: 7 Command: TitaniumStudio Path: /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/TitaniumStudio Version: 3.0 (3.0) Parent: launchd [226] PID: 20845 Event: hang Duration: 5.84s (sampling started after 2 seconds) Steps: 18 (100ms sampling interval) Pageins: 0 Pageouts: 0 Process: TitaniumStudio [20845] Path: /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/TitaniumStudio UID: 501 Thread 91d3 DispatchQueue 100 User stack: 18 start + 41 (in TitaniumStudio) [0x2781] 18 _start + 209 (in TitaniumStudio) [0x2853] 18 main + 1518 (in TitaniumStudio) [0x37e5] 18 original_main + 1782 (in TitaniumStudio) [0x30f8] 18 run + 4687 (in eclipse_1310.so) [0x75956] 18 startJavaVM + 120 (in eclipse_1310.so) [0x77492] 18 startJavaJNI + 1991 (in eclipse_1310.so) [0x7878d] 18 JVM_GetClassInterfaces + 7118 (in libjvm.dylib) [0x126443c6] 18 JVM_MonitorWait + 9994 (in libjvm.dylib) [0x12603267] 18 JVM_Lseek + 162116 (in libjvm.dylib) [0x125f4547] 18 JVM_Lseek + 162160 (in libjvm.dylib) [0x125f4573] 18 JVM_Lseek + 162812 (in libjvm.dylib) [0x125f47ff] 18 ??? [0x14001374] 18 ??? [0x14003e31] 18 ??? [0x14003e31] 18 ??? [0x14003f97] 18 ??? [0x14004473] 18 ??? [0x14003f97] 18 ??? [0x14003f97] 18 ??? [0x1400b9d9] 18 Java_sun_reflect_NativeMethodAccessorImpl_invoke0 + 38 (in libjava.jnilib) [0x6390fe] 18 JVM_InvokeMethod + 79 (in libjvmlinkage.dylib) [0xf174f] 18 JVM_InvokeMethod + 370 (in libjvm.dylib) [0x1260def4] 18 JVM_InvokeMethod + 1046 (in libjvm.dylib) [0x1260e198] 18 JVM_NewInstanceFromConstructor + 3585 (in libjvm.dylib) [0x1260ce21] 18 JVM_Lseek + 162116 (in libjvm.dylib) [0x125f4547] 18 JVM_Lseek + 162160 (in libjvm.dylib) [0x125f4573] 18 JVM_Lseek + 162812 (in libjvm.dylib) [0x125f47ff] 18 ??? [0x14001374] 18 ??? [0x14003f97] 18 ??? [0x14003f97] 18 ??? [0x14003f97] 18 ??? [0x14004473] 18 ??? [0x14004473] 18 ??? [0x14003f55] 18 ??? [0x14003f55] 18 ??? [0x14003e31] 18 ??? [0x1400430d] 18 ??? [0x14003f55] 18 ??? [0x14003f55] 18 ??? [0x14003e31] 18 ??? [0x147b0370] 18 ??? [0x14258ce6] 18 Java_org_eclipse_swt_internal_cocoa_OS_objc_1msgSend__III + 194 (in libswt-pi-cocoa-3659.jnilib) [0x6ae411c8] 18 ??? [0x6ace9058] 18 callback + 835 (in libswt-cocoa-3659.jnilib) [0x6aba0da0] 18 JVM_IsSameClassPackage + 1404 (in libjvm.dylib) [0x12648e82] 18 JVM_FindLoadedClass + 3478 (in libjvm.dylib) [0x126192d5] 18 JVM_Lseek + 162116 (in libjvm.dylib) [0x125f4547] 18 JVM_Lseek + 162160 (in libjvm.dylib) [0x125f4573] 18 JVM_Lseek + 162812 (in libjvm.dylib) [0x125f47ff] 18 ??? [0x14001374] 18 ??? [0x14003e31] 18 ??? [0x14003f55] 18 ??? [0x147a75f9] 18 Java_org_eclipse_swt_internal_cocoa_OS_objc_1msgSendSuper__Lorg_eclipse_swt_internal_cocoa_objc_1super_2II + 249 (in libswt-pi-cocoa-3659.jnilib) [0x6ae48458] 18 -[NSApplication sendEvent:] + 6431 (in AppKit) [0x9803b60b] 18 ??? [0x6ace91d8] 18 callback + 835 (in libswt-cocoa-3659.jnilib) [0x6aba0da0] 18 JVM_IsSameClassPackage + 1404 (in libjvm.dylib) [0x12648e82] 18 JVM_FindLoadedClass + 3478 (in libjvm.dylib) [0x126192d5] 18 JVM_Lseek + 162116 (in libjvm.dylib) [0x125f4547] 18 JVM_Lseek + 162160 (in libjvm.dylib) [0x125f4573] 18 JVM_Lseek + 162812 (in libjvm.dylib) [0x125f47ff] 18 ??? [0x1434f810] 18 ??? [0x14003e31] 18 ??? [0x147a7ad4] 18 ??? [0x147a75f9] 18 Java_org_eclipse_swt_internal_cocoa_OS_objc_1msgSendSuper__Lorg_eclipse_swt_internal_cocoa_objc_1super_2II + 249 (in libswt-pi-cocoa-3659.jnilib) [0x6ae48458] 18 -[NSWindow sendEvent:] + 5757 (in AppKit) [0x98122b28] 18 ??? [0x6ace91d8] 18 callback + 835 (in libswt-cocoa-3659.jnilib) [0x6aba0da0] 18 JVM_IsSameClassPackage + 1404 (in libjvm.dylib) [0x12648e82] 18 JVM_FindLoadedClass + 3478 (in libjvm.dylib) [0x126192d5] 18 JVM_Lseek + 162116 (in libjvm.dylib) [0x125f4547] 18 JVM_Lseek + 162160 (in libjvm.dylib) [0x125f4573] 18 JVM_Lseek + 162812 (in libjvm.dylib) [0x125f47ff] 18 ??? [0x1434fd20] 18 ??? [0x14003e31] 18 ??? [0x14003f55] 18 ??? [0x14258ce6] 18 Java_org_eclipse_swt_internal_cocoa_OS_objc_1msgSend__III + 194 (in libswt-pi-cocoa-3659.jnilib) [0x6ae411c8] 18 -[NSView interpretKeyEvents:] + 209 (in AppKit) [0x981eded1] 18 -[NSTextInputContext handleEvent:] + 1453 (in AppKit) [0x981f2084] 18 TSMProcessRawKeyEvent + 2515 (in HIToolbox) [0x9a3f7e32] 18 TSMKeyEvent + 998 (in HIToolbox) [0x9a406f65] 18 SendUnicodeTextAEToUnicodeDoc + 700 (in HIToolbox) [0x9a40735b] 18 SendTSMEvent + 82 (in HIToolbox) [0x9a4079de] 18 SendEventToEventTarget + 52 (in HIToolbox) [0x9a3a57f3] 18 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411 (in HIToolbox) [0x9a382ef6] 18 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1567 (in HIToolbox) [0x9a383c2f] 18 _NSTSMEventHandler + 209 (in AppKit) [0x981f27a5] 18 -[NSTextInputContext handleTSMEvent:] + 2657 (in AppKit) [0x981f3217] 18 -[NSTextInputContext insertText:replacementRange:] + 421 (in AppKit) [0x981f527a] 18 ??? [0x6ace91d8] 18 callback + 835 (in libswt-cocoa-3659.jnilib) [0x6aba0da0] 18 JVM_IsSameClassPackage + 1404 (in libjvm.dylib) [0x12648e82] 18 JVM_FindLoadedClass + 3478 (in libjvm.dylib) [0x126192d5] 18 JVM_Lseek + 162116 (in libjvm.dylib) [0x125f4547] 18 JVM_Lseek + 162160 (in libjvm.dylib) [0x125f4573] 18 JVM_Lseek + 162812 (in libjvm.dylib) [0x125f47ff] 18 ??? [0x1434f5fc] 18 ??? [0x1400405d] 18 ??? [0x1400405d] 18 ??? [0x14003e31] 18 ??? [0x14592380] 18 ??? [0x143e0060] 18 ??? [0x14003e31] 18 ??? [0x14003e31] 18 ??? [0x14003e31] 18 ??? [0x14003e31] 18 ??? [0x14003e31] 18 ??? [0x1400430d] 18 ??? [0x1400430d] 18 ??? [0x14003e31] 18 ??? [0x14003e31] ...
| 5 |
train
|
TISTUD-929
|
Dashboard SDK install use case should allow users to specify desired installation directory
|
The way the Dashboard installs Titanium/Mobile SDKs, it requires the SDK paths to be set in the preferences. In the case where the default SDK paths don't exist or invalid (ie, the user doesn't have permission), you will not be able to change the SDK paths to a desired location. To reproduce: 1. Have a valid Ti SDK setup 2. Export the all the preferences via File->Export->General->Preferences 3. Edit the exported preference entry: /instance/com.appcelerator.titanium.core/TITANIUM_SDK_PATH with an invalid path. I used a path that the user does not have permissions, /Users/invalidUser/xxx Save the file 4. Launch Ti Studio 5. Import the preferences via File->Import>General->Preferences 6. Restart Ti Studio Expected: Ti SDK installation starts and prompts for a new location for installation Actual: Ti SDK installation starts and fails The same issue is exhibited with the Android SDK as well. The preferences for them are: /instance/com.appcelerator.titanium.mobile/ANDROID_SDK_PATH The installation is triggered via the configuration in the Dashboard The installation should validate the SDK location to ensure it is valid (exists/write permission), if it is not the user is prompted for a new location
| 5 |
train
|
TISTUD-933
|
Rename imported projects
|
Currently, when importing a project in Studio, you aren't given the option to rename it. This could be useful - I can provide a test if one is requested.
| 1 |
train
|
TISTUD-952
|
Force installation of Android NDK if user is doing Android module development
|
Unsure how to have a conditional install, however, the user does need to have the Android NDK installed before proceeding with building an Android module. Suggest the following: # Add the NDK to the sdk_info.json file. Locations are available from http://developer.android.com/sdk/ndk/index.html # Download from that website # Perhaps install the NDK _under_ the chosen SDK directory, i.e. /android/ndk? # Create a Android NDK Home preference in Preferences > Titanium Studio > Titanium # Test for this preference being set when creating an Android module. # Update dashboard with new tests # Add NDK line in Titanium preferences
| 40 |
train
|
TISTUD-953
|
Pass Android NDK location to Titanium Module build scripts
|
When developing an Android module, you either need to set the ANDROID_NDK environment variable, or set android.ndk in the build.properties of the module Marshall suggested instead that when packaging we call ANT directly (instead of the module build scripts) and pass "-Dandroid.ndk=.." to the scripts. We can get the preference from TISTUD-952. To test: # Create a new Android modules # Set the NDK location # Package the module. If it succeeds, the test is successful. Incorrect packaging would result in the build failing and prompting a user to specify the NDK path manually.
| 5 |
train
|
TISTUD-954
|
Update Snippet Elements in Rubles to support Description, Category, Icon and Tags
|
The following attributes were added to a snippet element: description (String) - description of the snippet category (String) - category for the snippet icon_path (String) - path to icon file tags (list of strings) - tags for the snippet
| 13 |
train
|
TISTUD-957
|
Implement Snippet Popup Preview
|
Snippet Preview Popup display information about a snippet: Snippet name, scope, and triggers - honors theme colors Snippet expansion contents - Colorized/Formatted based on content-type settings Toolbar to perform additional actions - Navigate to source action (opens the contributing ruby file for modification of the snippet)
| 40 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.