@maccesar/titools 2.2.4 → 2.2.8

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

@@ -1,10 +1,10 @@
-# Alloy Command-Line Interface Reference
+# Alloy command-line interface reference
 
-The Alloy CLI is a command-line tool for managing and building Alloy projects.
+The Alloy CLI manages and builds Alloy projects.
 
 ## Installation
 
-The Alloy CLI is automatically installed when installing the `alloy` package.
+The Alloy CLI is installed when you install the `alloy` package.
 
 ### Manual Installation
 
@@ -19,7 +19,7 @@ For a specific version:
 sudo npm install -g alloy@1.10.0
 ```
 
-### Bleeding Edge Installation
+### Development install
 
 ```bash
 git clone https://github.com/tidev/alloy.git
@@ -71,7 +71,7 @@ alloy generate <component> [--widgetname <widget_name>] [--outputPath <output_pa
 | `-f, --force`             | Force execution                                  |
 | `-n, --no-colors`         | Disable color output                             |
 
-#### Model Format
+#### Model format
 
 Select adapter type:
 - `sql` - SQLite database for Android/iOS (also generates a migration file)
@@ -125,29 +125,29 @@ Compiler options reference the `event.alloyConfig` object in [Build Configuratio
 
 Use `titanium build` command to run Alloy projects. See [Titanium Command-Line Interface Reference](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_Guide/Titanium_Command-Line_Interface_Reference/).
 
-:::tip COMMON ti build PITFALLS
+:::tip Common ti build pitfalls
 
-**❌ Using `-C` flag without UDID:**
+Using `-C` flag without UDID:
 ```bash
-# WRONG - Prompts for simulator selection interactively
+# Prompts for simulator selection interactively
 ti build -p ios -T simulator -C
 ```
 
-**✅ Correct approach for simulator:**
+Correct approach for simulator:
 ```bash
-# GOOD - Runs on default simulator
+# Runs on default simulator
 ti build -p ios -T simulator
 ```
 
-**❌ Using `--no-prompt` incorrectly:**
+Using `--no-prompt` incorrectly:
 ```bash
 # Still may prompt for device selection if not specific
 ti build -p ios --no-prompt
 ```
 
-**✅ Always specify target:**
+Always specify target:
 ```bash
-# GOOD - Clear target specification
+# Clear target specification
 ti build -p ios -T simulator --no-prompt
 ```
 
@@ -184,7 +184,7 @@ Supported functions:
 - `Ti.Locale.getString()`
 - `L()`
 
-Usage Examples:
+Usage examples:
 ```bash
 # Preview changes for default (English)
 alloy extract-i18n

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

@@ -1,8 +1,8 @@
-# Alloy Configuration Files Reference
+# Alloy configuration files reference
 
-## Build Configuration File (alloy.jmk)
+## Build configuration file (alloy.jmk)
 
-Alloy provides hooks to customize compilation using a JS Makefile (JMK).
+Alloy exposes hooks to customize compilation with a JS Makefile (JMK).
 
 **Location:** `app/alloy.jmk`
 
@@ -18,7 +18,7 @@ task('post:compile', (event, logger) => {
 });
 ```
 
-### Compiler Tasks (Event Names)
+### Compiler tasks (event names)
 
 | Task             | When Called                                               |
 | ---------------- | --------------------------------------------------------- |
@@ -27,7 +27,7 @@ task('post:compile', (event, logger) => {
 | `post:compile`   | After compiler finishes, before exit                      |
 | `compile:app.js` | After compiling `app.js`, before writing to disk          |
 
-### Event Object
+### Event object
 
 | Property       | Type    | Description                                                                                                                                                                                                         |
 | -------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -41,9 +41,9 @@ task('post:compile', (event, logger) => {
 | `code`         | String  | *(compile:app.js only)* Contents of `app.js`                                                                                                                                                                        |
 | `appJSFile`    | String  | *(compile:app.js only)* Absolute path to `app.js`                                                                                                                                                                   |
 
-### Logger Object
+### Logger object
 
-The `logger` object provides methods and properties to control compilation log output.
+The `logger` object controls compilation log output.
 
 #### Properties
 
@@ -69,13 +69,13 @@ The `logger` object provides methods and properties to control compilation log o
 
 ---
 
-## Global Initializer (alloy.js)
+## Global initializer (alloy.js)
 
 **Location:** `app/alloy.js`
 
-Executed before any controllers load. Use it to set up globals and singletons.
+Runs before any controllers load. Use it to set up globals and singletons.
 
-**Common uses:**
+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)
@@ -95,11 +95,11 @@ Alloy.Globals.alert = (title, message) => {
 
 ---
 
-## Project Configuration File (config.json)
+## Project configuration file (config.json)
 
 **Location:** `app/config.json`
 
-Alloy uses `config.json` to specify global values, conditional environment and platform values, and widget dependencies.
+Alloy uses `config.json` for global values, environment and platform overrides, and widget dependencies.
 ### Objects
 
 | Object            | Description                                                 |
@@ -114,9 +114,9 @@ Alloy uses `config.json` to specify global values, conditional environment and p
 | `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 (e.g., `os:ios env:production`) override single values.
+**Precedence:** `os` > `env` > `global`. Combinations (for example, `os:ios env:production`) override single values.
 
-**Runtime Access:** Values are accessible at runtime via `Alloy.CFG.<key>`.
+**Runtime access:** Values are available at runtime via `Alloy.CFG.<key>`.
 
 **Example:**
 
@@ -136,11 +136,11 @@ Alloy uses `config.json` to specify global values, conditional environment and p
 }
 ```
 
-Accessing values: `Ti.API.info(Alloy.CFG.foo)` — on iPhone simulator this returns `6`.
+Accessing values: `Ti.API.info(Alloy.CFG.foo)` on iPhone simulator returns `6`.
 
 ---
 
-## Widget Configuration File (widget.json)
+## Widget configuration file (widget.json)
 
 **Location:** Root directory of the widget. Follows the npm `package.json` format with a few exceptions.
 ### Keys

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

@@ -1,16 +1,16 @@
-# Creating Custom Tags in Titanium with Alloy
+# Creating custom tags in Titanium with Alloy
 
-Custom tags allow you to create reusable UI components without the overhead of widgets. They are an incredibly fast way to build a suite of controls that are as easy to use as dropping a file into the `app/lib` folder.
+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?
+## Why use custom tags?
 
-When building cross-platform applications, you often need specific UI controls (like a web-style checkbox) that don't exist natively. You have three main approaches:
+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-pasting code into every view. Not reusable and messy.
-2.  **Widgets:** Highly reusable but requires a folder structure and `dependencies` in `config.json`.
-3.  **Custom Tags:** Single file in `app/lib/`, no config dependency, and very simple to share. They reduce the amount of platform-specific code in your views, keeping them simple and readable.
+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
+## Basic setup
 
 1.  Create a file in `app/lib/` (e.g., `checkbox.js`)
 2.  Export a `create<TagName>` function
@@ -24,9 +24,9 @@ When building cross-platform applications, you often need specific UI controls (
     onCaptionClick="doShowTerms"
     onChange="onCheckChange" />
 ```
-The `module` attribute tells Alloy to look in `checkbox.js` for a `createCheckBox` function, pass it the arguments from XML/TSS, and expect a `Ti.UI.*` component back.
+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
+## Robust example: CheckBox
 
 **app/lib/checkbox.js**
 ```javascript
@@ -101,9 +101,9 @@ exports.createCheckBox = args => {
 };
 ```
 
-## Global Module Override
+## Global module override
 
-Apply a module to all tags in a view by updating the `Alloy` tag. Alloy will check your specified file for any tag creation overrides before falling back to default implementations:
+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">
@@ -113,9 +113,9 @@ Apply a module to all tags in a view by updating the `Alloy` tag. Alloy will che
     </Window>
 </Alloy>
 ```
-This is powerful for adding default colors or properties (like a black default color for Android Labels) across an entire project.
+This is useful for adding default colors or properties (for example, a black default color for Android Labels) across a project.
 
-## Key Points
+## Key points
 
 | Aspect        | Description                                                   |
 | ------------- | ------------------------------------------------------------- |
@@ -136,9 +136,9 @@ const checkbox = require("checkbox").createCheckBox({
 win.add(checkbox);
 ```
 
-This works because custom tags are standard CommonJS modules — the `module` attribute in XML is just a convenience.
+This works because custom tags are standard CommonJS modules. The `module` attribute in XML is a convenience.
 
-## Custom Tags vs Widgets
+## Custom tags vs widgets
 
 | Custom Tags                           | Widgets                                  |
 | ------------------------------------- | ---------------------------------------- |

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

@@ -1,21 +1,17 @@
-# Alloy Debugging and Troubleshooting
-
-## Overview
-
-This guide covers debugging and troubleshooting Alloy applications.
+# Alloy debugging and troubleshooting
 
 ## Debugging
 
-### Compiler Error Messages
+### Compiler error messages
 
-The Alloy compiler generates error messages for syntax errors in JavaScript, JSON, TSS and XML files. Error messages report:
+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: No app.js found
 
 **Error:** `[ERROR] No app.js found. Ensure the app.js file exists in your project's Resources directory.`
 
@@ -24,13 +20,13 @@ The Alloy compiler generates error messages for syntax errors in JavaScript, JSO
 alloy compile --config platform=<platform>
 ```
 
-### Android: Images, HTML and Assets Not Displaying
+### 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
+### Android runtime error: cannot call method of undefined
 
 **Error:** `Uncaught TypeError: Cannot call method xxx of undefined`
 
@@ -38,7 +34,7 @@ alloy compile --config platform=<platform>
 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
+### Android runtime error: Alloy is not defined
 
 **Error:** `Uncaught ReferenceError: Alloy is not defined`
 
@@ -49,7 +45,7 @@ alloy compile --config platform=<platform>
 const Alloy = require('alloy');
 ```
 
-### iOS Application Error: Invalid Method Passed to UIModule
+### iOS application error: invalid method passed to UIModule
 
 **Error:** `invalid method (xxx) passed to UIModule (unknown file)`
 
@@ -57,7 +53,7 @@ const Alloy = require('alloy');
 
 **Solution:** Use the `platform` attribute in the view to enforce platform-specific objects.
 
-### iOS Application Error: Undefined is Not an Object
+### iOS application error: undefined is not an object
 
 **Error:** `undefined is not an object (evaluating $.xxx.open) (unknown file)`
 
@@ -65,14 +61,14 @@ const Alloy = require('alloy');
 
 **Solution:** The controller cannot use `$.<controller_name>` to reference it; use the assigned ID instead.
 
-## Getting Help
+## 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
+## 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

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

@@ -1,10 +1,10 @@
-# Alloy Samples
+# Alloy samples
 
-## Kitchen Sink
+## Kitchen sink
 
-See the [KitchenSink-v2 application on GitHub](https://github.com/tidev/kitchensink-v2) for Alloy samples in a real app.
+See the [KitchenSink-v2 application on GitHub](https://github.com/tidev/kitchensink-v2) for Alloy samples in a full app.
 
-## Controller Sample
+## Controller sample
 
 **index.js**
 ```javascript
@@ -52,15 +52,15 @@ if (!ENV_PROD) {
 }
 ```
 
-## Conditional Statements in Views
+## Conditional statements in views
 
-Alloy separates business logic (controllers) from UI definition (XML/TSS). A common challenge is showing/hiding content based on app state (e.g., login status).
+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).
 
-:::tip TSS DEFAULTS
+:::tip 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`.
 :::
 
-### The Problem with Traditional Approaches
+### Problems with traditional approaches
 
 **Approach 1: show/hide (in controller)**
 ```javascript
@@ -72,7 +72,7 @@ if (Alloy.Globals.isLoggedIn()) {
     $.notLoggedIn.show();
 }
 ```
-**Problem:** Both views render initially when the window opens. If the user isn't logged in, there's a big white space where the logged-in view was originally placed before it was hidden.
+**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
@@ -84,11 +84,11 @@ if (Alloy.Globals.isLoggedIn()) {
     $.notLoggedIn.setHeight(Ti.UI.SIZE);
 }
 ```
-**Problem:** This works but is messy and forces you to manage specific height values (`Ti.UI.SIZE`) in JavaScript logic, which should ideally stay in TSS.
+**Problem:** This works, but it forces you to manage height values (`Ti.UI.SIZE`) in JavaScript instead of TSS.
 
-### The Solution: IF Attributes in XML
+### Solution: IF attributes in XML
 
-Use `if` attributes directly within the XML View. These conditions are evaluated **before** rendering, providing a smoother experience.
+Use `if` attributes directly in the XML view. These conditions are evaluated before rendering.
 
 **index.xml**
 ```xml
@@ -107,14 +107,14 @@ Use `if` attributes directly within the XML View. These conditions are evaluated
 </Alloy>
 ```
 
-**Benefits:**
-- **No White Space:** Only the view that matches the condition is rendered to the UI.
-- **Pre-rendering Evaluation:** The UI is correct from the first frame.
-- **Cleaner Code:** No need for visibility logic in your controllers.
+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
+### Conditional queries in TSS
 
-Use IF attributes in TSS definitions:
+Use `if` attributes in TSS definitions:
 
 ```tss
 "#info[if=Alloy.Globals.isIos7Plus]": {
@@ -138,7 +138,7 @@ Use IF attributes in TSS definitions:
 }
 ```
 
-### Data-Binding with Conditional Queries
+### Data-binding with conditional queries
 
 Define custom methods in models and render based on those methods:
 

package/skills/purgetss/SKILL.md

@@ -40,7 +40,7 @@ This skill automatically detects PurgeTSS usage when invoked and provides utilit
 ├─ fonts/              # Custom font files (.ttf, .otf)
 ├─ styles/
 │  ├─ definitions.css  # For VS Code IntelliSense
-│  └─ utilities.tss     # All PurgeTSS utility classes
+│  └─ utilities.tss     # All PurgeTSS utility classes (renamed from tailwind.tss in v7.3)
 └─ config.cjs          # Theme configuration
 
 ./app/styles/
@@ -117,6 +117,16 @@ purgetss create 'MyApp' -d -v fa
 # -v: Copy icon fonts (fa, mi, ms, f7)
 ```
 
+## What's New in v7.3.x
+
+- `tailwind.tss` was renamed to `utilities.tss` (update any scripts or references).
+- XML syntax validation now runs before processing and reports line-level errors (for example, missing `<`).
+- `deviceInfo()` works in both Alloy and Classic (no `Alloy.isTablet`/`Alloy.isHandheld` dependency).
+- Node.js 20+ is required.
+- Font Awesome 7 is supported, including the new `--fa:` CSS custom properties.
+- VS Code: `KevinYouu.tailwind-raw-reorder-tw4` is recommended for class ordering.
+- If you hit issues after upgrading, try: `npm uninstall -g purgetss && npm install -g purgetss`.
+
 :::tip NEW PROJECT: Clean Up Default app.tss
 For new projects created with `purgetss create`, the default `app/styles/app.tss` contains a large commented template.
 

package/skills/purgetss/references/animation-system.md

@@ -171,7 +171,7 @@ The `open` and `close` methods provide a clear and straightforward way to manage
 
 By using these methods, you can ensure consistent and manageable animation behavior across your application, as opposed to using the `play` or `toggle` methods, which alternate between the `open` and `close` states based on the current state of the view.
 
-This explicit control helps in scenarios where the exact state of the view is crucial for the desired user experience or application logic.
+This explicit control helps in scenarios where the exact state of the view is important for the UI or application logic.
 
 ### `open(views, [callback])`
 

package/skills/purgetss/references/cli-commands.md

@@ -1,9 +1,9 @@
 # PurgeTSS CLI Commands Guide
 
-PurgeTSS provides a comprehensive suite of CLI commands for project setup, asset management, and development workflow automation.
+PurgeTSS provides a full set of CLI commands for project setup, asset management, and development workflow automation.
 
 :::info What's New in v7.2.x
-**FontAwesome 7 & Major Optimization**: PurgeTSS v7.2 introduces full support for **FontAwesome 7**, including the new CSS custom properties format. This version also features a significant reduction in installation size and a complete internal restructuring for better performance and maintainability.
+**FontAwesome 7 & Performance Updates**: PurgeTSS v7.2 adds full support for **FontAwesome 7**, including the new CSS custom properties format. It also reduces installation size and refactors internals for performance and maintainability.
 
 **Key Changes:**
 - **Node.js 20+** required (due to "inquirer" v13 upgrade)
@@ -149,7 +149,7 @@ purgetss w -o
 
 **Default behavior:** Activates auto-purge (runs on every compile)
 
-This functionality is particularly valuable when used with LiveView, as it automatically purges your project whenever you make changes, providing immediate feedback and significantly speeding up your prototyping process.
+This is especially useful with LiveView: it auto-purges on changes, gives fast feedback, and speeds up prototyping.
 
 **What it installs in `alloy.jmk`:**
 ```javascript

package/skills/purgetss/references/customization-deep-dive.md

@@ -62,7 +62,7 @@ purge: {
 **`mode: 'all'` (default)**
 - Scans EVERYWHERE in XML files (comments, attributes, classes, IDs, Ti Elements)
 - **REQUIRED** if you want PurgeTSS to parse any Ti Elements styled in `config.cjs`
-- Most comprehensive but slightly slower
+- Most complete but a bit slower
 
 **`mode: 'class'`**
 - Searches only in `class` and ID attributes in XML files

package/skills/purgetss/references/dynamic-component-creation.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-When creating components dynamically in Controllers (not declaratively in XML), PurgeTSS provides two powerful methods to apply utility classes:
+When creating components dynamically in Controllers (not declaratively in XML), PurgeTSS provides two methods to apply utility classes:
 
 1. **`$.UI.create()`** - Create components with PurgeTSS classes (Recommended)
 2. **`Alloy.createStyle()` + `applyProperties()`** - Apply PurgeTSS styles to existing components

package/skills/purgetss/references/icon-fonts.md

@@ -84,6 +84,10 @@ Font Awesome 7 uses different style prefixes:
 <Label class="fab fa-twitter fa-facebook fa-github" />
 ```
 
+:::tip
+PurgeTSS handles Font Awesome 7 CSS custom properties automatically (the `--fa:` format), so you do not need to edit icon CSS by hand.
+:::
+
 ### Material Icons
 
 ```xml

package/skills/purgetss/references/installation-setup.md

@@ -8,6 +8,13 @@ PurgeTSS must be installed globally and initialized within each Titanium Alloy p
 PurgeTSS has been thoroughly tested and proven to be compatible with Node 20.0.0 or higher.
 :::
 
+## Upgrade Notes (v7.3.x)
+
+- `tailwind.tss` was renamed to `utilities.tss`. Update any scripts or paths that reference the old filename.
+- PurgeTSS validates XML syntax before processing and reports line-level errors (for example, missing `<`).
+- `deviceInfo()` now works in both Alloy and Classic projects (no `Alloy.isTablet`/`Alloy.isHandheld` dependency).
+- If you hit issues after upgrading, try a clean reinstall: `npm uninstall -g purgetss && npm install -g purgetss`.
+
 ## Global Installation
 
 Install PurgeTSS globally on your machine using NPM:
@@ -69,7 +76,7 @@ PurgeTSS creates a `purgetss` folder at the root of your project:
 **File descriptions:**
 
 - **`config.cjs`**: Where you customize colors, spacing, fonts, border radius, and add custom rules for Ti Elements
-- **`styles/utilities.tss`**: All Tailwind-like utility classes + any custom classes from `config.cjs`
+- **`styles/utilities.tss`**: All utility classes + any custom classes from `config.cjs`
 - **`styles/definitions.css`**: Special CSS file incorporating ALL classes from `utilities.tss`, `_app.tss`, remaining `.tss` files, and `fonts.tss`. Used by VS Code extension for IntelliSense
 - **`fonts/`**: Directory for custom fonts (Icon, Serif, Sans-Serif, Cursive, Fantasy, Monospace). Use `purgetss build-fonts` after adding fonts
 

package/skills/purgetss/references/migration-guide.md

@@ -14,6 +14,10 @@ Before migrating, evaluate styling in the current codebase:
 | Manual 2D Matrix animations                  | PurgeTSS Animation component              |
 | Platform conditionals in controllers         | PurgeTSS platform modifiers (`ios:mt-10`) |
 
+:::info v7.3 Upgrade Note
+If your project or scripts reference `tailwind.tss`, update them to `utilities.tss` (the file was renamed in v7.3).
+:::
+
 ## Step 1: Initialize PurgeTSS
 
 ```bash