@maccesar/titools 4.4.0 → 4.4.2

package/skills/ti-api/references/api-ui-extras.md

@@ -24,21 +24,13 @@
 > Extends Ti.Proxy
 > Platforms: both
 
-An animation object describes the properties of an animation. At its most basic, an animation
-object represents a single-phase animation with an end state and a duration.
+An animation object describes the properties of an animation. At its most basic, an animation object represents a single-phase animation with an end state and a duration.
 
-When [animate](Titanium.UI.View.animate) is called on a [View](Titanium.UI.View), the view is
-animated from its current state to the state described by the animation object. The properties
-that can be animated include the view's position, size, colors, transformation matrix and opacity.
+When [animate](Titanium.UI.View.animate) is called on a [View](Titanium.UI.View), the view is animated from its current state to the state described by the animation object. The properties that can be animated include the view's position, size, colors, transformation matrix and opacity.
 
-You can also specify an animation curve or *easing function* to control the pace of the
-animation. To use an easing function, set the animation's `curve` property to one of the
-`ANIMATION_CURVE` constants defined in <Titanium.UI>. For example,
-[ANIMATION_CURVE_EASE_IN](Titanium.UI.ANIMATION_CURVE_EASE_IN) specifies an animation that
-starts slowly and then speeds up.
+You can also specify an animation curve or *easing function* to control the pace of the animation. To use an easing function, set the animation's `curve` property to one of the `ANIMATION_CURVE` constants defined in <Titanium.UI>. For example, [ANIMATION_CURVE_EASE_IN](Titanium.UI.ANIMATION_CURVE_EASE_IN) specifies an animation that starts slowly and then speeds up.
 
-Animations can be set to reverse themselves automatically on completion, and to repeat a given
-number of times. For more complicated effects, multiple animations can be combined in sequence,
+Animations can be set to reverse themselves automatically on completion, and to repeat a given number of times. For more complicated effects, multiple animations can be combined in sequence,
 
 *(See full overview in titanium-docs)*
 
@@ -100,8 +92,7 @@ number of times. For more complicated effects, multiple animations can be combin
 > Extends Ti.Proxy
 > Platforms: both
 
-A 2D matrix is used to rotate, scale, translate, or skew the objects in a two-dimensional space.
-A 2D affine transformation can be  represented by a 3 by 3 matrix:
+A 2D matrix is used to rotate, scale, translate, or skew the objects in a two-dimensional space. A 2D affine transformation can be  represented by a 3 by 3 matrix:
 
 ### Properties (unique: 6/9)
 | Property | Type | Default | Platform | Description |
@@ -131,12 +122,9 @@ A 2D affine transformation can be  represented by a 3 by 3 matrix:
 > Extends Ti.Proxy
 > Platforms: ios
 
-The 3D Matrix is created by <Titanium.UI.createMatrix3D>. A 3D transform is
-used to rotate, scale, translate, or skew the objects in three-dimensional
-space. A 3D transform  is represented by a 4 by 4 matrix.
+The 3D Matrix is created by <Titanium.UI.createMatrix3D>. A 3D transform is used to rotate, scale, translate, or skew the objects in three-dimensional space. A 3D transform  is represented by a 4 by 4 matrix.
 
-You create an `identity matrix` by creating a 3D Matrix with an empty
-constructor.
+You create an `identity matrix` by creating a 3D Matrix with an empty constructor.
 
 ### Properties (unique: 16/18)
 | Property | Type | Default | Platform | Description |
@@ -178,16 +166,13 @@ constructor.
 
 Use the <Titanium.UI.createWebView> method or **`<WebView>`** Alloy element to create a web view.
 
-Web views are more expensive to create than other native views because of the requirement to
-load the HTML browser into memory.
+Web views are more expensive to create than other native views because of the requirement to load the HTML browser into memory.
 
-The web view content can be any valid web content such as HTML, PDF, SVG or other WebKit supported
-content types.
+The web view content can be any valid web content such as HTML, PDF, SVG or other WebKit supported content types.
 
 ### JavaScript Context in WebViews--Local vs. Remote Content
 
-JavaScript in the web view executes in its own context.  The web view can interact with this
-content, but most of this functionality is limited to local content.
+JavaScript in the web view executes in its own context.  The web view can interact with this content, but most of this functionality is limited to local content.
 
 **Local Scripts**
 
@@ -326,19 +311,14 @@ content, but most of this functionality is limited to local content.
 
 A `Toolbar` is created by the <Titanium.UI.createToolbar> factory method or **`<Toolbar>`** Alloy element.
 
