{ "id": "91908", "key": "ALOY-23", "fields": { "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false }, "project": { "id": "11113", "key": "ALOY", "name": "Alloy", "projectCategory": { "id": "10400", "description": "Tools for developing applications", "name": "Tooling" } }, "fixVersions": [ { "id": "14036", "description": "2012 Sprint 14", "name": "2012 Sprint 14", "archived": true, "released": true, "releaseDate": "2012-07-19" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2012-07-19T11:52:06.000+0000", "created": "2012-05-16T08:57:39.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [], "versions": [ { "id": "14036", "description": "2012 Sprint 14", "name": "2012 Sprint 14", "archived": true, "released": true, "releaseDate": "2012-07-19" } ], "issuelinks": [], "assignee": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2014-06-22T13:21:11.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "12329", "name": "Runtime", "description": "Generic bucket for uncategorized runtime issues" } ], "description": "h2. description\r\n\r\nUntil zipti is integrated with Titanium Studio, its translation process needs to be run on the commandline through nodejs and then the resulting code needs to be placed in an existing Titanium project. After the code is placed in that existing project, a developer needs to open/access TiStudio and then launch the generated app against the emulator/simulator/device of their choice.\r\n\r\nIt would be quicker for testing if this could be reduced to 1 step, allowing a dev to deploy right from zipti. We need to investigate if this is a good idea, or if it creates an unnecessary separation from the existing build scripts. Duplicate effort is something we can't afford here.\r\n\r\nh2. proposed usage\r\n\r\nWe could add an additional option to the command line execution. For example, we could add {{-t, --target}} whose value would correspond to a valid build target. For example, \r\n\r\n{code}\r\nzipti -p -o ~/Titanium\\ Studio\\ Workspace/myTestProject -t iphone\r\n{code}\r\n\r\nOpen to alternatives here. Thoughts?", "attachment": [], "flagged": false, "summary": "Launch emulators, simulators, or devices directly from zipti", "creator": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "environment": null, "comment": { "comments": [ { "id": "195039", "author": { "name": "rmcmahon", "key": "rmcmahon", "displayName": "Russell McMahon", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Sounds good to have a -t flag for running a single command and have the app show. We may also need to specify, device vs simulator and release vs debug. I think for now let's just keep this ticket open as cli stuff with which we will interact is going through changes. I will bring this up with Neeraj to make sure as cli progresses that ZipTi functionality is included.", "updateAuthor": { "name": "rmcmahon", "key": "rmcmahon", "displayName": "Russell McMahon", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-05-16T14:02:37.000+0000", "updated": "2012-05-16T14:02:37.000+0000" }, { "id": "200617", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "The android emulator and ios sim can be launched with jake. Also, the {{alloy run}} command makes use of titanium.py, allowing developers to run existing alloy-powered projects.", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-06-27T11:35:45.000+0000", "updated": "2012-06-27T11:35:45.000+0000" } ], "maxResults": 2, "total": 2, "startAt": 0 } } }