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: "At the moment Studio team is not ready to work on this yet. The new CLI work is expected to take several more weeks. This work should wait until then."
Answer: 2075319.0

User story: "This task might need to be broken into separate tasks later on once we have a closure on the visual design."
Answer: 9597.0

User story: "1) implement support for the live tile in the framework  2) work with Appcel architects to define new APIs  3) implement new APIs"
Answer: 2075343.0

User story: "1) add support for the control in the framework  2) work with Appcel architects to identify new APIs  3) implement new APIs"
Answer: 17339.0

User story: "At some point Anvil was broken on Windows. A hack was put in place to overcome this issue on Blackberry. Once a proper solution is in, the hack needs to be reverted.    Ask Opie for details. He knows what this is about."
Answer: 399924.0

User story: "Based on the new image attached to TIMOB-10886, update the default image for samples and templates."
Answer: 2789.0

User story: "Dimensions: 640x1136  Name: <EMAIL>    See parent ticket for current image"
Answer: 14.0

User story: "The iPhone 5 requires the addition of a new-sized splash screen:    * Dimensions: 640x1136  * Name: <EMAIL>    I've attached the previous version we can use for creating the larger size."
Answer: 2830.0

User story: "Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades):  https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE    Implement at least:    * Titanium.UI.TableView.addEventListener  * Titanium.UI.TableView.appendRow  * Titanium.UI.TableView.setData"
Answer: 219434.0

User story: "Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades):  https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE"
Answer: 275479.0

User story: "Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades):  https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE"
Answer: 275481.0

User story: "Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades):  https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE"
Answer: 275483.0

User story: "Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades):  https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE"
Answer: 259911.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: "Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades):  https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE    Implement at least:    * Titanium.UI.TextField.blur  * Titanium.UI.TextField.focus  * Titanium.UI.TextField.keyboardType"
Answer: 234225.0

User story: "Review the BlackBerry Button features and see what functionality is not yet implemented.  Try running KS Button samples to verify behavior."
Answer: 209763.0

User story: "Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades):  https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE    Add at least:    * Titanium.UI.ActivityIndicator.style (does not appear to be applicable in Cascades)"
Answer: 236123.0

User story: "Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades):  https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE"
Answer: 209363.0

User story: "h2. Problem  When you create a New | Titanium Mobile Project, <iphone> and <mobileweb> sections get added to the initial TiApp.xml file, even though the project is Android only (iPhone and Mobile Web were unchecked).    h2. Expected Behavior  No <iphone> or <mobileweb> sections should be added to the initial TiApp.xml file when creating a new Android-only project.    Likewise, no <android> or <mobileweb> sections should be added when creating an iPhone-only project.    h2. Actual Behavior  # Create a New | Titanium Mobile Project.  # Uncheck Mobile Web and iPhone.  # The resulting TiApp.xml file will have <iphone> and <mobileweb> sections in it.  "
Answer: 2532007.0

User story: "Implement at least:    * Titanium.UI.Label.opacity  * Titanium.UI.Label.touchEnabled  * Titanium.UI.Label.url"
Answer: 203533.0

User story: Any changes made to KitchenSink to run it with Blackberry should be merged into  the <USER>KitchenSink repository in a "blackberry" branch.
Answer: 4515.0

User story: We need to review any Blackberry specific documentation additions we need to merge into titanium_mobile.  Note ONLY changes in "apidoc" should be merged. A pull request with these changes should be created  and reviewed by the documentation team and an <USER>platform engineer.    NOTE: a new "blackberry" branch should be created. This shouldn't go into master until release.
Answer: 11534.0

User story: "The blackberry implementation needs to move into the new titanium_mobile_blackberry repository.  This repository will house the platform implementation and the build scripts (new CLI/node).  "
Answer: 10308.0

User story: "Update the version # of the master branch to 3.0"
Answer: 5804.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 run hook is responsible for opening the app in a web browser.    Optionally, it can start an HTTP server to host the files. The HTTP server must support static file sharing. It can listen on any non-privileged port and would shutdown when the build command finished.    When no browser is specified, then it will use the system default. We should support all installed desktop browsers as well as Android and iOS. For Android, there would be a {{--device-id}} of the emulator/device to open the browser on. iOS Simulator may not be possible. iOS device should be possible once the node-ios-device module add support for opening URLs."
Answer: 2533145.0

User story: "It is required for the codestrong demo to run on the tablet simulator."
Answer: 21209.0

User story: "Create TextField. Try to set Value or get value during some action (for example button click event).  for getValue() -  undefined is returned.  for setValue() - doesn't set the textfield value.    "
Answer: 7022.0

