@maccesar/titools 2.10.1 → 3.1.0

package/skills/alloy-howtos/references/config_files.md

@@ -1,158 +0,0 @@
-# Alloy configuration files reference
-
-## Build configuration file (alloy.jmk)
-
-Alloy exposes hooks to customize compilation with a JS Makefile (JMK).
-
-**Location:** `app/alloy.jmk`
-
-**Example:**
-```javascript
-task('pre:compile', (event, logger) => {
-    logger.showTimestamp = true;
-    logger.info(`building project at ${event.dir.project}`);
-});
-
-task('post:compile', (event, logger) => {
-    logger.info('compile finished!');
-});
-```
-
-### Compiler tasks (event names)
-
-| Task             | When Called                                               |
-| ---------------- | --------------------------------------------------------- |
-| `pre:load`       | After project clean, before copying assets to `Resources` |
-| `pre:compile`    | Before compiler starts                                    |
-| `post:compile`   | After compiler finishes, before exit                      |
-| `compile:app.js` | After compiling `app.js`, before writing to disk          |
-
-### Event object
-
-| Property       | Type    | Description                                                                                                                                                                                                         |
-| -------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `adapters`     | Array   | List of adapters                                                                                                                                                                                                    |
-| `alloyConfig`  | Object  | Compiler config: `platform` (android/ios), `file` (selective compile), `deploytype` (development/test/production), `beautify` (Boolean)                                                                             |
-| `autoStyle`    | Boolean | Autostyle enabled for project                                                                                                                                                                                       |
-| `dependencies` | Object  | Value of `dependencies` key in config.json                                                                                                                                                                          |
-| `dir`          | Object  | Directory paths: `home` (app path), `project` (root path), `resources`, `resourcesAlloy`, `assets`, `config`, `controllers`, `migrations`, `models`, `styles`, `themes`, `views`, `widgets`, `builtins`, `template` |
-| `sourcemap`    | Boolean | If `true`, generates mapping files to link generated Titanium files in `Resources` back to the source files in `app` for debugging.                                                                                 |
-| `theme`        | String  | Theme name being used                                                                                                                                                                                               |
-| `code`         | String  | *(compile:app.js only)* Contents of `app.js`                                                                                                                                                                        |
-| `appJSFile`    | String  | *(compile:app.js only)* Absolute path to `app.js`                                                                                                                                                                   |
-
-### Logger object
-
-The `logger` object controls compilation log output.
-
-#### Properties
-
-| Property        | Type    | Description                                     |
-| --------------- | ------- | ----------------------------------------------- |
-| `DEBUG`         | Number  | READONLY. Output all log messages.              |
-| `INFO`          | Number  | READONLY. Output all except debug messages.     |
-| `WARN`          | Number  | READONLY. Output only warning and error.        |
-| `ERROR`         | Number  | READONLY. Output only error messages.           |
-| `NONE`          | Number  | READONLY. Disable log messages.                 |
-| `logLevel`      | Number  | Sets which log messages to output.              |
-| `showTimestamp` | Boolean | If `true`, outputs timestamp with log messages. |
-| `stripColors`   | Boolean | If `true`, suppresses color output.             |
-
-#### Methods
-
-| Method               | Description                    |
-| -------------------- | ------------------------------ |
-| `debug(msg: String)` | Outputs a debug log message.   |
-| `info(msg: String)`  | Outputs an info log message.   |
-| `warn(msg: String)`  | Outputs a warning log message. |
-| `error(msg: String)` | Outputs an error log message.  |
-
----
-
-## Global initializer (alloy.js)
-
-**Location:** `app/alloy.js`
-
-Runs before any controllers load. Use it to set up globals and singletons.
-
-Common uses:
-- Creating `Alloy.Collections` (e.g., `Alloy.Collections.myModel = Alloy.createCollection('myModel');`)
-- Setting up `Alloy.Globals` (shared references, utility functions)
-- Initializing singletons (analytics, logging, network managers)
-- Configuring global event listeners
-
-**Example:**
-```javascript
-// app/alloy.js
-Alloy.Globals.loading = Alloy.createWidget('com.example.loading');
-Alloy.Collections.users = Alloy.createCollection('user');
-
-// Global utility
-Alloy.Globals.alert = (title, message) => {
-    Ti.UI.createAlertDialog({ title, message }).show();
-};
-```
-
----
-
-## Project configuration file (config.json)
-
-**Location:** `app/config.json`
-
-Alloy uses `config.json` for global values, environment and platform overrides, and widget dependencies.
-### Objects
-
-| Object            | Description                                                 |
-| ----------------- | ----------------------------------------------------------- |
-| `global`          | Key-value pairs for all environments and platforms          |
-| `env:development` | Development builds (simulator/emulator)                     |
-| `env:test`        | Test builds on device                                       |
-| `env:production`  | Production builds (after package installation)              |
-| `os:android`      | Android-specific values                                     |
-| `os:ios`          | iOS-specific values                                         |
-| `dependencies`    | Widget dependencies (name: version)                         |
-| `autoStyle`       | Enable autostyle for entire project                         |
-| `backbone`        | Backbone.js version: `0.9.2` (default), `1.1.2`, or `1.3.3` |
-
-**Precedence:** `os` > `env` > `global`. Combinations (for example, `os:ios env:production`) override single values.
-
-**Runtime access:** Values are available at runtime via `Alloy.CFG.<key>`.
-
-**Example:**
-
-```json
-{
-    "global": { "foo": 1 },
-    "env:development": { "foo": 2 },
-    "env:test": { "foo": 3 },
-    "env:production": { "foo": 4 },
-    "os:ios env:production": { "foo": 5 },
-    "os:ios env:development": { "foo": 6 },
-    "os:ios env:test": { "foo": 7 },
-    "os:android": { "foo": 8 },
-    "dependencies": {
-        "com.foo.widget": "1.0"
-    }
-}
-```
-
-Accessing values: `Ti.API.info(Alloy.CFG.foo)` on iPhone simulator returns `6`.
-
----
-
-## Widget configuration file (widget.json)
-
-**Location:** Root directory of the widget. Follows the npm `package.json` format with a few exceptions.
-### Keys
-
-| Key                    | Type   | Required | Description                           |
-| ---------------------- | ------ | -------- | ------------------------------------- |
-| `id`                   | String | Yes      | Must match widget root folder name    |
-| `copyright`            | String | No       | Copyright information                 |
-| `license`              | String | No       | License information                   |
-| `min-alloy-version`    | Float  | No*      | Minimum Alloy version required        |
-| `min-titanium-version` | Float  | No*      | Minimum Titanium version required     |
-| `tags`                 | String | No       | Comma-delimited keywords              |
-| `platforms`            | String | No*      | Supported platforms (comma-delimited) |
-
-(*) Currently, `min-alloy-version`, `min-titanium-version`, and `platforms` are not strictly enforced, but Alloy will perform checks against these in future versions.

