@maccesar/titools 2.0.6 → 2.2.0

package/skills/ti-guides/references/alloy-cli-advanced.md

@@ -1,84 +0,0 @@
-# Alloy CLI Reference
-
-The `alloy` command is the primary interface for managing Alloy metadata and automation.
-
-## 1. Internationalization (i18n) Extraction
-
-Instead of manually managing `strings.xml`, use the `extract-i18n` command to automatically scan your XML, JS, and TSS files for `L()` or `Ti.Locale.getString()` calls.
-
-### Syntax
-```bash
-# Preview the strings found in the project
-alloy extract-i18n [language]
-
-# Create or update the strings.xml file
-alloy extract-i18n [language] --apply
-```
-
-### Key Benefits
-- **Accuracy**: Ensures all strings used in code are present in the translation files
-- **Safety**: The `--apply` flag only adds new entries and never deletes or overwrites existing ones
-- **Efficiency**: Faster than manual entry and prevents human error
-
-## 2. Code Generation
-
-Generate components from templates to speed up development:
-
-```bash
-# Create a new controller
-alloy generate controller <name>
-
-# Generate other component types
-alloy generate view <name>
-alloy generate model <name>
-alloy generate widget <name>
-alloy generate migration <name>
-```
-
-## 3. Installation Commands
-
-Install specialized components or themes:
-
-```bash
-# Install a widget or theme
-alloy install widget <path>
-alloy install theme <path>
-```
-
-## 4. Project Conversion
-
-Convert a Classic Titanium project to Alloy:
-
-```bash
-alloy new
-```
-
-## 5. Configuration Files
-
-### `config.json`
-Global app configuration file. Can store:
-- Theme settings (`theme: "theme_name"`)
-- Environment variables
-- Per-platform themes
-- App-specific metadata
-
-### `alloy.js`
-Global initializer executed before any controllers. Perfect for:
-- Creating `Alloy.Collections`
-- Setting up `Alloy.Globals`
-- Initializing singletons
-- Configuring global event listeners
-
-### `alloy.jmk`
-Build configuration file for pre-compile and post-compile hooks:
-```javascript
-task('pre:compile', (event, logger) => {
-  // Run before compilation
-  // Example: Auto-run PurgeTSS
-});
-```
-
-Common use cases:
-- Auto-running PurgeTSS
-- Custom asset processing
-- Environment-specific configurations

package/skills/ti-guides/references/alloy-data-mastery.md

@@ -1,29 +0,0 @@
-# Alloy Data Mastery: Sync Adapters and Binding
-
-## 1. Sync Adapters
-Sync adapters connect Backbone Models to persistent storage.
-- **Ready-Made Adapters**:
-  - `sql`: SQLite (Android/iOS). Supports `query` in `fetch()` and `idAttribute`.
-  - `properties`: `Ti.App.Properties` storage.
-- **Custom Adapters**: Created in `app/lib/alloy/sync`. Requires `sync` function implementation.
-- **Migrations**: Incremental database changes. Named `YYYYMMDDHHmmss_model.js`.
-  - **CRITICAL**: Do not close the `db` handle or open a second instance within a migration.
-
-## 2. Data Binding Principles
-- **Collection Binding**: Bind a collection to a container (ListView, TableView, ScrollableView).
-  - Mandatory: `dataCollection` attribute.
-  - Optional: `dataTransform` (JSON mapping), `dataFilter` (filtering models), `dataFunction` (manual update trigger).
-- **Model Binding**: Bind a single model to a view (e.g., `<Label text="{model.name}" />`).
-- **Memory Management**: **CRITICAL**: You MUST call `$.destroy()` on the controller's `close` event to unbind Backbone listeners and prevent leaks.
-
-## 3. High-Performance Transformations
-- **Lazy Transformation**: Use `Object.defineProperty` in `extendModel` to compute transformations only when accessed.
-  ```javascript
-    transform() {
-      const t = this.toJSON();
-      Object.defineProperty(t, 'friendlyDate', {
-        get: () => moment(t.date).fromNow()
-      });
-      return t;
-    }
-  ```

package/skills/ti-guides/references/alloy-widgets-and-themes.md

@@ -1,19 +0,0 @@
-# Alloy Widgets and Themes
-
-## 1. Widgets (Self-contained components)
-- **Structure**: Mirror the `app` directory. Main controller is `widget.js`.
-- **Public API**: Methods prefixed with `$` are public (e.g., `$.init = (args) => {}`).
-- **Resource Access**: Use `WPATH()` for widget assets and libs (e.g., `require(WPATH('helper'))`).
-- **Nesting**: Widgets can contain other widgets via `<Widget src="widgetName" name="subController" />`.
-
-## 2. Styling Priorities (Low to High)
-1. `app.tss` (Global)
-2. `themes/<name>/styles/app.tss` (Theme Global)
-3. `styles/<controller>.tss` (Controller Style)
-4. `themes/<name>/styles/<controller>.tss` (Theme Controller Style)
-5. XML attributes (Inline Style)
-
-## 3. Themes
-- Located in `app/themes/<theme_name>`.
-- Merges `config.json`, `i18n`, and `styles`. Overwrites `assets` and `lib`.
-- Configured in `config.json` via the `theme` key. Supports per-platform themes.