User story: "We should add the ability to add annotations for the code processor in code similar to how JSHint interprets /*global foo*/    There are a few key features we need to support:  * Whether or not the file should be evaluated in ambiguous mode if it's not processed  ** If it should be evaluated as a require or a Ti.include  ** Conditionals (e.g. should only be evaluated if on Android)  * Perhaps add hints for values being passed in to delayed functions (e.g. event handlers)  * Ability to suppress warnings"
Answer: 2100056.0

User story: The attached wireframe is a rough concept. There will be an updated wireframe provided by Susan later in the week.    - when the page is open for the first time, the charges table is empty  - the user uses the left panel to enter charge information; all fields are simple text fields without special logic or formatting  - tap "Add to Report" button to add the charge as a table entry in the report  - there is no sorting in the report table, all new charges are added at the top of the table  - the report table should be a simple table, taking up the whole right panel width, there is no need in alternating background (I didn't bother redoing style in the wireframe)  - expense report title is specified by typing it in the text field at the top of the right section
Answer: 28585.0

User story: "Now that TIMOB-10372 has been agreed upon, this needs to be put in place to support proper and consistent bubbling of events."
Answer: 211482.0

User story: "Go over API doc and transfer all implementation information into this table:  https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE#gid=0    For each API element we need to mark whether it was implemented or not."
Answer: 13501.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: "With the advent of applyProperties, the value of applyLayout lessens. For several reasons, the promise of delayed/batched UI had never reached fruition. There may be ways to do this more elegantly, to re-approach this situation.    In the mean time, it is suggested that we deprecate for 2.1.2 and remove the dead code afterwards."
Answer: 27283.0

User story: "We have a bunch of classes that are deprecated and should be removed.  We have avoided doing this in the past since it will break older modules like https://jira.<USER>org/browse/TIMOB-10404.  If we bump the module_apiversion, we should also remember to remove these deprecated classes as well.      Some examples:    org.<USER>titanium.util.Log  org.<USER>titanium.util.TiConfig"
Answer: 2537574.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 TIMOB-3749 scaling behavior of imageViews was changed. If either width or height of image view are set to follow SIZE behavior('auto',Ti.UI.SIZE,undefined) then the image is scaled with aspect ratio intact. Otherwise the image is scaled ignoring aspect ratio. Test code below  {code}  var win = Ti.UI.createWindow({      backgroundColor:'#fff',      layout:'vertical'  });     var image = Ti.UI.createImageView({       image: "http://www.catravelservices.com/management/hotels/pictures/Mawamba_lodge_nature.jpg",       backgroundColor : "red"   });        var label = Ti.UI.createLabel({      text:'Results Here'  })     var updateLabel = function(){      var size = image.size;      label.text = 'ImageView size is '+size.width+'x'+size.height;  }     var controlsContainer = Ti.UI.createView({      height:Ti.UI.SIZE  })     var widthControls = Ti.UI.createView({      width:'50%',      layout:'vertical',      left:0,      height:Ti.UI.SIZE  })     var heightControls = Ti.UI.createView({      width:'50%',      layout:'vertical',      right:0,      height:Ti.UI.SIZE  })     controlsContainer.add(widthControls);  controlsContainer.add(heightControls);     var b1 = Ti.UI.createButton({title:'WIDTH=SIZE'})  var b2 = Ti.UI.createButton({title:'WIDTH=165'})  var b3 = Ti.UI.createButton({title:'WIDTH=250'})  var b4 = Ti.UI.createButton({title:'HEIGHT=SIZE'})  var b5 = Ti.UI.createButton({title:'HEIGHT=50'})  var b6 = Ti.UI.createButton({title:'HEIGHT=165'})  b1.addEventListener('click',function(e){      image.width=Ti.UI.SIZE;      setTimeout(updateLabel,500);  })  b2.addEventListener('click',function(e){      image.width=165;      setTimeout(updateLabel,500);  })  b3.addEventListener('click',function(e){      image.width=250;      setTimeout(updateLabel,500);  })  b4.addEventListener('click',function(e){      image.height=Ti.UI.SIZE;      setTimeout(updateLabel,500);  })  b5.addEventListener('click',function(e){      image.height=50;      setTimeout(updateLabel,500);  })  b6.addEventListener('click',function(e){      image.height=165;      setTimeout(updateLabel,500);  })  win.add(image);  widthControls.add(b1);  widthControls.add(b2);  widthControls.add(b3);  heightControls.add(b4);  heightControls.add(b5);  heightControls.add(b6);  win.add(controlsContainer);  win.add(label)  win.open();  {code}
Answer: 450298.0

User story: "Accessing table view sections from a table view is currently limited to the data property which resets the entire table. This makes it extremely expensive to, say, add a new section to an already existing table. It has also given rise to poorly thought out API designs such as the 'header' property of TableViewRows.    We need to add methods for accessing and manipulating TableViewSections in a TableView akin to how we can access TableViewRows from a TableView.    We also need to document and deprecate the previously undocumented 'header' property."
Answer: 30334.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: "Accessing table view sections from a table view is currently limited to the data property which resets the entire table. This makes it extremely expensive to, say, add a new section to an already existing table. It has also given rise to poorly thought out API designs such as the 'header' property of TableViewRows.    We need to add methods for accessing and manipulating TableViewSections in a TableView akin to how we can access TableViewRows from a TableView.    We also need to document and deprecate the previously undocumented 'header' property."
Answer: 52045.0

User story: "Accessing table view sections from a table view is currently limited to the data property which resets the entire table. This makes it extremely expensive to, say, add a new section to an already existing table. It has also given rise to poorly thought out API designs such as the 'header' property of TableViewRows.    We need to add methods for accessing and manipulating TableViewSections in a TableView akin to how we can access TableViewRows from a TableView.    We also need to document and deprecate the previously undocumented 'header' property."
Answer: 3737.0

User story: "Accessing table view sections from a table view is currently limited to the data property which resets the entire table. This makes it extremely expensive to, say, add a new section to an already existing table. It has also given rise to poorly thought out API designs such as the 'header' property of TableViewRows.    We need to add methods for accessing and manipulating TableViewSections in a TableView akin to how we can access TableViewRows from a TableView.    We also need to document and deprecate the previously undocumented 'header' property."
Answer: 36544.0

User story: "Unmbrella task to link to all the bug and issue of the current framework that prevent easy extension of the api using js.    Will also need to be figured out: inheritance between native objects and js objects"
Answer: 458854.0

User story: On Android and iOS, the default unit can be overriden on a per-application level by setting the ti.ui.defaultunit property in tiapp.xml. For example, to use DIPs as the default on all platforms, set defaultunit to dip:    <property name="ti.ui.defaultunit" type="string">dip</property>    The value for ti.ui.defaultunit can be any of the unit specifiers defined above, or system to specify that the platform's default unit should be used.
Answer: 1417476.0

User story: This activity should be done at the "feature complete" stage of the project
Answer: 460618.0

User story: "Implement at least:    * Titanium.Network.httpURLFormatter  * Titanium.Network.networkType  * Titanium.Network.online  * Titanium.Network.registerForPushNotifications"
Answer: 321669.0

User story: "Implement:    getHeight  getWidth  getBottom  setBottom  getRight  setRight  getSize  setSize"
Answer: 9395.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: "Complete UI View methods / properties / events NOT required by Kitchen Sink    Add at least:    * Titanium.UI.View.animate  * Titanium.UI.View.append  * Titanium.UI.View.backgroundGradient  * Titanium.UI.View.borderColor  * Titanium.UI.View.borderRadius  * Titanium.UI.View.borderWidth  * Titanium.UI.View.control  * Titanium.UI.View.currentIndex  * Titanium.UI.View.currentY  * Titanium.UI.View.fireEvent  * Titanium.UI.View.id  * Titanium.UI.View.layout  * Titanium.UI.View.on  * Titanium.UI.View.refreshRssTable  * Titanium.UI.View.reset  * Titanium.UI.View.scrollView  * Titanium.UI.View.showArticle  * Titanium.UI.View.shuffle  * Titanium.UI.View.state  * Titanium.UI.View.titleId  * Titanium.UI.View.toggle  * Titanium.UI.View.toImage  * Titanium.UI.View.touchEnabled  * Titanium.UI.View.updateHandheldNav  * Titanium.UI.View.updateSubNav  * Titanium.UI.View.videoId    "
Answer: 321866.0

User story: "This umbrella task is to address functional delta in controls that were previously implemented using R4 release of Cascades. It could either mean implementing new functionality now available in R6, or redoing something that no longer works or was implemented as a workaround.    Refer to the implementation matrix to see what elements need to be implemented"
Answer: 61973.0

User story: "IOStream is the interface that all stream types implement.  Methods: 5  Sub Classes: 4"
Answer: 23288.0

User story: "Need to go over KS elements and grey out everything that is not implemented.  Make sure that this logic is Blackberry-specific so that things are not greyed-out on other platforms."
Answer: 41047.0

User story: "See TIMOB-10079 for details."
Answer: 369400.0

User story: "Depends on Cascades R6    An alert dialog is a modal view that includes an optional title, a message and buttons, positioned in the middle of the display.    In iOS:  https://developer.apple.com/library/ios/#documentation/UIKit/Reference/UIAlertView_Class/UIAlertView/UIAlertView.html"
Answer: 29956.0

User story: "port xml, ui layout and util test suites to anvil and add configs for both V8 and Rhino"
Answer: 9482.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: Like we do at create time where we can pass in an object representing properties, it would be helpful to have the same functionality available at runtime through an API like a applyProperties setter or getter or applyProperties({}) method. In Alloy we will dynamically set properties it would help performance if we could call a method to bulk set properties.    For example win1 = createWindow({    backgroundColor:'#336699',    borderWidth:8,    borderColor:'#999',    height:400,    width:300,    borderRadius:10,    opacity:0.92,})     currently is being done and the properties are being passed. A developer would like to have a way at runtime to change properties in a bulk for example win1.applyProperties({     backgroundColor:'#336699',     borderWidth:8,     borderColor:'#999',     height:400,     width:300,     borderRadius:10,     opacity:0.92,  });     Benefits  - code speed, and reduced code size    Edit: In discussion, the word styles were dropped because 1) some properties are not logically part of a style and 2) we wanted to avoid confusion given how complex and interacting styles can be.    Note that this is different than applyLayout because this is to be done at the proxy level (IE, you can do this to sounds, to HTTPClient, etc) and does not delay or apply other logic like applyLayout does. Instead, foo.applyProperties({bar:5, baz:"bat"}) is identical to foo.bar=5; foo.baz="bat"; but is more compact and more importantly, reduces bridge traversal.
Answer: 42234.0