package/skills/alloy-howtos/references/custom_tags.md

@@ -1,148 +0,0 @@
-# Creating custom tags in Titanium with Alloy
-
-Custom tags let you create reusable UI components without the overhead of widgets. You can keep controls in a single file under `app/lib`.
-
-## Why use custom tags?
-
-When building cross-platform apps, you often need UI controls (like a web-style checkbox) that do not exist natively. You have three approaches:
-
-1.  **Direct XML/JS:** Copy and paste code into each view. Not reusable and easy to drift.
-2.  **Widgets:** Reusable, but require a folder structure and `dependencies` in `config.json`.
-3.  **Custom tags:** Single file in `app/lib/`, no config dependency, easy to share. They reduce platform-specific code in views.
-
-## Basic setup
-
-1.  Create a file in `app/lib/` (e.g., `checkbox.js`)
-2.  Export a `create<TagName>` function
-3.  Use in XML with the `module` attribute
-
-**view.xml**
-```xml
-<CheckBox module="checkbox" id="termsAccepted"
-    caption="I agree to the terms of use"
-    underline="true"
-    onCaptionClick="doShowTerms"
-    onChange="onCheckChange" />
-```
-The `module` attribute tells Alloy to look in `checkbox.js` for a `createCheckBox` function. Alloy passes the XML/TSS arguments and expects a `Ti.UI.*` component back.
-
-## Robust example: CheckBox
-
-**app/lib/checkbox.js**
-```javascript
-exports.createCheckBox = args => {
-    // Wrapper view for all components
-    const wrapper = Ti.UI.createView({
-        top: args.top || 5,
-        width: Ti.UI.SIZE,
-        height: Ti.UI.SIZE,
-        layout: "horizontal",
-        left: args.left || 20,
-        right: args.right || null,
-        checked: args.checked || false
-    });
-
-    // The box itself
-    const box = Ti.UI.createView({
-        width: 15,
-        height: 15,
-        borderWidth: 1,
-        borderColor: "#02A9F4"
-    });
-
-    // Attributed string for styled caption (e.g. underline)
-    const attr = Ti.UI.createAttributedString({
-        text: args.caption
-    });
-
-    if (args.underline) {
-        attr.applyProperties({
-            attributes: [{
-                type: Ti.UI.ATTRIBUTE_UNDERLINES_STYLE,
-                value: Ti.UI.ATTRIBUTE_UNDERLINE_STYLE_SINGLE,
-                range: [0, args.caption.length]
-            }]
-        });
-    }
-
-    const caption = Ti.UI.createLabel({
-        color: "#000",
-        attributedString: attr,
-        left: 10,
-        text: args.caption,
-        font: { fontSize: 10 }
-    });
-
-    // The tick (using Unicode to avoid assets)
-    const tick = Ti.UI.createLabel({
-        text: "\u2713",
-        left: 1,
-        color: "#02A9F4",
-        font: { fontWeight: "bold" },
-        visible: args.checked || false
-    });
-
-    // Handle clicks
-    caption.addEventListener("click", () => {
-        wrapper.fireEvent("captionClick");
-    });
-
-    box.addEventListener("click", () => {
-        tick.visible = !tick.visible;
-        wrapper.checked = !wrapper.checked;
-        wrapper.fireEvent("change", { checked: wrapper.checked });
-    });
-
-    box.add(tick);
-    wrapper.add(box);
-    wrapper.add(caption);
-
-    return wrapper;
-};
-```
-
-## Global module override
-
-Apply a module to all tags in a view by updating the `Alloy` tag. Alloy checks your file for tag creation overrides before using default implementations:
-
-```xml
-<Alloy module="ui">
-    <Window>
-        <CustomButton />  <!-- Looks for createCustomButton in app/lib/ui.js -->
-        <Label />         <!-- Checks ui.js for createLabel first -->
-    </Window>
-</Alloy>
-```
-This is useful for adding default colors or properties (for example, a black default color for Android Labels) across a project.
-
-## Key points
-
-| Aspect        | Description                                                   |
-| ------------- | ------------------------------------------------------------- |
-| File location | `app/lib/<module_name>.js`                                    |
-| Function name | `create<TagName>` (e.g., `createCheckBox` for `<CheckBox>`)   |
-| Return value  | Must return a `Ti.UI.*` component (View, Button, Label, etc.) |
-| Arguments     | Receives all XML/TSS attributes in a single `args` object     |
-
-## Using Custom Tags Without Alloy XML
-
-You can also use custom tags from plain JavaScript via `require()`:
-
-```javascript
-const checkbox = require("checkbox").createCheckBox({
-    caption: "I agree",
-    underline: true
-});
-win.add(checkbox);
-```
-
-This works because custom tags are standard CommonJS modules. The `module` attribute in XML is a convenience.
-
-## Custom tags vs widgets
-
-| Custom Tags                           | Widgets                                  |
-| ------------------------------------- | ---------------------------------------- |
-| Single file in `app/lib/`             | Separate folder structure                |
-| No `config.json` dependency needed    | Requires `dependencies` in `config.json` |
-| Simpler for single-component controls | Better for complex multi-view components |
-| Easier to share across projects       | More formal packaging                    |

