udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "When debugging on device, Studio launches two launch configurations (see screenshot). This makes it confusing to the user since the first launch configuration (Install on device) finishes and terminates, and another launch configuration is launched.    There should only be one launch configuration and it should contain both the app installation and debug processes "
Answer: 27633.0

User story: "Currently, to clear the studio log, the user needs to navigate to Help > Titanium Studio > Clear Log File.    It would be ideal to have a more accessible and intuitive way to clear the log file."
Answer: 2570915.0

User story: During the packaging of an app for debugging on device, we need to amend the request with a list of the current IP addresses assigned to the machine (excluding loopback addresses)    Format: host:port:id:hosts where hosts will be coma separated values. For iOS on device debugging, this is going to be "::id:ip,ip,ip,ip"
Answer: 21436.0

User story: "The app icon is an important identifier for a 360 app. Users should be able to update hte app icon via the tiapp.xml editor    * Add a field showing the current icon (scaled for size)  * Add a browse button allowing the user to pick a new icon  * Restrict the icon to standard app store guidelines."
Answer: 22524.0

User story: "We have renamed the --dir CLI option to --project-dir for the following commands:    * build  * clean  * project    and --workspace-dir for:    * create    Note: there is no longer a run or install command."
Answer: 395910.0

User story: Add a right-click "Alloy > Add Widget > Browse..." menu item/command that opens a dialog/wizard similar to our Project template selection. This is a means of users being able to browse and explore the available widgets when they're not sure the specific one they want.    The list of available widgets and metadata will come from the "alloy list widgets" command. When user selects a widget put the id that is listed in the returned json metadata for the widget into the Alloy app/config.json in the dependencies object. For example if the user selected the "Search For Books" widget then the config should look like the following.      {      "global": {},      "env:development": {},      "env:test": {},      "env:production": {},      "os:ios": {},      "os:android": {},      "dependencies": {          "com.appcelerator.searchForBooks":"1.0"      }  }
Answer: 2575257.0

User story: "Titanium SDK added a feature that will default to the latest module version if none is specified int he tiapp.xml (TIMOB-7973). When specifying a module, we should default to no version (use latest). This will enable users to more easily update modules without having to modify the tiapp.xml"
Answer: 27777.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: We currently assume that a project root is the module root path. We need to query node/npm for the list of module load paths ($NODE_PATH) and try to resolve/search against those, as well as handle searching up the hierarchy for node_modules directories, and handle loading "core" modules from node itself. The following pseudo-code gives the algorithm:  http://nodejs.org/api/modules.html#modules_all_together    See:  http://www.bennadel.com/blog/2169-Where-Does-Node-js-And-Require-Look-For-Modules-.htm  http://nodejs.org/api/modules.html#modules_core_modules    Additionally, it may make sense to index the paths specified in NODE_PATH on startup.
Answer: 115339.0

User story: "The SDK changed its versioning from 2.2 to 3.0. We need to review any checks inside the code to see if they need to be updated."
Answer: 8141.0

User story: "See http://preview.appcelerator.com/dashboard/sdk_info.json for the current content. We need to update the versions for iOS to include 6.0.  "
Answer: 10062.0

User story: "Update the project and wizard icons with the updated imagery."
Answer: 8824.0

User story: This one is only for V2 (Node.js). The Python implementation in V1 does not support a building command.    We should try call "build" again when we've cleaned all our projects and build automatically is checked.  The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed.    {code}  titanium build [--platform=[iphone,ipad,ios,android,blackberry,mobileweb,etc.]] [--package] [--device] [--simulator|--emulator] [--production] [--development] [--verbose [0-5]] [project-dir]  {code}
Answer: 44593.0

User story: This one is only for V2 (Node.js). The Python implementation in V1 does not support a building command.    We should try call "build" again when we've cleaned all our projects and build automatically is checked.  The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed.    {code}  titanium build [--platform=[iphone,ipad,ios,android,blackberry,mobileweb,etc.]] [--package] [--device] [--simulator|--emulator] [--production] [--development] [--verbose [0-5]] [project-dir]  {code}
Answer: 44427.0

User story: "Based on the related ticket, we need to pass in appids or app names rather than the directory when calling:    * unpublish  * list  * logcat  * loglist"
Answer: 7140.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Add a right-click menu "Alloy > Add Widget > (dynamic list of widgets)". Place a separator between the dialog item (from TISTUD-2280) and the actual list.    Selecting an item adds it to the app right away, as a quick way to do so when you already know the widget you want.    The list of available widgets and metadata will come from the "alloy list widgets" command. When user selects a widget put the id that is listed in the returned json metadata for the widget into the Alloy app/config.json in the dependencies object. For example if the user selected the "Search For Books" widget then the config should look like the following.      {      "global": {},      "env:development": {},      "env:test": {},      "env:production": {},      "os:ios": {},      "os:android": {},      "dependencies": {          "com.appcelerator.searchForBooks":"1.0"      }  }
Answer: 2599692.0