User story: "Allow adding events with unknown names.  Add a generic way of firing those custom events."
Answer: 287322.0

User story: "To get this to work in KS, we need TIMOB-9879 and whatever else to fix the click event for TableView, but the Tab.open and setWindow can still be implemented separately.    Take a look at android/modules/ui/src/js/tab.js for .open(), but currently we can't use the bootstrapping to extend the API because we create different objects instead of using the prototype."
Answer: 2543.0

User story: "Implement 'remove' method for removing child controls from a container."
Answer: 2939.0

User story: Currently, when we throw an exception while a file is being loaded by include or require, both files are shown in the message (eg "file1.js line 2: file2.js line 5: Missing argument").  We need to make changes so the following is true:  # the exception has the [ERROR] tag  # only the filename containing the actual error is shown  ** might need to get rid of some TryCatch's  ** might need to use Message::GetScriptResourceName  # the filename shows the full path (minus the .../assets/)  # an exception thrown from an event handler shows the filename and crashes the app (eg calling Ti.API.debug() with no params in a button handler)    Also need to clean/split up TiRootObject::executeScript and implement Ti.API.log in .js.
Answer: 505859.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: Currently, include()'s method of doing relative files only works if all done in successive order. It does not work for windows with a url (not implemented) or if include is used in a function of a file in a subdir.  Also, require() does not have any method right now.    My proposal is to store the filepath in each TiObject so it can be retrieved later when needed.    Also, we need to make sure that require() properly handles a "native Titanium module" by its ID (eg com.example.module).
Answer: 322075.0

