@maccesar/titools 4.4.0 → 4.4.2

package/skills/ti-expert/references/theming.md

@@ -1,7 +1,6 @@
 # Theming and dark mode
 
-Choose the styling path from the project, not from personal memory. Semantic
-roles are the shared contract; PurgeTSS or standard Alloy materializes them.
+Choose the styling path from the project, not from personal memory. Semantic roles are the shared contract; PurgeTSS or standard Alloy materializes them.
 
 ## Contents
 
@@ -19,16 +18,13 @@ roles are the shared contract; PurgeTSS or standard Alloy materializes them.
 1. Detect `purgetss/` or `purgetss/config.cjs`.
 2. If detected, invoke the `purgetss` skill before writing any class or style.
 3. If not detected, use standard Alloy TSS and Titanium semantic colors.
-4. Use `Alloy.Globals` for a runtime palette only when the product requires
-   custom themes beyond the semantic light/dark/system model.
+4. Use `Alloy.Globals` for a runtime palette only when the product requires custom themes beyond the semantic light/dark/system model.
 
-Do not mix these paths accidentally. In particular, never teach a PurgeTSS
-project to maintain the generated `app/styles/app.tss` by hand.
+Do not mix these paths accidentally. In particular, never teach a PurgeTSS project to maintain the generated `app/styles/app.tss` by hand.
 
 ## Semantic color contract
 
-Name colors by purpose rather than appearance. A practical design-system
-contract includes:
+Name colors by purpose rather than appearance. A practical design-system contract includes:
 
 - app background and elevated surface;
 - primary and secondary text;
@@ -62,28 +58,20 @@ Example:
 }
 ```
 
-Titanium resolves a semantic color name when a color-accepting property uses
-that name. Keep component APIs tone-based (`neutral`, `success`, `warning`,
-`error`) and map tones to semantic roles inside the visual layer. Do not pass
-raw brand hex values through business controllers.
+Titanium resolves a semantic color name when a color-accepting property uses that name. Keep component APIs tone-based (`neutral`, `success`, `warning`, `error`) and map tones to semantic roles inside the visual layer. Do not pass raw brand hex values through business controllers.
 
 ## PurgeTSS projects
 
-The `purgetss` skill is the source of truth for supported classes, configuration,
-appearance behavior, and commands. Apply these integration rules:
+The `purgetss` skill is the source of truth for supported classes, configuration, appearance behavior, and commands. Apply these integration rules:
 
-- Map semantic color names under `theme.extend.colors` in
-  `purgetss/config.cjs`.
+- Map semantic color names under `theme.extend.colors` in `purgetss/config.cjs`.
 - Use verified utility classes in Alloy XML.
 - Configure `options.widgets: true` when Widgets contain utility classes.
 - Prefer `config.cjs` for reusable custom rules.
 - Treat `app/styles/app.tss` as generated output and never edit it.
-- Keep only truly specific properties in Widget/controller TSS when no verified
-  utility exists.
-- Use the PurgeTSS Appearance module for light/dark/system selection instead of
-  creating a competing mode service.
-- Read the current PurgeTSS references before naming any utility. Similarity to
-  Tailwind is not evidence that a class exists.
+- Keep only truly specific properties in Widget/controller TSS when no verified utility exists.
+- Use the PurgeTSS Appearance module for light/dark/system selection instead of creating a competing mode service.
+- Read the current PurgeTSS references before naming any utility. Similarity to Tailwind is not evidence that a class exists.
 
 Conceptual mapping only; verify the actual PurgeTSS syntax before use:
 
@@ -102,8 +90,7 @@ module.exports = {
 }
 ```
 
-After generation, inspect the final `app.tss` section for unused or unsupported
-classes. A clean build that still lists a new unsupported class is not complete.
+After generation, inspect the final `app.tss` section for unused or unsupported classes. A clean build that still lists a new unsupported class is not complete.
 
 ## Standard Alloy projects
 