-To provide spacing between items in the toolbar, on iOS you can use the special system button types,
-[FIXED_SPACE](Titanium.UI.iOS.SystemButton.FIXED_SPACE) and
-[FLEXIBLE_SPACE](Titanium.UI.iOS.SystemButton.FLEXIBLE_SPACE).
+To provide spacing between items in the toolbar, on iOS you can use the special system button types, [FIXED_SPACE](Titanium.UI.iOS.SystemButton.FIXED_SPACE) and [FLEXIBLE_SPACE](Titanium.UI.iOS.SystemButton.FLEXIBLE_SPACE).
 
-Note that toolbars are positioned like other views (using the `top` and `bottom` properties,
-for example), but the [iOS Human Interface Guidelines](https://developer.apple.com/ios/human-interface-guidelines/overview/themes/#//apple_ref/doc/uid/TP40006556-CH12-SW4)
-have specific requirements for placing toolbars, specifically:
+Note that toolbars are positioned like other views (using the `top` and `bottom` properties, for example), but the [iOS Human Interface Guidelines](https://developer.apple.com/ios/human-interface-guidelines/overview/themes/#//apple_ref/doc/uid/TP40006556-CH12-SW4) have specific requirements for placing toolbars, specifically:
 
 * On the iPhone and Android, a toolbar should be at the bottom of the window.
 * On the iPad, a toolbar should appear at the top or bottom of a window.
 
-Due to an iOS limitation, the buttons in the toolbar only support the `click` event.
-The native object underlying a toolbar button does not generate standard view events,
+Due to an iOS limitation, the buttons in the toolbar only support the `click` event. The native object underlying a toolbar button does not generate standard view events,
 
 *(See full overview in titanium-docs)*
 
@@ -393,15 +373,11 @@ The native object underlying a toolbar button does not generate standard view ev
 | ------- | --- |
 | ![Android](./buttonbar_android.png) |  |
 
-The button bar is a set of buttons joined into a single control.
-On iOS, you can set up the buttons with either a title or image, but not both.
-On Android, you can set up the buttons with a title, image, or both.
+The button bar is a set of buttons joined into a single control. On iOS, you can set up the buttons with either a title or image, but not both. On Android, you can set up the buttons with a title, image, or both.
 
 Use the <Titanium.UI.createButtonBar> method or **`<ButtonBar>`** Alloy element to create a button bar.
 
-The [TabbedBar](Titanium.UI.iOS.TabbedBar) control is a button bar where the
-last selected button maintains a pressed or selected state. The following discussion
-applies to both button bar and tabbed bar.
+The [TabbedBar](Titanium.UI.iOS.TabbedBar) control is a button bar where the last selected button maintains a pressed or selected state. The following discussion applies to both button bar and tabbed bar.
 
 ### Properties (unique: 5/76)
 | Property | Type | Default | Platform | Description |
@@ -426,11 +402,7 @@ applies to both button bar and tabbed bar.
 > Extends Ti.UI.View
 > Platforms: both
 
-A tabbed bar is a button bar that
-maintains a state (visually distinguished as a pressed or selected look).
-It is closely related to the `ButtonBar` control. See the description of
-[ButtonBar](Titanium.UI.ButtonBar) for information on styling tabbed bars and buttons
-bars.
+A tabbed bar is a button bar that maintains a state (visually distinguished as a pressed or selected look). It is closely related to the `ButtonBar` control. See the description of [ButtonBar](Titanium.UI.ButtonBar) for information on styling tabbed bars and buttons bars.
 
 Use the <Titanium.UI.createTabbedBar> method to create a Tabbed Bar.
 
@@ -465,11 +437,9 @@ Use the <Titanium.UI.createTabbedBar> method to create a Tabbed Bar.
 
 This is a view which shows a list of options where only 1 option is selectable by the user.
 
-On iOS, this displays a
-[segmented control](https://developer.apple.com/design/human-interface-guidelines/ios/controls/segmented-controls/).
+On iOS, this displays a [segmented control](https://developer.apple.com/design/human-interface-guidelines/ios/controls/segmented-controls/).
 
-On Android, this displays a
-[toggle button group](https://material.io/components/buttons/android#toggle-button).
+On Android, this displays a [toggle button group](https://material.io/components/buttons/android#toggle-button).
 
 Use the <Titanium.UI.createOptionBar> method to create a Option Bar.
 
@@ -498,11 +468,9 @@ Use the <Titanium.UI.createOptionBar> method to create a Option Bar.
 > Extends Ti.Proxy
 > Platforms: both
 
-Allows the creation of application shortcuts, which can be detected using
-the `click` event from <Titanium.UI.Shortcut>.
+Allows the creation of application shortcuts, which can be detected using the `click` event from <Titanium.UI.Shortcut>.
 
-On iOS, shortcuts are only supported on a 3D Touch compatible device.
-Use the <Titanium.UI.iOS.forceTouchSupported> property to see if it's supported.
+On iOS, shortcuts are only supported on a 3D Touch compatible device. Use the <Titanium.UI.iOS.forceTouchSupported> property to see if it's supported.
 
 ### Properties (unique: 2/5)
 | Property | Type | Default | Platform | Description |
@@ -531,15 +499,12 @@ Use the <Titanium.UI.iOS.forceTouchSupported> property to see if it's supported.
 > Extends Ti.Proxy
 > Platforms: both
 
-Allows the creation of dynamic application shortcut items which can be set in the app to 
-offer a dynamic behavior at runtime.
+Allows the creation of dynamic application shortcut items which can be set in the app to offer a dynamic behavior at runtime.
 
-Use the <Titanium.UI.createShortcutItem> method to create a shortcut item and pass it to
-the <Titanium.UI.Shortcut.add> method to add it to the application.
+Use the <Titanium.UI.createShortcutItem> method to create a shortcut item and pass it to the <Titanium.UI.Shortcut.add> method to add it to the application.
 
 ### Android Static Shortcuts
-Google documents how to add static shortcuts
-[here](https://developer.android.com/guide/topics/ui/shortcuts/creating-shortcuts#static).
+Google documents how to add static shortcuts [here](https://developer.android.com/guide/topics/ui/shortcuts/creating-shortcuts#static).
 
 In the `tiapp.xml` file, you will need to add a shortcuts `<meta-data/>` element to your main activity.
 
@@ -573,9 +538,7 @@ In the `tiapp.xml` file, you will need to add a shortcuts `<meta-data/>` element
 | ------- | --- |
 | ![Android](./emaildialog_android.png) | ![iOS](./emaildialog_ios.png) |
 
-The Email Dialog is created with the <Titanium.UI.createEmailDialog> method. The user needs to
-register an e-mail account on the device in order to open the dialog.  The dialog will not
-open when there is not a registered e-mail account.
+The Email Dialog is created with the <Titanium.UI.createEmailDialog> method. The user needs to register an e-mail account on the device in order to open the dialog.  The dialog will not open when there is not a registered e-mail account.
 
 **iOS Platform Notes**
 
@@ -624,20 +587,13 @@ On iOS, you cannot test the e-mail dialog on the iOS Simulator. Test the email d
 > Extends Ti.UI.View
 > Platforms: ios
 
-The DashboardView is created using the <Titanium.UI.createDashboardView> method or **`<DashboardView>`** 
-Alloy element.
+The DashboardView is created using the <Titanium.UI.createDashboardView> method or **`<DashboardView>`** Alloy element.
 
-Dashboard view's edit mode may be activated by a longpress of a <Titanium.UI.DashboardItem> item, 
-unless this behavior has been disabled by the [editable](Titanium.UI.DashboardView.editable) 
-property. As a dashboard view does not inherently provide a way to exit edit mode, this must be 
-explicitly defined.
+Dashboard view's edit mode may be activated by a longpress of a <Titanium.UI.DashboardItem> item, unless this behavior has been disabled by the [editable](Titanium.UI.DashboardView.editable) property. As a dashboard view does not inherently provide a way to exit edit mode, this must be explicitly defined.
 
-When edit mode has been activated, the item icons wobble by default to act as a visual cue. 
-This behavior may be disabled using the [wobble](Titanium.UI.DashboardView.wobble) property.
+When edit mode has been activated, the item icons wobble by default to act as a visual cue. This behavior may be disabled using the [wobble](Titanium.UI.DashboardView.wobble) property.
 
-If a dashboard contains more than 9 items, it will be paged into screens in a 3 x 3 formation 
-using its built-in scrollable view. A paging control is added to the bottom of the view to 
-indicate the active page.
+If a dashboard contains more than 9 items, it will be paged into screens in a 3 x 3 formation using its built-in scrollable view. A paging control is added to the bottom of the view to indicate the active page.
 
 
 *(See full overview in titanium-docs)*

package/skills/ti-api/references/api-ui-lists.md

@@ -25,9 +25,7 @@
 
 Use the <Titanium.UI.createListView> method or **`<ListView>`** Alloy element to create a `ListView`.
 
-A `ListView` object is a container for [ListSection](Titanium.UI.ListSection)
-objects that are, in turn, containers for [ListItem](Titanium.UI.ListItem) objects. This is
-easily visualized as an Alloy view:
+A `ListView` object is a container for [ListSection](Titanium.UI.ListSection) objects that are, in turn, containers for [ListItem](Titanium.UI.ListItem) objects. This is easily visualized as an Alloy view:
 
 
 ### Properties (unique: 54/122)
@@ -157,16 +155,11 @@ easily visualized as an Alloy view:
 > Extends Ti.Proxy
 > Platforms: both
 
-A list item is a combination of a <ListDataItem> and <ItemTemplate>.  The list data item
-represents the actual data, while the item template represents the style elements of the item.
+A list item is a combination of a <ListDataItem> and <ItemTemplate>.  The list data item represents the actual data, while the item template represents the style elements of the item.
 
-You should not create `ListItem` objects with a JavaScript factory method, as you do other Titanium proxies.
-Instead, you should pass a <ListDataItem> array to the `setItems` method of a `ListSection`. The list data items
-contain the data you want to display in the list.
+You should not create `ListItem` objects with a JavaScript factory method, as you do other Titanium proxies. Instead, you should pass a <ListDataItem> array to the `setItems` method of a `ListSection`. The list data items contain the data you want to display in the list.
 
-Alloy applications can use **`<ListItem>`** elements to create `ListItem` objects. `<ListItem>` elements
-must be nested inside a **`<ListSection>`** element, which itself is nested in a `<ListView>` element,
-as shown below:
+Alloy applications can use **`<ListItem>`** elements to create `ListItem` objects. `<ListItem>` elements must be nested inside a **`<ListSection>`** element, which itself is nested in a `<ListView>` element, as shown below:
 
 
 ### Properties (unique: 26/28)
@@ -238,8 +231,7 @@ as shown below:
 
 Use the <Titanium.UI.createListSection> method or **`<ListSection>`** Alloy element to create a `ListSection`.
 
-List sections are used to manipulate and organize list items contained within it. For examples 
-of using list sections, see the examples in <Titanium.UI.ListView> and <Titanium.UI.ListItem>.
+List sections are used to manipulate and organize list items contained within it. For examples of using list sections, see the examples in <Titanium.UI.ListView> and <Titanium.UI.ListItem>.
 
 ### Properties (unique: 7/9)
 | Property | Type | Default | Platform | Description |
@@ -308,8 +300,7 @@ of using list sections, see the examples in <Titanium.UI.ListView> and <Titanium
 | ------- | --- |
 | ![Android](./tableview_android.png) | ![iOS](./tableview_ios.png) |
 
-A `TableView` object is a container for [TableViewSection](Titanium.UI.TableViewSection)
-objects that are, in turn, containers for [TableViewRow](Titanium.UI.TableViewRow) objects.
+A `TableView` object is a container for [TableViewSection](Titanium.UI.TableViewSection) objects that are, in turn, containers for [TableViewRow](Titanium.UI.TableViewRow) objects.
 
 Use the <Titanium.UI.createTableView> method or **`<TableView>`** Alloy element to create a `TableView`.
 
@@ -460,20 +451,15 @@ There are few approaches to creating and using `TableView` object.
 > Extends Ti.UI.View
 > Platforms: both
 
-Use the <Titanium.UI.createTableViewRow> method or **`<TableViewRow>`** Alloy element to create
-a table view row.
+Use the <Titanium.UI.createTableViewRow> method or **`<TableViewRow>`** Alloy element to create a table view row.
 
-These may be explicitly added to [TableViewSection](Titanium.UI.TableViewSection) objects, which are applied
-to a [TableView](Titanium.UI.TableView). If a table section is not specified, one will be
-automatically created.
+These may be explicitly added to [TableViewSection](Titanium.UI.TableViewSection) objects, which are applied to a [TableView](Titanium.UI.TableView). If a table section is not specified, one will be automatically created.
 
-A row's contents can be as simple as a single line of text, or comprised of a completely
-customized layout of child views.
+A row's contents can be as simple as a single line of text, or comprised of a completely customized layout of child views.
 
 ### Creating Table View Rows
 
-Rows may be created using the properties directly available on the `TableViewRow` object, to
-achieve the following:
+Rows may be created using the properties directly available on the `TableViewRow` object, to achieve the following:
 
 
 *(See full overview in titanium-docs)*
@@ -539,20 +525,13 @@ achieve the following:
 > Extends Ti.Proxy
 > Platforms: both
 
-Use the <Titanium.UI.createTableViewSection> method or **`<TableViewSection>`** Alloy element to 
-create a `TableViewSection`.
+Use the <Titanium.UI.createTableViewSection> method or **`<TableViewSection>`** Alloy element to create a `TableViewSection`.
 
-Before the table is rendered, the `TableViewSection` [add](Titanium.UI.TableViewSection.add) 
-method may be used to add [TableViewRow](Titanium.UI.TableViewRow) objects to a section. After 
-it is rendered, one of the `TableView` [insertRowBefore](Titanium.UI.TableView.insertRowBefore), 
-[insertRowAfter](Titanium.UI.TableView.insertRowAfter), or 
-[appendRow](Titanium.UI.TableView.appendRow) methods must be used instead. 
+Before the table is rendered, the `TableViewSection` [add](Titanium.UI.TableViewSection.add) method may be used to add [TableViewRow](Titanium.UI.TableViewRow) objects to a section. After it is rendered, one of the `TableView` [insertRowBefore](Titanium.UI.TableView.insertRowBefore), [insertRowAfter](Titanium.UI.TableView.insertRowAfter), or [appendRow](Titanium.UI.TableView.appendRow) methods must be used instead.
 
-To remove a row from a section after the table is rendered, use the `TableView` 
-[deleteRow](Titanium.UI.TableView.deleteRow) method. 
+To remove a row from a section after the table is rendered, use the `TableView` [deleteRow](Titanium.UI.TableView.deleteRow) method.
 
-In order for a section to be visible, either its `headerTitle` or `headerView` property must be 
-configured. 
+In order for a section to be visible, either its `headerTitle` or `headerView` property must be configured.
 
 
 *(See full overview in titanium-docs)*

package/skills/ti-api/references/api-ui-text-input.md

@@ -28,8 +28,7 @@ Use the <Titanium.UI.createTextField> method or **`<TextField>`** Alloy element
 
 ### `click` event in iOS
 
-In iOS 11+, `click` event in text field is not fired due to changes from apple.
-Use `touchstart` event instead of `click` event.
+In iOS 11+, `click` event in text field is not fired due to changes from apple. Use `touchstart` event instead of `click` event.
 
 ### Properties (unique: 45/116)
 | Property | Type | Default | Platform | Description |
@@ -144,8 +143,7 @@ Use the <Titanium.UI.createTextArea> method or **&lt;TextArea&gt;** Alloy elemen
 
 ### `click` event in iOS
 
-In iOS 11+, `click` event in text area is not fired due to changes from apple.
-Use `touchstart` event instead of `click` event.
+In iOS 11+, `click` event in text area is not fired due to changes from apple. Use `touchstart` event instead of `click` event.
 
 ### Properties (unique: 40/111)
 | Property | Type | Default | Platform | Description |
@@ -252,10 +250,7 @@ Use `touchstart` event instead of `click` event.
 | ------- | --- |
 | ![Android](./searchbar_android.png) | ![iOS](./searchbar_ios.png) |
 
-Search bars are most commonly used for filtering the rows in a [TableView](Titanium.UI.TableView) and
-[ListView](Titanium.UI.ListView). You can add a search bar to a table view via its
-[search](Titanium.UI.TableView.search) property. You can add a search bar to a list view via its
-[searchBar](Titanium.UI.SearchBar) property.
+Search bars are most commonly used for filtering the rows in a [TableView](Titanium.UI.TableView) and [ListView](Titanium.UI.ListView). You can add a search bar to a table view via its [search](Titanium.UI.TableView.search) property. You can add a search bar to a list view via its [searchBar](Titanium.UI.SearchBar) property.
 
 A search bar can also be used on its own.
 
@@ -340,11 +335,9 @@ Use the <Titanium.UI.createSearchBar> method or Alloy **`<SearchBar>`** element
 
 The AttributedString proxy is created with the <Titanium.UI.createAttributedString> method.
 
-The `text` property must be set initially in the constructor when creating an attributed string.
-The [attributes](Titanium.UI.AttributedString.attributes) can either be set in the constructor or after it has been created.
+The `text` property must be set initially in the constructor when creating an attributed string. The [attributes](Titanium.UI.AttributedString.attributes) can either be set in the constructor or after it has been created.
 
-For examples of Attributed Strings, see the
-[Attributed Strings guide](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/User_Interface_Deep_Dives/Attributed_Strings.html).
+For examples of Attributed Strings, see the [Attributed Strings guide](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/User_Interface_Deep_Dives/Attributed_Strings.html).
 
 ### Properties (unique: 2/5)
 | Property | Type | Default | Platform | Description |
@@ -377,9 +370,7 @@ For examples of Attributed Strings, see the
 > Extends Ti.Proxy
 > Platforms: both
 
-This type may be used on iOS for assignment to any property typically taking a String color value.
-A developer is not expected to typically interact with a <Titanium.UI.Color> object, as we generate them
-under the hood when converting the passed in String representations. One major exception is use of the
+This type may be used on iOS for assignment to any property typically taking a String color value. A developer is not expected to typically interact with a <Titanium.UI.Color> object, as we generate them under the hood when converting the passed in String representations. One major exception is use of the
 
 
 ### Methods (1)
@@ -396,18 +387,11 @@ under the hood when converting the passed in String representations. One major e
 > Platforms: both
 > Type: module
 
-The Clipboard is a temporary data store, used to save a single item of data that may then
-be accessed by the user using UI copy and paste interactions within an app or between apps.
+The Clipboard is a temporary data store, used to save a single item of data that may then be accessed by the user using UI copy and paste interactions within an app or between apps.
 
-On iOS, the module's `setData()` and `getData()` methods enable multiple representations of the
-same data item to be stored together with their respective
-[MIME type](http://en.wikipedia.org/wiki/Internet_media_type) to describe their format. For
-example, `'text'` and `'text/plain'` for text, and `'image/jpg'` and `'image/png'` for an image.
-iOS Will report back the type of data representation in `getItems()` as 
-[Universal Type Identifiers](https://developer.apple.com/library/archive/documentation/Miscellaneous/Reference/UTIRef/Articles/System-DeclaredUniformTypeIdentifiers.html).
+On iOS, the module's `setData()` and `getData()` methods enable multiple representations of the same data item to be stored together with their respective [MIME type](http://en.wikipedia.org/wiki/Internet_media_type) to describe their format. For example, `'text'` and `'text/plain'` for text, and `'image/jpg'` and `'image/png'` for an image. iOS Will report back the type of data representation in `getItems()` as [Universal Type Identifiers](https://developer.apple.com/library/archive/documentation/Miscellaneous/Reference/UTIRef/Articles/System-DeclaredUniformTypeIdentifiers.html).
 
-When working with text, either of the `getData()`/`setData()` methods may be used with a `'text/plain'` type, or
-the `getText()`/`hasText()`/`setText()` methods without the need to specify the type.
+When working with text, either of the `getData()`/`setData()` methods may be used with a `'text/plain'` type, or the `getText()`/`hasText()`/`setText()` methods without the need to specify the type.
 
 Android currently only supports text data to be stored.
 
@@ -464,15 +448,9 @@ Android currently only supports text data to be stored.
 
 Use the <Titanium.UI.createPicker> method or Alloy **`<Picker>`** element to create a picker control.
 
-On Android, the `useSpinner` property must be enabled to support multiple columns.
-By default, the spinner is automatically sized to fit its content and can overflow
-to additional spinner rows. The size of the picker can be adjusted with the `width`
-and `height` properties, but may omit picker columns or cut off picker rows
-if the size is set too small. This property is deprecated. Please use the default
-Android native "dropdown" style by not setting `useSpinner` to `true`.
+On Android, the `useSpinner` property must be enabled to support multiple columns. By default, the spinner is automatically sized to fit its content and can overflow to additional spinner rows. The size of the picker can be adjusted with the `width` and `height` properties, but may omit picker columns or cut off picker rows if the size is set too small. This property is deprecated. Please use the default Android native "dropdown" style by not setting `useSpinner` to `true`.
 
-On iOS, the `height` property is only available in iOS 9 and later.
-By default, the size of the picker, including its background, is fixed at the
+On iOS, the `height` property is only available in iOS 9 and later. By default, the size of the picker, including its background, is fixed at the
 
 *(See full overview in titanium-docs)*
 
@@ -542,9 +520,7 @@ By default, the size of the picker, including its background, is fixed at the
 > Extends Ti.UI.View
 > Platforms: both
 
-Use the <Titanium.UI.createPickerColumn> method to create a picker column control. In an Alloy application,
-you can use a **`<PickerColumn>`** element inside a `<Picker>` element. You can also use `<Column>`
-as a shorthand for `<PickerColumn>` (see Examples).
+Use the <Titanium.UI.createPickerColumn> method to create a picker column control. In an Alloy application, you can use a **`<PickerColumn>`** element inside a `<Picker>` element. You can also use `<Column>` as a shorthand for `<PickerColumn>` (see Examples).
 
 On Android, the `useSpinner` property must be enabled to support multiple columns.
 
@@ -585,9 +561,7 @@ See <Titanium.UI.Picker> for further examples of usage.
 > Extends Ti.UI.View
 > Platforms: both
 
-Use the <Titanium.UI.createPickerRow> method to create a picker row control. In an Alloy application,
-you can use a **`<PickerRow>`** element inside a `<PickerColumn>` element. You can also use `<Row>`
-as a shorthand for `<PickerRow>` (see Examples).
+Use the <Titanium.UI.createPickerRow> method to create a picker row control. In an Alloy application, you can use a **`<PickerRow>`** element inside a `<PickerColumn>` element. You can also use `<Row>` as a shorthand for `<PickerRow>` (see Examples).
 
 Views added to picker rows is only supported on iOS.
 

package/skills/ti-api/references/api-ui-windows-navigation.md

@@ -20,13 +20,9 @@
 
 To create a window, use the <Titanium.UI.createWindow> method or a **`<Window>`** Alloy element.
 
-A window is a top-level container which can contain other views. Windows can
-be *opened* and *closed*.  Opening a window causes the window and its child
-views to be added to the application's render stack, on top of any previously opened
-windows. Closing a window removes the window and its children from the render stack.
+A window is a top-level container which can contain other views. Windows can be *opened* and *closed*.  Opening a window causes the window and its child views to be added to the application's render stack, on top of any previously opened windows. Closing a window removes the window and its children from the render stack.
 
-Windows *contain* other views, but in general they are not *contained* inside
-other views. There are a few specialized views that manage windows:
+Windows *contain* other views, but in general they are not *contained* inside other views. There are a few specialized views that manage windows:
 
 * [NavigationWindow](Titanium.UI.NavigationWindow)
 * [SplitWindow](Titanium.UI.iOS.SplitWindow)
@@ -202,13 +198,9 @@ This applies to Windows inside both standalone NavigationWindow and TabGroup (wh
 > Extends Ti.UI.Window
 > Platforms: both
 
-You create a `NavigationWindow` with the <Titanium.UI.createNavigationWindow> factory method or
-a `<NavigationWindow>` Alloy element.
+You create a `NavigationWindow` with the <Titanium.UI.createNavigationWindow> factory method or a `<NavigationWindow>` Alloy element.
 
-All `NavigationWindow` objects must have at least one root window that cannot be removed. When
-creating a `NavigationWindow` with the factory method, you must set its `window` property to the
-root level window. Equivalently, in an Alloy application, insert a `<Window>` element as a child of the
-`<NavigationWindow>` element. See examples below.
+All `NavigationWindow` objects must have at least one root window that cannot be removed. When creating a `NavigationWindow` with the factory method, you must set its `window` property to the root level window. Equivalently, in an Alloy application, insert a `<Window>` element as a child of the `<NavigationWindow>` element. See examples below.
 
 This object is not meant to be added to other windows. However, it can be used within a <Titanium.UI.iOS.SplitWindow>.
 
@@ -250,14 +242,11 @@ This object is not meant to be added to other windows. However, it can be used w
 | ------- | --- |
 | ![Android](./tabgroup_android.png) |  |
 
-A tab group can contain one or more [Tab](Titanium.UI.Tab) objects, each of which has an
-associated tab control that is used to bring it into focus.
+A tab group can contain one or more [Tab](Titanium.UI.Tab) objects, each of which has an associated tab control that is used to bring it into focus.
 
-Use the <Titanium.UI.createTabGroup> method or **`<TabGroup>`** Alloy element to create a tab group
-that, in turn, contains one or more `<Tab>` elements.
+Use the <Titanium.UI.createTabGroup> method or **`<TabGroup>`** Alloy element to create a tab group that, in turn, contains one or more `<Tab>` elements.
 
-You can add tabs to the group using [addTab](Titanium.UI.TabGroup.addTab), and programmatically
-switch to a specific tab using [setActiveTab](Titanium.UI.TabGroup.setActiveTab).
+You can add tabs to the group using [addTab](Titanium.UI.TabGroup.addTab), and programmatically switch to a specific tab using [setActiveTab](Titanium.UI.TabGroup.setActiveTab).
 
 ### Platform Implementation Notes
 
@@ -392,21 +381,17 @@ switch to a specific tab using [setActiveTab](Titanium.UI.TabGroup.setActiveTab)
 > Extends Ti.UI.View
 > Platforms: both
 
-A `TabGroup` tab instance. Each tab includes a button and one or more windows, which
-holds the "contents" of the tab. Users can select a tab by clicking on the tab button.
+A `TabGroup` tab instance. Each tab includes a button and one or more windows, which holds the "contents" of the tab. Users can select a tab by clicking on the tab button.
 
 Use the <Titanium.UI.createTab> method or **`<Tab>`** Alloy element to create a tab.
 
-Use [TabGroup.setActiveTab](Titanium.UI.TabGroup.setActiveTab) to switch between tabs
-in a tab group.
+Use [TabGroup.setActiveTab](Titanium.UI.TabGroup.setActiveTab) to switch between tabs in a tab group.
 
-The behavior of tabs and tab groups follows the platform's native navigation style,
-which varies significantly between platforms.
+The behavior of tabs and tab groups follows the platform's native navigation style, which varies significantly between platforms.
 
 ### iOS Platform Implementation Notes
 
-On iOS, the tab maintains a stack of windows. Windows on top
-of the stack can partially or totally obscure windows lower in the stack.  Calling
+On iOS, the tab maintains a stack of windows. Windows on top of the stack can partially or totally obscure windows lower in the stack.  Calling
 
 *(See full overview in titanium-docs)*
 
@@ -502,15 +487,11 @@ of the stack can partially or totally obscure windows lower in the stack.  Calli
 
 An alert dialog is created using <Titanium.UI.createAlertDialog> or **`<AlertDialog>`** Alloy element.
 
-Although this dialog always appears in the middle of the display (not touching the edges),
-other aspects of its aesthetics and the way the user interacts with it are different for each
-platform, as described below.
+Although this dialog always appears in the middle of the display (not touching the edges), other aspects of its aesthetics and the way the user interacts with it are different for each platform, as described below.
 
 ### Android
 
-On Android, the default alert dialog displays text information, via a title and message, without
-any buttons. As the user can use the system hardware `back` button to dismiss it, a button is
-optional.
+On Android, the default alert dialog displays text information, via a title and message, without any buttons. As the user can use the system hardware `back` button to dismiss it, a button is optional.
 
 *(See full overview in titanium-docs)*
 
@@ -586,16 +567,13 @@ optional.
 | ------- | ------ | ---- |
 | ![Android](./optiondialog_android.png) | ![iPhone](./optiondialog_iphone.png) | ![iPad](./optiondialog_ipad.png) |
 
-An option dialog is created using <Titanium.UI.createOptionDialog> or Alloy `<OptionDialog>`
-element. See Examples below for usage.
+An option dialog is created using <Titanium.UI.createOptionDialog> or Alloy `<OptionDialog>` element. See Examples below for usage.
 
 This dialog is presented differently on each platform, as described below.
 
 ### Android
 
-On Android, the dialog is shown in the middle of the display (not touching the edges),
-with the option items represented in a picker. The previously-selected, or default, item can be
-set on creation.
+On Android, the dialog is shown in the middle of the display (not touching the edges), with the option items represented in a picker. The previously-selected, or default, item can be set on creation.
 
 
 *(See full overview in titanium-docs)*
@@ -659,13 +637,9 @@ set on creation.
 | ------- | --- |
 | ![Android](./toast_android.png) |  |
 
-A toast notification is an unobtrusive, pop-up notification that does not
-block the UI. Use the <Titanium.UI.createNotification> method or **`<Notification>`** Alloy element
-to create a Toast notification.
+A toast notification is an unobtrusive, pop-up notification that does not block the UI. Use the <Titanium.UI.createNotification> method or **`<Notification>`** Alloy element to create a Toast notification.
 
-On Android, by default, a toast notification appears centered on the bottom half of the screen.
-On Windows Phone, by default, a toast notification appears over the status bar on the top part
-of the screen.
+On Android, by default, a toast notification appears centered on the bottom half of the screen. On Windows Phone, by default, a toast notification appears over the status bar on the top part of the screen.
 
 ### Properties (unique: 7/10)
 | Property | Type | Default | Platform | Description |