User story: "Need to create snapshots of all UI elements that need designing and document some guidelines for each.    The UI elements include:    * Ti.UI.MapView (Annotation only)  * Ti.UI.ActivityIndicator  * Ti.UI.AlertDialog  * Ti.UI.Button  * Ti.UI.MobileWeb.NavigationGroup  * Ti.UI.OptionDialog  * Ti.UI.Picker  * Ti.UI.PickerColumn  * Ti.UI.PickerRow  * Ti.UI.ProgressBar  * Ti.UI.ScrollableView  * Ti.UI.SearchBar  * Ti.UI.Slider  * Ti.UI.Switch  * Ti.UI.Tab  * Ti.UI.TableViewSection  * Ti.UI.Textarea  * Ti.UI.TextField    Optionally there are scrollbars.  "
Answer: 49006.0

User story: "Need to see if we can find a tool to analyze memory usage for any memory leaks. So far what we detected was done manually through code review."
Answer: 493746.0

User story: "Android API's need to be updated to post 2.2 support.  IOS needs to research new features that have been introduced in IOS6 and make sure we are IOS6 compatible    Estimate is combined for all platforms."
Answer: 379225.0

User story: "This task is a holder for all bug scrubs that will be done by developers during the current quarter."
Answer: 116969.0

User story: "FB SDK needs to be updated across all mobile platforms"
Answer: 18869.0

User story: "Need to make a sweep of all functions that receive a param of type Arguments and add parameter validation.    At the very least the length of the Arguments list needs to be validated before accessing items to avoid crashes.  Additionally the type of the args can be validated where appropriate.    One known such occurence is TiUITableView::_scrollToIndex "
Answer: 499378.0

