id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
611 |
TISTUD-2151
|
08/27/2012 11:41:01
|
Tweak new device and packaging icons
|
Related to TISTUD-1351, we request a few small changes to the icons: # The Android device debugging icon looks odd next to the iOS one. The phones should probably be at least similar in width # The shadows around the boxes for distribution are too dark. Perhaps just reduce the opacity a bit.
| 5 |
612 |
TISTUD-2156
|
08/27/2012 17:08:14
|
Download the latest Android SDK directly
|
Download the latest SDK unless the user has a compatible SDK already installed. See https://wiki.appcelerator.org/display/tools/Android+SDK+Installation for reference.
| 8 |
613 |
TISTUD-2157
|
08/27/2012 17:10:37
|
Download and install the base required packages
|
The packages include: 1. Platform tools 2. Google Maps v8 3. Base Platform v8 See https://wiki.appcelerator.org/display/tools/Android+SDK+Installation for reference.
| 13 |
614 |
TISTUD-2158
|
08/27/2012 17:25:23
|
"Enable Cloud Services" button is enabled for external tiapp.xml files
|
When opening an external tiapp.xml in the TiApp editor, the 'Cloud Services' button should be disabled just like the other controls that require a project context.
| 2 |
615 |
TISTUD-2159
|
08/27/2012 17:37:06
|
Notify the dashboard when a module installation is completed
|
Fire a dashboard notification at the end of the Module installation.
| 5 |
616 |
TISTUD-2163
|
08/28/2012 14:10:43
|
Rename the configure tab to "Get Started"
|
# Rename the first tab in the Dashboard to "Get Started" # Update the wiki documentation to reference the new tab name (https://wiki.appcelerator.org/display/guides2/Setting+up+Titanium+Studio)
| 5 |
617 |
TISTUD-2164
|
08/28/2012 14:12:29
|
Run the browser configuration check to make sure Mobile Web can be used
|
# If on Mac and Windows, the check described in TISTUD-2187 will be run on dashboard open with the other platform configuration options # If there are compatible browsers, indicate the user is good to go # If there are no compatible browsers, or you are on Linux, indicate the set of required browsers. # Add a button to refresh the check (if it failed)
| 13 |
618 |
TISTUD-2165
|
08/28/2012 14:37:32
|
Add button to create a new Mobile Web project from the dashboard
|
See https://wiki.appcelerator.org/display/prd/Studio+Dashboard for more information.
| 5 |
619 |
TISTUD-2166
|
08/28/2012 14:43:26
|
Add button to dashboard to run previously created projects
|
# Add button to call new action to run project created in above step (APSTUD-4801), greyed out until a project is created, or there is at least one project in the workspace. # If the user happened to close and reopen the dashboard, the "just created" project might be lost. So, we always run the most recent project based on timestamp.
| 8 |
620 |
TISTUD-2167
|
08/28/2012 15:40:08
|
Debugger: Incompatible debugger version.
|
Starting around 2:20 pm PST 8/28/2012, while working in Titanium Studio, build: 2.2.0.201208272345 I started seeing the following on all three OS (Win7, Ubuntu 12.04 and Mac OS 10.8.1): A popup error reading "Incompatible debugger version: The remote debugger version might not match the expected protocol verison (2006040705). The following was in the log: {noformat} !ENTRY com.aptana.php.debug.epl 4 0 2012-08-28 14:21:46.587 !MESSAGE (Build 2.2.0.201208272345) [ERROR] com.aptana.php.debug/debug Unexpected Exception: Listener thread still listening !STACK 0 java.lang.NegativeArraySizeException at org2.eclipse.php.internal.debug.core.xdebug.dbgp.session.DBGpSession.readResponse(DBGpSession.java:490) at org2.eclipse.php.internal.debug.core.xdebug.dbgp.session.DBGpSession.<init>(DBGpSession.java:91) at org2.eclipse.php.internal.debug.core.xdebug.communication.XDebugCommunicationDaemon.startConnectionThread(XDebugCommunicationDaemon.java:166) at org2.eclipse.php.internal.debug.core.daemon.AbstractDebuggerCommunicationDaemon$ReceiverThread.run(AbstractDebuggerCommunicationDaemon.java:244) at java.lang.Thread.run(Unknown Source) !ENTRY com.aptana.php.debug.epl 4 4 2012-08-28 14:21:51.634 !MESSAGE class org2.eclipse.php.internal.debug.core.xdebug.dbgp.protocol.DBGpResponse : org.xml.sax.SAXParseException: Premature end of file. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at org2.eclipse.php.internal.debug.core.xdebug.dbgp.protocol.DBGpResponse.parseResponse(DBGpResponse.java:207) at org2.eclipse.php.internal.debug.core.xdebug.dbgp.protocol.DBGpResponse.parseResponse(DBGpResponse.java:193) at org2.eclipse.php.internal.debug.core.xdebug.dbgp.session.DBGpSession.<init>(DBGpSession.java:94) at org2.eclipse.php.internal.debug.core.xdebug.communication.XDebugCommunicationDaemon.startConnectionThread(XDebugCommunicationDaemon.java:166) at org2.eclipse.php.internal.debug.core.daemon.AbstractDebuggerCommunicationDaemon$ReceiverThread.run(AbstractDebuggerCommunicationDaemon.java:244) at java.lang.Thread.run(Unknown Source) !ENTRY com.aptana.php.debug.epl 4 4 2012-08-28 14:21:51.637 !MESSAGE class org2.eclipse.php.internal.debug.core.xdebug.dbgp.session.DBGpSession : Init response not received. XML=[B@12b9c6d !ENTRY com.aptana.php.debug.epl 4 4 2012-08-28 14:22:06.604 !MESSAGE class org2.eclipse.php.internal.debug.core.xdebug.dbgp.session.DBGpSession : Unexpected null from readResponse waiting for Init !ENTRY com.aptana.php.debug.epl 4 4 2012-08-28 14:22:06.606 !MESSAGE class org2.eclipse.php.internal.debug.core.xdebug.dbgp.session.DBGpSession : Unexpected null from readResponse waiting for Init !ENTRY com.aptana.php.debug.epl 4 4 2012-08-28 14:22:06.641 !MESSAGE class org2.eclipse.php.internal.debug.core.xdebug.dbgp.session.DBGpSession : Unexpected null from readResponse waiting for Init !ENTRY com.aptana.php.debug.epl 4 150 2012-08-28 14:24:59.441 !MESSAGE Incompatible debugger version. The remote debugger version might not match the expected protocol version (2006040705). {noformat} No idea what caused the issue but it spawned a large number of pop up errors. Errors stopped appearing around 2:35 PM PST 8/28/2012. I was unable to find a specific reproduction case.
| 0 |
621 |
TISTUD-2169
|
08/28/2012 16:22:22
|
Add user-friendly labels for template types
|
We have a way of defining groups or categories of templates, but there is no user-friendly name for them such that it could be displayed to the user. Add something that would allow us to group templates as shown in the mockup.
| 5 |
622 |
TISTUD-2170
|
08/28/2012 16:22:56
|
Rework template selection UI to new version
|
By default, the first item in the first group is selected, and the corresponding description is shown. This should be the "Alloy blank" template for Titanium Mobile projects, assuming they have alloy installed
| 13 |
623 |
TISTUD-2172
|
08/28/2012 18:11:04
|
Create build participant to auto-compile embedded ACCS service when changes occur
|
For an integrated project, where the client and server are the same thing, we need to update the bindings for the embedded service when the service changes # Watch for changes in the service.js file # If a change happens, re-run the compilation step to update the bindings.
| 8 |
624 |
TISTUD-2174
|
08/29/2012 10:02:39
|
Dashboard: Develop: Create New Project template is duplicated and deprecated
|
The 'Create New Project' template on the dashboard is duplicated and deprecated by 'Default Project'. 'Default Project' is the option that exists in the New Project Wizard. This occurs on the Dashboard and Dashboard Preview. Steps to Reproduce: 1. Open the Dashboard. 2. View Develop. Actual Result: 'Create New Project' and 'Default Project' both exist though they are the same. 'Create New Project' is deprecated. Expected Result: Only 'Default Project' should exist because it is the option available in the New Project Wizard.
| 5 |
625 |
TISTUD-2178
|
08/29/2012 11:48:07
|
Add version information to Mac browser configuration names and refresh version info on demand
|
Related to TISTUD-1414. As discussed, we need to include the version of the browser in question as part of the browser name (see image for example) Ideally, this value would be dynamic, but that appears to be impossible given the current UI. In the case where the user upgrades the browser later, the suggestion is that when the user re-runs the configuration step to auto-search, we replace the version #s of the existing browsers with the newer version. *Chrome* /Applications/Google\ Chrome.app/Contents/Info.plist *Safari:* /Applications/Safari.app/Contents/version.plist *Firefox:* firefox -v
| 8 |
626 |
TISTUD-2180
|
08/29/2012 13:40:20
|
Add tags column to project template selections screen
|
Once APSTUD-7352 is implemented, add a column to the left displaying a list of all the tags assigned to templates. A template might appear in one or more tagged areas: Left column is separated by template tag. For Titanium Mobile projects, we might see: * Alloy * Titanium Mobile Other project types might just see (assuming there is no tags) * Ruby * Mobile Web * etc Suggest having an "All" tag at the bottom that shows all templates if you'd like to browse the complete list
| 8 |
627 |
TISTUD-2186
|
08/29/2012 16:00:04
|
Publishing: Distribute > Apple iTunes Store: success dialog does not appear
|
When Distribute > Apple iTunes Store is complete, there is no success dialog, but the process appears to have been completed successfully. This is not a regression. Steps to Reproduce: 1. Create a new project. 2. Distribute > Apple iTunes Store. Actual Result: Process completes successfully and the Xcode Organizer is brought up. Expected Result: Process completes successfully, Xcode Organizer is brought up, success dialog appears.
| 5 |
628 |
TISTUD-2187
|
08/29/2012 16:24:40
|
Compare Mobile Web requirements as part of Dashboard MobileSDKConfigurationProcessor.configure() check
|
Mobile Web has minimum supported browser requirements. As part of the dashboard configuration process, we need to check if the current browsers a user has configured match those requirements * Add info to the sdk_info.json file * Check to see if we have configured browsers via TISTUD-1414 and TISTUD-1738 * If not, configure them * If so, check the version strings in the name vs the versions in sdk_info * Return a similar success value to iosSdk with installedBrowsers and installedBrowsers
| 0 |
629 |
TISTUD-2188
|
08/29/2012 16:26:23
|
Add Mobile Web requirements to sdk_info.json file
|
Mobile Web has minimum supported browser requirements. Add an element to sdk_info.json for the dashboard that encapsulates this information (the values below are correct): {code} "mobileweb":{ "win32":{"Firefox":["10.0"],"InternetExplorer":["9.0"],"Chrome":["10.0"],"Safari":["5.0"]}, "macosx":{"Firefox":["10.0"],"Chrome":["10.0"],"Safari":["5.0"]}, "linux":{"Firefox":["10.0"],"Chrome":["10.0"]} } {code} Note that a single number is actually an OSGI version range, i.e. "4.0" == >= 4.0. The above values should accept version ranges
| 5 |
630 |
TISTUD-2189
|
08/29/2012 16:38:05
|
Run browser configuration check on Mac and Windows if necessary
|
If on Mac or Windows, run the configuration in TISTUD-1414 and TISTUD-1738 if there are no browsers configured (if not, you would notice no browser names have version #s attached)
| 5 |
631 |
TISTUD-2190
|
08/29/2012 16:38:35
|
Check version strings from the browser settings vs the versions in sdk_info and return results
|
# Check the version strings in the name vs the versions in sdk_info. The version string is appended to the end of the browser name. # Return a similar success value to iosSdk with installedBrowsers and installedBrowsers
| 5 |
632 |
TISTUD-2200
|
08/30/2012 18:24:27
|
Dashboard: Update Android SDK to 20.0.3 on Production
|
Android SDK 20.0.3 has been tested on all platforms, there are no issues, it can be pushed to the live dashboard.
| 3 |
633 |
TISTUD-2201
|
08/31/2012 01:58:57
|
New user on Appcelerator if directly logins to Titanium Studio, their Login Splash Screen text boxes dislocates upwards and covers Appcelerator logo.
|
This bug affects Titanium Studio 2.1.2; 2.1.1; 2.1.0 Steps : 1.Log out from titanium studio. 2.Launch Titanium Studio . 3.Select second option on Titanium Splash screen : "I don't have an account with Appcelerator".( Screenshot- Titanium Studio_004.png attached) 4. Press "Next" button. 5.Observe the splash screen which asks for login credentials (Screenshot Titanium Studio _001.png attached ) [Expected Result] No UI related error should happen . [Actual Result] Login Screen text boxes are dislocated upwards and covering Appcelerator logo. Note: This issue is specific to Ubuntu 12.04 and Ubuntu 10.04; unable to recreate it on Mac OS X and Windows OS
| 5 |
634 |
TISTUD-2212
|
08/31/2012 11:59:58
|
Auto-update ACCS local port numbers if related projects change
|
When we bind a ACCS service to a Titanium Mobile project, the local port number for the ACCS service might change. We need to listen for these port event changes, and update the references in the local project.
| 8 |
635 |
TISTUD-2213
|
08/31/2012 13:02:43
|
Add Alloy Widget menu item to select/import widgets that are available locally
|
Add a right-click menu "Alloy > Add Widget > (dynamic list of widgets)". Place a separator between the dialog item (from TISTUD-2280) and the actual list. Selecting an item adds it to the app right away, as a quick way to do so when you already know the widget you want. The list of available widgets and metadata will come from the "alloy list widgets" command. When user selects a widget put the id that is listed in the returned json metadata for the widget into the Alloy app/config.json in the dependencies object. For example if the user selected the "Search For Books" widget then the config should look like the following. { "global": {}, "env:development": {}, "env:test": {}, "env:production": {}, "os:ios": {}, "os:android": {}, "dependencies": { "com.appcelerator.searchForBooks":"1.0" } }
| 13 |
636 |
TISTUD-2214
|
08/31/2012 17:43:03
|
Titanium Studio: License Agreement is not provided.
|
Installer copyright information is not available in Installer copyright option. Step to Reproduce: 1. Click on 'Help Menu' 2. Click 'Install New Software' 3. Click on 'Already Install' Link 4. Select Installed 'Titanium Studio' 5. Click on 'Property' Option 6. Select 'License Agreement' Actual Result: No License Agreement is present. Expected Result: Present License Agreement available for user.
| 3 |
637 |
TISTUD-2216
|
08/31/2012 17:44:32
|
Titanium Studio: New Installation Copyright information is missing.
|
Installer copyright information is not available. Step to Reproduce: 1. Click on 'Help Menu' 2. Click 'Install New Software' 3. Click on 'Already Install' Link 4. Select Installed 'Titanium Studio' 5. Click on 'Property' Option 6. Select 'Copyright' Actual Result: No Copyright Information is present. Expected Result: Present copyright Information available for user.
| 5 |
638 |
TISTUD-2217
|
08/31/2012 17:51:42
|
Update ACCS unpublish/list/logcat/loglist commands to pass an appid or app name rather than a directory
|
Based on the related ticket, we need to pass in appids or app names rather than the directory when calling: * unpublish * list * logcat * loglist
| 8 |
639 |
TISTUD-2220
|
08/31/2012 19:56:56
|
Debugger for iOS: Studio does try to connect to device on all networks
|
When trying to connect to device, where both device and system are on the same wifi, but system is also on ethernet, system fails to connect to device.
| 0 |
640 |
TISTUD-2221
|
09/04/2012 09:16:21
|
Dashboard: Dashboard displays old version for build numbers higher then 2.X
|
After updating to the nightly 3.3.0.201209032204 build of Titanium Studio, I now only get the generic old dashboard rather then the new dashboard. Loading in any 2.X build of Titanium Studio loads the correct dashboard. This is a regression as this works in the 2.x builds. Steps to reproduce: 1. Install any Titanium Studio build in the 2.x range. 2. Upgrade from the nightly build to 3.3.0.201209032204. 3. Open Titanium Studio. Expected results: The dashboard should correctly load with the new dashboard content. Actual results: The dashboard loads with the default older dashboard (see screenshot).
| 5 |
641 |
TISTUD-2224
|
09/04/2012 18:28:04
|
Add CLI command support for building an iOS project
|
This one is only for V2 (Node.js). The Python implementation in V1 does not support a building command. We should try call "build" again when we've cleaned all our projects and build automatically is checked. The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed. {code} titanium build [--platform=[iphone,ipad,ios,android,blackberry,mobileweb,etc.]] [--package] [--device] [--simulator|--emulator] [--production] [--development] [--verbose [0-5]] [project-dir] {code}
| 5 |
642 |
TISTUD-2225
|
09/04/2012 18:29:27
|
Add CLI command support for building an Android project
|
This one is only for V2 (Node.js). The Python implementation in V1 does not support a building command. We should try call "build" again when we've cleaned all our projects and build automatically is checked. The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed. {code} titanium build [--platform=[iphone,ipad,ios,android,blackberry,mobileweb,etc.]] [--package] [--device] [--simulator|--emulator] [--production] [--development] [--verbose [0-5]] [project-dir] {code}
| 5 |
643 |
TISTUD-2226
|
09/05/2012 01:40:05
|
Prevent users from using a capital letter in module name or module ID
|
While creating a new android or mobile web module,if the 'Project name' field contains any capital letter, then it is giving error message.Screenshot of the message and studio logs are attached with the bug. Steps to reproduce 1. Create a new titanium mobile module project and select android as deployment target. 2. Give project name - 'MyAndroidModule' and module id - 'ti.mymodule' .Click next and then finish Expected result 2. Android module should get created. Actual result 2. It creates module with many files missing. Gives an error message for the same. Snapshot attached.
| 5 |
644 |
TISTUD-2231
|
09/05/2012 12:48:27
|
Update Alloy branding
|
Update the project and wizard icons with the updated imagery.
| 3 |
645 |
TISTUD-2236
|
09/06/2012 15:37:38
|
Update sdk_info.json file in dashboard to support iOS 6
|
See http://preview.appcelerator.com/dashboard/sdk_info.json for the current content. We need to update the versions for iOS to include 6.0.
| 5 |
646 |
TISTUD-2239
|
09/06/2012 17:40:35
|
Update SDK version checks from 2.2 to 3.0
|
The SDK changed its versioning from 2.2 to 3.0. We need to review any checks inside the code to see if they need to be updated.
| 5 |
647 |
TISTUD-2241
|
09/07/2012 11:11:42
|
Modules in the tiapp section shows as not supported by sdk
|
Steps: 1. Open a tiapp.xml 2. Add a module that has both a name and id (look at the module manifest file) Expected Results: Module should appear as valid and enabled Actual Results: Module is displayed as not supported by sdk Looking at the code, it looks like the issue is with mismatch between id and name. It is also causing junit failures
| 8 |
648 |
TISTUD-2243
|
09/07/2012 14:53:26
|
Build: running titanium project causes No enum const class error
|
Launching Android Emulator in debug, or iPhone Simulator w/o debug mode prompts error message. Android Error Message: "An internal error occurred during: "Launching Titanium Android Emulator - Default_Project". No enum const class com.appcelerator.titanium.core.launching.LogLevel.info" iOS Error Message: "An internal error occurred during: "Launching Titanium iPhone Simulator - Default_Project". No enum const class com.appcelerator.titanium.core.launching.LogLevel.info" Steps to Reproduce: 1. Create Default Mobile Project 2. Run Project Debug as "Android Emulator" OR run in iOS Simulator. Actual Result: Error Message, but app otherwise runs successfully. Expected Result: Debug/run is successful.
| 3 |
649 |
TISTUD-2244
|
09/07/2012 16:28:49
|
NPE in the log when opening Titanium preferences page on Linux
|
When the Titanium Studio > Titanium preference page is opened on Linux, the following exception is generated in the log: {code} !ENTRY com.appcelerator.titanium.ui.ide 4 0 2012-09-04 13:01:14.789 !MESSAGE (Build 2.1.2.201208301612) [ERROR] Failed to load BlackBerry device password !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.ui.preferences.TitaniumPreferencePage.initialize(TitaniumPreferencePage.java:153) at org.eclipse.jface.preference.FieldEditorPreferencePage.createContents(FieldEditorPreferencePage.java:233) at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232) at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501) at org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:674) at org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:888) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:886) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1726) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139) at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1054) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:729) at org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:375) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:371) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.createDialogOn(WorkbenchPreferenceDialog.java:102) at org.eclipse.ui.dialogs.PreferencesUtil.createPreferenceDialogOn(PreferencesUtil.java:192) at org.eclipse.ui.dialogs.PreferencesUtil.createPreferenceDialogOn(PreferencesUtil.java:116) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection$2.linkActivated(TiAppDeployTargetsSection.java:278) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} This is because we are only creating BlackBerry fields on Mac and Windows. Think we should instead always create the fields but then hide them using GridData.exclude according to the OS; that way we don't have to check if a field is null all over the place.
| 5 |
650 |
TISTUD-2245
|
09/07/2012 16:57:44
|
iOS Device Debug and deployment ends up in Error " java.lang.NullPointerException..."
|
An error occurred while running debug on iOS device Error: "java.lang.NullPointerException..." Steps to Reproduce: 1. Create default mobile application 2. Debug on iOS device Actual Result: Error Expected Result: App installed on the device and run in debug perspective.
| 5 |
651 |
TISTUD-2246
|
09/07/2012 18:25:44
|
Android Device Debugger pointer is not pointing to the current lines
|
The debugger Arrow pointer does not indicate any breakpoints in app.js. Steps to Reproduce: 1. Create default project 2. Run debug on the device 3. Press "Step Over" in debug window Actual Result: No Arrow pointer hits the breakpoints in app.js Expected result: Arrow pointer hits the breakpoints.
| 8 |
652 |
TISTUD-2251
|
09/10/2012 15:05:57
|
Support Node/NPM module loadpaths
|
We currently assume that a project root is the module root path. We need to query node/npm for the list of module load paths ($NODE_PATH) and try to resolve/search against those, as well as handle searching up the hierarchy for node_modules directories, and handle loading "core" modules from node itself. The following pseudo-code gives the algorithm: http://nodejs.org/api/modules.html#modules_all_together See: http://www.bennadel.com/blog/2169-Where-Does-Node-js-And-Require-Look-For-Modules-.htm http://nodejs.org/api/modules.html#modules_core_modules Additionally, it may make sense to index the paths specified in NODE_PATH on startup.
| 13 |
653 |
TISTUD-2263
|
09/11/2012 14:36:52
|
Add ability to pass a list of platforms to be initially selected in Titanium Mobile project wizard
|
The Titanium mobile project wizard page currently will select all deployment targets that are enabled. For creating new mobile web project from dashboard, we need the ability to pass in the list of platforms to be selected by default.
| 13 |
654 |
TISTUD-2264
|
09/12/2012 04:41:08
|
HTML Files get !DOCTYPE declarations marked as warnings for unclosed tags
|
This is not a regression bug.This happens on Titanium Studio, build: 2.1.0 as well. Tested and found this bug on : Ubuntu 10.04 and Mac Mountain Lion 10.8.1. Steps to reproduce: 1. Open File > New -> Web Project > and choose "Next" 2. Select the HTML Boilerplate (cached) version and select "Finish" 3. Observe the 'red color' error mark on created new web project. 4. Expand created new web project. Actual result: The "New web project" is throwing error on style.css file. Expected result: Default Project should be error free. Screenshots attached.
| 8 |
655 |
TISTUD-2265
|
09/12/2012 10:38:55
|
Remove extraneous templates as part of Custom Cloud project wizard
|
When creating a new ACCS/Node.ACS project, the project wizard shows Web templates. This is confusing, as those templates don't apply. They should be removed. It's likely we need a project type of nodeacs (since that is different than a straight node.js project might be)
| 2 |
656 |
TISTUD-2267
|
09/12/2012 14:08:09
|
Add deprecated flag to JSCA spec for functions, events and properties
|
Currently only types can be marked as deprecated. We need to extend this to functions, properties, events, and event properties
| 8 |
657 |
TISTUD-2268
|
09/12/2012 14:15:13
|
Add validation build participant to highlight deprecated Titanium Mobile code
|
Once we have the deprecated flag for more JSCA members, we need to validate and warn about deprecated usage on both build and reconcile. This would leave the typical yellow "squiggly" underlining of the reference, as well as an entry in the Problems view.
| 13 |
658 |
TISTUD-2269
|
09/12/2012 16:42:14
|
Preferences: Add ability to display full Xcode path if truncated
|
In the Titanium preferences, if the Xcode path is too long, there is no way to view the full path because the text field is locked. There is no way of knowing which Xcode is being used. This blocks testing. See Screenshot. Steps to Reproduce: 1. Open Preferences > Titanium Studio > Titanium > Xcode Path. Actual Result: If the path is too long, it will be visually truncated, without the ability to reveal the full path. Expected Result: Some mechanism to view the full path.
| 3 |
659 |
TISTUD-2729
|
09/12/2012 17:43:42
|
Update Titanium Mobile HTML template with new iPhone 5 splash image
|
Based on the new image attached to TIMOB-10886, update the default image for samples and templates. Marking this for 3.0.0, as we'll need a new Studio build to get this into user's hands.
| 3 |
660 |
TISTUD-2275
|
09/14/2012 15:18:25
|
Make the left and right arrow keys traverse the list of project templates
|
Left and right arrow keys fail to select project templates. Steps to reproduce. 1. Select 'New' Menu bar 2. Select 'Titanium Mobile Project' 3. Try to select project templates with 'Arrow Keys' ex: Left and Right Keys. Actual Result: Fail to select project templates. Expected Result: Project templates get selected with arrow keys.
| 5 |
661 |
TISTUD-2276
|
09/14/2012 16:14:39
|
Support adding modules with no version specified
|
Titanium SDK added a feature that will default to the latest module version if none is specified int he tiapp.xml (TIMOB-7973). When specifying a module, we should default to no version (use latest). This will enable users to more easily update modules without having to modify the tiapp.xml
| 13 |
662 |
TISTUD-2277
|
09/14/2012 16:31:32
|
Add vertical scrolling to project template description area
|
Unable to scroll down to view project template's detailed description. Steps to Reproduce: 1. Select 'Titanium Mobile Project' from the menu bar 2. Select 'Master Detail Application' 3. Observe the detail description area. Actual Result: 1. The text is hidden and unable to scroll down. Expected Result: 1. All text should be visible and if scroll able in case if text are more descriptive or long.
| 5 |
663 |
TISTUD-2280
|
09/17/2012 12:17:12
|
Present user with Alloy Widget selection dialog to select widgets that are available locally
|
Add a right-click "Alloy > Add Widget > Browse..." menu item/command that opens a dialog/wizard similar to our Project template selection. This is a means of users being able to browse and explore the available widgets when they're not sure the specific one they want. The list of available widgets and metadata will come from the "alloy list widgets" command. When user selects a widget put the id that is listed in the returned json metadata for the widget into the Alloy app/config.json in the dependencies object. For example if the user selected the "Search For Books" widget then the config should look like the following. { "global": {}, "env:development": {}, "env:test": {}, "env:production": {}, "os:ios": {}, "os:android": {}, "dependencies": { "com.appcelerator.searchForBooks":"1.0" } }
| 13 |
664 |
TISTUD-2286
|
09/17/2012 16:48:49
|
Each Platform should have separate pages for their settings, not enough space to adjust all the platform settings on one page.
|
A) Preferences>Titanium Studio>Titanium The 'Titanium' drop node should have the subclasses for: 1. iOS Platform 2. Android Platform 3. BlackBerry Platform 4. Windows Platform a) Each Platform should have different pages for their settings. There is not enough space for all of the platform to be on one page. b) Currently there is only iOS platform for x-code certification settings. It should include all the 'iOS Certification' settings and 'iOS SDK Home' path settings'.
| 13 |
665 |
TISTUD-2287
|
09/17/2012 17:14:48
|
TiApp Editor: prompt to save when focus leaves tiapp editor
|
Android Device Debugger: debug drop-down menu fails to list device option if tiapp.xml is dirty yet has a valid SDK. For instance, if a project has SDK 2.1.2 selected in the tiapp.xml and the xml is saved, then the tiapp.xml sdk version is changed to 3.0.0 but not saved, the debug to device option is not available under Debug > Android Device until the tiapp.xml is saved. There are probably many edge cases surrounding this issue. We are reading the tiapp.xml that is saved, not the one in memory (OR we should just list all run options by default because there is already an invalid config error, see screenshot 'Correct Error'). This is a usability issue. Steps to Reproduce: 1. Create a new project with the SDK set to a version such as 2.1.2.GA or lower (pre-device debugging support). 2. In the project tiapp.xml, change the sdk without saving to a version such as 3.0.0.X or higher (sdk w/device debugging support). 3. Go to Debug > Android Device. Actual Result: Android Device is not there because the tiapp.xml is not saved. See Screenshot 'Usability'. Expected Result: The Android Device entry should exist, and the tiapp.xml should be prompted for save before deployment. Note: There is currently an error pop-up if device debugging is attempted on an sdk below 2.2, so the current implementation already has a safeguard. See screenshot 'Correct Error'.
| 5 |
666 |
TISTUD-2288
|
09/17/2012 17:17:26
|
iOS Device Debugger: Failed to debug on Device and install on Device after relaunch Studio.
|
Description: Debug as iOS device is not working after relaunch TiStud. Log is attached. Debug_test.zip is attached. Steps to reproduce: Import debug_test (debug_test is attached) > Relaunch studio > Debug as iOS. Actual result: Debug is failed. Expected result. Debugger should work
| 5 |
667 |
TISTUD-2290
|
09/17/2012 17:33:06
|
iOS Device Debugging: no console output from device
|
Titanium Studio Console output fail to display output results. Steps to Reproduce: 1. Create default project, add sample code: {code} Ti.API.info('INFO LOGGED'); {code} 2. Run 'debug' on iOS Device. Port forward message should appear on console. 3. Launch app from device. Actual Result: Titanium Studio console log fail to display the console output Expected Result: Titanium Studio console log display the console output.
| 13 |
668 |
TISTUD-2291
|
09/18/2012 01:16:20
|
Update CLI --dir to --project-dir and --workspace-dir
|
We have renamed the --dir CLI option to --project-dir for the following commands: * build * clean * project and --workspace-dir for: * create Note: there is no longer a run or install command.
| 3 |
669 |
TISTUD-2292
|
09/18/2012 09:01:58
|
Add ability to edit app icon as part of tiapp.xml
|
The app icon is an important identifier for a 360 app. Users should be able to update hte app icon via the tiapp.xml editor * Add a field showing the current icon (scaled for size) * Add a browse button allowing the user to pick a new icon * Restrict the icon to standard app store guidelines.
| 8 |
670 |
TISTUD-2295
|
09/18/2012 16:21:43
|
Dashboard: Linux: dashboard is not open as expected, pop up error msg "Internal error ..."
|
Dashboard Fail to Open. Steps to Reproduce: 1. Open Ti.Studio Actual Result: Fail to load Dashboard. Error#1: {Failed to install alloy. Please see http://go.aptana.com/installing+Node.js for additional information} Error#2: {An internal error has occurred. org.eclipse.ui.internal.ErrorEditorPart cannot be cast to com.aptana.portal.ui.browser.AbstractPortalBrowserEditor} Expected Result: Display Dashboard.
| 8 |
671 |
TISTUD-2298
|
09/18/2012 16:44:31
|
iOS Device Debugging: debugger silently fails to connect
|
Description: After installing app on device unable to connect to debugger, progress bar stops at 57%"Waiting for device". Opening app on device is not open debugger. Debug_test is attached screenshot is attached xcode log is attached (log.txt) jstack.log is attached Steps to Reproduce: Import debug_test (debug_test is attached) 1. From TiStudio go to Debug perspective 2. In the Breakpoints view, Remove All existing breakpoints and right-click to "Import Breakpoints..." 3. Browse to breakpoint-basic.bkpt in Test File Location 4. Run in debug as iOS device. 5. After installing app on device. Launch app from device. Actual Result: Open app on device Debugger mode is not running. Expected Result: Debugger mode should run on Studio.
| 13 |
672 |
TISTUD-2300
|
09/18/2012 19:14:28
|
Alloy: Cannot create migration files with the same name
|
I cannot generate more than one migration file in Titanium Studio using the Alloy Feature plugin. I receive the warning: " A Migration 'book' already exists." However, all migration files have the same base name only the datetime changes. Reproduction: Create a new Alloy project in Titanium Studio. Perform the steps twice with the same migration name: # Right-click on your project in App or Project Explorer. # Select New > Alloy Migration. The New Migration dialog box will appear. # In the Migration name textbox, enter the name of the migration. # Click the OK button.
| 3 |
673 |
TISTUD-2301
|
09/18/2012 21:39:19
|
Pass in multiple IP addresses to debugger command
|
During the packaging of an app for debugging on device, we need to amend the request with a list of the current IP addresses assigned to the machine (excluding loopback addresses) Format: host:port:id:hosts where hosts will be coma separated values. For iOS on device debugging, this is going to be "::id:ip,ip,ip,ip"
| 8 |
674 |
TISTUD-2307
|
09/19/2012 11:18:22
|
Detect Alloy project on import and set project nature accordingly
|
On project import, Studio should detect whether the project is an Alloy project or a traditional project and set the nature accordingly. Scanning for the presence of files (e.g. /app/config.json) might be sufficient. The Alloy team might have better thoughts on reliable detection.
| 8 |
675 |
TISTUD-2311
|
09/19/2012 16:33:46
|
Studio: Build for device and packaging show a list of simulators instead of SDK.
|
While investigating issues discovered with Xcode 4.5, it became clear that what we were seeing as a bug where the SDK scripts were ignoring what was set as iOS SDK during Studio build for device or packaging was actually Studio displaying a list of simulator versions. This option should show either the actual list of SDK versions. The result of setting something other than an available SDK is that the setting is ignored. Since this is a list of emulators, this happens nearly every build (unless you choose a version where you have both simulator and SDK). This is not a regression, it occurs in many previous versions. Steps to reproduce: 1) Ensure xcode-select path and Studio preference are in sync. (refresh and restart Studio if required) 2) run terminal command "xcodebuild -showsdks" for later comparison 3) Create a new project in Studio and attempt to build for device. 4) Note pull-down options Result: Pull-down contains a list of simulators. Check the xcodebuild results which should be something like: {code} OS X SDKs: Mac OS X 10.7 -sdk macosx10.7 OS X 10.8 -sdk macosx10.8 iOS SDKs: iOS 6.0 -sdk iphoneos6.0 iOS Simulator SDKs: Simulator - iOS 5.0 -sdk iphonesimulator5.0 Simulator - iOS 5.1 -sdk iphonesimulator5.1 Simulator - iOS 6.0 -sdk iphonesimulator6.0 {code} Expected: A list of SDKs.
| 5 |
676 |
TISTUD-2312
|
09/19/2012 17:29:50
|
iOS Device Debugger: Debugging session persists but does not resume after app exit.
|
While debugging via wifi on device, after starting a debug session and minimizing the app (round button) on device the debugging session in Titanium is still active but the app will not reconnect after restart. This is different from the functionality seen in the simulator where the app will resume debugging after minification. Steps to reproduce: 1. Start a debugging session on device. 2. Minimize the app on device (front round button). 3. Reopen the app on device. Expected result: The debugging session should continue as normal. Actual result: The debugging session stays open in Titanium after the app is restarted but the app no longer responds to the debugger commands.
| 0 |
677 |
TISTUD-2316
|
09/19/2012 18:11:25
|
Project Explorer: can't copy/paste files from project explorer to filesystem
|
Cannot copy/paste files from Project Explorer to Finder. Screenshot attached. Error is: 'The items on the Clipboard can't be pasted to this location. One or more of the items may have been deleted or are no longer available' Steps to Reproduce: 1. Select a file in the project explorer. 2. Press 'Copy'. 3. Click on the Desktop, press 'Paste'. Actual Result: OS Error, file not found. Expected Result: File should be copied pasted.
| 8 |
678 |
TISTUD-2318
|
09/20/2012 14:23:48
|
When Android Device debugging is ready, Studio should display a prompt to start the app on the device
|
Currently, when the device is ready for debug, the only indicator is in the Console log (which is not very noticeable). Ideally, we should start the app like when we debug on emulator. But if that's not feasible, we should display a prompt to users to start the app like: "Application installed. Launch the app from the device to start debugging" We should accompany this with a checkbox that essentially says "Don't ask me again". Using the device debugging for the first time, I was unaware I had to start the app.
| 5 |
679 |
TISTUD-2321
|
09/20/2012 16:00:53
|
Change Android debug/run on device launch configuration names
|
Currently, both the Android install on the device and debug on device are both using the same launch configuration type : Titanium Android Application Installer". The name doesn't really apply to Debug on device, since "Application Installer" implies something different. I suggest changing it to "Titanium Android On Device"
| 5 |
680 |
TISTUD-2322
|
09/20/2012 16:33:23
|
Canceling Android Emulator/Application Installer processes does not stop/remove process from Debug view
|
During failed attempts to start debugging on both android debugger and device, I am left with multiple launch entries in the Debug view that appear to be running. When I try to cancel/stop the processes, it does nothing. The emulators and devices have been killed or disconnected. See screenshot. There are no errors in the error log
| 8 |
681 |
TISTUD-2326
|
09/21/2012 15:10:22
|
Fail to write metadata for properties.index in Windows Environment.
|
Creating default Ti.Mobile Project, Fails to write metadata for properties.index This is a regression. Steps to Reproduce: 1. Create default Titanium Mobile Project 2. Click on tiapp.xml Actual Result: Could not write Metadata Expected Result: tiapp.xml code.
| 3 |
682 |
TISTUD-2327
|
09/21/2012 18:14:51
|
iOS debug on device should be one debug launch configuration
|
When debugging on device, Studio launches two launch configurations (see screenshot). This makes it confusing to the user since the first launch configuration (Install on device) finishes and terminates, and another launch configuration is launched. There should only be one launch configuration and it should contain both the app installation and debug processes
| 8 |
683 |
TISTUD-2333
|
09/24/2012 22:52:52
|
Android Device Debugger: Failure to launch Android emulator
|
The following issue results from trying to debug on emulator on android in Windows 7: {noformat} [INFO] logfile = C:\Users\qatester\My Documents\Titanium_Studio_Workspace\android1\build.log [DEBUG] C:\Users\qatester\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20120924114913\android\builder.py emulator android1 C:\SDK C:\Users\qatester\My Documents\Titanium_Studio_Workspace\android1 com.shastaqa.android1 8 WVGA854 armeabi-v7a [TRACE] app property, ti.ui.defaultunit : system [INFO] Launching Android emulator...one moment [DEBUG] From: C:\SDK\tools\emulator.exe [DEBUG] SDCard: C:\Users\qatester\.titanium\android2.sdcard [DEBUG] AVD ID: 8 [DEBUG] AVD Skin: WVGA854 [DEBUG] SDK: C:\SDK [DEBUG] C:\SDK\platform-tools\adb.exe start-server [ERROR] Invalid switch - /tmp\temp-android-tool\lib\x86 [ERROR] The syntax of the command is incorrect. [ERROR] Exception occured while building Android project: [ERROR] Traceback (most recent call last): [ERROR] File "C:\Users\qatester\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20120924114913\android\builder.py", line 2258, in <module> [ERROR] builder.run_emulator(avd_id, avd_skin, avd_name, avd_abi, add_args) [ERROR] File "C:\Users\qatester\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20120924114913\android\builder.py", line 485, in run_emulator [ERROR] avd_name = self.create_avd(avd_id, avd_skin, avd_abi) [ERROR] File "C:\Users\qatester\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20120924114913\android\builder.py", line 408, in create_avd [ERROR] available_avds = avd.get_avds(self.sdk) [ERROR] File "C:\Users\qatester\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20120924114913\android\avd.py", line 23, in get_avds [ERROR] for line in run.run([sdk.get_android(),'list','target'],debug=False).split("\n"): [ERROR] AttributeError: 'NoneType' object has no attribute 'split' {noformat} Steps to reproduce: 1. Create a new Android project. 2. Debug on emulator. Expected result: Android emulator should begin and debugging should proceed normally. Actual result: Process throws the above error then tries to relaunch the fastdev server.
| 8 |
684 |
TISTUD-2335
|
09/25/2012 00:37:15
|
iOS device debugging logging messages does not honor console log level
|
The log messages during iOS device debugging does not get filtered properly. Steps: 1. Set the log level to Debug 2. Run the device debugging that outputs Trace and Debug messages Expected Results: Only Debug messages are displayed Actual Results: Both Trace and debug message are displayed
| 8 |
685 |
TISTUD-2341
|
09/25/2012 21:51:28
|
'Web Browser Editor' Shows 'Eclipse' icon on top right side.
|
'Web Browser Editor' Shows 'Eclipse' icon on top right corner, Should be replaced by 'Appcelerator' icon and on click it should open the Appcelerator web site. Steps to Reproduce: 1. Open Titanium Studio 2. Click on 'Window' Menu bar and Select 'Show View' 3. Click ' Web Browser Editor' Actual Result: The Web Browser Editor opens with an Eclipse icon on top right corner. On click it's Opens the Eclipse Web Site. Expected Result: Appcelerator Icon. On click opens Appcelerator Web Site.
| 5 |
686 |
TISTUD-2344
|
09/26/2012 00:57:51
|
Alloy templates should denote "beta"
|
The Alloy templates should be displayed as follows: Alloy (Beta) The tag/category and the template title/description should also denote "beta"
| 3 |
687 |
TISTUD-2345
|
09/26/2012 15:26:27
|
Display deprecation status of JS CA proposals
|
We currently do not show any sort of indicator that a particular method/property/type/event is deprecated in our CA proposals and popup. JDT uses a strikethrough overlay on the proposal icon, and in the additional info popup, it shows "Deprecated" in bold at the top followed by the text after the @deprecated tag all in italics.
| 8 |
688 |
TISTUD-2346
|
09/26/2012 16:12:47
|
Add our project shortcuts to File > New in Debug Perspective
|
While in the debug perspective, the file > New menu does not contain the usual options (Titanium Project, Titanium Module, Web Project, etc.). Steps to reproduce: 1. Open Titanium Studio 2. Switch to the Debug Perspective (Window > Open Perspective > Debug) 3. Open the New Menu Dropdown (File > New) Expected result: This menu should match the Studio Perspective's choices. Actual result: Only the generic Project and File choices appear.
| 3 |
689 |
TISTUD-2347
|
09/26/2012 23:16:13
|
Debugger: Process does not always gain focus when session is launched
|
In Debug Perspective, the app thread/process does not always gain focus when session is launched. This is intermittent, and is more likely to occur if there are previously existing terminated debugging sessions in the thread view. This is a usability issue because the debugger controls cannot be active unless the correct thread is selected. See screenshots. Steps to Reproduce: 1. Launch a debugging session. 2. When a breakpoint is hit, click on a line (in Debug View) that is different than the default selected thread. 3. Repeat step 1. Actual Result: Intermittently the correct thread in the Debug View is not selected when the first breakpoint is hit. Expected Result: The correct thread should always be selected whenever a debugging session is launched and the first breakpoint is hit. The debugger controls should be active (e.g., Step Into, Step Over, etc.).
| 8 |
690 |
TISTUD-2355
|
09/27/2012 21:08:34
|
Doubled Copy/Edit/Delete/Paste right-click menu entries
|
I'm often seeing doubled entries for simple cut/copy/paste/delete entries in the right-click context menu in the Project Explorer.
| 8 |
691 |
TISTUD-2356
|
09/28/2012 02:17:31
|
Update iOS device debugging status to display an animated 'start app' image
|
When performing the debug on iOS device using the wizard, the status will be displayed as the app is built and installed. When the 'Start app' step is the current step, we need to remove the step control and replace it with an animated gif of an app starting on a device.
| 8 |
692 |
TISTUD-2357
|
09/28/2012 16:36:46
|
Project Wizard: Template names offset in Ubuntu 12.04
|
Template names are off center in the new project wizard, see screenshot for more details. Steps to reproduce: 1. Open the new Titanium project wizard (File > New > Titanium Project) 2. Click on one of the templates Expected result: Template name should be centered under template image. Actual results: Template names are offset under their associated images.
| 5 |
693 |
TISTUD-2363
|
09/28/2012 21:46:30
|
Allow iOS debug session without app build
|
In the iOS debug on device wizard, add a checkbox that states "Use previous build". If it is checked, the build parameter UI is disabled and the user can proceed with the wizard. Doing so will re-use the last used app key and ip-address associated with the launch configuration
| 8 |
694 |
TISTUD-2364
|
09/28/2012 21:48:00
|
Allow iOS and Android debug on device wizard to launch in background
|
Add a checkbox to the iOS debug on device wizard to "Run in the background". Upon finish, the launch configuration will behave similar to performing an iOS debug on device launch shortcut
| 8 |
695 |
TISTUD-2365
|
09/28/2012 21:49:35
|
Display a set of instructions when launching Android "Debug on Device"
|
Debugging on Device is a multi-step process, and we should guide the user through the steps. Once the user presses the "debug on device" command, pop up a dialog that shows the four steps: * Build application * Installing on Device * Launch app on device (waiting for connection) Suggest having a wizard page that appears when launching. The page will describe the four steps (1-4), and can help to resolve any setup issues.
| 8 |
696 |
TISTUD-2368
|
10/01/2012 19:48:48
|
For Android module builds on Windows, set an Ant property pointing to the Python plugin's executable
|
cf. TIMOB-11119 Currently, if a Studio user on Windows creates an Android module project and then tries to package it, it will fail if there is no Python interpreter found. Since we ship with an interpreter, it would nice if we could let the module's ant build script know where that packaged python executable is located. Via TIMOB-11119, Bill will change the build.xml for modules to become aware of a property named "python.exec" which should be the full path to a python.exe (including "python.exe" -- not just the directory.) For this Studio ticket, please just pass the AntRunner a -Dpython.exec=... (the full path to the .exe). Thank you!
| 5 |
697 |
TISTUD-2370
|
10/01/2012 23:52:30
|
iOS Device Debugger: iOS "Debug on Device" wizard has broken link
|
The iOS "Debug on Device" wizard more information and Help button links have no effect when clicked. When I copy the link from the more information anchor, it copies "More Information" into the clipboard. Steps to reproduce: 1. Create a Titanium Project. 2. Debug on iOS device. 3. Click the more information button on the iOS "Debug on Device" wizard. Expected result: Link should open to a more information page. Actual result: Nothing happens, and no link is present to copy. Note: This also happens for the "help" button in the lower left.
| 3 |
698 |
TISTUD-2377
|
10/02/2012 21:49:32
|
iOS Device Debugger Wizard: spelling error 'wasnt'
|
In iOS Debug on Device progress wizard, 'wasn't' is spelled as 'wasnt'. See screenshot. Steps to Reproduce: 1. Launch iOS Debug on Device Session. Actual Result: Wizard contains missspelling. Expected Result: No misspelling.
| 1 |
699 |
TISTUD-2378
|
10/02/2012 23:00:11
|
iOS: Device Debugger: launching debug session from history doesn't show progress wizard
|
If a device debug session is launched from debug history shortcut (see screenshot 'history debug launch.png'), the progress wizard (see screenshot 'ios device debugger wizard.png') is not launched. Instead, a notification is presented when the process is complete (see screenshot 'end notification.png'). This is a usability issue. Relates to user ability to hide progress wizard. Steps to Reproduce: 1. Run debug session from history. See screenshot 'history debug launch.png'. Actual Result: No progress wizard. Expected Result: Progress wizard.
| 0 |
700 |
TISTUD-2380
|
10/03/2012 01:07:12
|
Windows 7: Preferences: Could not detect a path to the Xcode folder
|
Windows 7 Preferences > Titanium Studio > Titanium menu displays error: Could not detect a path to the Xcode folder Note: Xcode is not supported on Windows 7. Steps to Reproduce: 1. Open Titanium Studio in Windows 7 (possibly Ubuntu). 2. Go to Preferences > Titanium Studio > Titanium. Actual Result: Xcode path error. Expected Result: No mention of Xcode.
| 3 |
701 |
TISTUD-2382
|
10/03/2012 01:33:17
|
Change in Titanium SDK preference is not reflected in New Titanium Project wizard
|
In the new Titianium Project wizard, if the SDK path is modified in preferences through 'Set-up/Configure SDKs' link, then the new wizard still shows the list of SDKs from previous path. The list should be re-loaded in this case.
| 5 |
702 |
TISTUD-2383
|
10/03/2012 06:04:51
|
Studio: Alloy installation error in Studio 3.0 in Ubuntu 12.04
|
Steps To Reproduce: 1. Download Titanium Studio 2.1.2 2. Upgrade Studio to 3.0 using instructions in https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager link. 3. Restart Studio. Actual: Error Message appears "Launching Studio Portal.." and "failed to Install Alloy" [Refer Screenshot and Logs] An internal error SwigDirector_CefHandler_HandleBeforeCreated appears. Expected: Installation and Launching of Studio must occur without any error.
| 8 |
703 |
TISTUD-2384
|
10/03/2012 10:00:26
|
Android: Add 'debug on android device' option in context menu list
|
This is not a regression bug. Steps to reproduce: 1)Open Titanium Studio. 2)Open/Create a Titanium Mobile project -> Android 3)Open context menu by right clicking on that project in Titanium Studio. 4)Observe that debug as -> 'android device' icon is unavailable. Actual result: In context menu list, debug as -> 'android device' icon is unavailable. Expected result: In context menu list, debug as ->'android device' icon should be available. Screenshots attached.
| 8 |
704 |
TISTUD-2385
|
10/03/2012 20:39:18
|
Add CLI command support to load an iOS Provisioning Profile from a filepath
|
We currently have a script living under the SDK's iphone/provisioner.py that loads a provisioning profile given a filepath argument to the .mobileprovision file. There doesn't appear to be an equivalent in the new CLI for this, though {{titanium info}} does list provisioning profiles by type ("development", "distribution", "adhoc").
| 0 |
705 |
TISTUD-2388
|
10/04/2012 08:21:41
|
Studio: "Failed to execute runnable" error appears while running app in debug mode on android device.
|
Steps To Reproduce: 1. Upgrade Titanium Studio to 3.0.0.201210021936 release. 2. Create any Default Project. 3. Connect to Android Device using USB. 4. Run app on device in debug mode. Actual: Error appears while running in debug mode. Refer Log file. App Installer does not start. Expected: No error must appear. App must get installed on device.
| 8 |
706 |
TISTUD-2393
|
10/04/2012 17:04:29
|
Keep the focus in the editor when console generates error output
|
h2. Actual results Output to the console causes focus to switch to the console pane rather than the code pane. h2. Expected results Focus should stay where you put it (e.g. in the code window). h2. Steps to reproduce # Build an app for the Android emulator # Click in the code window # As soon as new log info is output, focus goes to the console pane This happens when building for both iOS Simulator and Android emulator. But the behavior is much more annoying when working with Android. ADB seems to continually output logging info so you can get into this battle with Studio where you click in the code window and by the time you type a character, focus has switched back to the console. So you click, focus changes, your text goes to the wrong spot.
| 8 |
707 |
TISTUD-2395
|
10/04/2012 18:29:09
|
Titanium SDK Release Notes has giant text, update table formatting
|
Release Notes pop-up has giant text, we need to update the table formatting. Note: The affected text was removed from the release notes in 2.1.3 as a work-around. TIDOC-838 Steps to Reproduce: 1. Remove latest stable SDK and check for stable SDK updates to bring up Release Notes. Actual Result: Some text is giant in the table sections. Expected Result: Table should be formatted.
| 3 |
708 |
TISTUD-2399
|
10/05/2012 22:20:41
|
Project Explorer: Publish icon active when it shouldn't be
|
In Project Explorer, if there are no projects, the Publish icon is still active (regression), however no entries are available (correct). See screenshots. No log info. Steps to Reproduce: 1. Open Titanium Studio. 2. View the Project Explorer. Make sure there are no projects in the explorer. Actual Result: Publish icon is incorrectly active (but no list appears when clicked, as expected). Expected Result: Publish icon should be grayed-out.
| 5 |
709 |
TISTUD-2400
|
10/05/2012 22:43:33
|
Unpublish Node.ACS service menu is disbled even though the Node.ACS app is published
|
1. Create a Node.ACS project; 2. Create a Node.ACS method in the project; 3. Publish the app using Publish > Deploy App; 4. Select Publish > Unpublish Node.ACS Service. Expected result: item "0.1.0" appears under the pull-over menu. Actual result: no menu item appears under Unpublish Node.ACS Service menu.
| 5 |
710 |
TISTUD-2402
|
10/05/2012 23:47:43
|
Node.ACS: New > Node.ACS Service menu item exists if project already has a service
|
If a titanium project contains a node.acs service, and the user selects project right-click > New, Node.ACS Service appears as a menu entry. As a further complication, when New > Node.ACS Service is selected, the New > Node.ACS Method dialog is invoked instead. Steps to Reproduce: 1. Create a titanium mobile project. 2. Right-click > New > Node.ACS Service to create service. 3. Right-click > New again. Actual Result: New > Node.ACS Service exists as a menu item when the project already has a service. Expected Result: Menu item should not exist. 4. Actually click on New > Node.ACS Service. Actual Result: New > Node.ACS Method dialog is invoked, which is not correct. Expected Result: Either a new service should be created, or a dialog indicating a service already exists.
| 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.