User story: "Mobile Web has minimum supported browser requirements. As part of the dashboard configuration process, we need to check if the current browsers a user has configured match those requirements    * Add info to the sdk_info.json file  * Check to see if we have configured browsers via TISTUD-1414 and TISTUD-1738  * If not, configure them  * If so, check the version strings in the name vs the versions in sdk_info  * Return a similar success value to iosSdk with installedBrowsers and installedBrowsers"
Answer: 25027.0

User story: For ticket TISTUD-1234, we need to allow the addition of a checkbox to the launch configuration for the "Custom Cloud", allowing the user to choose if they wish to auto-deploy the project as part of the application launch or package.    * Define a new tab name and UI  * Define which launch configurations inherit this new tab  * Define a tab order or priority (unsure if this is necessary)  
Answer: 55.0

User story: "If you have an older version of node.js, you can just install a newer version over the top. Currently we direct the user to a troubleshooting page, but we can improve that process.    If the version of node.js is out of date:  # Pop up a dialog (currently implemented) letting the user know the version is out of date  # Offer to install a newer version for the user (mac and windows). Follow the same steps as the normal installation  # If that fails, or on Linux, direct the user to the previous troubleshooting page."
Answer: 50078.0

User story: "Currently, we require node.js to be version 0.8.0 or higher. This can be reduced to 0.6.0."
Answer: 8648.0

User story: "This was found in the course of testing TISTUD-1527. Steps:    1. Open dashboard  2. Right click (on a link) > Open in new window    Expected  Link is opened in a browser based on the Eclipse/Studio settings    Actual  Link is opened in a new external generic browser with no navigation controls    This is currently only occurring on Windows, but an implementation change will affect osx/linux as well"
Answer: 70739.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We have the following issue open for iOS to add debugging support for device  Enhancement request - Add Support for debugging on device    http://jira.appcelerator.org/browse/TIMOB-4625    Once it is addressed, Studio would need to add UI to support the feature.  "
Answer: 452800.0

User story: "Add keyboard shortcut for opening dialog and generating Alloy resources (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard)  This includes key-bindings for:  # Widget  # Migration  # Controller  # Model"
Answer: 161914.0

User story: "The icons for the RedHat Open Shift client/server are not in keeping with rest of the icon templates. They need to be upgraded."
Answer: 48573.0

User story: Now that the template selection page is first, it's somewhat confusing if you _don't_ want to use a template.    Similar to what was done for Alloy, remove the checkbox for "Create the project using one of the templates" and instead replace it with an entry in the template list.    # Named "Default Project"  # Icon is the default icon  # Description is "A default [Wizard Type] project without a template"
Answer: 10331.0

User story: When links are clicked in the browser, they are opened in an external browser. The links should be opened using the eclipse preference (either internally or externally in either a specified or default browser). The following tasks are required:    -Add a portal action that opens a url in the prefered browser - "openUrl"  -Update the portal core.js to use the new action
Answer: 30686.0

User story: "JavaScript files become associated with Titanium Studio as a default without user notification.    Steps to Reproduce:    1. Launch Titanium Studio.  2. Create a .js file on the desktop.  3. Context click the .js file and Open With...    Actual Result:    Titanium Studio is the default associated program for opening javascript files.    Expected Result:    TextEdit (or whatever it was before) should be the default program."
Answer: 1048.0

User story: Alloy templates are similar to rails templates--less preset set of files, more a set of commands to run to generate a scaffold. We need to present Alloy templates alongside traditional templates as part of the new project wizard.    * Need metadata format for Alloy templates and location on disk where they are stored (or how we will grab them)  * Alloy templates need to specify "Alloy" in the tags
Answer: 83680.0

User story: "This makes the latest version of Rubles available to all Studio users    * Merge the appcelerator/*.ruble projects from the master to the stable branch  * Push the results back to Github"
Answer: 16336.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: As part of the http://hudson-master.hdqt.appcelerator.com/hudson/job/push-titanium-stable/ build, (before the push):    * Find the version # in the version.txt file  * See if that git tag has not already been created. If not, create a new tag of the form "vX.X.X.XXXXX" (note the additional "v" at the front)  * Push the tag to the following repos:  ** titanium_studio  ** titanium_studio_rcp  ** appcelerator/*.ruble    And on Aptana:  ** studio3  ** studio3-php  ** studio3-ruby  ** Pydev  ** libraries_com  ** swt-webkit  ** aptana/*.ruble  
Answer: 29034.0