User story: Needs to implement the "minispec" for require() that was decided on by core:    # Conform to commonjs spec: http://wiki.commonjs.org/wiki/Modules/1.1  -> Testing to be https://github.com/commonjs/commonjs/tree/master/tests/modules  # non-MW platforms throw an exception when confronted with async syntax  -> {{ require(["foo"], callbackFunction); }}    There is also the possibility of:  # Leading '/' not allowed in module names  # Leading '/' always indicates a resource at the root of the project    This should be done for all platforms.
Answer: 3120426.0

User story: " When building release for device, minimize the js code and encode it for obscurity"
Answer: 2465781.0

User story: "When building for devices, the js code is to be parsed to determine the necessary modules and only compile those in."
Answer: 375011.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: "Ti module other than the core ones (API, UI, Analytics and possibly App, Filesystem and Gesture) need to be loaded only when needed by the js code"
Answer: 380575.0

User story: "Implement require()"
Answer: 12134.0

User story: "Our Titanium Android module projects are Android library projects (from Eclipse's perspective) containing AndroidManifest.xml files that currently are still pointing to api level 7 (which we don't support).  Same with the project.properties files.  These files need to be updated to api level 8 (our minimum supported)"
Answer: 143.0

User story: "This is a tracking ticket basically for general refactor work, documentation and feature addition that was not able to be included before code freeze for 2.1 release.    test case for this ticket is kinda generic given how new Anvil is and the wide scope of these changes.  Testing should really just be running Anvil with a custom config set (refer to README) for all 3 platforms."
Answer: 12928.0

User story: "- Implement platform specific file in anvil/driver/platforms (closest match likely to be android.js)  - minor updates to anvil/driver/driver.js to add BB as a known platform  - select a socket port for BB in anvil/driver/config.js created from a copy of exampleConfig.js  - Identify necessary Ti API calls needed for the harness app and implement them  - Figure out the communication between driver and harness"
Answer: 101284.0

User story: "We recently fixed an issue in Titanium Studio with JS Lint running slowly by upgrading to the latest version of Rhino.    Based on the release notes for 1.7R4, there seem to be performance improvements over the last release. It appears that the 1.7R4 release happened after Titanium Mobile last upgraded.    https://developer.mozilla.org/en/New_in_Rhino_1.7R4"
Answer: 275236.0

