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
|
|---|---|---|---|---|---|
211 |
TISTUD-1287
|
03/06/2012 16:07:31
|
Titanium Studio: Content Assist: no Titanium SDK proposals are generated
|
Content Assist fails to generate Titanium SDK proposals. Regression. Steps to Reproduce: 1. Open studio 2.0. 2. Edit app.js. Type 'Ti.'. Look at Content Assist suggestions (cntrl + space to force CA window). Expected Result: Titanium SDK proposals should appear. Actual Result: No proposals.
| 8 |
212 |
TISTUD-1292
|
03/07/2012 09:55:49
|
Clarify wording on iOS configuration screen
|
The current iOS dashboard configuration screen is a confusing regarding min/max versions of SDKs. So lets display which iOS versions are compatible with this and below that have a link that points to here : https://wiki.appcelerator.org/display/guides/Titanium+Compatibility+Matrix#TitaniumCompatibilityMatrix-iOSSDK%2FTargetiOSPlatform. Regarding the actual text, here is a proposal: An iOS SDK is missing. Titanium supports the following range of iOS versions: Min iOS version: ... Max iOS version: ... Algorithm to calculate this: if inclusive '[', leave the versions as is. if exclusive '(', subtract .1 from the last position, and add .X to the end, i.e. 5.2) => 5.1.X. 5.1.0) => 5.0.9.X (We can ignore the exclusive lower bound case at the moment: https://mail.osgi.org/pipermail/osgi-dev/2008-July/001330.html...It's unlikely we'll need it) Button ('install or update iOS SDK") Note: If you intend to develop mobile applications using an earlier version of the Titanium Mobile SDK , please consult the Titanium Compatibility Matrix. (this is the link shown above)
| 8 |
213 |
TISTUD-1294
|
03/08/2012 06:13:29
|
App Id causing "[ERROR] Error generating R.java from manifest"
|
Same issues as referenced in [TIDEV-115|https://jira.appcelerator.org/browse/TIDEV-115] If you specify an app id as simply a single word, as opposed to a reverse domain format, you get an error when building for android (but not ios): {code} [ERROR] Error generating R.java from manifest {code} It's a very cryptic error and really hard to track down. If this type of app id is illegal for Android, the user needs to be notified by Titanium Studio that this is the case. Also, in case a user manually changes the app id and runs into the above error, it would be a lot more useful if the error message actually indicated that the app id was the problem. It's near impossible to figure out that the app id is the issue from that error message alone.
| 3 |
214 |
TISTUD-1295
|
03/08/2012 08:15:19
|
Convert wiki.appcelerator.org URLs inside Studio into redirects off studio.appcelerator.com
|
There are approximately 22 links inside Studio that need to be redirectable, since the exact endpoint is not known at this time. Instead, let's create a PHP page off of studio.appcelerator.com to redirect to the current location, and then we can change it as necessary.
| 8 |
215 |
TISTUD-1296
|
03/08/2012 13:03:06
|
Add an Android NDK path field in the Titanium Preferences
|
Add a preference key, and a field editor, for the Andriod NDK path into the Android group at the Titanium preference page.
| 8 |
216 |
TISTUD-1297
|
03/08/2012 13:31:59
|
Titanium MobileWeb when previewed against an internal browser shows empty content
|
[This one happens on Windows] Create a mobile-web project (with Titanium SDK 2.0). Right click to run the 'Titanium Mobile Web Previewer'. An internal browser is opened, but the page is blank. Right-clicking and viewing the source shows lot of code there, so we have the content, yet it's not rendering. Selecting the launch (via the Run configurations) and editing it to run on external browser works fine.
| 8 |
217 |
TISTUD-1299
|
03/08/2012 14:55:20
|
Extra space in "Import Existing Titanium Project" error message
|
This is very minor, but I noticed that the warning message in the Import Existing Titanium Project dialog appears to have an extra space (see attached).
| 1 |
218 |
TISTUD-1301
|
03/08/2012 17:41:57
|
Update Studio Dashboard to adjust to packaging changes for 2.0 launch
|
The available packages in 2.0 will change names and pricing of those will be on a per-app basis. Hence a paid subscriber might have more than one package, so we can no longer display the user's plan level on the dashboard. Instead we should just display the following: * a link labeled "My Apps" pointing to the site where the user's can view his Apps * a link labeled "My Account" pointing to the user's account
| 5 |
219 |
TISTUD-1304
|
03/09/2012 11:27:04
|
Add DEVELOPER_DIR to environment variables when launching iOS scripts
|
Any time we interact with an iOS script, we need to set the DEVELOPER_DIR environment variable equal to the current Xcode location (i.e. what you would normally get from xcode-select -print-path)
| 8 |
220 |
TISTUD-1305
|
03/09/2012 14:57:45
|
Add support for CommonJS modules to JS content assist
|
Below are several simple examples of a CommonJS Module {code:title=module_1.js} //helper function to construct light views function createLightView(color,on) { return Ti.UI.createView({ backgroundColor:color, top:10, width:60, height:60, opacity:(on) ? 1 : 0.2 }); } //main component constructor function StopLightView() { //create component instance var self = Ti.UI.createView({ height:220, width:80, backgroundColor:'#232323', layout:'vertical' }); //create state/instance data var lightColor = 'red'; //construct UI var greenLight = createLightView('green'); self.add(greenLight); var yellowLight = createLightView('yellow'); self.add(yellowLight); var redLight = createLightView('red', true); self.add(redLight); //private helper function to handle changing of light colors function changeColor(newColor) { //update object state lightColor = newColor; //toggle opacity, based on the color requested switch(newColor) { case 'green': greenLight.opacity = 1; yellowLight.opacity = 0.2; redLight.opacity = 0.2; break; case 'yellow': greenLight.opacity = 0.2; yellowLight.opacity = 1; redLight.opacity = 0.2; break; default: greenLight.opacity = 0.2; yellowLight.opacity = 0.2; redLight.opacity = 1; break; } //when light change is complete, fire custom event on component instance self.fireEvent('lightchange', { color:lightColor }); } //create public component interface //create an accessor for the current color state //CAUTION - "getXXX" and "setXXX" functions are RESERVED on iOS, and you can't name functions with that prefix! self.lightColor = function() { return lightColor; }; //after a transitional period, change the color from yellow to red self.stop = function() { if (lightColor !== 'red') { changeColor('yellow'); setTimeout(function() { changeColor('red'); },1500); } }; //change the light color to green for a time, then stop self.go = function() { changeColor('green'); setTimeout(function() { self.stop(); },4000); }; //return component instance return self; } //make component constructor the public interface for the module module.exports = StopLightView; {code} {code:title=module_2.js} /** * description * @classDescription This class creates a new Test. * @return {Test} Returns a new Test. * @type {Object} A class with constructor and prototype methods */ var Test = function() { var _question = []; /** * Adds a question to the internal stack * @return {Number} The index of the added question */ this.addQuestion = function(question) { return _question.push(question); //TODO: possible 1-based need to take measure if cross-platform }; /** * getQuestion * @return {Object} A Question object */ this.getQuestion = function(index) { return _question[index]; }; /** * getAllQuestion * @return {Array} A reference to the internal question array */ this.getAllQuestion = function() { return _question; } }; /** * Blah * @return {void} */ Test.blah = function(){ return void(0); } /** * Takes a function * @return {Array} */ Test.prototype.eachPossibility = function(questionIndex, fn) { //Array.prototype.forEach.call(this.getAllQuestion()[questionIndex].possibilities, fn) return this.getAllQuestion()[questionIndex].possibilities.forEach(fn); } // fix cross debug output and add support for multiple arguments to Ti debug this.console || (this.console = {}, console.log = function(){ Ti.API.debug( Array.prototype.slice.call(arguments) ); }); // Check if we're in a CommonJS environment if( typeof require == 'function' && typeof module == 'object' ) { exports['quiz'] = Test; } {code} {code:title=module_3.js} (function (Ti, Titanium, exports) { var Test; if (Titanium == undefined /* Android */) { Test = {}; exports.bootstrap = function (TiSDK) { Ti = Titanium = TiSDK; return Test; }; } else { Test = exports; } Test.retrieveSuccessLabel = function () { return Ti.UI.createLabel({ text: 'Success!', textAlign: 'center', color: '#000' }); }; })(Ti, Titanium, exports); {code} {code:title=module_4.js} exports.info = function(str) { Titanium.API.info(new Date()+': '+str); }; exports.debug = function(str) { Titanium.API.debug(new Date()+': '+str); }; {code} {code:title=module_5.js} module.exports = { someprop: 'coolbeans' }; {code}
| 0 |
221 |
TISTUD-1306
|
03/09/2012 15:12:43
|
Add support for the @module sdoc tag
|
Following JSDoc as a guide, we need to add support for an @module tag. The syntax would be: {code} /** * @module {dir1/dir2/myModuleName} */ {code} This will require us to: # Add support for @module and its parameters to the SDoc parser # Add a module element to the SDoc model # Possibly store a reference of the module name to the document defining it in the JS index
| 13 |
222 |
TISTUD-1307
|
03/09/2012 15:14:44
|
Create sample documentation of an SDoc'ed CommonJS module
|
Using the sample snippets in the Epic containing this ticket, we will need to create documentation that shows that code being scriptdoc'ed for use as a module. We need to update the wiki pages here: * https://wiki.appcelerator.org/display/guides2/ScriptDoc+%28SDOC%29+2.0+Specification * https://wiki.appcelerator.org/display/guides2/Documenting+Your+Code+Using+ScriptDoc * https://wiki.appcelerator.org/display/guides2/ScriptDoc+tag+quick+reference
| 13 |
223 |
TISTUD-1308
|
03/09/2012 15:26:41
|
Only show content assist from the current JS file and JS files it has required
|
Our current JS CA implementation queries the index file for the entire project. This means that we show content assist for all JS files in a project when bringing up CA in a JS file. We now detect "require" invocations and store the required module name in the index. We also have the ability to filter index query results by a list of documents. Using these two items together, we should be able to filter JS CA by required files only. Note, that we may not want this as a default behavior for web projects. So, for the time being, we should implement this for the TiMobile nature only.
| 20 |
224 |
TISTUD-1309
|
03/11/2012 08:17:54
|
Change Studio to reference new platform -clean option
|
Once TIMOB-7652 is complete, we'll need to switch to using that mechanism over the current one. Note, this only will work on SDKs above 2.0.1+, so if the SDK is less than that version, we need to use the old system for now.
| 8 |
225 |
TISTUD-1310
|
03/12/2012 07:52:52
|
Treat CommonJS modules specially when showing JS CA in a file that includes it
|
CommonJS modules make use of a "module" object that has an "exports" property. Also, there is an "exports" global that can be used similarly to "module.exports". There are rules in how these two items influence one another as is covered in http://www.hacksparrow.com/node-js-exports-vs-module-exports.html. So, whenever we include CA from a "require"d module, we need to grab properties from the "module.exports/exports" type instead of grabbing items from its global scope.
| 13 |
226 |
TISTUD-1312
|
03/12/2012 10:25:22
|
TiStudio: Mobile Web - index.html file is not generated when packaging for Mobile Web
|
Steps to reproduce: 1. Package default Titanium project for Mobile Web 2. Select "Create a new project for the Mobile Web app" 3. Open newly created Mobile Web project Actual: index.html does not appear in the packaged mobile web. See attachment for log. Expected: The packaged mobile web should contain the index.html in order to preview the app. Note: If ti.cloud module exists in the TiApp Editor, remove it from the project.
| 5 |
227 |
TISTUD-1313
|
03/12/2012 10:53:49
|
Comments are removed when formatting JS code
|
Format the following code: {code} function uploadImage() { if(Titanium.Platform.name == 'android') { req.send({ 'aToken' : Titanium.Locale.getString('app_token_only'), 'uToken' : Titanium.App.Properties.getString('uToken'), 'fileType' : '2'}) // Only Change, Added single quote for Android 'fileObject' : blob }); } else { req.send({ 'aToken' : Titanium.Locale.getString('app_token_only'), 'uToken' : Titanium.App.Properties.getString('uToken'), 'fileType' : 2}) // Only Change, No change needed for IPhone 'fileObject' : blob }); } } {code} Expected result: Code formats with all the comments included Actual results: The '// Only Change' comments are removed during the formatting process.
| 5 |
228 |
TISTUD-1314
|
03/12/2012 10:56:26
|
Titanium Studio: TiApp Editor: Build Properties: Titanium SDK: if no sdk's exist, sdk list not cleared
|
If all SDKs are removed from the SDK folder, they remain in the TiApp Editor SDK list. Note: They are later correctly removed when the tiapp.xml file is reloaded. The tiapp.xml SDK version remains as the last available version (expected). Steps to Reproduce: 1. Create a new project. 2. Remove all SDK's from the SDK folder (i.e., Application Support/Titanium/mobilesdk/osx/2.0.0.v20120312104735). Expected Result: TiApp Editor SDK list should be cleared and the tiapp.xml SDK version should be the last available version. Actual Result: The TiApp Editor SDK list is full, and any selected versions do not change the tiapp.xml (because they do not exist). However, the list is properly cleared on tiapp.xml reload.
| 3 |
229 |
TISTUD-1315
|
03/12/2012 10:59:45
|
Titanium Studio: TiApp Editor: Build Properties: Titanium SDK: if sdk field is set after being blank, tiapp.xml not updated
|
In the TiApp Editor, if another SDK is selected in the TiApp Editor SDK field when the field was previously blank (linked issue), the respective tiapp.xml is not updated, resulting in an invalid configuration. Steps to Reproduce: 1. Create new project. 2. Remove current SDK from SDK folder (i.e., Application Support/Titanium/mobilesdk/osx/2.0.0.v20120312104735). The TiApp Editor SDK field should be blank. 3. Select another available SDK from the TiApp Editor SDK list. 4. View the tiapp.xml. Expected Result: The SDK version in the tiapp.xml should reflect the version selected in the TiApp Editor SDK drop-down list. Actual Result: The SDK version in the tiapp.xml is whatever was last set, resulting in an invalid configuration. Note: The tiapp.xml SDK version is correctly updated if the tiapp.xml file is reloaded.
| 2 |
230 |
TISTUD-1316
|
03/12/2012 11:00:36
|
Titanium Studio: TiApp Editor: Build Properties: Titanium SDK: if current sdk removed from filesystem, tiapp not updated
|
When an SDK folder (i.e., Application Support/Titanium/mobilesdk/osx/2.0.0.v20120312104735) is removed from the filesystem (moved or deleted), the TiApp Editor SDK field for any open projects is set to nothing, and the tiapp.xml remains as the deleted SDK version. It is expected that the SDK field in the TiApp Editor would immediately be updated to the latest SDK, as well as the tiapp.xml. This expectation is reinforced by the fact that when the tiapp.xml file is re-opened in Studio, the TiApp Editor SDK field is set to the latest existing version of the SDK, and the tiapp.xml is updated to the latest SDK. Note: As a related consequence (linked issue), when another SDK is selected in the TiApp Editor SDK field (when the field was previously blank), the respective tiapp.xml is not updated, resulting in an invalid configuration. Note: As an edge case (linked issue), if all SDKs are removed from the SDK folder, they remain in the TiApp Editor SDK list, but they are later correctly removed when the tiapp.xml file is reloaded. The tiapp.xml SDK version remains as the last available version (expected). Steps to Reproduce: 1. Create a new project. 2. Move the selected SDK version folder from it's directory to another location. Expected Result: The TiApp Editor SDK should immediately update to the highest available SDK version, and the tiapp.xml should be updated. This would occur anyway if the tiapp.xml file were re-opened in Studio. Actual Result: The TiApp Editor SDK field is blank, the tiapp.xml SDK version remains as the one removed.
| 5 |
231 |
TISTUD-1318
|
03/12/2012 12:49:29
|
Filter out CommonJS modules from the tiapp.xml editor screen
|
We have implemented ACS module as a CommonJS module and bundled it with the Mobile SDK. We are not officially supporting CommonJS modules (yet) and we have added this support to Mobile SDK just for ACS module. Please filter out CommonJS modules from Studio UI and other tools.
| 8 |
232 |
TISTUD-1320
|
03/12/2012 14:20:13
|
Tabbed Template is giving a runtime error on Android
|
Steps To Reproduce: 1. Create a new TiMob project with the Tabbed Template 2. Run on Device/Emulator 3. Click on Open New Window Actual: Runtime Error (See attachment) Expected: To open a new window
| 3 |
233 |
TISTUD-1321
|
03/13/2012 11:11:39
|
TiStudio: TiApp - Do not see any obvious activity that a project is being rebuilt when cleaning
|
*Details:* After making changes in TiApp Editor and saving, then cleaning my project, I do not see any obvious indication that my project is being re-built. But, I see a small progress bar at the bottom of the Titanium icon. *Steps to reproduce:* 1. Create the default Titanium project 2. Turn Build Automatically off 3. Make changes in TiApp Editor and save 4. Then go to Project > Clean ... 5. Select *Clean projects selected below* and *Start a build immediately* 6. Select OK *May need to repeat steps again to see bug.* *Actual:* When I clean a project, I do not see any obvious activity that my project is being built e.g. Progress View. But, I do see a progress bar at the bottom of the Titanium icon. See attachment. *Expected:* Should be able to see an obvious activity that my project is being built. *Note* There are obvious activity on the following OS using Titanium Studio, build: 2.0.0.201203121914: * Windows 7 * Linux 10.04 * Snow Leopard (10.6.8)
| 0 |
234 |
TISTUD-1322
|
03/13/2012 11:45:35
|
Confim links as part of Studio 2.0 release.
|
Before release, we need to confirm the links listed on TISTUD-1295 are still correct.
| 5 |
235 |
TISTUD-1323
|
03/13/2012 11:48:12
|
Studio: Collapsing Javascript outline node crashes Ti Studio.
|
While testing APSTUD-4178, I had Studio crash while trying to collapse a node on a Javascript outline. Nothing is reported to the log file but Lion generates the attached crash report. Steps to reproduce: 1. Open TIStudio. 2. Open the js.js file. 3. Open the html.html file. 4. Use the outline windows to expand all on the Javascript file. 5. Close the iadt function in the Javascript file. 6. Use the outline window to expand all on the HTML file. 7. Close the iadt function in the HTML file. Actual Results: Collapsing one of the two functions will cause the program to hang and then crash. Expected Results: Both outlines should collapse the function and the program should respond normally.
| 13 |
236 |
TISTUD-1325
|
03/13/2012 12:11:31
|
Update dashboard to remove warning about Xcode 4.3
|
Currently, we warn users about _not_ installing Xcode 4.3. Once that support is in, we'll need to remove that warning: {code} <h3>Note:</h3> <p>Xcode 4.3 (the most recent version which is downloadable in the Mac App Store) is not yet supported by Titanium Studio or the Mobile SDK.</p> <h3>Lion and Snow Leopard:</h3> <ol> <li>Visit developer.apple.com/downloads</li> <li>Search for Xcode 4.2</li> <li>Download and install Xcode 4.2 for your OS version:</li> </ol> <br /> <p>Once finished, return here.</p> {code} new text: {code} <h3>Lion:</h3> <ol> <li>Click the "Install" button, or open the Mac App Store application</li> <li>Search for Xcode</li> <li>Download and install Xcode 4.2</li> </ol> <h3>Snow Leopard:</h3> <ol> <li>Visit developer.apple.com/downloads (paid account required)</li> <li>Search for Xcode 4.2</li> <li>Download and install Xcode 4.2</li> </ol> <br /> <p>Once finished, return here.</p> {code} We also need to update the sdk_info links for the Xcode download to http://itunes.apple.com/us/app/xcode/id497799835?ls=1&mt=12
| 5 |
237 |
TISTUD-1329
|
03/13/2012 12:58:43
|
Auto-detect and set up CA platform filters for Titanium projects
|
We should set up the CA platform list on Titanium mobile projects based on the deployment targets specified in the tiapp.xml itself.
| 8 |
238 |
TISTUD-1332
|
03/13/2012 15:41:03
|
MobileWeb launches are never removed from the Debug view
|
Launch a MobileWeb preview in a browser. A launch is added to the Debug view, and it's there to stay. The only way to remove it is to click it and hit 'delete'.
| 5 |
239 |
TISTUD-1333
|
03/13/2012 16:24:07
|
Seeing error on unrecognized type name with JSMetadata
|
When running Titanium Studio 2.0.0.201203121914, I saw many entries of the following in the log: {code} !ENTRY com.aptana.editor.js 4 0 2012-03-13 16:57:37.690 !MESSAGE (Build 3.0.3.1331566826) [ERROR] Unrecognized type name in JSCAHandler#createType: JSMetadata {code}
| 2 |
240 |
TISTUD-1334
|
03/13/2012 16:44:44
|
An empty version in the modules section of the tiapp.xml prevents the TiApp editor from being opened
|
1. Have a module directive in the tiapp.xml without a 'version=...' attribute. 2. Open the TiApp editor Result: A null pointer exception prevents it from getting opened.
| 3 |
241 |
TISTUD-1335
|
03/13/2012 16:56:33
|
Content Assist: JavaScript class objects generate non-static proposals
|
JavaScript objects such as Array, Boolean, Date, Number, and RegExp generate Content Assist proposals that are not static methods. The methods are generated correctly in Eclipse. Screenshot attached. For instance, String.charCodeAt is proposed when it is an instance method, and will not work on the String object. Steps to Reproduce: 1. Create a new project. 2. In app.js, type a JavaScript class object followed by a dot, activate Content Assist. Expected Result: Static methods and/or methods that work should be proposed. Actual Result: Instance methods are proposed (which will not work), along with many other generic properties which are questionable.
| 8 |
242 |
TISTUD-1336
|
03/13/2012 17:11:24
|
Content Assist: String.fromCharCode: no proposal generated
|
Using Content Assist, 'String.' does not propose the method 'fromCharCode' (though it does work when run). However, the method is proposed in Eclipse. The method is also erroneously proposed in string instances (and the method does not work, as expected) (linked issue). Steps to Reproduce: 1. Create a new project. 2. In app.js, type String. and activate Content Assist. Expected Result: String.fromCharCode should be proposed. Actual Result: Method is not proposed.
| 5 |
243 |
TISTUD-1337
|
03/13/2012 17:16:52
|
Content Assist: string instance.fromCharCode: static proposal erroneously generated
|
When a String instance invokes Content Assist, 'fromCharCode' is proposed when it is a static method and will not work on an instance. Steps to Reproduce: 1. Create a new project. 2. Type: {code:title=app.js} // var x = "xxx".; // {code} 3. Place the cursor after the dot and activate Content Assist. Expected Result: "xxx".fromCharCode should not be proposed. Actual Result: fromCharCode is proposed, though it will not work, and is a static String method.
| 5 |
244 |
TISTUD-1338
|
03/13/2012 17:21:55
|
Content Assist: string instance.charCodeAt: proposal missing
|
String instance method: charCodeAt not proposed in Content Assist, though it works at runtime. Steps to Reproduce: 1. Create a new project, type: {code:title=app.js} // var x = "xxx".; // {code} 2. Activate Content Assist after the string instance to generate proposals for "xxx".-> Expected Result: charCodeAt should be proposed. Actual Result: charCodeAt not proposed, but does run correctly.
| 5 |
245 |
TISTUD-1341
|
03/14/2012 11:36:10
|
Studio: SDK Update release note view has no "back" capability
|
Description: While testing the new feature that provides users with a view of the release notes, I clicked a link which opened JIRA in the same view. There was no option to return to the release notes, so I was forced to close the view. Steps to reproduce: 1) Install the latest Studio 2.0 version 2) Remove SDK version 1.8.2 if you have it installed (and any later versions) from your Titanium folder 3) Launch Studio and click the yellow "updates available" box or use the help>Check for titanium SDK updates option 4) When the "Titanium SDK Upgrade Available" window appears, click one of the JIRA ticket links Result: JIRA displayed, with no way to return to release notes Expected: Link opens in new window or method of navigation available
| 3 |
246 |
TISTUD-1342
|
03/14/2012 11:41:06
|
Studio: SDK Update release note view link for "Titanium mobile reference documentation for 1.8.2" fails with error
|
Description: While testing the new feature that provides users with a view of the release notes, I clicked the link for "Titanium mobile reference documentation for 1.8.2". This failed with an error. Steps to reproduce: 1) Install the latest Studio 2.0 version 2) Remove SDK version 1.8.2 if you have it installed (and any later versions) from your Titanium folder 3) Launch Studio and click the yellow "updates available" box or use the help>Check for titanium SDK updates option 4) When the "Titanium SDK Upgrade Available" window appears, click the "Titanium mobile reference documentation for 1.8.2" link Result: Failure with an error, see attached image Expected: Link opens
| 3 |
247 |
TISTUD-1343
|
03/14/2012 12:31:32
|
Studio: SDK Update release note view will not come up if dismissed and then help>Check for titanium sdk updates option is used
|
Description: While testing the new feature that provides users with a view of the release notes, I clicked a link which opened JIRA in the same view. There was no option to return to the release notes, so I was forced to close the view. Steps to reproduce: 1) Install the latest Studio 2.0 version 2) Remove SDK version 1.8.2 if you have it installed (and any later versions) from your Titanium folder 3) Launch Studio and click the yellow "updates available" box 4) When the "Titanium SDK Upgrade Available" window appears, select "remind me later" 5) Use the help>Check for titanium SDK updates option Result: SDK install begin with no preview of the release notes Expected: Release notes view always presented when installing SDK update
| 5 |
248 |
TISTUD-1345
|
03/14/2012 13:05:13
|
Remove 2.1 as Android SDKs requirement for Android development
|
Description: On one of our newer installations of Studio, the Android SDK is properly configured to support 1.8.0+ SDKs. The Dashboard configuration page shows an incorrectly configured Android SDK. In comparing the listed text to the actual configuration: {code} Android configuration details. One or more pieces are missing from the Android SDK. It may be that the Android SDK is already installed and Titanium Studio cannot locate the directory, or it may be that some additional components need to be installed. Items required: An Android SDK is missing. Titanium requires Android platforms 2.1.* and 2.2.* Add-Ons Google APIs 7, Google APIs 8 {code} We were missing the 2.1 SDK. The result is that imported samples could be run as expected in the emulator, but no project could have the deployment target set during creation of afterward. The tooltip text lists similar requirements, see attached image. Steps to reproduce: 1) Configure a system with ANY supported SDK 1.8.0+ Android SDK (Android 2.2 - 4.0) 2) Launch Studio, add the Android SDK path in the studio preferences 3) On the dashboard, check the configuration utility's report on the usability of the Android SDK Result: If you don't have both 2.1 and 2.2 SDKs, the configuration is determined to be incorrect Expected: Only 2.2 is installed (and required) by default
| 5 |
249 |
TISTUD-1346
|
03/14/2012 16:00:06
|
Studio: Edit this bundle from Commands/Titanium Mobile gives an Error
|
Edit this bundle from Commands/Titanium Mobile gives an Error "Grabbing bundle Titanium Mobile..has encountered a problem Git Clone failed. screen shot is attached log file is attached Steps to reproduce : 1: click on Commands 2: Click on Titanium Mobile 3: Click on Edit the bundle Actual result : Error Message Grabbing bundle Titanium Mobile ..has encountered a problem Expected results : should be able to Edit the bundle
| 3 |
250 |
TISTUD-1348
|
03/15/2012 09:48:34
|
Studio: Cannot open tiapp.xml from FTP source.
|
Trying to open the Tiapp.xml from an FTP server returns this error: {noformat} "Could not open the editor: Expected a tiapp.xml path and got '/var/folders/yl/gg2bc1h9767cchr1wrmrhkjr0000gp/T/aptanavfs706594519621445678tiapp.xml' {noformat} This caused the attached logfile to be generated in the Titanium log. Steps to reproduce: 1. Create a Titainum Mobile project. 2. Upload the Mobile project to an FTP server. 3. Attempt to open the tiapp.xml Actual result: An editor opens showing the above error. Expected result: You should be able to open the tiapp.xml, but it will be treated as an "external" tiapp.xml, so some editing options are disabled.
| 5 |
251 |
TISTUD-1351
|
03/15/2012 12:11:53
|
Update Titanium Studio Run/Debug/Publish wizard/dialog banners
|
The wizard banners should be consistent with the action icons * Run on iOS Device Wizard * iOS Distribution Wizard * Android Distribution Wizard * Mobile Web packaging Wizard See attached request document
| 5 |
252 |
TISTUD-1352
|
03/15/2012 14:50:51
|
Studio: Insert line below current returned divide by zero error.
|
While testing APSTUD-3553 I went to edit an file that I had opened from the FTP server. When I tried to add a second line, the machine hung and gave me a / by zero error and told me to check the log. Attached is the photo of the error and below is the event from the log. {noformat} !ENTRY org.eclipse.ui 4 4 2012-03-14 13:15:36.553 !MESSAGE "Insert Line Below Current Line" did not complete normally. Please see the log for more information. !ENTRY org.eclipse.ui 4 0 2012-03-14 13:15:36.554 !MESSAGE / by zero !STACK 0 java.lang.ArithmeticException: / by zero at com.aptana.editor.php.internal.ui.editor.formatting.AbstractPHPAutoEditStrategy.getIndentationString(AbstractPHPAutoEditStrategy.java:690) at com.aptana.editor.php.internal.ui.editor.formatting.AbstractPHPAutoEditStrategy.getIndentationAtOffset(AbstractPHPAutoEditStrategy.java:607) at com.aptana.editor.php.internal.ui.editor.formatting.PHPAutoIndentStrategy.customizeCloseCurly(PHPAutoIndentStrategy.java:405) at com.aptana.editor.php.internal.ui.editor.formatting.PHPAutoIndentStrategy.innerCustomizeDocumentCommand(PHPAutoIndentStrategy.java:194) at com.aptana.editor.php.internal.ui.editor.formatting.PHPAutoIndentStrategy.customizeDocumentCommand(PHPAutoIndentStrategy.java:58) at org.eclipse.jface.text.TextViewer.customizeDocumentCommand(TextViewer.java:3745) at org.eclipse.jface.text.TextViewer.handleVerifyEvent(TextViewer.java:3782) at org.eclipse.jface.text.source.projection.ProjectionViewer.handleVerifyEvent(ProjectionViewer.java:1277) at org.eclipse.jface.text.TextViewer$TextVerifyListener.verifyText(TextViewer.java:435) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:265) 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.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1061) at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7148) at org.eclipse.swt.custom.StyledText.replaceTextRange(StyledText.java:7762) at org.eclipse.ui.texteditor.InsertLineAction.run(InsertLineAction.java:144) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1531) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1257) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Control.traverse(Control.java:4858) at org.eclipse.swt.widgets.Control.translateTraversal(Control.java:4836) at org.eclipse.swt.widgets.Composite.translateTraversal(Composite.java:1542) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3016) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:734) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1743) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5016) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4408) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8422) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1245) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2276) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) 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) {noformat}
| 5 |
253 |
TISTUD-1353
|
03/15/2012 17:32:19
|
iOS: Clean needs to call `xcodebuild clean` to remove stale files
|
The {{Project->Clean}} command in Studio needs to call out to {{xcodebuild}} when cleaning iOS targets in order to ensure that stale information is removed. The exact command that needs to be performed is: {code} xcodebuild -project $\{PROJECT_DIR\}/build/iphone/$\{PROJECT_NAME\}.xcodeproj -sdk iphoneos -alltargets clean xcodebuild -project $\{PROJECT_DIR\}/build/iphone/$\{PROJECT_NAME\}.xcodeproj -sdk iphonesimulator -alltargets clean {code} We need to call this _before_ deleting the iPhone folder. This bug is the Studio version of TIMOB-8025. Please get cbarber to test and resolve that ticket when complete.
| 5 |
254 |
TISTUD-1354
|
03/16/2012 10:38:41
|
Newly created apps are not appearing on the Apps page.
|
New apps are not appearing on the https://my.appcelerator.com/apps/ page. I'm currently using Titanium Studio, build: 2.0.0.201203152033. The account I've discovered this on is [email protected] and the app guid of one of the missing apps is 75629f0e-def5-45f3-b8be-92b840eec93d (CFish4). I've checked the admin system and the app is not associated with the account.
| 3 |
255 |
TISTUD-1357
|
03/19/2012 09:46:30
|
app-track called thousands of times (started today)
|
We're getting thousands of repeated calls to app-track from Titanium Studion 2.0 and Aptana 3.1. This started today, and his happening sporadically (once an hour or so) so it maybe a newly introduced bug. Looking at our logs, it looks like repeated calls for portal.samples.getSamples. Below is one mid that made the same call over 6000 times in the last hour. % grep e5254afa-f674-ea48-e1c7-69b86c6a62be des* | grep getSamples | wc -l 6831 {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"17ef49c6-52ea-f56a-4248-603f-ae0ad370","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"45e6f73a-9238-30aa-2bdf-60a7-931fd787","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"08597ce2-defe-5631-5671-1ac2-d5a2cd79","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"fba34374-83b6-6e1c-4f06-3011-d2551211","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"e1261085-61ce-b302-5cfe-f846-94c0a68a","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"f47c30f9-37b7-eeaa-090a-3fc0-c71047cf","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"a0e66d11-60d8-fb5a-315f-33cc-84a9bdc3","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"91ede117-b2fb-35a6-77b6-6ec3-40dc5580","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"fe19d99e-542e-5d26-5ca0-5dbc-d49bc060","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"06dca5b8-9a0e-e606-780f-73a9-46a27b71","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"fb019521-7af3-43f5-84b6-e5f6-a4ae2e8e","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"218e2fcb-3ca4-a4ab-d5b0-c9c9-5ee494a5","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540","ip":"10.0.1.3","id":"1fa0b6bb-d023-34c0-f6b7-2b5d-c8a7ba93","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"} {"event":"portal.samples.getSamples","type":"portal","sid":"69d66b6f3be7ca8bde1f1567ed63f4368e67846c","guid":"9f5c585e-b9e6-40b4-8ae9-c9d75cf32884","mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be","app_id":"com.appcelerator.titanium_developer_2","app_name":"Titanium Studio","app_version":"2.0.0.1327441212","mac_addr":"00:23:32:de:0f:a8","platform":"osx","version":"1.1.0","os":"Mac OS X","ostype":"32bit","osver":"10.7.3","osarch":"i386","oscpu":"2","un":"[email protected]","ver":"2","tz":"-540"^C,"ip":"10.0.1.3","id":"aad3e846-8987-7f6d-a81b-6d8d-70914595","server_ts":"2012-03-19T10:21:34-07:00","server_mid":"e5254afa-f674-ea48-e1c7-69b86c6a62be"}
| 8 |
256 |
TISTUD-1358
|
03/19/2012 11:49:09
|
iOS Preference page should utilize vertical scroll bars on tables
|
If you have a long list of certificates or provisioning profiles, the preference dialog gets very tall. We need to specify a standard height for the table so the vertical scroll bars are utilized
| 3 |
257 |
TISTUD-1363
|
03/19/2012 16:57:04
|
Application "null" has been packaged message when starting a server
|
Stumbled into this one when validating APSTUD-3664. # Create a new Server. # Insert the start and stop commands into the server-dialog. In my case, I tried that with both xampp commands, and with apache commands (same result). # Start the server from the Servers view. A message appears and inform you that the server is running, and press any key to continue. Press a key... # A message dialog appears and notify something about packaging. # The servers view displays the server as stopped, while it's still running. # When staring the server again, you get a message that says that the server is running, and press any key to continue. Do that, and you get the packaging dialog again.
| 5 |
258 |
TISTUD-1365
|
03/20/2012 05:31:43
|
"Source not found" while iOS debugging
|
Steps to reproduce: # Create a new Titanium Mobile project # Put a breakpoint on one of the "var" declarations in app.js # Launch the iOS simulator # When debugging stops on the breakpoint, note the error as shown in the screenshot
| 8 |
259 |
TISTUD-1366
|
03/20/2012 07:27:57
|
Only check apiversion tag in manifest for Android modules
|
iPhone modules are displayed as not supported when the Titanium SDK version is set to version 1.8.0.1 or newer. This appears to be due to the fact that the manifest file for iPhone modules currently do not include the 'apiversion: 2' entry. The 'apiversion' entry was added for Android modules in Titanium SDK version 1.8.0.1 to indicate that the internal module API had changed. This change only impacted Android modules and it should be checked for Android modules because older versions of Android modules will not work with Titanium SDK version 1.8.0.1 or newer (and vice-versa). This is not the case for iPhone modules (currently). The check for the 'apiversion' tag should ONLY be done for Android modules. It should be ignored for iPhone modules. 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" in the iOS and Android (current maximum version is 2 for 1.8/2.0) # Save tapp.xml and restart Studio. Note that the module now appears greyed out, but should be available for iOS
| 5 |
260 |
TISTUD-1367
|
03/20/2012 10:16:21
|
Studio: Clean single project does not clean, does not log any errors when Mobile Web folder is empty
|
Description: While testing, we tried to clean a project using the single project clean option. Nothing happened, both the Android and iPhone folder contents were untouched. Nothing was logged even when I included the debug single component setting. Only when I previewed in browser for mobile web, and then cleaned did the project actually clean Steps to reproduce: 1) Create a project with studio using all deployment targets 2) Build the project for iOS and Android to get some content in the build folders 3) Choose Project > Clean and select only the project you created 4) Check the contents of the build folders Result: The contents of the build folders remain - no clean occurred Expected: The project build folders are emptied Note: I was able to clean only after launching a mobile web preview in Browser. Then the clean functioned as expected.
| 8 |
261 |
TISTUD-1368
|
03/20/2012 10:51:28
|
Studio: Kitchen Sink Nook not available in samples
|
Description: The sample Kitchen Sink Nook is not available on Linux systems. Steps to reproduce: 1) Install Titanium Studio, build: 2.0.0.v20120320000301 on a linux system 2) Navigate to the samples Result: Kitchen Sink Nook is not available Expected: The sample for Kitchen Sink Nook should be available on Linux
| 3 |
262 |
TISTUD-1369
|
03/20/2012 11:25:32
|
Studio: Titanium Studio Samples: Incorrect message shown at top of the New sample project window while importing the sample
|
Description: While importing a sample application, an incorrect message is shown at the top of New Sample Project pop up window that Files already exist in your destination directory. They will be deleted if you continue. Steps to Reproduce: 1. Open Titanium Studio 2. Use a workspace that does not have the folder for the sample to be imported 3. Go to samples section/dashboard, select a sample and import sample as project 4. A pop window for New Sample Project opens up Actual: A message is shown at the top as "Files already exist in your destination directory. They will be deleted if you continue." Expected: The message should not be shown as there does not already exist files for the sample being imported
| 5 |
263 |
TISTUD-1370
|
03/20/2012 11:52:15
|
Remove extraneous "No file system is defined for scheme: git" messages
|
# Create a new rubbly file with a link like git:// in it (could be a github repo URL) # Hold down the Ctrl key and hover over the link # See the item below in the log file Suggest just not writing out the message for protocols we don't understand or handle. {code} (Build 3.0.3.qualifier) [ERROR] No file system is defined for scheme: git org.eclipse.core.runtime.CoreException: No file system is defined for scheme: git at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55) at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:50) at org.eclipse.core.internal.filesystem.InternalFileSystemCore.getFileSystem(InternalFileSystemCore.java:65) at org.eclipse.core.filesystem.EFS.getFileSystem(EFS.java:430) at com.aptana.editor.common.resolver.URIResolver.getFileStore(URIResolver.java:76) at com.aptana.editor.common.resolver.URIResolver.resolveURI(URIResolver.java:119) at com.aptana.editor.common.text.hyperlink.HyperlinkDetector.detectHyperlinks(HyperlinkDetector.java:81) at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:286) at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:258) at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:462) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:211) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4125) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3971) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3610) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.aptana.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code}
| 3 |
264 |
TISTUD-1373
|
03/20/2012 13:34:21
|
ModulesTable - Replace the iPhone and iPad columns with a single iOS column
|
The Modules table in the TiApp editor should not display two platforms for iPhone and iPad. It should only display one column for iOS.
| 8 |
265 |
TISTUD-1376
|
03/20/2012 14:55:28
|
Titanium Studio: Samples: RSS Reader and Geocoder: reimported projects rename and disappear on second install
|
When RSS Reader or Geocoder are installed from the dashboard/samples pane, deleted (without filesystem removal), and reimported into studio, the projects import with a different project name: Sample.Mapping and Sample.RSS instead of Geocoder and RSS Reader. If the user attempts to reinstall the sample from the dashboard/samples pane, there will be a fatal git dialog box and the project will disappear from the filesystem. Steps to Reproduce: 1. Install RSS Reader or Geocoder from the samples pane or dashboard links. 2. Delete project from workspace without removing it from the filesystem. 3. Re-import project back into studio from workspace. Expected Result: Project should have same name as before. Actual Result: Project has different name. 4. Install the project again from the samples pane or dashboard links. 5. Press ok, accept the install. Expected Result: Project should be overwritten and a new version of the sample should take its place. Actual Result: Git warning dialog, followed by automatic deletion of project from the OS.
| 8 |
266 |
TISTUD-1377
|
03/20/2012 14:57:04
|
Unable to locate module ti.cloud when launching Mobile Web application
|
Summary: When a single window template application is selected to be run on Mobile Web Preview on Browser and Mobile Web Preview on Emulator, an error is shown Steps to Reproduce: 1. Create a new app, with template as Single Windows 2. Click on the run button and select the option for Mobile Web Preview on Browser or Mobile Web Preview on Emulator An error is shown Unable to generate Mobile Web App. Error: [INFO] Titanium Mobile Web Compiler v2.0.0.v20120320000301 [INFO] Compiling Mobile Web project "SingleWindow" [development] [INFO] Copying /Library/Application Support/Titanium/mobilesdk/osx/2.0.0.v20120320000301/mobileweb/themes... [INFO] Copying /Users/ingo/Documents/Aptana Studio 3 Workspace/SingleWindow/Resources... [INFO] Copying /Users/ingo/Documents/Aptana Studio 3 Workspace/SingleWindow/Resources/mobileweb... [INFO] Copying /Library/Application Support/Titanium/mobilesdk/osx/2.0.0.v20120320000301/mobileweb/titanium... [INFO] Scanning project for dependencies... [INFO] Searching for all required modules... [INFO] Locating Ti+ modules... [ERROR] Unable to find Ti+ module "ti.cloud", v2.0 It appears that the platform="commonjs" is being left off the module definition, which then causes this issue.
| 5 |
267 |
TISTUD-1378
|
03/20/2012 15:14:25
|
Add iOS Ad Hoc package launch configuration that produces an ipa/app
|
Currently, production builds of iOS targeted projects produce an archived XCode project. For ad hoc distribution, users are expected to take the generated ipa/app and distribute it accordingly, so they would have to go into XCode to generate the output. To simplify the distribution process and reduce the need for users to mess with XCode, we should provide a separate Ad Hoc distribution launch configuration and wizard The Ad hoc distribution process with be similar to the app store distribution with the following differences: -Only ad hoc distribution certificates/profiles are displayed -Specify either app or ipa output -Specify a location for the output
| 8 |
268 |
TISTUD-1380
|
03/20/2012 16:07:32
|
Studio: Tiapp.xml editor gets out of sync and warns of changes in filesystem.
|
Description: WHile testing, Natalie noticed that her changes to Tiapp (for the SDK version) were not being reflected, and subsequent builds were still using the previous SDK setting. We investigated, and noted that manipulating the pop-up for the SDK version would warn that the file had changed on the file system,and did she want to sync. With Shalom running us through some tests we determined a few things, most disconcerting is the fact that the Tiapp XML view had a different SDK listed than showed in the Overview. This explained the issue with building with the wrong SDK. We still are investigating why the TiApp.xml is showing as out of sync from the file system perspective. Steps to reproduce: 1) Install and run Studio 2) Create a project and build for device 3) Open TiApp.xml editor and change SDK then save 4) Continue to change SDK and save until you get warned about file system sync Result: After a few moments you should see the sync warning. You may also notice if you examine the XML that the SDK setting is not matching. Expected: No sync warnings simply manipulating the tiapp. No SDK setting mismatch.
| 8 |
269 |
TISTUD-1381
|
03/20/2012 16:10:03
|
Unable to preview mobile web application when launching preview of index.html page
|
Steps to reproduce: 1. Create a Single Window project from template wizard 2. Select the application in Project Explorer 3. Choose Publish > Package - Mobile Web 4. Select "Create a new Project" and give the project a unique name 5. Complete the wizard 6. Find the new project in the workspace 7. Double-click on the index.html file to open up the main page 8. Click on the preview button in the header Actual: The app is stuck at the splash screen Expected: The mobile web app should work like a regular Single Window app on the phone. Note: The default TiMob project packaged for mobile web works as expected i.e. it does not get stuck at the splash screen. I believe the issue here is that we are launching the preview for the mobile web application from a file URL, and evidently it does not work that way. It is probably easier to extend Studio than to fix this behavior in Mobile Web. Suggested fix: * When creating a new project as part of the mobile web packaging wizard, create a new default server for use in preview and associate it with that project.
| 8 |
270 |
TISTUD-1382
|
03/20/2012 16:32:58
|
Titanium Studio: Samples: samples pane and samples dashboard links intermittently disappear
|
When using studio, the samples pane and samples dashboard links intermittently disappear. They exist on launch, disappear once in a while, then re-appear on studio restart. Has occurred twice in a few hours. Studio log attached. Steps to Reproduce: 1. Start studio. 2. Use studio for hours. Expected Result: Samples pane should contain samples, dashboard samples links should exist. Actual Result: Once in a while, the samples disappear.
| 3 |
271 |
TISTUD-1383
|
03/20/2012 16:38:53
|
Widget is disposed related to SamplesView.run()
|
Noticed this in a log file. Add reproduction steps if you can figure them out {code} !ENTRY org.eclipse.jface 4 0 2012-03-16 10:59:55.337 !MESSAGE Unhandled event loop exception during blocked modal context. !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed) at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:275) at com.appcelerator.titanium.rcp.IDEWorkbenchAdvisor.disconnectFromWorkspace(IDEWorkbenchAdvisor.java:499) at com.appcelerator.titanium.rcp.IDEWorkbenchAdvisor.postShutdown(IDEWorkbenchAdvisor.java:407) at org.eclipse.ui.internal.Workbench.shutdown(Workbench.java:3023) at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1118) at org.eclipse.ui.internal.Workbench.access$15(Workbench.java:1035) at org.eclipse.ui.internal.Workbench$25.run(Workbench.java:1279) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.Workbench.close(Workbench.java:1277) at org.eclipse.ui.internal.Workbench.close(Workbench.java:1249) at com.appcelerator.titanium.core.TitaniumUserManager.signOut(TitaniumUserManager.java:172) at com.appcelerator.titanium.ui.internal.TitaniumHomeControlContribution.signOut(TitaniumHomeControlContribution.java:110) at com.appcelerator.titanium.ui.internal.TitaniumHomeControlContribution.access$2(TitaniumHomeControlContribution.java:104) at com.appcelerator.titanium.ui.internal.TitaniumHomeControlContribution$2.widgetSelected(TitaniumHomeControlContribution.java:86) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1094) at org.eclipse.swt.widgets.Link.wmNotifyChild(Link.java:1071) at org.eclipse.swt.widgets.Control.wmNotify(Control.java:5534) at org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:1896) at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:5086) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4584) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2425) at org.eclipse.swt.widgets.Link.callWindowProc(Link.java:172) at org.eclipse.swt.widgets.Widget.wmLButtonUp(Widget.java:2057) at org.eclipse.swt.widgets.Control.WM_LBUTTONUP(Control.java:4912) at org.eclipse.swt.widgets.Link.WM_LBUTTONUP(Link.java:909) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4565) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2531) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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) Caused by: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.widgets.Widget.error(Widget.java:468) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340) at org.eclipse.swt.widgets.Tree.getSelection(Tree.java:3402) at org.eclipse.jface.viewers.TreeViewer.getSelection(TreeViewer.java:256) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:344) at org.eclipse.jface.viewers.AbstractTreeViewer.setSelectionToWidget(AbstractTreeViewer.java:2521) at org.eclipse.jface.viewers.AbstractTreeViewer.setSelectionToWidget(AbstractTreeViewer.java:2944) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1450) at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1506) at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:537) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1465) at com.aptana.samples.ui.views.SamplesView$1$1.run(SamplesView.java:63) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 61 more {code}
| 2 |
272 |
TISTUD-1384
|
03/20/2012 16:58:08
|
Clicking "Publish" multiple times when package application for distribution on Mobile Web results in an error
|
Summary: When an application is selected to be packaged for distribution on Mobile Web, an error is shown Steps to Reproduce: 1. Create a new project 2. Click on the Publish button and select the option for Package Mobile Web 3. In the pop up window, select the third option for Create a new project for the new mobile web app 4. Put in a project name and click on Publish (do it at least 2x quickly) A packaging error is shown with the message "Failed to package project"
| 8 |
273 |
TISTUD-1392
|
03/20/2012 18:35:38
|
Unable to package mobile web to a project with a space in the name
|
# Create a new project # Click on the Publish button and select the option for Package Mobile Web # In the pop up window, select the third option for Create a new project for the new mobile web app # Put in a project name with a space (I used "test 4" and click on Publish It appears to work, but ultimately fails, as shown in attached screenshot See this in details view: {code} Creation Problems Invalid project description. OK /Users/ingo/Documents/Titanium Studio Workspace 3/test overlaps the location of another project: 'test ' {code}
| 5 |
274 |
TISTUD-1393
|
03/20/2012 21:13:27
|
Launching a mobile web preview resets the default web server root
|
# Create a new Mobile Web project # Launch it in the browser preview # Package it into a new project # Press the Firefox - Internal Server Run configuration # Get "Launch URL is not defined" as a popup error Looking into the code, it appears that the currently running internal server now has a project root under /build/mobileweb for the last project, for the URL mapping fails.
| 13 |
275 |
TISTUD-1395
|
03/21/2012 08:31:38
|
Running package operations (on multiple platforms) on the same project multiple times causes errors
|
Since package operations are now public launch configurations, you can run multiple configurations in quick succession. This will cause errors since the package operations operate on the build directory. We should queue up the launch configurations so they are sequential, scheduling launches based on the project. Steps: 1. Create a mobile project with iOS, Android and mobile web deployment targets 2. Perform project package for iOS 3. Perform project package for android 4. Perform project package for mobile web 5. From the run shortcut, re-run 2/3/4 operations multiple times Expected: Each package operation completes successfully Actual: Error occurs
| 8 |
276 |
TISTUD-1396
|
03/21/2012 08:48:20
|
Auto-select API version of Android SDK if available
|
When the Android SDK is installed, auto-select (in Preferences > Titanium > Default Android SDK) the "Google APIs..." version of the correct Android SDK version for the installed Titanium SDK version. This will make it easier for new users installing Titanium for the first time, who are unaware of the difference between the standard and enhanced Android SDK versions. Note that this request may be somewhat related to TISTUD-1350 when implemented.
| 5 |
277 |
TISTUD-1402
|
03/21/2012 15:04:08
|
ACS keys cut off when generated in TiApp Editor
|
When enabling the ACS on Windows, the ACS labels at the TiApp cloud section get cut off from the bottom. (see screenshot) It's visible only when enabling ACS. When re-opening the TiApp editor, it looks fine.
| 3 |
278 |
TISTUD-1404
|
03/21/2012 15:36:36
|
Add description to iOS SDK location to describe how to run with different Xcode versions
|
For Xcode4.3, the xcode-select command must be run to ensure properly function of the iOS platform scripts. Running the command can be foreign and difficult for some users. We should display a informative description and link on how to run xcode-select. There should be a linked wiki/doc page that describes in further detail on how to run the command. The description should be included in the iOS section of the Titanium preferences. It should state: "If the desired Xcode installation is not displayed, you will need to run "sudo xcode-select <xcode_folder_path>" to target a specific installation. <a>More details</a>"
| 8 |
279 |
TISTUD-1407
|
03/22/2012 06:06:22
|
Add platform attribute to module element(s)
|
When a module that supports only a single platform is added to a project using the new modules table, the module element is added to tiapp.xml but it is missing the platform tag. Steps to reproduce: 1. Create a new mobile application project -- use defaults of all application target types 2. Click on the button to add a new module (+) 3. Select a module that is only available on one platform (e.g. ti.push) 4. Save the project 5. Attempt to run the application in the iPhone simulator 6. Build should fail with an error indicating that the ti.push module is missing Without the 'platform' tag on the module entry, the build script will attempt to locate the module for all application targets. The module element needs to include the 'platform' tag so that the module is only searched for when building for that target. For example, 'platform="android"'. Also, without the 'platform' tag the module displays in the Modules table with its version number available on all platforms -- which is incorrect since it is only available on the single platform.
| 8 |
280 |
TISTUD-1508
|
03/22/2012 07:05:03
|
Console view doesn't use background color when already open and a new process is launched
|
See screencast at: http://dl.dropbox.com/u/11524266/tistudio.mov He has the console open with some prior output from a previous run of an app (properly colored), then he launches a new run from the App Explorer, a new console page is added that has the theme fg colors, but stays with a white bg. When he clicks on the console to focus it, it gets the black bg applied.
| 8 |
281 |
TISTUD-1410
|
03/22/2012 10:41:06
|
Add URL bar to integrated mobileweb preview
|
The integrated web preview in TiStudio does not expose the local URL to which the preview pane is connected. You can see it in the title bar of TiStudio itself, but its not copyable. It would be helpful to have the URL bar shown above mobileweb preview panes.
| 3 |
282 |
TISTUD-1414
|
03/22/2012 15:01:10
|
Auto-configure browser list to contain all installed browsers on Windows
|
Description: While attempting to set a browser before running a mobile web preview, I noticed that the list of browsers did not include any specific browsers except firefox. It would be ideal to populate the list of installed browsers rather than have the user populate the list manually. Steps to reproduce: 1) Install Studio 2) Create project with mobile web target 3) Run in browser 4) Select "run configurations" and use the browser selection section Result: Firefox is the only 3rd-party browser listed although I have Chrome, Firefox, and Safari Expected: Firefox not displayed, or all installed browsers displayed
| 20 |
283 |
TISTUD-1415
|
03/22/2012 15:23:27
|
Update Studio to ship with Android tools r17 by default
|
Update the sdk_info file to point to the newest r17 version of the tools. To test, remove your Android folder and start the configuration process on Window, Linux and mac. It should install r17 of the tooling.
| 3 |
284 |
TISTUD-1416
|
03/22/2012 19:13:54
|
Titanium Mobile Module project wizard overwrites default manifest content
|
Close to a blocker, but you can get around it # Create a new mobile module project for iOS. Fill in any default values # Go through the wizard # Attempt to package the project. You will get an error of "missing required manifest key 'name'" Inspecting the manifest file, you should have something like: {code} # # this is your module manifest and used by Titanium # during compilation, packaging, distribution, etc. # version: 0.1 apiversion: 2 description: My module author: Your Name license: Specify your license copyright: Copyright (c) 2012 by Your Company # these should not be edited name: testmodule4 moduleid: asdasd.asdas guid: 60a2774b-54c6-47d2-9889-d38698d3c0d3 platform: iphone minsdk: 2.0.0.v20120322190311 {code} but instead, you get: {code} #appname: testModule #publisher: ingo #url: #image: appicon.png #appid: com.test #desc: undefined #type: module #guid: e292c47a-1210-46e9-9721-4444553793dd {code} We need to preserve the contents of the manifest file and only change elements as necessary. BasicNewTitaniumProject.generateInitialManifest() is not useful in the context of module generation. It may also cause problems with other templates too, as it seems we are completely overwriting the original manifest. We should append/modify as necessary.
| 8 |
285 |
TISTUD-1417
|
03/22/2012 19:35:43
|
Convert release notes to use new URL
|
Once the release notes are in the new location, we may need to update the code that parses them, and modify the redirect off of studio.appcelerator.com. See TitaniumSDKReleaseNotesDialog.
| 5 |
286 |
TISTUD-1419
|
03/22/2012 19:58:57
|
"Installed JREs" page missing
|
# Create a new Android Mobile Module project # It should create the project, but have the warning "Unbound classpath container: 'Default System Library' in project 'testAndroid'" # Attempting to fix that, it seems you should edit your Installed JREs preference page. However, the Standalone version of Studio doesn't have it, unlike the version of Eclipse (see screenshots). # Attempting to install the JDT tools via the notes on this page (though substituting Indigo as a version) does not appear to work as you get conflicting dependency errors. It seems we either need to remove the JDT items, or we're not fully shipping the full set. Suggested fixes: * Do not ship optional components (i.e. JDT) * Remove the django templates from Pydev, and allow users to install them optionally.
| 13 |
287 |
TISTUD-1420
|
03/23/2012 11:38:46
|
Open-source Titanium Desktop Studio integration
|
We'd like to make it easier for users to extend and contribute to the Titanium Desktop (TIDe) project. # Refactor the current Titanium Desktop plugin(s) into a new repo ## We can remove references in the *.update plugin, since the update process will likely be much different in the future ## Do we need to create the concept of a Titanium <Platform> type (i.e. desktop, mobile, ?) that would contribute a few things into the system # Add a feature enabling users to install the plugin separately on top of Studio # Create a hudson build to build this plugin and push it to a deployment site # Change the license of the plugin to Apache 2 See attached image for dependencies.
| 20 |
288 |
TISTUD-1421
|
03/23/2012 12:31:08
|
Titanium Studio: MobileWeb: Preview in Emulator conditionally fails with: Launch url is not defined
|
When deploying a second mobile web project to preview in emulator browser, studio fails with error: Launch url is not defined. Studio log identical to dialog box screenshot. Found in Windows 7, but not Snow Leopard. Steps to Reproduce: 1. Create two projects. 2. Preview first project in emulator browser. 3. Preview second project in emulator browser. Expected Result: Second project should deploy. Actual Result: Deployment fails in studio. Note: Relaunching the first project works as expected.
| 8 |
289 |
TISTUD-1422
|
03/23/2012 12:37:10
|
Titanium Studio: MobileWeb: cannot re-deploy app in Firefox on OSX
|
When re-deploying a mobile web app to firefox, the app is launched in a new window, instead of a new tab. Firefox on Snow Leopard can only have one instance, so the deployment fails and the new window is closed. MobileWeb Firefox preview should be deployed to a new tab. Does not occur on Windows 7 (app is opened in new tab). Steps to Reproduce: 1. Create project. 2. Preview in browser to firefox. 3. Preview again in browser to firefox. Expected Result: App should open in new tab. Actual Result: App opens in new window, which is automatically closed due to firefox single instance policy on Snow Leopard.
| 8 |
290 |
TISTUD-1426
|
03/23/2012 12:40:05
|
Remove option to launch Mobile Web Preview in internal browser
|
The studio internal browser may not fire touch events to mobile web apps. Steps to Reproduce: 1. Create default app. 2. Preview in internal browser. 3. Click on buttons. Expected Result: The app should respond to click events. Actual Result: No response. Works on the other external browsers. It apparently sometimes works on some machines and not on others. Based on feedback, it appears there is some conflict between Mobile Web and the internal browser. Thus, the best option is to remove the ability to use the internal browser.
| 5 |
291 |
TISTUD-1424
|
03/23/2012 13:45:02
|
Titanium Studio: MobileWeb: Packaging: allow packaging to non-existent directory
|
When packaging to a non-existent directory, an error is presented and the user cannot package. Steps to Reproduce: 1. Create a new project. 2. Package for mobile web. 3. Create a path using a new sub-directory hand-typed. Expected Result: Should be able to package app and new directory is created. Actual Result: Warning prevents app from packaging. Suggested solution: * Create directory * Don't show warning * Pop up error if issue creating dir
| 5 |
292 |
TISTUD-1428
|
03/24/2012 10:43:43
|
Studio preferences > titanium General - an error is shown if desktop sdk is not installed (may no longer be appropriate and cause unnecessary alarm)
|
h2. Problem # Do not have the desktop sdk installed # Titanium studio menu item > preferences > titanium studio > titanium # check the window for errors {noformat} An error was detected with the SDKs configuration. Reason: [Titanium SDK Home] Could not locate a Titanium Desktop SDK at the given path {noformat} Note that Ti Desktop is no longer officially supported, so this validation should be removed, or result in a warning rather than error. results: https://skitch.com/thomashue/8ch87/preferences. the user is shown an error. Being that we have put the desktop out to pasture, it might cause unnecessary alarm to user h2. Workaround Install Desktop SDK from [Continuous Builds|https://wiki.appcelerator.org/display/guides/Installing+Titanium+SDK+Continuous+Builds] site
| 3 |
293 |
TISTUD-1432
|
03/26/2012 15:20:37
|
Titanium Studio: Preferences: Titanium: cannot save Titanium SDK home path
|
When editing the titanium sdk home path, cannot save changes. The workaround is to click 'restore defaults', make the changes, then save. Steps to Reproduce: 1. Copy Application Support/Titanium (the sdk super-folder) to another location. 2. In studio, preferences, change the titanium sdk home to this new location. Expected Result: Should be able to save changes. Actual Result: Cannot save changes. Must restore defaults, then edit and save changes.
| 5 |
294 |
TISTUD-1435
|
03/26/2012 18:54:39
|
Android module projects should have better validation for name and id
|
When creating a mobile module project, we should be more strict about the name validation and the module-id validation. * Names should not contain any hyphens (and other special characters that can 'kill' the generated JavaScript example, or the packaging). Suggest we use the javascript identifier rules here. * module-id should follow the Java conventions for package names (just like we do with Android).
| 8 |
295 |
TISTUD-1442
|
03/27/2012 09:49:08
|
Prevent an Android Mobile Module project creation when JDT is not installed
|
Android mobile-module project should not be created unless the JDT plugins (feature) are installed. Right now, a created project on an environment without JDT is not usable.
| 5 |
296 |
TISTUD-1447
|
03/27/2012 16:00:49
|
Run preference page platform loading using a job
|
Currently when the preference page is opened, it takes some time for the dialog to appear, resulting in a wait cursor to appear. This is very confusing for users. The proposed solution is: -When the preference page is opened, run the loading of platform information in a background job -While the platform information is loaded, the corresponding platform UI is disabled and the value of "Loading..." is displayed. We should do this for the two main platforms, iOS and Android, since they require the most processing time.
| 13 |
297 |
TISTUD-1450
|
03/27/2012 17:51:03
|
Studio: Updated modules delivered via CI builds are not replacing existing modules if they share the same name
|
While evaluating ACS features, we encountered an Android issue that was supposed to have been fixed in the latest ti.cloud module. Upon further investigation we determined that the module was in fact included with the latest CI build. We conducted a few experiments and determined that although the module was updated, the name was the same so during the unzipping process, the module was not replacing the existing older module. Steps to reproduce: 1) Delete your existing common JS module folder from the Titanium folder 2) install a CI build from 3/24 or before 3) Check the contents of the module folder 4) install a CI build from 3/27 or later 5) Check the contents of the module folder Results: The ti.cloud module is the older broken module, not the newer fixed module Expected: The module is overwritten by the newer module with the same name. Note: There is no relevant content in the log
| 8 |
298 |
TISTUD-1452
|
03/28/2012 08:55:33
|
Simplify initial Studio UI and perspective
|
An exercise in simplifying the new user experience: * Rename Web perspective to "Studio (extended)" * Create new "Studio" perspective ** remove top level toolbar ** add keyboard shortcuts commands for "occurrences", "block selection", "show whitespace characters" ** remove samples view ** remove outline view ** remove snippets view ** remove servers, problems, terminal, console view ** keep console view hidden unless an error comes up
| 13 |
299 |
TISTUD-1456
|
03/28/2012 12:05:14
|
Add default UI configuration options to dashboard
|
* Remove Welcome page * Replace with accordion. Initially open a section to configure TISTUD-1456 ** Light/dark theme ** Simple/advanced perspective ** See APSTUD-4798 and APSTUD-4799 for actions to call The bottom half of the accordion is similar to what we have currently If we reduce or remove the top toolbar, we may wish to surface some common initial configuration options to the first tab of the dashboard--something equivalent to an initial questionnaire. It could be perhaps in some normally "hidden" area for "advanced configuration" if we determine it's useful but is confusing on first run.
| 20 |
300 |
TISTUD-1464
|
03/29/2012 08:13:55
|
Inform users they need to switch to a workspace without spaces if doing Android Module development
|
When using the Android NDK, if you have spaces in your path (i.e. /Users/username/Documents/Titanium Studio Workspace), Studio will fail to be able to build an Android module project. Suggest putting up a warning when creating a mobile module project warning users about the issue and informing them how to solve it (direct them to the wiki page on how to move/switch their workspace: http://docs.appcelerator.com/titanium/2.0/index.html#!/guide/Switching_your_Workspace).
| 5 |
301 |
TISTUD-1466
|
03/29/2012 10:20:30
|
Use built-in ANT when packaging Android modules
|
# Created a new Android mobile module project # Attempt to package the project # Run into this error: {code} Caused by: java.lang.NullPointerException at com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate.launch(AndroidModulePackageLaunchConfigurationDelegate.java:83) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) at org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1023) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Root exception: java.lang.NullPointerException at com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate.launch(AndroidModulePackageLaunchConfigurationDelegate.java:83) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) at org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1023) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code} snippet of code: final Process osProcess = ProcessUtil.run(antPath.toOSString(), project.getLocation()); It appears it can't find ANT. We package ANT as part of Studio, so we should instead use the built-in ANT rather than calling it on the command line. Workaround: Right-click on build.xml. Click *Run As* > *Ant Build* (the first option)
| 5 |
302 |
TISTUD-1468
|
03/29/2012 11:35:42
|
Add Titanium Project GUID to ACS application creation call
|
When creating an application in ACS, we need to pass the GUID along with the call. The format will be: ti_guid=<Project GUID>, passed to the create.json call.
| 3 |
303 |
TISTUD-1469
|
03/29/2012 14:17:34
|
Studio: HTML Template selection does not load correctly.
|
After first loading Titanium Studio the template selection for the New from template > HTML has the wrong selection (see screen shot). If I load a template for HTML this fixes the template selection found in the menu. Steps to reproduce: 1. Open Titanium Studio. 2. Click File > New From Template > HTML Expected results: Should see a list of all available templates for HTML files. Actual results: Only a strange entry and the HTML 5 template appear.
| 8 |
304 |
TISTUD-1474
|
03/31/2012 11:00:02
|
Titanium Studio: Installer - On Windows 7, when installing Titanium Studio, the License Agreement has a bad refresh screen
|
Steps to reproduce: 1. Get Titanium Studio 2.0.0 installer for Windows 2. Hit next until you see the License Agreement screen Actual: The License Agreement has a bad refresh screen. See attachment Expected: Should be able to see the License Agreement. Note: Does not occur with the Titanium Studio 1.0.9 installer.
| 5 |
305 |
TISTUD-1476
|
04/02/2012 09:13:35
|
NPE in TitaniumUpdateStartup.run()
|
Found in my log file. To replicate (my be intermittent), try shutting down Studio right in the middle of the "log in" process {code} !ENTRY org.eclipse.core.jobs 4 2 2012-03-31 07:44:07.268 !MESSAGE An internal error occurred during: "Checking for new Titanium SDK Updates...". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.update.TitaniumUpdateStartup$1.run(TitaniumUpdateStartup.java:79) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 3 |
306 |
TISTUD-1477
|
04/02/2012 09:18:07
|
Make Titanium SDK release-notes grabbing more robust
|
If the current set of release notes is from a full HTML page that _does not_ contain a <div class="apidoc">, the release noes will launch in a new browser window. # Allow for override of TitaniumSDKReleaseNotesDialog.RELEASE_NOTES_URL as a command-line option to make testing this easier. # First try to grab apidiv. # Then try to grab interior of body node, or if no body node, then whole content. If either work then replace release_notes template with new content. # If all else fails, use whole content and don't use the template. Notes: * Be careful of nulls * Anchor links didn't appear to work (might need to be munged?)
| 8 |
307 |
TISTUD-1479
|
04/02/2012 11:35:27
|
Allow selecting a non-existing directory as the Titanium SDK directory
|
When a user selects a Titanium SDK path in the preference page, we don't allow a path that has no Titanium SDK in it. A better behavior would be: # Allow an arbitrary directory selection. # Prompt the user that the Titanium SDK will be downloaded into the new location (in case it's missing an SDK). # In case a directory creation is needed, we'll do that *before* the preference dialog is closed (on apply/ok). This will clear any permission issues with the selected path before the SDK is downloaded. # If everything is OK with the new location, start the SDK update process into the new path.
| 8 |
308 |
TISTUD-1481
|
04/03/2012 09:11:13
|
Studio: Install site will not allow for software to be installed.
|
When trying to install the TestFlight software plugin following the steps below I found that I can not proceed to the licence page in the installation. Steps to reproduce: 1. From the Help menu, select Install New Software... to open an Install pop-up window. 2. In the Work with: text box of the Install window, type the URL http://ec2-50-16-19-245.compute-1.amazonaws.com/appcelerator/studio/testflight/update/release/ for the update site, and hit the Enter key. 3. In the populated table below, check the box next to the name of the plug-in, and click the Next button. 4. Click the Next button to go to the license page. Expected result: The licence page is displayed and the installation can be completed. Actual result: The next button does not become active and there is no way to continue to the next part of the installation.
| 5 |
309 |
TISTUD-1488
|
04/03/2012 09:11:20
|
ACS Keys not copy-able
|
I enabled ACS for one of my apps using early access 2.0 Studio, and it shows the production and development keys, but you can't copy it, if we need to use HTTP access or test using other software - we would have to manually type this out, or go to the ACS website, can the keys in Studio be copy-able?
| 5 |
310 |
TISTUD-1482
|
04/03/2012 09:14:47
|
NPE in Log when Studio is shutdown
|
Found in my log file. To replicate (my be intermittent): 1. Start up Studio 2. Open the Progress View 3. Restart Studio 4. When Studio is started, take note of the items in the Progress view 5. When there are items running int he progress view, close Studio I repeated this 4 times, with different tasks in the progress view running, and saw the NPE twice !MESSAGE Errors running builder 'Studio Unified Builder' on project 'testMe'. !STACK 0 java.lang.NullPointerException at com.aptana.core.build.UnifiedBuilder.getIndexManager(UnifiedBuilder.java:367) at com.aptana.core.build.UnifiedBuilder.filterFiles(UnifiedBuilder.java:471) at com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:400) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:302) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:148) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
| 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.