User story: "Once we have a XSD for tiapp.xml, we need to validate the UI elements in the TiApp editor against it.   Doing so requires:  * Investigate how to link the UI elements in the editor with the XSD errors.  * replacing whatever possible for the current validation scheme in the TiApp editor with the XSD validation.        "
Answer: 2756.0

User story: "The search option in Dashboard needs to point to the new https://www.appcelerator.com/search endpoint. An example query is http://www.appcelerator.com/search/devblog?qry=wiki"
Answer: 111513.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The videos in (https://github.com/appcelerator/titanium_studio_dashboard/blob/master/data/videoCategories.json):    {code}   {    "id": "zero-to-app",    "title": "Zero-to-App",    "videos": [     {      "id": 1,      "title": "Preparing for Mobile Development",      "isFeatured": true,      "length": "6:24",      "description": "Learn how to configure your computer with the software necessary to develop Titanium Mobile applications. We will also look at some TODO items for development teams looking to publish applications to the Apple App Store and Android Market.",      "thumbnail": "img/mock_video.png",      "href": "http://training.appcelerator.com/zero-to-app#102"     },     {      "id": 2,      "title": "Getting Started and the Development Workflow",      "length": "6:40",      "description": "Learn the basics of building, testing and deploying mobile apps with Titanium. This video introduces you to the Titanium Studio IDE and development workflow. We'll step through creating and importing projects, editing source code, launching mobile emulators and debugging your Titanium applications.",      "thumbnail": "img/mock_video.png",      "href": "http://training.appcelerator.com/zero-to-app#103"     },     {      "id": 3,      "title": "Importing Sample Projects",      "length": "4:30",      "description": "Use the project import capabilities of Titanium Studio to import sample applications like the Kitchen Sink, Tweetanium, or ARTi to explore the capabilities of Titanium.",      "thumbnail": "img/mock_video.png",      "href": "http://training.appcelerator.com/zero-to-app#104"     }    ]   },  {code}    need to be switched to:    http://vimeopro.com/appcelerator/zero-to-app/video/24896537 - Preparing for mobile development'  http://vimeopro.com/appcelerator/zero-to-app/video/24896600 - Getting Stated with Development Workflow  http://vimeopro.com/appcelerator/zero-to-app/video/25102426 - importing sample projects
Answer: 3189.0

User story: "Open Shift has new images and logos. Replace the branding in the project wizards with new images.    * Create new project dialog (16px icon)  * Wizard banners during project creation (48px image)  * Deploy wizards (16px images)"
Answer: 33.0

User story: "Modify the new project wizard to incorporate the Alloy integration. The changes are:  * the first page of the wizard should prompt the user to select a template. the second page is the page that the users enters the app info (exists today)  * in the first page, add the ability to:  ** list all available Alloy templates  ** ability to search for templates  ** user should be able to select only one template  ** there should be an empty template. this template will create non Alloy apps  "
Answer: 24265.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The new Kitchen Sink version is designed to replace the 3 existing versions.    Remove the Kitchen Sink iPad version, and if possible, also remove the Kitchen Sink Nook version. You will need to confirm with eric Merriman about whether or not we can leave the Kitchen Sink Nook version in."
Answer: 14407.0

User story: "We've bundled together the node.js code and the nettle code in a single plugin.    Instead, we should create:    * com.appcelerator.titanium.acs.core  * com.appcelerator.titanium.acs.ui    and make those depend on the existing nodejs plugins."
Answer: 19895.0

User story: "If the Android update utility is run from the Studio Dashboard Configure utility, and the Android update utility does not exist (because it was removed after studio launched), there will be an error.    This is not a regression.    Steps to Reproduce:    1. Launch Studio.  2. Open Dashboard > Configure > Android.  3. Press 'Install or Update'.    If the Android SDK is not installed, install it, otherwise close the Android install utility menu and related Studio pop-up dialogs.    4. While Studio is open, remove the installed Android SDK folder from the OS filesystem.  5. Press 'Install or Update' again.    Actual Result:    Error.    Expected Result:    The user should be prompted to install the Android SDK."
Answer: 737767.0

User story: implement sign up process through Studio. Flow should be:  * option for selecting "new User" or "Existing user"  * if New User show sign up form with fields:  ** First, Last, email ,password, verify password, Agree to EULA, Submit or Cancel (Cancel takes you back to the first screen)  ** Once submit show some visual indicator that there is progress  * If existing user, then follow current flow (username / password)        ** If new user sign up success, then auto login in Studio and launch dashboard (configuration wizard). Also show toaster, asking user to activate his account
Answer: 21686.0

User story: "We need to replace the current Node.js branding with new branding.    * Project wizards  * Icons  * Project nature"
Answer: 48695.0

User story: We should support that for MobileWeb.    h3. Run MobileWeb  V1:  {code:title=V1 (Browser)|borderStyle=solid}  "sdk-version/mobileweb/builder.py" [project-dir] "development"  Working directory: /Users/<USER>Documents/Aptana Studio 3 Workspace/MobileProject  {code}    V1:  {code:title=V1 (Android Emulator)|borderStyle=solid}  sdk-version/android/builder.py emulator [name] [android.sdk] [project-dir] [id] "6" "HVGA"  sdk-version/android/wait_for_device.py [android.sdk]  android.sdk/platform-tools/adb -e shell "rm /data/data/com.android.browser/cache/webviewCache/*"  android.sdk/platform-tools/adb -e shell am start -a android.intent.action.VIEW -d 'http://10.0.2.2:8020/index.html'  {code}    V2:  {code:title=V2|borderStyle=solid}  Switch calling builder.py to the new CLI build command (related to TISTUD-1886); everything else stays the same (? may need to confirm with the CLI team)  {code}
Answer: 136086.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: h3. Debug iOS  V1:  {code}  /usr/bin/killall -2 "iPhone Simulator"  /usr/bin/killall -2 "iphonesim"  /usr/bin/killall -2 "ios-sim"  sdk-version/iphone/builder.py simulator [ios.version] [project-dir] [id] [name] universal ipad 192.168.0.101:55205     Environment: DEVELOPER_DIR=ios.tools  {code}    V2:  {code}  titanium build --platform=ios --simulator=[ios.version] [project-name]  {code}    h3. Notes  # For iOS, we may still need to call the _'killall'_ before the command.
Answer: 138853.0

User story: We should support that for iOS.    h3. Run iOS  V1:  {code:title=V1|borderStyle=solid}  /usr/bin/killall" -2 "iPhone Simulator"  /usr/bin/killall" -2 iphonesim  /usr/bin/killall" -2 ios-sim  sdk-version/iphone/builder.py simulator [ios.version] [project-dir] [id]     Environment: DEVELOPER_DIR=ios.tools  {code}    V2:  {code:title=V2|borderStyle=solid}  titanium build --platform=ios --simulator=[ios.version] sample  titanium run --platform=ios --simulator=[ios.version] --debug sample  {code}  
Answer: 136107.0

User story: "The first page of the new project wizard should prompt the user to select a template. the second page is the page that the users enters the app info (exists today)    In the first page, add the ability to:  * List all available Alloy templates (TISTUD-2057)  * User should be able to select only one template  * There should be an empty template. this template will create non Alloy apps (TISTUD-2070)"
Answer: 97262.0

User story: "h2. Module Creation    V1:  {code}  sdk-version/titanium.py create --type=[module] --id=[id] --name=[name] --dir=[project-parent-dir] --platform=[iphone]  Environment: ANDROID_SDK=[android.sdk], DEVELOPER_DIR=[ios.tools]  {code}    V2:  {code}  titanium create --platforms=[iphone,ipad,ios,android,blackberry,mobileweb,etc.] [--type=[module]]  [--id=string] [--sdk=sdk-version] [--verbose|-v [0-5]] [--template=name] [--[no-]cloud] [--dir=dir] name  {code}    Reference: https://wiki.appcelerator.org/display/tools/Studio+support+for+new+Module+structure+and+CLI"
Answer: 1139835.0

User story: "Once a user has Node.js installed, we need to install the nettle package for ACS/Node.js deployment:    * We need to check to see if the package is installed  * If not, install it.  {code}  [sudo] npm install nettle -g  {code}    Suggestion is that we don't really know if we need to sun under sudo. We should try without, and then prompt the user if we fail in that case."
Answer: 51033.0

User story: Existing Node.js functionality is labelled as a "Node.js" project. We need to replace that name with a new name in wizards, project descriptions and preferences (as appropriate)
Answer: 915.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The V2 CLI requires log-in before execution.    The implementation should probably log-in once per session with the credentials the user already provided for the studio.  We'll need to make sure we log-out in case the user clicked the log-out.    The Studio support a limited time of offline work, and we need to make sure that the platforms supports it as well.  "
Answer: 106025.0

User story: "Add support for the packaging command via the CLI extension.    V1.  {code}  sdk-version/mobileweb/builder.py [project-dir] production  Working directory: [project-dir]  {code}    V2.  {code}  titanium build --package --platform=mobileweb [project-dir]  {code}"
Answer: 126618.0

User story: Add support for the packaging command via the CLI extension.    V1:  {code}    sdk-version/iphone/prereq.py package  Environment: DEVELOPER_DIR=ios.tools     sdk-version/iphone/prereq.py package  Environment: DEVELOPER_DIR=ios.tools     sdk-version/iphone/builder.py distribute [ios.version] [project-dir] [id] [name] "C694789B-BEF5-49BE-800C-A5F4C8EADF5F" "Roland Muschenetz" "" "universal"  Environment: DEVELOPER_DIR=ios.tools  {code}    V2.  {code}  titanium build --package --platform=ios sample  {code}
Answer: 374334.0

User story: "Add support for the packaging command via the CLI extension.    V2:  {code}  titanium build --package --platform=[platform] [project.dir]  {code}    +create the V1 (need to investigate what it is)"
Answer: 164455.0

User story: "h3. Debug Android  V1:  {code}  sdk-version/android/builder.py emulator [name] [android.sdk] [project-dir] [id] 6 HVGA  sdk-version/android/fastdev.py start [project-dir]  sdk-version/android/builder.py simulator [name] [android.sdk] [project-dir] [id] 6 HVGA /127.0.0.1:55040  {code}    V2:  {code}  titanium build --platform=android --emulator=[emulator.name] [project.dir]  titanium run --platform=android --emulator=[emulator.name] --debug [project.dir]  {code}    h3. Notes  # We need to make sure that FastDev is supported by the new CLI  "
Answer: 163056.0

User story: "We should support that for all platforms.    h3. Run Android  V1:  {code:title=V1|borderStyle=solid}  sdk-version/android/builder.py emulator name [android.sdk] [project-dir] id 6 HVGA  sdk-version/android/fastdev.py start [project-dir]  {code}    V2:  {code:title=V2|borderStyle=solid}  titanium build --platform=[platform] --emulator=[emulator.name] [project-dir]  titanium run --platform=[platform] --emulator=[emulator.name] [project-dir]  {code}  "
Answer: 163060.0

User story: "On V1 CLI support there are scripts that check for prerequisites.    Android V1:  {code}  Process: android.sdk/android list targets  Working directory: android.sdk  {code}    iOS V1:  {code}  sdk-version/iphone/prereq.py package     Environment: DEVELOPER_DIR=ios.tools  {code}    There does not yet appear to be an analogue of these commands in V2 of the CLI. It's unclear how multiple commands that gather information like this would be structured."
Answer: 126484.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Add "clean" support via the CLI commands extension.    V1 (Python):  {code}  sdk-version/titanium.py clean    Working directory: [project-dir]  {code}    V2 (Node.js):  {code}  titanium clean [project-dir]  {code}
Answer: 81972.0

User story: This one is only for V2 (Node.js). The Python implementation in V1 does not support a building command.    We should try call "build" again when we've cleaned all our projects and build automatically is checked.  The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed.    {code}  titanium build --platform [iphone,ipad,ios,android,blackberry,mobileweb,etc.] --sdk <value> [--build-type [production | development | test]] [--log-level [trace | debug | info | warn | error]] --dir <project-path>  {code}
Answer: 83228.0

User story: V2 (Node.js) CLI will support querying for command availability.    This would be a check we can do against a SDK to see if a new command is supported by a particular version.  For example, rather than doing a version check, we can query the SDK to see if the command "clean" is available.    {code}  titanium available [--command|--feature|--platform] [--version] [--sdk=sdk-version] name  {code}    _Note:_ We may want to consider how we define the versioning of the CLI. Will it have a different version, or will it map to an SDK version.    _V1 CLI does not support this feature._
Answer: 631467.0

User story: "Add an extension for the CLI command that updates the project with new deploy targets.    V1 (Python):  {code}  sdk-version/project.py [name] [id] [project.dir] [platform] -u  {code}    As it looks like, V2 does not require the *-u* command, and it's suppose to auto-detect the targets in the tiapp.xml, and build the required resources."
Answer: 133980.0

User story: "Add extensions for the CLI commands that create a Titanium project (mobile / module).    h2. Project Creation  V1 (Python):  {code}  /sdk-version/project.py [name] [id] [project-parent-dir] [iphone] [android] [mobileweb] [android.sdk]  Environment: DEVELOPER_DIR=[ios.tools]  {code}    V2 (Node.js):  {code}  titanium create --platforms=[iphone,ipad,ios,android,blackberry,mobileweb,etc.] [--type=[app]]  [--id=string] [--sdk=sdk-version] [--verbose|-v [0-5]] [--template=name] [--[no-]cloud] [--dir=dir] name  {code}  "
Answer: 82003.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We need to be able to support V1 (Python) and V2 (Node.js) of the SDKs directly.    # Create an extension point which describes the SDK per version range (< 2.2 is v1, >= 2.2 is v2), and allow contributing commands that are designed to run on a specific CLI.  # The extension will return a 'command' to run by asking for a specific command key and passing the SDK version to filter by. A returned command will then be executed and provide progress as it's being executed.  # When the CLI has no support for a specific command, a 'no-op' command (or null) can be returned.    The extension should also allow querying for a command on a specified CLI version (V1/V2). "
Answer: 82012.0

User story: "The JSON style files specify style information for an app. We can provide CA for the property names, and also possibly common values similar to CSS CA.    Need XML file containing CSS style information for the JSON configuration. See https://raw.github.com/aptana/studio3/development/plugins/com.aptana.editor.css/metadata/css_metadata.xml"
Answer: 185887.0

User story: For Alloy XML files, it is a file with XML tags, i.e.:  {code}  <View id="a">      <Button id="b">Hello</Button>      <Label id="t"></Label>  </View>  {code}   Need XML file containing tag information for Alloy tags. See https://github.com/aptana/studio3/blob/development/plugins/com.aptana.editor.html/metadata/html_metadata.xml
Answer: 185840.0

User story: As an example:  {code}  <Window>      <Button id="b"></Button>  </Window>  {code}  You would then define a controller named index.js and you could automatically bind events inline in your controller code:  {code}  $.b.addEventListener("click",function(){      alert("You clicked the button");  });     // "$.index" is the default variable for a top-level container inside the index.xml  $.index.open();  {code}  So, we would need introspection on the items defined in the XML and display them appropriately in the content assist for the JS files
Answer: 221725.0

User story: "Right-click app/models folder  Pop up dialog box asking for model name, with a small table below for adding new values/types   {{alloy generate model <name> [column_name:type, ...]}}  For example:  {{alloy generate model todo name:string active:boolean}}  Add keyboard shortcut for opening dialog and generating widget (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard)  "
Answer: 45807.0

User story: "Right-click app/widgets folder  Pop up dialog box asking for widget name   {{alloy generate widget <name>}}  Add keyboard shortcut for opening dialog and generating widget (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard)  This will create a default widget in your projects's app/widgets path."
Answer: 44299.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Right-click app/migrations folder  Pop up dialog box asking for migration name   {{alloy generate migration <name>}}  Add keyboard shortcut for opening dialog and generating migration (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard)    This will create a timestamp-ordered migration file for the model specified."
Answer: 44305.0

User story: "Right-click app/controllers folder  Pop up dialog box asking for controller name   {{alloy generate controller <name>}}  Add keyboard shortcut for opening dialog and generating controller (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard)"
Answer: 44305.0

User story: "Right-click app/views folder  Pop up dialog box asking for view name   {{alloy generate view <name>}}  Add keyboard shortcut for opening dialog and generating view (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard)"
Answer: 35928.0

User story: "*.JMK file extension  "
Answer: 32658.0

User story: What is the alloy JSON style configuration custom file extension we need to associate with?  Does our JSOn parser/editor handle the non-standard "expression" syntax?
Answer: 161785.0

User story: Associate XML editor with "*.txml" files
Answer: 32696.0

User story: "This may not require any additional work. We may simply need to run the existing builder.py script as we do with typical Titanium projects. See here for confirmation: https://github.com/appcelerator/alloy"
Answer: 44678.0

User story: "It's currently unclear if the work needs to mostly be done on the Studio side or the SDK side. In general, we would need a source map to connect the generated source code with the original source code so that users could place breakpoints in the original JS files and have it break appropriately."
Answer: 161809.0

User story: "This may not require any additional work. We may simply need to run the existing builder.py script as we do with typical Titanium projects. See here for confirmation: https://github.com/appcelerator/alloy"
Answer: 44684.0

User story: Hide Resources folder  - Alloy generates the intermediate files there, most of the app lives in the "app" folder    Long-term:  - perhaps we root Alloy projects on the "app" folder, and choose an alternate presentation structure like Package Explorer.  - What additional folders do we need to hide?
Answer: 41337.0

User story: By default, a new Titanium project is an Alloy project. Select the "blank new alloy template" as the default in the titanium mobile project wizard. This creates an alloy project without any template.
Answer: 41326.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Creating a new "blank" alloy project is as follows:    - Run regular Titanium Mobile project creations (titanium/project.py scripts)  - Run 'alloy new path/to/project' to run the alloy generators  - Add Alloy project nature (in addition to the titanium mobile nature, web nature)    By default, a new Titanium project is an Alloy project    Note that an Alloy "template" likely would already have all the generated files, so we shouldn't need to do the script executions (running titanium scripts/alloy binary)
Answer: 50164.0

User story: "Need a new Alloy project nature to tag projects with (and with which we can hang new icons, etc, on)"
Answer: 31412.0

User story: "Need icons for Alloy project nature"
Answer: 31413.0

User story: "We move project template selection to the first screen in the project wizard (see Xcode for an example here)    This allows the user to focus on what they want to create (blank project, game, rss reader, master/detail, etc.). We then ask the user to fill in the name/location/etc later. (Basically swap the first and second page in most project wizards)."
Answer: 35886.0

User story: "The determination of whether or not this needs to be run under sudo may not be easy for us to determine. We may need to assume no need for sudo? If we do need to run under sudo we'll need to handle prompting for the sudo password and piping it along to the command.    {code}  [sudo] npm install -g alloy  {code}"
Answer: 50176.0

User story: "Instead of sending users through the Android UI, we instead download the components directly.    https://wiki.appcelerator.org/display/tools/Android+SDK+Installation    "
Answer: 632538.0

User story: "https://wiki.appcelerator.org/pages/viewpage.action?pageId=37522780    Currently, Studio involves a three-step installation:    # Install Titanium Studio  # Install required software (JDK, Node.js, Git)  # Configure platforms    The first two steps seem clumsy and should be collapsed. This requires the following:    # For windows, add JDK, git and Node.js checks and installs to the installer  # For Mac, create an installer, and add Node.js check/install. Alternatively, publish Studio as an App Store app (requires OpenJDK: http://intransitione.com/blog/take-java-to-app-store/)  # For Linux (Ubuntu), create a proper package with dependencies.    For the third step, how can we prompt the user which platforms they wish to develop for, and help them through the configuration? Examples:    * Android SDK pre-configuration  * Android NDK  * BlackBerry (VMWare Fusion, NDK)    This should be an extensible model that allows us to plug in new platforms in the future. Ideally, we should also not require it all to be part of some monolithic installer, and some of these things can be downloaded on demand as needed.    In 3.2.0, we will add JDK, git, and Node.js to Windows installer, and after the installation, we will prompt user which platforms they would like to setup and guide them through the process.  "
Answer: 691171.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We have the following issues open for ios and android to add debugging support for device  Enhancement request - Add Support for debugging on device    http://jira.appcelerator.org/browse/TIMOB-4626  http://jira.appcelerator.org/browse/TIMOB-4625    Once these are addressed studio would need to add UI to support the features.    This applies just to the iOS half of the equation. Note that this is considered much harder (and perhaps impossible) on iOS and on Android."
Answer: 48155.0

User story: "Dashboard > Develop > Templates > Create New Project still has a dropdown that allows the user to select a desktop project.    There should only be one button that only creates a titanium studio project."
Answer: 18727.0

User story: We need to remove the Titanium Desktop project wizard from the File > New menu, or being "promoted" in any other areas.
Answer: 1679.0

User story: "There is no visual/icon way to open the dashboard using the new simple perspective.    Steps to Reproduce:    1. Open Studio.    Actual Result:    No dashboard icon. If the dashboard is closed, you can only open it from Help > Titanium Studio > Show Dashboard.    Expected Result:    Dashboard icon should exist."
Answer: 7025.0

User story: "We need to add launch configurations for packaging mobile web modules. The steps to do so are:    Inside the generated module directory is the build.py. Simply run that and it'll generate a mymodule-mobileweb-0.1.zip file. During compilation, it will create a build directory. This directory can be nuked when doing a clean."
Answer: 7.0

User story: "The Titanium Studio dashboard shows two dollar signs next to module prices. See attached images."
Answer: 7146.0

User story: "# Remove Welcome page  # Replace with accordion. Initially open a section to configure TISTUD-1456  ## See APSTUD-4798 and APSTUD-4799 for actions to call  # Confirm the Titanium SDK is downloaded (continuously check the SDKLocator to see if it's configured)  # Run the browser configuration check to make sure Mobile Web is available (TISTUD-1414)  # Once that area is done, add button for users create a new project from a template (reuse existing system to create a project from a template)  ## Extend current action to provide callback returning the name of the project (APSTUD-4800)  ## Add button to call new action to run project created in above step (APSTUD-4801)    Once users have completed these items, the top part collapses, and the bottom half of the accordion appears, similar to what we have currently"
Answer: 54612.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: When filing a ticket in JIRA, we need to reconfigure the current fields ever so slightly.    Instead of a single "Steps to Reproduce" we need three fields:    * Steps to Reproduce*  * Actual Result*  * Expected Result    (*d fields are required)    From a space perspective, "Steps" should be 2X the height of the other two.    When the ticket is filed, replace any empty fields with "N/A", and use the following template:    {code}  h3. Steps to Reproduce  [Steps]    h3. Actual Result  [Actual]    h3. Expected Result  [Expected/N/A]  {code}
Answer: 18165.0

User story: "When filing a ticket inside Titanium Studio using the new JIRA integration (APSTUD-2916), we need to file the ticket in APSTUD if it came from Aptana Studio, and TC if it came from Titanium community"
Answer: 17793.0

User story: "Add the ability to create a javascript module (commonJS or MobileWeb, depending on implementation of MOD-701)."
Answer: 2765681.0

User story: "There is a growing demand for a pre-packaged install of Node.js to be shipped with Titanium Studio. We should detect if node.js is currently installed and if not, run latest node.js installer in our installer."
Answer: 782024.0

User story: "Right now studio has hard coded api.cloud.appcelerator.com, in order to test in staging environment, we need to be able to change it to point to api.staging.cloud.appcelerator.com instead"
Answer: 38473.0

User story: "At the moment, packaging a mobile modules on MacOSX requires an installation of the Command Line Tools through XCode in order to resolve dependency issues that are required by the build scripts (_make_ and _gperf_, at least).  Also, the packager script cannot handle spaced in the path to the project's build.xml file.    We need to improve this behavior, either by working something out on the Studio side, or by changing something on the platform side requirements."
Answer: 2772333.0

User story: "# Add the path to the simulator to the BlackBerry preference screen  # Update the sdk_info.json with links to the blackberry NDK download and simulator downloads (https://bdsc.webapps.blackberry.com/native/download)  # Upgrade the configuration code to look for those two preferences  # Upgrade the configuration UI (similar to iOS) to alert the user where and how to download them if they aren't set"
Answer: 596712.0

User story: "Similar to other platforms, support the creation of BlackBerry modules. We don't yet know exactly the steps involved.    "
Answer: 779751.0

User story: This incorporates the new configuration tab, allowing users to choose between a "simple" and "advanced" perspective.
Answer: 46532.0

User story: "Add a dashboard controller when given the URL to a module .zip file, installs the module to the SDK location on disk.    * Allow the user to choose either a global install, or a per-project install.  * If for a specific project, update the tiapp.xml file (equivalent to what we do now when packaging a module for local distribution)"
Answer: 31136.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This should contain the following:  Type - Story Reporter - <USER>Summary & Steps to reproduce - same texts as in the dialog Logs - both Studio and diagnostic logs attached Screenshots - a screenshot of this dialog"
Answer: 987.0

User story: "Found in Eric's log file. I though this was a duplicate of another ticket, but I can't find the first version.    {code}  !ENTRY com.aptana.git.core 4 0 2012-03-30 11:52:03.083  !MESSAGE (Build 3.0.0.1332346356) [ERROR] com.aptana.git.core/debug Unable to correctly parse git version 1.7.7.5 (Apple Git-26)  !STACK 0  java.lang.IllegalArgumentException: invalid qualifier: 5 (Apple Git-26)  at org.osgi.framework.Version.validate(Version.java:195)  at org.osgi.framework.Version.<init>(Version.java:161)  at org.osgi.framework.Version.parseVersion(Version.java:225)  at com.aptana.git.core.model.GitExecutable.version(GitExecutable.java:399)  at com.aptana.git.core.model.GitExecutable.clone(GitExecutable.java:431)  at com.aptana.git.ui.CloneJob.run(CloneJob.java:86)  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)  {code}"
Answer: 176.0

User story: "based on TISTUD-1539, we should fail the build if the Titanium Rubles fail to package. One suggested approach is to copy the plugin, unzip it and manually check for the bundles and fail if they're not there."
Answer: 12652.0

User story: "See link here for list of mobile web configuration options.    https://wiki.appcelerator.org/display/mobileweb/Mobile+Web+tiapp.xml+Options"
Answer: 2291006.0

User story: "As a way of keeping ourselves from accidentally releasing JDT into the wild as part of Studio, we need to fail the Aptana Studio and Titanium Studio builds if either the plugin or standalone versions come packaged with the JDT plugins. This prevents half-baked JDT installs which hen keep a user from later installing the whole JDT proper for module development."
Answer: 14309.0

User story: Currently, changes made to the console log level during a launch can cause the launch configuration log settings to be out of sync. I think this is very confusing for the end user. I propose the possibilities:    # Remove the Run Configuration log level setting (note: mobileweb does not have a log level setting in Run Configs).  # Pass "TRACE" as a log level to the SDK when launching  # Set the console view log level filter to trace by default.  # The console view log level remains at the same value as when last launched.  
Answer: 528478.0

User story: "For clarity, we should pass in the parameters we know about explicitly - Publish target, platform type, and output location. "
Answer: 178619.0

User story: The default version selected for Android is 'Android 2.2', while we probably want to set it to "Google APIs Android 2.2".
Answer: 3562.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "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.  "
Answer: 327824.0

User story: "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."
Answer: 3.0

User story: "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)."
Answer: 127339.0

User story: * 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.
Answer: 114081.0

User story: "Apart from giving us a newer code base, it appears this will give us substantial ability to customize the UI. Scheduling this for 2.2-2.3 timeframe based on Eclipse schedules.    More details here: http://www.eclipse.org/projects/project-plan.php?projectid=eclipse"
Answer: 576173.0