User story: "The current default duration and minimum animation time for imageviews is inconsistent on all platforms.     For parity, make all platform follow the same default duration and min animation interval.    *Default Duration: 200ms  *Minimum Duration: 30ms      "
Answer: 48576.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: Currently the two streams (continuous integration and release) have different formats:    Release:  {code}  {     "success":true,     "releases":[        {           "build_type":"64bit_i386",           "name":"mobilesdk",           "guid":"05645B49-C629-4D8F-93AF-F1CF83200E34",           "version":"1.7.5",           "os":"linux",           "url":"http:\/\/api.<USER>net\/p\/v1\/release-download?token=G4tzN4F4",           "checksum":"140dc9865cd538b03224199d28d80f31",           "children":null        },  {code}    Continuous integration:  {code}  [     {        "sha1":"eac32bde4c914aded595a655fd7bcab7978a3617",        "build_url":"http://ec2-184-72-158-179.compute-1.amazonaws.com/hudson/job/titanium_mobile_master/331/",        "git_revision":"bd12917d2bd83d555608c28049855b29a0defc6f",        "filename":"mobilesdk-1.6.0-20110126185552-osx.zip",        "git_branch":"master",        "build_type":"mobile",        "size":58530276     },  {code}    Converting the continuous integration stream to the same format as release will allow us to provide it as an option to download in the "Install Titanium SDK from URL" feature/
Answer: 2194799.0

User story: The current polynomial algorithm can be improved.     Each layout calculates its own set of coefficients, but it is possible to merge the calculation into a single algorithm. To do this, we need to create a set of intermediate properties. For example, left is context dependent in the Titanium API, but if we split left into _left and _paddingLeft (determined by the layout), then _left is no longer context dependent and the coefficients can be calculated by a single algorithm, thus saving a ton of code space.    The layout algorithm sometimes needs to defer the calculation of a nodes position until more information is obtained from other nodes. We should categorized these types of defers into "pass queues". Instead of determining this information dynamically at layout time, this can be determined statically at coefficient calculation time. By removing all of the conditionals in the layout algorithm, performance will be increased.
Answer: 2556685.0

User story: "Revisit the behaviour of the cascades formats for dates and time in R6.  Adjust the output in the formatDate/Time methods to match that of other platforms"
Answer: 542345.0

User story: "calling toString() on an object created by the Ti framework fails.  We think that the property enumeration doesn't enumerate the inherited properties.  "
Answer: 68737.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: "Modules that only support specific chip sets such as i386 and armv7 have no way of specifying this in the build stream causing customers and module developers to modify the python build scripts to use the module    https://github.com/aoberoi/Opentok-Titanium/blob/master/README.md    As the device penetration for armv6 is quite low at this point, we will be removing armv6 support.    Dropping armv6 in conjunction with no longer claiming support for Mac OS 10.6.x results in the following:    * Minimum Xcode version: 4.3  ** Also supported 4.4 and 4.5 - soon 4.6  ** Since we don't support Snow leopard (10.6.8), you can't run:  *** Xcode 4.1 - otherwise possible, they dropped support for pre 4.3 builds (which require armv6)   *** Xcode 4.2 – The last to support Snow leopard  * Minimum iOS SDK for compile: 5.1  ** 5.1 – Shipped with Xcode 4.3 has no support for armv6 by default  * Minimum Mac OS – 10.7  ** Xcode determine this, if you have Xcode 4.3.3+ (If I remember correctly), you need Mac OS 10.7.4 or better to run  * Minimum target device iOS version: 4.3    As a note, when you submit without armv6 you must set the minimum iOS version to 4.3 or higher or Apple will reject the application."
Answer: 343556.0

User story: "Use the implementation matrix to see what's remaining: https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE  Implement at least:  * Titanium.UI.Window.modal (sheets/dialogs in Cascades?) * Titanium.UI.Window.setKeepScreenOn"
Answer: 395504.0

User story: "Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades):  https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE    Add at least:    * Titanium.UI.TabGroup.enabled  * Titanium.UI.TabGroup.touchEnabled"
Answer: 395240.0

User story: "Review current BlackBerry functionality and open tickets for any missing features.  Try testing the KS Tab/TabGroup samples to verify behavior."
Answer: 404066.0

User story: "For each module (see sub-tasks):  1) Discuss with RIM to identify what unimplemented elements are going to be supported in the future  2) Discuss with <USER>what remaining elements require custom implementation"
Answer: 337487.0

User story: "The customer is requesting the ability to capture content from a webcam, upstream it to a server and then downstream it to the app.  This feature will be used for videochating so the performance should be real time.  The request is for both iOS and Android"
Answer: 552164.0

User story: "Scrolling scrollable views doesn't work on WP7.5 because it doesn't support the events necessary to do dragging and it doesn't support animation. In this case, we should add buttons to the scrollable view that a user can tap to go forwards and backwards.    We should consider making a new top-level API for managing these buttons."
Answer: 2567840.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: "Implement build support for the new CLI. This will be replacing the current Python implementation.    Review https://wiki.<USER>org/display/CLI/Adding+a+Platform+to+the+CLI for information on how to do the switch (work in progress)."
Answer: 429901.0

User story: "Part of this task need to clean left and top properties from inherited classes that don't need to override the default implementation.  One such occurence is in NativeListViewObject"
Answer: 78141.0

User story: "building for simulator should only build the debug version, currently it builds both debug and release.  Same likely goes when building for the device.    This may require changing the Makefile to one like is used for tibb and add the needed targets."
Answer: 541188.0

User story: "Currently the when packaging with scons, files starting with '.' are added to the zip when they should not.    All files starting with '.' should be ignored"
Answer: 541223.0

User story: "things like the following don't currently work in V8:    var v = new String('bla bla'); // v is undefined after executing that line    var i = parseInt('5');         // TypeError: parseInt not a member of #error      These are just 2 examples, many more likely have the same behavior.    "
Answer: 21148.0

User story: Ti.UI docs mentions the following:    "Optimizations  UI objects are optimized by Titanium to not be realized into the drawing context and placed into the device UI surface until needed. That means that you can create UI objects, set their properties and add them to their hierarchy without much worry about memory or performance.  When the native drawing surface needs to render a specific view or control, Titanium will automatically create the view as needed. Additionally, Titanium is optimized to also release memory once the view is no longer needed, on screen or in low memory situations. However, it's a good idea to help Titanium along in certain cases where you are no longer using objects. For example, you should call close on a Window instance when you are no longer using it. You can safely call open on the window again to re-open it."      Profiling should be realized to verify if any modifications are necessary to align with this documented behavior.
Answer: 607964.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: "[Tatyana] A note to myself: this task is a necessary step to be able to deploy an app to a device.    This could be added to the devicemanagement.py script.    {noformat}  blackberry/devicemanagement.py createDebugToken --store-pass <password> --csj-pin <csj-pin> --csj-file <csj-file> (--device-pin <device-pin> | --device-pin-list <device-pin-list>) --debug-token-bar-file <debug-token-bar-file> --device <device> --device-password <password>    <password>             password for keystore and device  <csj-pin>              PIN associated with CSJ file  <csj-file>             input CSJ file for registration  <device-pin>           device PIN in hex without the '0x' (e.g. 50F2D211)  <device-pin-list>      file containing a list of device PINs  <debug-token-bar-file> debug token file  <device>               hostname or the IP address of the target device or simulator  {noformat}    This is an example of what the script should do:  {noformat}  blackberry-debugtokenrequest -register -storepass 123456 -csjpin 729759 client-RDK-584232624.csj client-PBDT-584232624.csj  blackberry-debugtokenrequest -storepass 123456 -devicepin 29AFDEBD dt.bar  blackberry-deploy -installDebugToken dt.bar 169.254.0.1 -password 1234  {noformat}"
Answer: 1502492.0

User story: "Cleanup the existing TODO's in the scripts?"
Answer: 426603.0

User story: "The argparse module was introduced in python 2.7 but we need to support 2.6 so we need to use optparse instead. It's fairly similar except it doesn't support sub-parsers."
Answer: 19899.0

User story: "Need to add a universal logger to the framework.  May use exceptions and stop the app in debug mode and only log in release mode.    Also go over all existing qDebug and printf to update them to use the new logger.    The logger will also need to do some locking to ensure that logging from concurrent threads doesn't result in logs cut and merged in the middle."
Answer: 43391.0

User story: "Error messages during runtime are, in most cases, not returning a readable message. A centralized string table should be created with properly formatted messages to help users with debugging."
Answer: 32951.0

User story: "The current state of Android animation APIs and its limitations/bugs needs a review to address various animation issues."
Answer: 622105.0

User story: "NativeObject classes should be grouped into a single sub-directory to separate target platform from Titanium runtime."
Answer: 435561.0

User story: "Add event handler embedded class for each native controllers, which will be responsible for handling QT cascade events."
Answer: 8921.0

User story: "Updating API doc is now part of the patch cycle.  However, some components added in the past have not been reflected in API doc:  - ImageView  - TextField  - ActivityIndicator (maybe, check it out)    This task is to add past work to the API doc."
Answer: 11747.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: "Currently the Titanium runtime haults JS execution prints information to the stdout during an exception and then the Cascades message loop is entered. This should be changed to shutdown the app and return an error code.    Pull request: https://github.com/Macadamian/titanium_mobile/pull/66  "
Answer: 12815.0

User story: "For now used native DropDown component for OptionDialog. In future when modal dialog will be supported by cascades, we need to switch to something more similar thing for OptionDialog, as already in Android and iPhone."
Answer: 576820.0

User story: "We need to be able to support ti.verify on javascript (commonJS and MobileWeb) modules. This is a requirement for some of the enterprise-related modules that we are developing. In addition, module developers would like to put their javascript modules on the MarketPlace with ti.verify being used to confirm authorization to use the module."
Answer: 14176.0

User story: "An analysis was performed, and checking for the possibility malloc producing a NULL value is not being done. In the majority of cases, these allocations are small constant sizes (such as the size of an internet address structure) and do not need checks (The iOS watchdog would be shutting things down long beforehand). However, I did note a few places where such checks may be of use:    * AsyncUdpSocket.m uses a DEFAULT_MAX_RECEIVE_BUFFER_SIZE of 9KB.  * AudioStreamer relies on getting a value from iOS for the size of the buffer to allocate.  * NSData * decode64 (NSData * thedata) may be dealing with base64 encodings of binary blobs in the multi-kilobytes.  * -\[TiDataStream writeToStream:chunkSize:callback:\] and -\[TiDataStream pumpToCallback:chunkSize:synch:\] does not check the sign or value of size before using it in a malloc, nor does its subclass TiFilesystemStreamProxy.  * TiNetworkTCPSocketProxy uses a bufferSize of 4KB.  * TiUIWebView and UtilsModule, when preparing to Base64Encode, do not check the malloc caused by an estimated encoded data size."
Answer: 5886.0

User story: "the bar-descriptor file needs to be updated everytime we package to pick up potential changes to the tiapp.xml file"
Answer: 56016.0

User story: "Create working harness manager sub component that allows for multiplatform expansion and built in CLI.  Should be able to generate harness for Android, install, launch and get test results back.  Base harness should be able to run test suites and return results to harness manager subcomponent over tcp server.    Communication with hub, mw integration, iOS integration and test creation is not included in the scope of this task."
Answer: 6679.0

User story: "- remove extra libs from common.mk  - adjust paths to R4 ndk for default detection in blackberryndk.py  - And other things that might not work"
Answer: 8080.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 is for control of the devices physical LED.  And looking at the 2.0 API it would be the equivalent to:    - Titanium.Android.Notification.ledARGB  - Titanium.Android.Notification.ledOffMS  - Titanium.Android.Notification.ledOnMS"
Answer: 1531301.0

User story: "Should be available after R6 release in early July."
Answer: 652847.0

User story: "Currently the unit tests create a temp project folder in the temp folder, but the default location on Windows XP (or if the user changed it) contains spaces. For some reason python receives this in 8.3 format (eg C:\DOCUME~1\<username>\LOCALS~1\Temp and there doesn't seem to be a built-in python way to expand the string to detect spaces. The build fails when there are spaces so this should be fixed.  Note: the default temp folder on Windows 7 (and probably Vista) is fine: C:\Users\<username>\AppData\Local\Temp"
Answer: 448648.0

User story: "As per our discussion, QE needs a list of everything that will be included in the coming 2.0.2 drop. Please indicate if any files are platform specific."
Answer: 26002.0

User story: "Could be done by using a tibbversion.h file that defines externs for the following:  - Titanium SDK version  - timestamp  - git hash    Also, need to replace the defines in tibbversion.h when packaging in site_scons/package.py"
Answer: 575512.0

User story: "Create prototype of Anvil sub components for single developer Anvil test run based on spec."
Answer: 13068.0

User story: Android platform displays a number of error and warning messages that are not very helpful and are confusing to a number of developers. For example, "[WARN] [object TiUILabel] has an auto width value of 0, meaning this view may not be visible."     We need to evaluate all the external errors and warning messages -  1. Remove unnecessary messages. Every message should serve a specific purpose and provide meaningful information.  2. Make sure that these messages have consistent language style. Documentation team should review these messages.
Answer: 133901.0

User story: iOS platform displays a number of error and warning messages that are not very helpful and are confusing to a number of developers. For example, "[WARN] [object TiUILabel] has an auto width value of 0, meaning this view may not be visible."     We need to evaluate all the external errors and warning messages -  1. Remove unnecessary messages. Every message should serve a specific purpose and provide meaningful information.  2. Make sure that these messages have consistent language style. Documentation team should review these messages.
Answer: 35037.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: "See pull request: #18      1. void TiUIBase::setTiMappingProperties(const TI_PROPERTY* prop, int propertyCount)  prop should be props since it's a pointer to an array of prop objects    --    2. TiUIBase::setParametersFromObject(Local obj)        Local propValue;  +    Handle propString;  +    TiObject* foundProp;    3 last lines,  It's cleaner to declare variables inside the smallest scope they are to be used in and also helps prevent referencing them outside of their scope. In this case the declarations should be inside the for    --    3. int NativeContainerObject::initialize()  add protection agains multiple invocations    --    4. if((args.Length()!=2)||(!args[0]->IsString())||(!args[1]->IsFunction()))  This line is definitely worth a comment. How come args[0] needs to be a string and args[1] needs to be a function? reminds me of perl :S    --    5. blackberry/tibb/TiUIObject.cpp  •   createXXXX_ methods  out of 14 lines of code in the functions, only 1 really differs. It'd be nice to have a way of abstrating that to remove code duplication which would be a maintenance nightmare as i also forsee many many such functions being created for all the UI controls we need to implement    Similarly the associtated classes look very bare and very much alike, is there actual value in having all these look alike classes? Maybe the actual question is can we avoid them?    --    6. VALUE_MODIFY TiPropertyMapObject::onValueChange(Handle oldValue, Handle newValue)  the 3 lines inside the the ifs are the same in all cases, they should be rolled into a helper function.    --    7. we should review the logical separation of classes with regards to cascades awareness, separation into folders    --    8. review error handling strategy  - run it by <USER>   --    9. class TiEventContainer  please add spaces around the = sign for consistency with the rest of the code. The formatter doesn't enforce it here.    There is at least another instance of that in TiEvent.h    --    10. blackberry/tibb/TiUIBase.h  description comment references TiCascadesApp when it should be TiUIBase    --    11. embed class TiInternalEventListener inside TiV8EventContainer? To reenforce it's internalness"
Answer: 80420.0

User story: Currently tibbtest is used for demos and testing. It should be productized by renaming it to "tibbapp" and robustness must be added. Currently the bootstrap JavaScript gets truncated to 4k.
Answer: 467248.0

User story: "Work with studio to know how to get the build issues to be captured inside the Problems window in Studio"
Answer: 595875.0

User story: "Add building of libtibb.ca in the scons script and package it properly in the resulting zip file, also remove any unnecessary files from the zip"
Answer: 32925.0

User story: "Once familiarized with the project, write a testing strategy. A concise Confluence page should be sufficient."
Answer: 128036.0