@maccesar/titools 4.3.0 → 4.4.2

package/README.md

@@ -2,9 +2,7 @@
 
 <div align="center">
 
-![npm](https://img.shields.io/npm/dm/@maccesar%2Ftitools)
-![npm](https://img.shields.io/npm/v/@maccesar%2Ftitools)
-![NPM](https://img.shields.io/npm/l/@maccesar%2Ftitools)
+![npm](https://img.shields.io/npm/dm/@maccesar%2Ftitools) ![npm](https://img.shields.io/npm/v/@maccesar%2Ftitools) ![NPM](https://img.shields.io/npm/l/@maccesar%2Ftitools)
 
 </div>
 
@@ -95,9 +93,7 @@ Why NPM?
 | **Slash commands**  | `/ti-check`, `/ti-new-screen`, `/ti-audit` | Same three (`~/.claude/commands/`) |
 | **Session hook**    | Auto-detects Titanium projects             | Auto-update only          |
 
-Having both installed is fine: the CLI detects an enabled marketplace plugin and skips
-its own skill symlinks and command copies, so nothing shows up twice. `titools doctor`
-reports which channel is serving Claude Code.
+Having both installed is fine: the CLI detects an enabled marketplace plugin and skips its own skill symlinks and command copies, so nothing shows up twice. `titools doctor` reports which channel is serving Claude Code.
 
 Use **Option A** if you only use Claude Code. Use **Option B** if you use multiple AI assistants or want the Knowledge Index feature.
 
@@ -238,10 +234,7 @@ Key difference:
 
 ## Slash Commands (Claude Code)
 
-TiTools provides slash commands for common tasks. Both channels ship them: the
-plugin serves them from its own cache, and `titools install` copies them into
-`~/.claude/commands/`. If you have both, the CLI detects the plugin and skips its
-own copy so the command does not appear twice in the autocomplete.
+TiTools provides slash commands for common tasks. Both channels ship them: the plugin serves them from its own cache, and `titools install` copies them into `~/.claude/commands/`. If you have both, the CLI detects the plugin and skips its own copy so the command does not appear twice in the autocomplete.
 
 | Command                 | Description                                                                         |
 | ----------------------- | ----------------------------------------------------------------------------------- |
@@ -333,6 +326,12 @@ When it activates:
 - Choosing data strategies (Models vs Collections)
 - Writing clean ES6+ code
 - Memory management and cleanup patterns
+- Choosing a feedback surface (Snackbar, Dialog, Bottom Sheet) and deciding what stays native
+- Designing reusable Alloy Widgets and their lifecycle contracts
+- Adaptive layouts for tablets, foldables, and large screens
+- Associating a custom file type with the app so tapping a document opens it
+- Sharing a link or a file out through the iOS share sheet or the Android intent chooser
+- Theming and dark mode
 - Performance optimization
 - Security patterns
 - Migrating legacy apps
@@ -343,13 +342,17 @@ Example prompts:
 "Create a user service that fetches data from an API."
 "What's the best pattern for navigation between screens?"
 "Prevent memory leaks in my controllers."
+"Every confirmation in my app is an alertDialog — what should each one actually be?"
+"Should this be a Widget or just a <Require>?"
+"Tapping my .backup file in iOS Files previews it instead of opening my app."
+"My Share button works on Android but does nothing on iOS, with no error."
 "Migrate classic Titanium code to modern Alloy patterns."
 "What's a clean way to organize services in an Alloy app?"
 ```
 
 Key features:
 - Quick decision matrix for common questions
-- 21 reference guides for deep dives
+- 26 reference guides for deep dives
 - Delegates to specialized skills when needed
 
 ---
@@ -718,7 +721,7 @@ This pattern is documented across three TiTools skills: `ti-ui`, `ti-expert`, an
 
 | Skill     | SKILL.md                      | References                                            |
 | --------- | ----------------------------- | ----------------------------------------------------- |
-| ti-expert | Architecture + Implementation | 21 files (patterns, testing, security, etc.)          |
+| ti-expert | Architecture + Implementation | 26 files (patterns, feedback surfaces, file type association, sharing, testing, security, etc.) |
 | purgetss  | Setup + Critical Rules        | 33 files (grid, animations, icons, class-index, SVG pipeline, etc.) |
 | ti-ui     | UI Rules + Platform Diffs     | 14 files (layouts, lists, gestures, etc.)             |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maccesar/titools",
-  "version": "4.3.0",
+  "version": "4.4.2",
   "description": "Titanium SDK skills and agents for AI coding assistants (Claude Code, Gemini CLI, Codex CLI)",
   "main": "lib/index.js",
   "type": "module",

package/skills/purgetss/SKILL.md

@@ -11,9 +11,7 @@ Utility-first styling toolkit for Titanium/Alloy mobile apps.
 
 ## Required workflow (read before responding)
 
-The SKILL.md alone is an **index** of references. The detail you need
-to give accurate answers lives in the reference files. **Reading this
-SKILL.md is not enough.**
+The SKILL.md alone is an **index** of references. The detail you need to give accurate answers lives in the reference files. **Reading this SKILL.md is not enough.**
 
 ### Step 1 — Open the relevant reference files
 
@@ -31,8 +29,7 @@ SKILL.md is not enough.**
 
 ### Step 2 — Output contract
 
-Every utility class you suggest and every styling pattern you describe
-MUST be backed by a citation in the form:
+Every utility class you suggest and every styling pattern you describe MUST be backed by a citation in the form:
 
 `[source: references/<file>.md]`
 
@@ -40,8 +37,7 @@ Example: *"Use `wh-12` to set width and height to 48px [source: references/class
 
 ### Step 3 — If you must answer from memory
 
-If you write a claim without having read the reference that backs it,
-prepend `FROM_MEMORY (unverified):` to that claim. Do not hide it.
+If you write a claim without having read the reference that backs it, prepend `FROM_MEMORY (unverified):` to that claim. Do not hide it.
 
 ### Banned behaviors
 
@@ -352,8 +348,7 @@ const view = $.UI.create('View', {
 > **🚨 CRITICAL: VERIFY CLASSES BEFORE SUGGESTING**
 > **NEVER guess or hallucinate classes based on other CSS Frameworks knowledge!**
 
-PurgeTSS shares naming with some CSS Frameworks but has DIFFERENT classes for Titanium.
-Always verify a class exists before suggesting it.
+PurgeTSS shares naming with some CSS Frameworks but has DIFFERENT classes for Titanium. Always verify a class exists before suggesting it.
 
 ### Verification Steps
 

package/skills/ti-api/references/api-core.md

@@ -28,14 +28,11 @@
 > Platforms: both
 > Type: module
 
-The Titanium module provides the Titanium Mobile API, allowing developers to access native
-features of each target environment. Currently, the Android and iOSenvironments are supported.
+The Titanium module provides the Titanium Mobile API, allowing developers to access native features of each target environment. Currently, the Android and iOSenvironments are supported.
 
 ### Titanium Namespace
 
-The complete Titanium API is accessible from the `Titanium` namespace but, for convenience and
-brevity, the alias `Ti` is also provided. As the `Titanium` namespace is functionally-identical
-to its `Ti` alias, it is always recommended to use `Ti` in your code.
+The complete Titanium API is accessible from the `Titanium` namespace but, for convenience and brevity, the alias `Ti` is also provided. As the `Titanium` namespace is functionally-identical to its `Ti` alias, it is always recommended to use `Ti` in your code.
 
 For example, the following pairs of Titanium calls behave exactly the same.
 
@@ -82,21 +79,13 @@ Ti.API.info('Hello Titanium!');
 > Platforms: both
 > Type: module
 
-The UI module is responsible for native user-interface components and interaction inside
-Titanium.  The goal of the UI module is to provide a native experience along with native
-performance by compiling Javascript code into their native counterparts as part of the
-build process.
+The UI module is responsible for native user-interface components and interaction inside Titanium.  The goal of the UI module is to provide a native experience along with native performance by compiling Javascript code into their native counterparts as part of the build process.
 
 ### Design
 
 The UI module is broken down into 3 major area:
 
-* **Views** - [Views](Titanium.UI.View) are containers that host visual elements such as
-controls or other views.  Views can have their properties customized, such as their border color
-and radius, can fire events such as swipe events or touches, and can optionally contain a
-hierarchy or other views as children. In Titanium, most views are specialized to perform both a
-visual function and set of interaction behaviors such as [Table View](Titanium.UI.TableView) or
-[Coverflow View](Titanium.UI.iOS.CoverFlowView).  Views are always named with the suffix `View`.
+* **Views** - [Views](Titanium.UI.View) are containers that host visual elements such as controls or other views.  Views can have their properties customized, such as their border color and radius, can fire events such as swipe events or touches, and can optionally contain a hierarchy or other views as children. In Titanium, most views are specialized to perform both a visual function and set of interaction behaviors such as [Table View](Titanium.UI.TableView) or [Coverflow View](Titanium.UI.iOS.CoverFlowView).  Views are always named with the suffix `View`.
 
 *(See full overview in titanium-docs)*
 
@@ -350,16 +339,11 @@ visual function and set of interaction behaviors such as [Table View](Titanium.U
 > Platforms: both
 > Type: module
 
-An accelerometer is a hardware unit integrated into a mobile device, that detects when the 
-device has moved, and returns its new orientation in a three-dimensional space. With its 
-single `update` event, this module provides an interface to access the output positional data.
+An accelerometer is a hardware unit integrated into a mobile device, that detects when the device has moved, and returns its new orientation in a three-dimensional space. With its single `update` event, this module provides an interface to access the output positional data.
 
-An accelerometer needs to be switched on in order for it to report to the operating system, 
-which consumes a lot of power that will deplete the battery over time. This is why it is 
-recommended that the accelerometer is switched off when not in use.
+An accelerometer needs to be switched on in order for it to report to the operating system, which consumes a lot of power that will deplete the battery over time. This is why it is recommended that the accelerometer is switched off when not in use.
 
-The accelerometer may be switched on and off by simply adding and removing the `update` 
-event listener function. See the example for a demonstration.
+The accelerometer may be switched on and off by simply adding and removing the `update` event listener function. See the example for a demonstration.
 
 
 
@@ -375,21 +359,15 @@ event listener function. See the example for a demonstration.
 > Extends Ti.Proxy
 > Platforms: both
 
-A `Blob` represents a chunk of binary information, often obtained through
-an [HTTPClient](Titanium.Network.HTTPClient) or by reading a [File](Titanium.Filesystem.File).
+A `Blob` represents a chunk of binary information, often obtained through an [HTTPClient](Titanium.Network.HTTPClient) or by reading a [File](Titanium.Filesystem.File).
 
-Blobs are often used to store text or image data.
-The `Blob` object includes a number of properties and methods specific to image blobs.
+Blobs are often used to store text or image data. The `Blob` object includes a number of properties and methods specific to image blobs.
 
-Android supports an [append](Titanium.Blob.append) method, but
-otherwise blobs are immutable.
+Android supports an [append](Titanium.Blob.append) method, but otherwise blobs are immutable.
 
-The <Titanium.Utils> module provides several utility methods for working with
-blobs, including methods for converting between blobs and Base64-encoded strings,
-and methods for generating SHA-1 and SHA-256 hashes and MD5 digests from blob data.
+The <Titanium.Utils> module provides several utility methods for working with blobs, including methods for converting between blobs and Base64-encoded strings, and methods for generating SHA-1 and SHA-256 hashes and MD5 digests from blob data.
 
-The [Buffer](Titanium.Buffer) object can also contain binary data, and is
-more easily mutable. Extracting blob data to a buffer is somewhat roundabout:
+The [Buffer](Titanium.Buffer) object can also contain binary data, and is more easily mutable. Extracting blob data to a buffer is somewhat roundabout:
 
 *(See full overview in titanium-docs)*
 
@@ -444,8 +422,7 @@ more easily mutable. Extracting blob data to a buffer is somewhat roundabout:
 > Extends Ti.IOStream
 > Platforms: both
 
-Use the <Titanium.Stream.createStream> method to create a `BlobStream` instance from a
-`Blob`.
+Use the <Titanium.Stream.createStream> method to create a `BlobStream` instance from a `Blob`.
 
 
 
@@ -491,8 +468,7 @@ Use the <Titanium.createBuffer> method to create a buffer.
 > Extends Ti.IOStream
 > Platforms: both
 
-Use the <Titanium.Stream.createStream> method to create a `BufferStream` instance from a
-`Buffer`.
+Use the <Titanium.Stream.createStream> method to create a `BufferStream` instance from a `Buffer`.
 
 
 
@@ -505,18 +481,13 @@ Use the <Titanium.Stream.createStream> method to create a `BufferStream` instanc
 > Platforms: both
 > Type: module
 
-The `Codec` module can be used for encoding strings and numbers into [Buffer](Titanium.Buffer)
-objects, and decoding primitive types from buffers.
+The `Codec` module can be used for encoding strings and numbers into [Buffer](Titanium.Buffer) objects, and decoding primitive types from buffers.
 
 ### Byte Order
 
-Multi-byte data can be stored in two different byte orders: big-endian or
-little-endian. In big-endian byte order, the most significant or highest-value
-byte is stored first. For example, the 4-byte integer 0xFEDCBA98 is made up of the
-bytes 0xFE, 0xDC, 0xBA and 0x98, from most-significant to least-significant.
+Multi-byte data can be stored in two different byte orders: big-endian or little-endian. In big-endian byte order, the most significant or highest-value byte is stored first. For example, the 4-byte integer 0xFEDCBA98 is made up of the bytes 0xFE, 0xDC, 0xBA and 0x98, from most-significant to least-significant.
 
-If we represent a buffer as an array of byte values, a big-endian encoding of
-0xFEDCBA98 would look like this:
+If we represent a buffer as an array of byte values, a big-endian encoding of 0xFEDCBA98 would look like this:
 
 ``` js
 [ 0xFE, 0xDC, 0xBA, 0x98 ]
@@ -609,8 +580,7 @@ If we represent a buffer as an array of byte values, a big-endian encoding of
 > Extends Ti.Proxy
 > Platforms: both
 
-See the <Titanium.Stream> module for related utility methods that support asynchronous
-I/O.
+See the <Titanium.Stream> module for related utility methods that support asynchronous I/O.
 
 
 ### Methods (5)
@@ -631,10 +601,7 @@ I/O.
 > Platforms: both
 > Type: module
 
-The `Locale` module works with localization files to which are generated during compilation 
-into the operating system specific localization formats. The `Locale` module provides 
-locale-specific strings which can be referenced at runtime.  Additionally, the module 
-contains a few methods and properties for querying device locale information.
+The `Locale` module works with localization files to which are generated during compilation into the operating system specific localization formats. The `Locale` module provides locale-specific strings which can be referenced at runtime.  Additionally, the module contains a few methods and properties for querying device locale information.
 
 The macro `L` can be used as an alias for the <Titanium.Locale.getString> method.
 
@@ -670,11 +637,7 @@ The macro `L` can be used as an alias for the <Titanium.Locale.getString> method
 > Platforms: both
 > Type: module
 
-This module provides a set of methods for interacting with
-[IOStream](Titanium.IOStream) objects, including asynchronous versions of the
-`read` and `write` methods offered by all stream objects. These
-methods should be used in any place where reading from or writing
-to a stream might block.
+This module provides a set of methods for interacting with [IOStream](Titanium.IOStream) objects, including asynchronous versions of the `read` and `write` methods offered by all stream objects. These methods should be used in any place where reading from or writing to a stream might block.
 
 See also:
 
@@ -735,14 +698,9 @@ See also:
 > Extends Object
 > Platforms: both
 
-On platforms that use native code (Android and iOS), the `Proxy` type represents a
-JavaScript wrapper or _proxy_ around a native object. Setting or getting a property
-on a proxy object results in a method invocation on the native object. Likewise,
-calling a method on the proxy object results in a method invocation on the native
-object.
+On platforms that use native code (Android and iOS), the `Proxy` type represents a JavaScript wrapper or _proxy_ around a native object. Setting or getting a property on a proxy object results in a method invocation on the native object. Likewise, calling a method on the proxy object results in a method invocation on the native object.
 
-Some Titanium objects are _createable_: new instances of these objects can be created using
-factory methods. For example, a [Window](Titanium.UI.Window) object can be created using the
+Some Titanium objects are _createable_: new instances of these objects can be created using factory methods. For example, a [Window](Titanium.UI.Window) object can be created using the
 
 ### Properties (unique: 3/3)
 | Property | Type | Default | Platform | Description |
@@ -774,12 +732,9 @@ factory methods. For example, a [Window](Titanium.UI.Window) object can be creat
 > Platforms: both
 > Type: module
 
-A Titanium module is a non-createable Titanium object that is exposed through the
-global Titanium object.
+A Titanium module is a non-createable Titanium object that is exposed through the global Titanium object.
 
-For example, the <Titanium.UI> module provides constants and factory methods related
-to UI objects, as well as a few UI-related properties that are not related to a
-specific object.
+For example, the <Titanium.UI> module provides constants and factory methods related to UI objects, as well as a few UI-related properties that are not related to a specific object.
 
 
 

package/skills/ti-api/references/api-data-network.md

@@ -73,17 +73,11 @@
 
 A result set represents the results returned by a database query.
 
-The [rowCount](Titanium.Database.ResultSet.rowCount) property identifies the number of
-rows in the result set. The `ResultSet` object maintains an internal record of the 
-current row. As shown in the example, you can use the 
-[next](Titanium.Database.ResultSet.next) method to iterate through the rows in the set.
+The [rowCount](Titanium.Database.ResultSet.rowCount) property identifies the number of rows in the result set. The `ResultSet` object maintains an internal record of the current row. As shown in the example, you can use the [next](Titanium.Database.ResultSet.next) method to iterate through the rows in the set.
 
-Use the [field](Titanium.Database.ResultSet.field) or
-[fieldByName](Titanium.Database.ResultSet.fieldByName) methods to query the fields for
-the current row.
+Use the [field](Titanium.Database.ResultSet.field) or [fieldByName](Titanium.Database.ResultSet.fieldByName) methods to query the fields for the current row.
 
-On the iOS platform, closing the database also closes the result set, that is,
-you can only access the result set if the database is currently open.
+On the iOS platform, closing the database also closes the result set, that is, you can only access the result set if the database is currently open.
 
 ### Properties (unique: 3/6)
 | Property | Type | Default | Platform | Description |
@@ -113,9 +107,7 @@ you can only access the result set if the database is currently open.
 > Platforms: both
 > Type: module
 
-For examples of using the Filesystem APIs, refer to the
-[Filesystem Access and Storage guide](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/Working_with_Local_Data_Sources/Filesystem_Access_and_Storage.html)
-as well as the other Filesystem submodule API documentation.
+For examples of using the Filesystem APIs, refer to the [Filesystem Access and Storage guide](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/Working_with_Local_Data_Sources/Filesystem_Access_and_Storage.html) as well as the other Filesystem submodule API documentation.
 
 ### Properties (unique: 11/21)
 | Property | Type | Default | Platform | Description |
@@ -160,20 +152,13 @@ as well as the other Filesystem submodule API documentation.
 > Extends Ti.Proxy
 > Platforms: both
 
-Use the <Titanium.Filesystem.getFile> method to get a handle to a `File` object,
-which represents a given path.  There does not need to be an existing file or directory
-does not need to exist before `getFile` is called. If the file doesn't exist, and
-the file path identifies a file in a writable directory, writing to the file
-creates the file implicitly.
+Use the <Titanium.Filesystem.getFile> method to get a handle to a `File` object, which represents a given path.  There does not need to be an existing file or directory does not need to exist before `getFile` is called. If the file doesn't exist, and the file path identifies a file in a writable directory, writing to the file creates the file implicitly.
 
 See <Titanium.Filesystem> for constants identifying commonly-used device directories.
 
 Use the [exists](Titanium.Filesystem.File.exists) method to test whether the file exists.
 
-A file object can point to an ordinary file, a directory or a symbolic link.
-Use [createDirectory](Titanium.Filesystem.File.createDirectory) to create a directory.
-Use the [getDirectoryListing](Titanium.Filesystem.File.getDirectoryListing) method to
-retrieve a list of the directory's contents.
+A file object can point to an ordinary file, a directory or a symbolic link. Use [createDirectory](Titanium.Filesystem.File.createDirectory) to create a directory. Use the [getDirectoryListing](Titanium.Filesystem.File.getDirectoryListing) method to retrieve a list of the directory's contents.
 
 
 *(See full overview in titanium-docs)*
@@ -249,16 +234,13 @@ The `Network` module is used to access networking related functionality.
 
 For TCP sockets, see <Titanium.Network.Socket.TCP>.
 
-The legacy <Titanium.Network.TCPSocket> object is still required
-by the [BonjourBrowser](Titanium.Network.BonjourBrowser) and
-[BonjourService](Titanium.Network.BonjourService) objects.
+The legacy <Titanium.Network.TCPSocket> object is still required by the [BonjourBrowser](Titanium.Network.BonjourBrowser) and [BonjourService](Titanium.Network.BonjourService) objects.
 
 For all other socket needs, use <Titanium.Network.Socket.TCP>.
 
 ### App Transport Security
 
-Starting with iOS 9, Apple introduced new security and compatibility guidelines for networking
-and connectivity, which include:
+Starting with iOS 9, Apple introduced new security and compatibility guidelines for networking and connectivity, which include:
 
 
 *(See full overview in titanium-docs)*
@@ -330,16 +312,7 @@ and connectivity, which include:
 
 Use the <Titanium.Network.createBonjourBrowser> method to create a `BonjourBrowser` instance.
 
-If your application publishes Bonjour services itself, that service will be discovered 
-by the browser if necessary; be prepared to perform a check if you do not want to list 
-local services as available.  Bonjour service browsing is an asynchronous operation, 
-meaning that you should be extremely careful when caching values from the `services` 
-property returned by the `updatedservices` event.  In particular, if you maintain a 
-local copy of available services and a user tries to connect to one, you should be prepared 
-to handle failures gracefully; the next `updatedservices` event should provide the new 
-services list, but you should not rely on it being delivered before user input.  When 
-a window which uses Bonjour browsing is closed, if you do not want to continue searching, 
-you must call the stop() method.
+If your application publishes Bonjour services itself, that service will be discovered by the browser if necessary; be prepared to perform a check if you do not want to list local services as available.  Bonjour service browsing is an asynchronous operation, meaning that you should be extremely careful when caching values from the `services` property returned by the `updatedservices` event.  In particular, if you maintain a local copy of available services and a user tries to connect to one, you should be prepared to handle failures gracefully; the next `updatedservices` event should provide the new services list, but you should not rely on it being delivered before user input.  When a window which uses Bonjour browsing is closed, if you do not want to continue searching, you must call the stop() method.
 
 In iOS 14.0+, to browse services add key `NSLocalNetworkUsageDescription` and `NSBonjourServices` to the `ios plist` section of the tiapp.xml file.
 
@@ -372,16 +345,9 @@ In iOS 14.0+, to browse services add key `NSLocalNetworkUsageDescription` and `N
 > Extends Ti.Proxy
 > Platforms: ios
 
-You can obtain a `BonjourService` instance by calling <Titanium.Network.createBonjourService> 
-or from the `service` list from a [BonjourBrowser](Titanium.Network.BonjourBrowser)  
-`updatedservices` event.   
+You can obtain a `BonjourService` instance by calling <Titanium.Network.createBonjourService> or from the `service` list from a [BonjourBrowser](Titanium.Network.BonjourBrowser) `updatedservices` event.
 
-You can only publish Bonjour services attached to a socket which is currently listening; 
-you cannot publish a service for a remotely connected socket.  If you stop the Bonjour 
-service and wish to close the socket it uses, it is strongly recommended that you stop 
-the service first.  When a window which publishes a Bonjour service is closed, you must 
-stop the service if the associated socket is also to be closed, or if it is no longer 
-necessary to publish.  Bonjour service resolution and publishing is asynchronous.
+You can only publish Bonjour services attached to a socket which is currently listening; you cannot publish a service for a remotely connected socket.  If you stop the Bonjour service and wish to close the socket it uses, it is strongly recommended that you stop the service first.  When a window which publishes a Bonjour service is closed, you must stop the service if the associated socket is also to be closed, or if it is no longer necessary to publish.  Bonjour service resolution and publishing is asynchronous.
 
 In iOS 14.0+, to publish service add key `NSLocalNetworkUsageDescription` and `NSBonjourServices` in tiapp.xml file.
 
@@ -421,8 +387,7 @@ Example:
 > Extends Ti.Proxy
 > Platforms: both
 
-Use <Titanium.Network.createCookie> to create a new `Cookie` object.
-The following is an example of how to setup and read a cookie on a web view:
+Use <Titanium.Network.createCookie> to create a new `Cookie` object. The following is an example of how to setup and read a cookie on a web view:
 
 ``` js
 if (!Date.prototype.toISOString) {
@@ -471,8 +436,7 @@ if (!Date.prototype.toISOString) {
 
 Use <Titanium.Network.createHTTPClient> to create a new `HTTPClient` object.
 
-An `HTTPClient` object is intended to be used for a single request. It may be
-possible to re-use an `HTTPClient` object, but this use case is not tested.
+An `HTTPClient` object is intended to be used for a single request. It may be possible to re-use an `HTTPClient` object, but this use case is not tested.
 
 There are three steps in making a typical HTTP request:
 
@@ -480,8 +444,7 @@ There are three steps in making a typical HTTP request:
 * Opening the `HTTPClient` object.
 * Sending the request.
 
-Before opening the request, you must define one or more callbacks to handle
-the HTTP response, as well as errors, progress updates, and other conditions.
+Before opening the request, you must define one or more callbacks to handle the HTTP response, as well as errors, progress updates, and other conditions.
 
 The `HTTPClient` callbacks operate somewhat differently from other
 
@@ -573,21 +536,13 @@ The `HTTPClient` callbacks operate somewhat differently from other
 > Extends Ti.IOStream
 > Platforms: both
 
-Most socket operations are asynchronous. When you create a socket, you can define
-callback functions to receive the results of API calls, as well as to handle incoming
-data.
+Most socket operations are asynchronous. When you create a socket, you can define callback functions to receive the results of API calls, as well as to handle incoming data.
 
-For example, for a client-side socket, you define
-[connected](Titanium.Network.Socket.TCP.connected) and
-[error](Titanium.Network.Socket.TCP.error) callback functions.
+For example, for a client-side socket, you define [connected](Titanium.Network.Socket.TCP.connected) and [error](Titanium.Network.Socket.TCP.error) callback functions.
 
-To connect to a remote host, call the socket's
-[connect](Titanium.Network.Socket.TCP.connect) method. If the socket connects
-successfully, your `connected` callback is invoked, and you can send and receive data
-on the socket. If the socket connection fails, your `error` callback is invoked.
+To connect to a remote host, call the socket's [connect](Titanium.Network.Socket.TCP.connect) method. If the socket connects successfully, your `connected` callback is invoked, and you can send and receive data on the socket. If the socket connection fails, your `error` callback is invoked.
 
-After a socket is connected, you can access it like any other <Titanium.IOStream>.
-Note that the socket's `read` and `write` methods may block, so in most cases
+After a socket is connected, you can access it like any other <Titanium.IOStream>. Note that the socket's `read` and `write` methods may block, so in most cases
 
 *(See full overview in titanium-docs)*
 

package/skills/ti-api/references/api-media.md

@@ -21,17 +21,7 @@
 > Platforms: both
 > Type: module
 
-The Media module is used to access the device's media-related functionality, such
-as using the device's camera and photo gallery, playing media files, or recording
-audio or video.
-For examples of using the Media APIs, refer to the
-[Working with Media APIs guide](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/Working_with_Media_APIs/)
-in addition to the other media submodule API documentation.
-**Note**: Some third party Android camera apps may choose to ignore video recording quality
-settings. If you wish to specifically set the video quality, don't assume
-`EXTRA_VIDEO_QUALITY` intent will be respected by the camera app and use Titanium's built-in
-camera window which can be used to assign the `overlay` property when calling the
-`showCamera()` method.
+The Media module is used to access the device's media-related functionality, such as using the device's camera and photo gallery, playing media files, or recording audio or video. For examples of using the Media APIs, refer to the [Working with Media APIs guide](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/Working_with_Media_APIs/) in addition to the other media submodule API documentation. **Note**: Some third party Android camera apps may choose to ignore video recording quality settings. If you wish to specifically set the video quality, don't assume `EXTRA_VIDEO_QUALITY` intent will be respected by the camera app and use Titanium's built-in camera window which can be used to assign the `overlay` property when calling the `showCamera()` method.
 
 ### Properties (unique: 28/178)
 | Property | Type | Default | Platform | Description |
@@ -263,16 +253,9 @@ camera window which can be used to assign the `overlay` property when calling th
 > Extends Ti.Proxy
 > Platforms: both
 
-On Android, when you are done playing a given audio file, you must call the
-[release](Titanium.Media.AudioPlayer.release) method to stop buffering audio data and
-release associated system resources. Since 7.5.0, this method is available on iOS as well
-and will release all audio-player related resources. After this method has been called,
-the object should not be accessed anymore.
+On Android, when you are done playing a given audio file, you must call the [release](Titanium.Media.AudioPlayer.release) method to stop buffering audio data and release associated system resources. Since 7.5.0, this method is available on iOS as well and will release all audio-player related resources. After this method has been called, the object should not be accessed anymore.
 
-On iOS, you can control how the audio stream interacts with other system sounds
-by setting <Titanium.Media.audioSessionCategory>. Since Titanium 7.5.0, this API
-uses the [AVPlayer API](https://developer.apple.com/documentation/avfoundation/avplayer) for a more modern
-and performant audio playback.
+On iOS, you can control how the audio stream interacts with other system sounds by setting <Titanium.Media.audioSessionCategory>. Since Titanium 7.5.0, this API uses the [AVPlayer API](https://developer.apple.com/documentation/avfoundation/avplayer) for a more modern and performant audio playback.
 
 Use the <Titanium.Media.createAudioPlayer> method to create an audio player.
 
@@ -343,13 +326,9 @@ Use the <Titanium.Media.createAudioPlayer> method to create an audio player.
 
 Use the <Titanium.Media.createAudioRecorder> method to create an audio recorder.
 
-Ensure to request the permissions for audio-recording before starting a new record-session.
-This can be done by using <Titanium.Media.hasAudioRecorderPermissions> to check whether
-audio-permissions are granted and <Titanium.Media.requestAudioRecorderPermissions> to 
-request audio-permissions. 
+Ensure to request the permissions for audio-recording before starting a new record-session. This can be done by using <Titanium.Media.hasAudioRecorderPermissions> to check whether audio-permissions are granted and <Titanium.Media.requestAudioRecorderPermissions> to request audio-permissions.
 
-**Android Platform Note**: On Android, you also need to include the following permission
-into the `<android>` section of the tiapp.xml:
+**Android Platform Note**: On Android, you also need to include the following permission into the `<android>` section of the tiapp.xml:
 
 
 ### Properties (unique: 5/8)
@@ -378,13 +357,9 @@ into the `<android>` section of the tiapp.xml:
 > Extends Ti.Proxy
 > Platforms: ios
 
-This is a read-only object that describes a single media item, not a playlist. 
-Titanium does not support access to playlists.
+This is a read-only object that describes a single media item, not a playlist. Titanium does not support access to playlists.
 
-`Item` objects cannot be created explicitly.  The 
-[openMusicLibrary](Titanium.Media.openMusicLibrary) returns `Item` objects in its
-`success` callback function, while [queryMusicLibrary](Titanium.Media.queryMusicLibrary)
-returns an array of `Item` objects.
+`Item` objects cannot be created explicitly.  The [openMusicLibrary](Titanium.Media.openMusicLibrary) returns `Item` objects in its `success` callback function, while [queryMusicLibrary](Titanium.Media.queryMusicLibrary) returns an array of `Item` objects.
 
 ### Properties (unique: 36/38)
 | Property | Type | Default | Platform | Description |
@@ -477,14 +452,11 @@ To retrieve an instance of a MusicPlayer object, use either the
 > Extends Ti.Proxy
 > Platforms: both
 
-The `Sound` object loads the entire media resource in memory before playing.  If you need to 
-support streaming, use the [AudioPlayer](Titanium.Media.AudioPlayer) API.
+The `Sound` object loads the entire media resource in memory before playing.  If you need to support streaming, use the [AudioPlayer](Titanium.Media.AudioPlayer) API.
 
-You can control how the sound interacts with other system sounds
-by setting <Titanium.Media.audioSessionCategory>.
+You can control how the sound interacts with other system sounds by setting <Titanium.Media.audioSessionCategory>.
 
-Use the <Titanium.Media.createSound> method to create a `Sound` object. You can play audio 
-in any format supported by the target platform(s), as described in the following documents:
+Use the <Titanium.Media.createSound> method to create a `Sound` object. You can play audio in any format supported by the target platform(s), as described in the following documents:
 
 * [Android](https://developer.android.com/guide/topics/media/media-formats#core)
 * [iOS](https://developer.apple.com/audio/)
@@ -538,10 +510,9 @@ in any format supported by the target platform(s), as described in the following
 > Extends Ti.Proxy
 > Platforms: ios
 
-You can use this module to provide audible system alerts. 
+You can use this module to provide audible system alerts.
 
-You can use it to play short (30 seconds or shorter) sounds. The interface does not provide level, positioning, 
-looping, or timing control, and does not support simultaneous playback: You can play only one sound at a time. 
+You can use it to play short (30 seconds or shorter) sounds. The interface does not provide level, positioning, looping, or timing control, and does not support simultaneous playback: You can play only one sound at a time.
 
 This module differs from the Sound module because it honors the ringtone volume, not the Music volume.
 
@@ -568,20 +539,15 @@ Know more about [System Sound Services](https://developer.apple.com/reference/au
 > Extends Ti.UI.View
 > Platforms: both
 
-The video player is a native view that can be used to play videos, either stored
-locally or streamed from a web server. The player can occupy the full screen, or can
-be used as a view that can be added to other views.
+The video player is a native view that can be used to play videos, either stored locally or streamed from a web server. The player can occupy the full screen, or can be used as a view that can be added to other views.
 
 Use the <Titanium.Media.createVideoPlayer> method to create a video player.
 
-All platforms support specifying the video content as a URL, either to a local file or
-a remote stream. This is done by setting the [url](Titanium.Media.VideoPlayer.url) property.
+All platforms support specifying the video content as a URL, either to a local file or a remote stream. This is done by setting the [url](Titanium.Media.VideoPlayer.url) property.
 
 ### iOS Implementation Notes
 
-On iOS, video content can also be specified as a [Blob](Titanium.Blob) or
-[File](Titanium.Filesystem.File) object using the
-[media](Titanium.Media.VideoPlayer.media) property.
+On iOS, video content can also be specified as a [Blob](Titanium.Blob) or [File](Titanium.Filesystem.File) object using the [media](Titanium.Media.VideoPlayer.media) property.
 
 
 *(See full overview in titanium-docs)*