@@ -133,23 +120,17 @@ Example:
 }
 ```
 
-Do not copy a large utility system into manual TSS. Create only the small set of
-selectors the app actually uses.
+Do not copy a large utility system into manual TSS. Create only the small set of selectors the app actually uses.
 
 ## Alloy build-time themes
 
-Alloy's `app/themes/<name>/` folders can override views, styles, and assets at
-build time. Select a theme through `app/config.json`. This is appropriate for
-separate branded builds or compile-time variants.
+Alloy's `app/themes/<name>/` folders can override views, styles, and assets at build time. Select a theme through `app/config.json`. This is appropriate for separate branded builds or compile-time variants.
 
-Do not describe an Alloy build-time theme as runtime light/dark switching.
-Semantic colors are the default for appearance changes while the app runs.
+Do not describe an Alloy build-time theme as runtime light/dark switching. Semantic colors are the default for appearance changes while the app runs.
 
 ## Runtime custom themes
 
-Use a centralized runtime palette or theme service only when semantic
-light/dark/system colors cannot model the requirement, such as multiple user
-selectable brand themes.
+Use a centralized runtime palette or theme service only when semantic light/dark/system colors cannot model the requirement, such as multiple user selectable brand themes.
 
 If that exception applies:
 
@@ -157,11 +138,9 @@ If that exception applies:
 - expose semantic roles, not control IDs;
 - document how already-created proxies receive updates;
 - remove all listeners in controller cleanup;
-- avoid rebuilding the entire window tree unless the app has measured and
-  accepted that tradeoff.
+- avoid rebuilding the entire window tree unless the app has measured and accepted that tradeoff.
 
-`Alloy.Globals` is a legacy/advanced interoperability option, not the first
-recommendation for ordinary dark mode.
+`Alloy.Globals` is a legacy/advanced interoperability option, not the first recommendation for ordinary dark mode.
 
 ## Component rules
 
@@ -169,10 +148,8 @@ recommendation for ordinary dark mode.
 - Widgets own anatomy and behavior, not the product palette.
 - Localized strings and business callbacks come from the host.
 - Destructive styling must remain distinguishable in both appearances.
-- Overlays, focus indicators, disabled states, and text must retain usable
-  contrast in light, dark, and system modes.
-- Do not create separate light/dark controller branches when a semantic color
-  can express the difference.
+- Overlays, focus indicators, disabled states, and text must retain usable contrast in light, dark, and system modes.
+- Do not create separate light/dark controller branches when a semantic color can express the difference.
 
 ## Verification
 
@@ -185,6 +162,4 @@ For every supported platform and form factor:
 5. run PurgeTSS generation when detected and resolve unsupported classes;
 6. compile and build both platform targets before claiming completion.
 
-For exact PurgeTSS behavior, load its current `semantic-colors.md` and
-`appearance-module.md` references. For Titanium property availability, verify
-against the current `ti-api` skill.
+For exact PurgeTSS behavior, load its current `semantic-colors.md` and `appearance-module.md` references. For Titanium property availability, verify against the current `ti-api` skill.

package/skills/ti-guides/references/coding-best-practices.md

@@ -66,8 +66,7 @@ if (isAndroid) { /* Android path */ } else { /* iOS path */ }
 - Avoid extending the `Ti` namespace. Three reasons:
   1. Ti objects are proxies to native OS components — your extensions may conflict with native functionality.
   2. Arrays stored on the namespace may be immutable; objects may be null unexpectedly.
-  3. There is no guarantee properties persist across SDK versions.
-  Use your own namespace or CommonJS module instead of modifying `Ti`.
+  3. There is no guarantee properties persist across SDK versions. Use your own namespace or CommonJS module instead of modifying `Ti`.
 
 ## 5. App architecture recommendations
 

package/skills/ti-guides/references/style-and-conventions.md

@@ -46,8 +46,7 @@ else
 const fullName = firstName + ' ' + lastName
 ```
 