package/skills/alloy-howtos/references/debugging_troubleshooting.md

@@ -1,78 +0,0 @@
-# Alloy debugging and troubleshooting
-
-## Debugging
-
-### Compiler error messages
-
-The Alloy compiler reports syntax errors in JavaScript, JSON, TSS, and XML. Error messages include:
-- File path
-- Line and character position
-- Description of the error
-
-## Troubleshooting
-
-### Error: No app.js found
-
-**Error:** `[ERROR] No app.js found. Ensure the app.js file exists in your project's Resources directory.`
-
-**Solution:** If part of the contents of your `Resources` folder were deleted, run:
-```bash
-alloy compile --config platform=<platform>
-```
-
-### Android: images, HTML, and assets not displaying
-
-**Problem:** Assets display on iOS and Mobile Web but not Android.
-
-**Solution:** Android requires absolute paths. Precede asset paths with a slash ('/'). iOS and Mobile Web accept both relative and absolute paths.
-
-### Android runtime error: cannot call method of undefined
-
-**Error:** `Uncaught TypeError: Cannot call method xxx of undefined`
-
-**Causes:**
-1. Creating an iOS-only Titanium object. Use the `platform` attribute in views to enforce platform-specific objects.
-2. Top-level UI component has an assigned ID. The controller cannot use `$.<controller_name>` to reference it; use the assigned ID instead.
-
-### Android runtime error: Alloy is not defined
-
-**Error:** `Uncaught ReferenceError: Alloy is not defined`
-
-**Cause:** Non-controller JavaScript files are not automatically wrapped by Alloy. See [best_practices.md](best_practices.md) for the safe require pattern for non-controller files.
-
-**Solution:** Require the 'alloy' module:
-```javascript
-const Alloy = require('alloy');
-```
-
-### iOS application error: invalid method passed to UIModule
-
-**Error:** `invalid method (xxx) passed to UIModule (unknown file)`
-
-**Cause:** Trying to create an Android-only Titanium object.
-
-**Solution:** Use the `platform` attribute in the view to enforce platform-specific objects.
-
-### iOS application error: undefined is not an object
-
-**Error:** `undefined is not an object (evaluating $.xxx.open) (unknown file)`
-
-**Cause:** Top-level UI component has an assigned ID in XML markup.
-
-**Solution:** The controller cannot use `$.<controller_name>` to reference it; use the assigned ID instead.
-
-## Getting help
-
-Use the [TiDev Community Slack](https://slack.tidev.io/) or [GitHub Discussions](https://github.com/tidev/titanium-sdk/discussions):
-- Include 'alloy' as a tag
-- Include the Alloy version (run `alloy --version`)
-- Include platform information
-
-## Submitting a bug report
-
-Search [existing issues](https://github.com/tidev/alloy/issues) first to avoid duplicates. If none match, create a new issue:
-- Select 'Alloy' as the component
-- Include Alloy version (`alloy --version`)
-- Include environment information
-
-For detailed instructions, see [How to Report a Bug or Make a Feature Request](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_Guide/Contributing_to_Titanium/How_to_Report_a_Bug_or_Make_a_Feature_Request/).

package/skills/alloy-howtos/references/samples.md

@@ -1,156 +0,0 @@
-# Alloy samples
-
-## Kitchen sink
-
-See the [KitchenSink-v2 application on GitHub](https://github.com/tidev/kitchensink-v2) for Alloy samples in a full app.
-
-## Controller sample
-
-**index.js**
-```javascript
-// These "builtin" requires are detected by alloy compile process
-// Automatically included as Resources/alloy/animation.js and Resources/alloy/string.js
-const animation = require('alloy/animation');
-const string = require('alloy/string');
-
-function shake(e) {
-    animation.shake($.mover, 0, () => {
-        alert("Shake ended.");
-    });
-}
-
-function flash(e) {
-    animation.flash($.mover);
-}
-
-function trim(e) {
-    $.label.text = string.trim($.label.text);
-}
-
-if (OS_IOS) {
-    function flip(e) {
-        let front, back;
-        e.bubbleParent = false;
-        if (e.source === $.back) {
-            front = $.back;
-            back = $.front;
-        } else {
-            front = $.front;
-            back = $.back;
-        }
-        animation.flipHorizontal(front, back, 500, (e) => {
-            Ti.API.info('flipped');
-        });
-    }
-}
-
-$.index.open();
-
-// Runtime unit tests
-if (!ENV_PROD) {
-    require('specs/index')($);
-}
-```
-
-## Conditional statements in views
-
-Alloy separates business logic (controllers) from UI definition (XML/TSS). A common challenge is showing or hiding content based on app state (for example, login status).
-
-> **💡 TSS defaults**
-> The samples below assume some additional TSS: views and windows use a vertical layout, and the `View` tag has a default height and width of `Ti.UI.SIZE`.
-
-### Problems with traditional approaches
-
-**Approach 1: show/hide (in controller)**
-```javascript
-if (Alloy.Globals.isLoggedIn()) {
-    $.loggedIn.show();
-    $.notLoggedIn.hide();
-} else {
-    $.loggedIn.hide();
-    $.notLoggedIn.show();
-}
-```
-**Problem:** Both views render when the window opens. If the user isn't logged in, there is empty space where the logged-in view was.
-
-**Approach 2: setHeight (in controller)**
-```javascript
-if (Alloy.Globals.isLoggedIn()) {
-    $.loggedIn.setHeight(Ti.UI.SIZE);
-    $.notLoggedIn.setHeight(0);
-} else {
-    $.loggedIn.setHeight(0);
-    $.notLoggedIn.setHeight(Ti.UI.SIZE);
-}
-```
-**Problem:** This works, but it forces you to manage height values (`Ti.UI.SIZE`) in JavaScript instead of TSS.
-
-### Solution: IF attributes in XML
-
-Use `if` attributes directly in the XML view. These conditions are evaluated before rendering.
-
-**index.xml**
-```xml
-<Alloy>
-    <Window>
-        <View>
-            <!-- Only one of these will ever be rendered -->
-            <View if="Alloy.Globals.isLoggedIn()" id="notLoggedIn" class="vertical">
-                 <Label text="Not logged in" />
-            </View>
-            <View if="!Alloy.Globals.isLoggedIn()" id="loggedIn" class="vertical">
-                <Label text="Logged in" />
-            </View>
-        </View>
-    </Window>
-</Alloy>
-```
-
-Benefits:
-- Only the view that matches the condition is rendered.
-- The UI is correct from the first frame.
-- No visibility logic in controllers.
-
-### Conditional queries in TSS
-
-Use `if` attributes in TSS definitions:
-
-```tss
-"#info[if=Alloy.Globals.isIos7Plus]": {
-    font: {
-        textStyle: Ti.UI.TEXT_STYLE_FOOTNOTE
-    }
-},
-"#title[if=Alloy.Globals.isIos7Plus]": {
-    top: "25dp",
-    font: {
-        textStyle: Ti.UI.TEXT_STYLE_HEADLINE
-    }
-},
-"#content[if=Alloy.Globals.isIos7Plus]": {
-    font: {
-        textStyle: Ti.UI.TEXT_STYLE_CAPTION1
-    }
-},
-"ScrollView[if=Alloy.Globals.iPhoneTall]": {
-    height: "500dp"
-}
-```
-
-### Data-binding with conditional queries
-
-Define custom methods in models and render based on those methods:
-
-**Model Method:** `shouldShowCommentRow()` returns `true`
-
-**XML View:**
-```xml
-<Alloy>
-    <TableViewRow id="commentRow" hasChild="false" if="$model.shouldShowCommentRow()" onClick="onSelectComment">
-        <Label id="commentPlaceholderLabel" class="commentRowPreviewLabel placeholderLabel" text="Ti.App.L('AddComment')" />
-        <Label id="commentRowLabel" class="commentRowPreviewLabel" text="{Comment}" />
-    </TableViewRow>
-</Alloy>
-```
-
-See `VIEWS_STYLES.md` in the `alloy-guides` skill (Custom Query Styles section) for more details.

package/skills/ti-api/SKILL.md

@@ -1,109 +0,0 @@
----
-name: ti-api
-description: "Titanium SDK complete API reference. Use when looking up properties, methods, events, constants, or type signatures for any Ti.* or Modules.* API. Covers Ti.UI, Ti.Android, Ti.App, Ti.Media, Ti.Network, Ti.Database, Ti.Filesystem, Ti.Geolocation, Ti.Contacts, Ti.Calendar, Global, and third-party modules (Map, BLE, NFC, Facebook, Identity, CoreMotion). AUTO-DETECT: If tiapp.xml exists in the project, this is a Titanium project — invoke this skill BEFORE writing any code that uses Ti.* APIs. Do NOT rely on training data for Titanium APIs; always check the reference files in this skill first."
-argument-hint: "[Ti.UI.Window | Ti.Network.HTTPClient | Modules.Map.View | ...]"
-allowed-tools: Read, Grep, Glob
----
-
-# Titanium API Reference
-
-Quick lookup for properties, methods, events, and constants across all Titanium SDK and module APIs.
-
-## How to use this skill
-
-1. Identify which namespace the API belongs to
-2. Look up the reference file in the table below
-3. Read the reference file for full property/method/event tables
-
-## Namespace Lookup
-
-| Namespace | Reference File | Contents |
-|-----------|---------------|----------|
-| Titanium.UI.View, Titanium.UI.Label, Titanium.UI.Button, Titanium.UI.ImageView, ... | [api-ui-views.md](references/api-ui-views.md) | Ti.UI Core Views (13 APIs) |
-| Titanium.UI.Window, Titanium.UI.NavigationWindow, Titanium.UI.TabGroup, Titanium.UI.Tab, ... | [api-ui-windows-navigation.md](references/api-ui-windows-navigation.md) | Ti.UI Windows & Navigation (7 APIs) |
-| Titanium.UI.TextField, Titanium.UI.TextArea, Titanium.UI.SearchBar, Titanium.UI.AttributedString, ... | [api-ui-text-input.md](references/api-ui-text-input.md) | Ti.UI Text & Input (9 APIs) |
-| Titanium.UI.ListView, Titanium.UI.ListItem, Titanium.UI.ListSection, Titanium.UI.ListViewScrollPosition, ... | [api-ui-lists.md](references/api-ui-lists.md) | Ti.UI Lists & Tables (8 APIs) |
-| Titanium.UI.Animation, Titanium.UI.Matrix2D, Titanium.UI.Matrix3D, Titanium.UI.WebView, ... | [api-ui-extras.md](references/api-ui-extras.md) | Ti.UI Extras (13 APIs) |
-| Titanium.UI.iOS | [api-ui-ios.md](references/api-ui-ios.md) | Ti.UI.iOS (36 APIs) |
-| Titanium.UI.iOS | [api-ui-ios-animator.md](references/api-ui-ios-animator.md) | Ti.UI.iOS Animator & Physics (8 APIs) |
-| Titanium.UI.Android, Titanium.UI.iPad | [api-ui-android.md](references/api-ui-android.md) | Ti.UI.Android (10 APIs) |
-| Titanium.Android, Titanium.Android.ActionBar, Titanium.Android.Activity, Titanium.Android.BigPictureStyle, ... | [api-android.md](references/api-android.md) | Ti.Android (17 APIs) |
-| Titanium.App, Titanium.App.Android, Titanium.App.Properties, Titanium.App.iOS, ... | [api-app-platform.md](references/api-app-platform.md) | Ti.App & Ti.Platform (18 APIs) |
-| Titanium.Media, Titanium.Media.Android, Titanium.Media.AudioPlayer, Titanium.Media.AudioRecorder, ... | [api-media.md](references/api-media.md) | Ti.Media (9 APIs) |
-| Titanium.Database, Titanium.Database.DB, Titanium.Database.ResultSet, Titanium.Filesystem, ... | [api-data-network.md](references/api-data-network.md) | Ti.Network, Ti.Database & Ti.Filesystem (14 APIs) |
-| Titanium.Calendar, Titanium.Calendar.Alert, Titanium.Calendar.Attendee, Titanium.Calendar.Calendar, ... | [api-services.md](references/api-services.md) | Ti.Geolocation, Ti.Contacts, Ti.Calendar & Ti.WatchSession (15 APIs) |
-| Titanium, Titanium.UI, Titanium.API, Titanium.Accelerometer, ... | [api-core.md](references/api-core.md) | Ti Core (16 APIs) |
-| Titanium.XML, Titanium.XML.Attr, Titanium.XML.CDATASection, Titanium.XML.CharacterData, ... | [api-xml-global.md](references/api-xml-global.md) | Ti.XML & Global (25 APIs) |
-| Modules.Map, Modules.Map.Annotation, Modules.Map.Camera, Modules.Map.Circle, ... | [api-modules-map.md](references/api-modules-map.md) | Modules: Map (11 APIs) |
-| Modules.Applesignin, Modules.Applesignin.LoginButton, Modules.Barcode, Modules.Crypto, ... | [api-modules-social-misc.md](references/api-modules-social-misc.md) | Modules: Facebook, Identity, Crypto & More (16 APIs) |
-| Modules.BLE, Modules.BLE.Beacon, Modules.BLE.BeaconIdentityConstraint, Modules.BLE.BeaconRegion, ... | [api-modules-ble-bluetooth.md](references/api-modules-ble-bluetooth.md) | Modules: BLE & Bluetooth (20 APIs) |
-| Modules.Nfc, Modules.Nfc.MifareTagTechnology, Modules.Nfc.NativeTagTechnology, Modules.Nfc.NdefMessage, ... | [api-modules-nfc.md](references/api-modules-nfc.md) | Modules: NFC (28 APIs) |
-| Modules.CoreMotion, Modules.CoreMotion.Accelerometer, Modules.CoreMotion.Altimeter, Modules.CoreMotion.DeviceMotion, ... | [api-modules-coremotion-urlsession.md](references/api-modules-coremotion-urlsession.md) | Modules: CoreMotion & URLSession (12 APIs) |
-
-## Quick lookup by common task
-
-| Task | API | Reference |
-|------|-----|-----------|
-| Create a window | Ti.UI.Window | [api-ui-windows-navigation.md](references/api-ui-windows-navigation.md) |
-| HTTP request | Ti.Network.HTTPClient | [api-data-network.md](references/api-data-network.md) |
-| Show an alert | Ti.UI.AlertDialog | [api-ui-windows-navigation.md](references/api-ui-windows-navigation.md) |
-| Play audio | Ti.Media.AudioPlayer | [api-media.md](references/api-media.md) |
-| Read a file | Ti.Filesystem.File | [api-data-network.md](references/api-data-network.md) |
-| SQLite query | Ti.Database.DB | [api-data-network.md](references/api-data-network.md) |
-| GPS location | Ti.Geolocation | [api-services.md](references/api-services.md) |
-| Push notification | Ti.App.iOS | [api-app-platform.md](references/api-app-platform.md) |
-| ListView | Ti.UI.ListView | [api-ui-lists.md](references/api-ui-lists.md) |
-| Camera/gallery | Ti.Media | [api-media.md](references/api-media.md) |
-| Map view | Modules.Map.View | [api-modules-map.md](references/api-modules-map.md) |
-| BLE scanning | Modules.BLE | [api-modules-ble-bluetooth.md](references/api-modules-ble-bluetooth.md) |
-| Animation | Ti.UI.Animation | [api-ui-extras.md](references/api-ui-extras.md) |
-| WebView | Ti.UI.WebView | [api-ui-extras.md](references/api-ui-extras.md) |
-| Contacts | Ti.Contacts | [api-services.md](references/api-services.md) |
-
-## Reading the reference tables
-
-Each API entry includes:
-
-- **Summary** — one-line description
-- **Extends** — parent type (inherited properties/methods not repeated)
-- **Platforms** — `both` (android + ios), `android`, or `ios`
-- **Properties table** — unique properties (not inherited), with type, default, platform
-- **Methods table** — unique methods with parameters, return type, platform
-- **Events table** — unique events with platform and description
-- **Related Types** — inline struct definitions used by that API
-
-### Property counts
-
-Tables show `unique: X/Y` where X is properties defined on this class and Y is total including inherited. To see inherited properties, check the parent class.
-
-## API coverage
-
-| Category | APIs | Reference File |
-|----------|------|---------------|
-| Ti.UI Core Views | 13 | api-ui-views.md |
-| Ti.UI Windows & Navigation | 7 | api-ui-windows-navigation.md |
-| Ti.UI Text & Input | 9 | api-ui-text-input.md |
-| Ti.UI Lists & Tables | 8 | api-ui-lists.md |
-| Ti.UI Extras | 13 | api-ui-extras.md |
-| Ti.UI.iOS | 36 | api-ui-ios.md |
-| Ti.UI.iOS Animator & Physics | 8 | api-ui-ios-animator.md |
-| Ti.UI.Android | 10 | api-ui-android.md |
-| Ti.Android | 17 | api-android.md |
-| Ti.App & Ti.Platform | 18 | api-app-platform.md |
-| Ti.Media | 9 | api-media.md |
-| Ti.Network, Ti.Database & Ti.Filesystem | 14 | api-data-network.md |
-| Ti.Geolocation, Ti.Contacts, Ti.Calendar & Ti.WatchSession | 15 | api-services.md |
-| Ti Core | 16 | api-core.md |
-| Ti.XML & Global | 25 | api-xml-global.md |
-| Modules: Map | 11 | api-modules-map.md |
-| Modules: Facebook, Identity, Crypto & More | 16 | api-modules-social-misc.md |
-| Modules: BLE & Bluetooth | 20 | api-modules-ble-bluetooth.md |
-| Modules: NFC | 28 | api-modules-nfc.md |
-| Modules: CoreMotion & URLSession | 12 | api-modules-coremotion-urlsession.md |
-
-## Related skills
-
-- **ti-ui** — UI/UX patterns, layout strategies, performance tips (narrative)
-- **ti-expert** — Architecture patterns, memory management, anti-patterns
-- **ti-howtos** — Integration guides for push, camera, maps, networking
-- **ti-guides** — SDK fundamentals, tiapp.xml, Hyperloop