-Return statement placement:
-Do not put `return` on its own line followed by an object literal. JavaScript will insert a semicolon automatically and return `undefined`.
+Return statement placement: Do not put `return` on its own line followed by an object literal. JavaScript will insert a semicolon automatically and return `undefined`.
 ```javascript
 // Wrong
 return

package/skills/ti-howtos/references/debugging-profiling.md

@@ -382,8 +382,7 @@ Android Studio (GUI): Tools → Device Manager → Create Device.
 
 ### Modifying emulators
 
-Increase disk space:
-Edit `~/.android/avd/<NAME>.avd/config.ini`:
+Increase disk space: Edit `~/.android/avd/<NAME>.avd/config.ini`:
 ```
 disk.dataPartition.size=1024m
 ```

package/skills/ti-howtos/references/location-and-maps.md

@@ -3,8 +3,7 @@
 ## 1. GPS position tracking
 
 ### FusedLocationProvider (Android)
-Since TiSDK 7.1.0, Titanium supports `FusedLocationProvider` for significant battery savings.
-Requirement: include the `ti.playservices` module in your project.
+Since TiSDK 7.1.0, Titanium supports `FusedLocationProvider` for significant battery savings. Requirement: include the `ti.playservices` module in your project.
 
 ### Accuracy configuration
 

package/skills/ti-howtos/references/using-modules.md

@@ -25,8 +25,7 @@ Community modules:
 - From Zero To App list: https://fromzerotoapp.com/modules/
 - Curated list of modules maintained by Michael Gangolf
 
-Marketplace:
-The original Appcelerator Marketplace is no longer available. Find community modules on GitHub and npm. A curated list is at https://fromzerotoapp.com/modules/.
+Marketplace: The original Appcelerator Marketplace is no longer available. Find community modules on GitHub and npm. A curated list is at https://fromzerotoapp.com/modules/.
 
 ### Pre-installed modules
 Some modules ship with the SDK and do not need separate installation: `ti.map`, `ti.identity`, `ti.webdialog`, `ti.applesignin`.

package/skills/ti-howtos/references/web-content-integration.md

@@ -80,8 +80,7 @@ Events:
 
 ### Local web content communication
 
-Logging from WebView:
-Ti.API methods work inside local HTML.
+Logging from WebView: Ti.API methods work inside local HTML.
 
 ```html
 <html>

package/skills/ti-howtos/references/webpack-build-pipeline.md

@@ -53,8 +53,7 @@ Example:
 When you `import { func } from '@/utils'`, Webpack picks the correct version for the build target.
 
 ## 5. Diagnostic web UI
-Webpack includes a web interface to analyze builds and asset sizes.
-Default URL: `http://localhost:1732/webpack/latest/web`
+Webpack includes a web interface to analyze builds and asset sizes. Default URL: `http://localhost:1732/webpack/latest/web`
 
 ## 6. Project plugins
 Webpack support is powered by plugins chosen based on project type:

package/skills/ti-ui/references/listviews-and-performance.md

@@ -202,8 +202,7 @@ The following views can be used as child elements in custom templates: ActivityI
 
 ### Binding syntax
 
-XML (Alloy): `bindId:property="value"`
-JavaScript: `{ bindId: { property: value } }`
+XML (Alloy): `bindId:property="value"` JavaScript: `{ bindId: { property: value } }`
 
 ### Programmatic binding with custom templates
 
@@ -741,14 +740,10 @@ $.myList.cacheSize = 3;  // Default
 
 ### Common issues
 
-Problem: Jerky scrolling
-Solution: Remove `Ti.UI.SIZE` from templates
+Problem: Jerky scrolling Solution: Remove `Ti.UI.SIZE` from templates
 
-Problem: Data changes not visible
-Solution: Use `updateItemAt()` instead of modifying views
+Problem: Data changes not visible Solution: Use `updateItemAt()` instead of modifying views
 
-Problem: Event not firing on template element
-Solution: Check `bindId` in event handler
+Problem: Event not firing on template element Solution: Check `bindId` in event handler
 
-Problem: Wrong item updated
-Solution: Use `e.section.getItemAt(e.itemIndex)` not a global reference
+Problem: Wrong item updated Solution: Use `e.section.getItemAt(e.itemIndex)` not a global reference

package/skills/ti-ui/references/orientation.md

@@ -141,8 +141,7 @@ Ti.Gesture.addEventListener('orientationchange', (e) => {
 });
 ```
 
-Anti-pattern warning: Do not use `orientationchange` listeners to force an orientation. It causes the wrong orientation to flash, repeated firing, and bad behavior. Use `tiapp.xml` or window `orientationModes`.
-...
+Anti-pattern warning: Do not use `orientationchange` listeners to force an orientation. It causes the wrong orientation to flash, repeated firing, and bad behavior. Use `tiapp.xml` or window `orientationModes`. ...
 ### Window orientation events
 
 ```javascript