npm - @maccesar/titools - Versions diffs - 2.10.1 → 3.1.0 - Mend

@maccesar/titools 2.10.1 → 3.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (81) hide show

package/AGENTS-VERCEL-RESEARCH.md +23 -12
package/README.md +81 -182
package/agents/ti-pro.md +8 -14
package/lib/cleanup.js +13 -0
package/lib/commands/skills.js +2 -1
package/lib/config.js +9 -11
package/lib/platform.js +1 -1
package/package.json +2 -3
package/skills/alloy-guides/SKILL.md +0 -190
package/skills/alloy-guides/references/CLI_TASKS.md +0 -233
package/skills/alloy-guides/references/CONCEPTS.md +0 -171
package/skills/alloy-guides/references/CONTROLLERS.md +0 -279
package/skills/alloy-guides/references/MODELS.md +0 -1214
package/skills/alloy-guides/references/PURGETSS.md +0 -46
package/skills/alloy-guides/references/VIEWS_DYNAMIC.md +0 -235
package/skills/alloy-guides/references/VIEWS_STYLES.md +0 -375
package/skills/alloy-guides/references/VIEWS_WITHOUT_CONTROLLERS.md +0 -102
package/skills/alloy-guides/references/VIEWS_XML.md +0 -581
package/skills/alloy-guides/references/WIDGETS.md +0 -160
package/skills/alloy-howtos/SKILL.md +0 -181
package/skills/alloy-howtos/references/best_practices.md +0 -121
package/skills/alloy-howtos/references/cli_reference.md +0 -230
package/skills/alloy-howtos/references/config_files.md +0 -158
package/skills/alloy-howtos/references/custom_tags.md +0 -148
package/skills/alloy-howtos/references/debugging_troubleshooting.md +0 -78
package/skills/alloy-howtos/references/samples.md +0 -156
package/skills/ti-api/SKILL.md +0 -109
package/skills/ti-api/references/api-android.md +0 -675
package/skills/ti-api/references/api-app-platform.md +0 -636
package/skills/ti-api/references/api-core.md +0 -764
package/skills/ti-api/references/api-data-network.md +0 -641
package/skills/ti-api/references/api-media.md +0 -655
package/skills/ti-api/references/api-modules-ble-bluetooth.md +0 -657
package/skills/ti-api/references/api-modules-coremotion-urlsession.md +0 -411
package/skills/ti-api/references/api-modules-map.md +0 -632
package/skills/ti-api/references/api-modules-nfc.md +0 -725
package/skills/ti-api/references/api-modules-social-misc.md +0 -526
package/skills/ti-api/references/api-services.md +0 -700
package/skills/ti-api/references/api-ui-android.md +0 -499
package/skills/ti-api/references/api-ui-extras.md +0 -702
package/skills/ti-api/references/api-ui-ios-animator.md +0 -378
package/skills/ti-api/references/api-ui-ios.md +0 -756
package/skills/ti-api/references/api-ui-lists.md +0 -581
package/skills/ti-api/references/api-ui-text-input.md +0 -607
package/skills/ti-api/references/api-ui-views.md +0 -572
package/skills/ti-api/references/api-ui-windows-navigation.md +0 -676
package/skills/ti-api/references/api-xml-global.md +0 -743
package/skills/ti-guides/SKILL.md +0 -75
package/skills/ti-guides/references/advanced-data-and-images.md +0 -155
package/skills/ti-guides/references/android-manifest.md +0 -97
package/skills/ti-guides/references/app-distribution.md +0 -373
package/skills/ti-guides/references/application-frameworks.md +0 -366
package/skills/ti-guides/references/cli-reference.md +0 -700
package/skills/ti-guides/references/coding-best-practices.md +0 -150
package/skills/ti-guides/references/commonjs-advanced.md +0 -279
package/skills/ti-guides/references/hello-world.md +0 -99
package/skills/ti-guides/references/hyperloop-native-access.md +0 -458
package/skills/ti-guides/references/javascript-primer.md +0 -402
package/skills/ti-guides/references/reserved-words.md +0 -36
package/skills/ti-guides/references/resources.md +0 -172
package/skills/ti-guides/references/style-and-conventions.md +0 -104
package/skills/ti-guides/references/tiapp-config.md +0 -655
package/skills/ti-howtos/SKILL.md +0 -143
package/skills/ti-howtos/references/android-platform-deep-dives.md +0 -609
package/skills/ti-howtos/references/automation-fastlane-appium.md +0 -96
package/skills/ti-howtos/references/buffer-codec-streams.md +0 -162
package/skills/ti-howtos/references/cross-platform-development.md +0 -358
package/skills/ti-howtos/references/debugging-profiling.md +0 -473
package/skills/ti-howtos/references/extending-titanium.md +0 -684
package/skills/ti-howtos/references/google-maps-v2.md +0 -172
package/skills/ti-howtos/references/ios-map-kit.md +0 -149
package/skills/ti-howtos/references/ios-platform-deep-dives.md +0 -595
package/skills/ti-howtos/references/local-data-sources.md +0 -310
package/skills/ti-howtos/references/location-and-maps.md +0 -267
package/skills/ti-howtos/references/media-apis.md +0 -268
package/skills/ti-howtos/references/notification-services.md +0 -539
package/skills/ti-howtos/references/remote-data-sources.md +0 -339
package/skills/ti-howtos/references/tutorials.md +0 -552
package/skills/ti-howtos/references/using-modules.md +0 -182
package/skills/ti-howtos/references/web-content-integration.md +0 -288
package/skills/ti-howtos/references/webpack-build-pipeline.md +0 -125

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

@@ -1,288 +0,0 @@
-# Web content integration
-## 1. The WebView component
-### WKWebView (Titanium SDK 8.0.0+)
-As of Titanium SDK 8.0.0, WKWebView is the only supported web view on iOS. UIWebView was deprecated and removed. WKWebView behaves differently, so plan for that.
-### Basic WebView creation
-Remote URL:
-```javascript
-const webview = Ti.UI.createWebView({
-  url: 'https://titaniumsdk.com'
-});
-win.add(webview);
-win.open();
-```
-Local HTML:
-```javascript
-const webview = Ti.UI.createWebView({
-  url: 'local.html' // Relative to Resources or app/assets/app/lib
-});
-win.add(webview);
-```
-Inline HTML:
-```javascript
-const webview = Ti.UI.createWebView({
-  html: '<html><body><h1>Hello</h1></body></html>'
-});
-```
-### Local web content with assets
-Local content can include CSS, JS, and images. Paths are relative to Resources (Classic) or app/assets/app/lib (Alloy).
-`local.html`:
-```html
-<html>
-  <head>
-    <link rel="stylesheet" type="text/css" href="local.css"/>
-    <script src="local.js"></script>
-  </head>
-  <body>
-    <p>Local content</p>
-  </body>
-</html>
-```
-### WebView properties and methods
-Navigation:
-- `canGoBack()` - returns true if possible to go back
-- `canGoForward()` - returns true if possible to go forward
-- `goBack()` - navigate back in history
-- `goForward()` - navigate forward in history
-Load control:
-- `loading` (Boolean) - current loading state
-- `reload()` - refresh the page
-- `stopLoading()` - stop loading
-- `repaint()` - force repaint
-Data handling:
-- `url` - local or remote URL
-- `html` - inline HTML string
-- `scalesPageToFit` - scale content to dimensions
-- `setBasicAuthentication(host, username, password)` - HTTP auth
-```javascript
-webView.setBasicAuthentication('myDomain.com', 'username', 'password');
-```
-Events:
-- `beforeload` - fires before loading begins (`e.url` contains the source)
-- `load` - fires when content has loaded
-- `error` - fires on load failures (`e.url`, `e.message`)
-## 2. Communication between WebViews and Titanium
-### Local web content communication
-Logging from WebView:
-Ti.API methods work inside local HTML.
-```html
-<html>
-  <body onload="Ti.API.info('Page loaded!');">
-    <p>Logging works!</p>
-  </body>
-</html>
-```
-Bidirectional events with `Ti.App`:
-In local HTML:
-```html
-<html>
-  <head>
-    <script>
-      // Listen for events from Titanium
-      Ti.App.addEventListener('app:fromTitanium', (e) => {
-        alert(e.message);
-        document.getElementById('output').textContent = e.message;
-      });
-      // Send event to Titanium
-      function sendToApp() {
-        Ti.App.fireEvent('app:fromWebView', {
-          message: 'Hello from WebView!'
-        });
-      }
-    </script>
-  </head>
-  <body>
-    <button onclick="sendToApp()">Send to Titanium</button>
-    <div id="output"></div>
-  </body>
-</html>
-```
-In Titanium:
-```javascript
-const webview = Ti.UI.createWebView({ url: 'local.html' });
-// Listen for events from the WebView
-Ti.App.addEventListener('app:fromWebView', (e) => {
-  alert(e.message);
-});
-// Send event to the WebView
-const button = Ti.UI.createButton({
-  title: 'Send to WebView'
-});
-button.addEventListener('click', () => {
-  Ti.App.fireEvent('app:fromTitanium', {
-    message: 'Hello from Titanium!'
-  });
-});
-```
-### Remote web content communication
-Titanium statements (`Ti.API`, `Ti.App`) do not work in remote HTML content.
-Warning: On iOS 12.0+, calling `evalJS()` synchronously from some contexts can deadlock. Prefer the async version with a callback.
-#### Using `evalJS()` for remote content
-Inject JavaScript and retrieve results as strings:
-```javascript
-const webview = Ti.UI.createWebView({ url: 'https://example.com' });
-webview.addEventListener('load', (e) => {
-  // Get the page title
-  const title = webview.evalJS('document.title');
-  Ti.API.info(`Page title: ${title}`);
-  // Get cookies
-  const cookies = webview.evalJS('document.cookie');
-  Ti.API.info(`Cookies: ${cookies}`);
-  // Execute a custom function
-  webview.evalJS('alert("Hello from Titanium!");');
-});
-```
-`evalJS()` rules:
-- Call it from the `load` event (page must be loaded)
-- Pass code as a single string
-- Returns a string (or null)
-- Use `JSON.stringify()` for complex data
-#### Passing data to remote content
-```javascript
-webview.addEventListener('load', () => {
-  const data = { user: 'John', score: 100 };
-  webview.evalJS(`window.appData = ${JSON.stringify(data)};`);
-});
-```
-Then in remote HTML:
-```html
-<script>
-  console.log(window.appData.user); // 'John'
-</script>
-```
-## 3. Performance and interaction concerns
-### WebView performance
-WebView consumes significant resources:
-- Each WebView has its own rendering context
-- Memory overhead is high
-- Load time is independent of content complexity
-Best practice: if you can recreate the content with native Titanium components, do it.
-### WebView in TableViews
-Anti-pattern: embedding WebViews in TableViewRows causes slow scrolling.
-### WebView in scrollable components
-WebViews do not behave well inside other scrollable containers (ScrollView, TableView). They consume touch events.
-Workaround: set `touchEnabled: false` on the WebView if it sits inside a scrollable parent:
-```javascript
-const webview = Ti.UI.createWebView({
-  url: 'content.html',
-  touchEnabled: false // Allow parent to handle touches
-});
-```
-### Viewport meta tag
-For mobile-optimized content, use the viewport meta tag:
-```html
-<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
-```
-## 4. WebView use cases
-Common WebView use cases:
-- HTML forms: auto-scroll to focused fields, next/previous navigation, native keyboard integration
-- Rich text or HTML email: render styled content that is hard to replicate with native labels
-- Canvas/graphics: HTML5 Canvas provides 2D drawing not available in native Titanium APIs
-- OAuth flows: load third-party auth pages in a WebView and intercept redirects
-### Authentication flows
-Many OAuth providers use WebView for login (for example, the Facebook module).
-```javascript
-const authWebView = Ti.UI.createWebView({
-  url: 'https://auth.example.com/oauth'
-});
-authWebView.addEventListener('load', (e) => {
-  // Detect redirect to callback URL with token
-  if (e.url.indexOf('myapp://callback') === 0) {
-    const token = extractTokenFromUrl(e.url);
-    Ti.App.fireEvent('auth:success', { token: token });
-  }
-});
-```
-### Canvas and graphics
-For complex graphics, use HTML5 Canvas:
-`local.html`:
-```html
-<canvas id="myCanvas" width="300" height="200"></canvas>
-<script>
-  const ctx = document.getElementById('myCanvas').getContext('2d');
-  ctx.fillStyle = 'green';
-  ctx.fillRect(10, 10, 150, 100);
-</script>
-```
-## 5. WKWebView behavioral differences (iOS)
-- Cookies: WKWebView uses a separate cookie store from `Ti.Network`. Cookies set via HTTPClient are not shared with WebViews.
-- `localStorage`/`sessionStorage`: not shared between the native app and the WebView. Each WKWebView has its own storage.
-- `evalJS` is async: on iOS 12.0+, synchronous `evalJS()` can deadlock. Use the callback form instead:
-```javascript
-webView.evalJS('document.title', (result) => {
-  Ti.API.info(`Title: ${result}`);
-});
-```
-- Viewport meta tag required: WKWebView needs an explicit viewport tag to scale content correctly:
-```html
-<meta name="viewport" content="width=device-width, initial-scale=1.0">
-```
-- Custom fonts: use a special `@font-face` path format in WKWebView CSS. Fonts must be in the app bundle and referenced correctly.
-- Remote HTML limitations: `Ti.API`, `Ti.App.fireEvent()`, and other Titanium calls do not work in remotely-loaded HTML. Only local HTML can communicate with the Titanium runtime.
-## Best practices summary
-1. Avoid WebViews when possible. Use native components.
-2. Never embed a WebView in a TableView.
-3. Use local content for integration. Only local content supports `Ti.App` events.
-4. Use `evalJS()` for remote content. It is the only way to interact with remote pages.
-5. Wait for the `load` event before calling `evalJS()`.
-6. Configure the viewport for proper mobile rendering.

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

@@ -1,125 +0,0 @@
-# Webpack build pipeline
-> **⚠️ Appcelerator/Axway era feature**
-> The Webpack pipeline documented here was introduced with Titanium SDK 9.1.0 as part of the Axway AMPLIFY toolchain (`appcd` daemon). Since Axway discontinued Appcelerator, this feature is **not maintained** in the current TiDev CLI (`ti`). If you are using the community TiDev CLI, this pipeline may not be available. Prefer the standard `ti build` pipeline unless your project already uses Webpack.
-Webpack integration is an alternative build pipeline starting with Titanium SDK 9.1.0. It is optional. When enabled, Webpack manages asset and code bundling.
-## 1. Key benefits
-- Fast incremental builds: only changed files are processed.
-- npm support: install packages in the root and import them directly.
-- Build-time resolution: `require` calls are resolved during compilation, not at runtime.
-## 2. The `@` alias
-Webpack adds the `@` alias to reference the source root without deep relative paths.
-| Project type | Path mapped by `@` |
-| :----------- | :----------------- |
-| Alloy        | `app/lib`          |
-| Classic      | `src`              |
-Usage example:
-```javascript
-// Before (without webpack)
-import Utils from '../../utils/helper';
-// Now (with webpack)
-import Utils from '@/utils/helper';
-```
-## 3. npm dependency management
-Install a package in the project root:
-```bash
-npm install lodash
-```
-Use it in Titanium code:
-```javascript
-import _ from 'lodash';
-const data = _.chunk(['a', 'b', 'c', 'd'], 2);
-```
-## 4. Platform-specific files
-Webpack detects platform-specific files using the `filename.<platform>.js` pattern.
-Example:
-- `utils.js` (common)
-- `utils.ios.js` (iOS only)
-- `utils.android.js` (Android only)
-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`
-## 6. Project plugins
-Webpack support is powered by plugins chosen based on project type:
-| Plugin                             | Purpose                 |
-| ---------------------------------- | ----------------------- |
-| `@appcd/webpack-plugin-alloy`      | Alloy project support   |
-| `@appcd/webpack-plugin-classic`    | Classic project support |
-| `@appcd/webpack-plugin-babel`      | Babel transpilation     |
-| `@appcd/webpack-plugin-typescript` | TypeScript support      |
-### Custom plugin configuration
-Customize with the `webpack-chain` API in `webpack.config.js`:
-```javascript
-module.exports = (api) => {
-  // Add a custom alias
-  api.chainWebpack((config) => {
-    config.resolve.alias.set('@utils', api.resolve('app/lib/utils'));
-  });
-};
-```
-Common customizations:
-- Add alias: `config.resolve.alias.set(name, path)`
-- Add loader: `config.module.rule(name).use(name).loader(loader)`
-- Delete plugin: `config.plugins.delete(name)`
-## 7. Advanced configuration
-Extend configuration via plugins in `package.json`:
-```json
-{
-  "appcdWebpackPlugins": [
-    "my-local-plugin.js"
-  ]
-}
-```
-## 8. Global configuration
-Configure Webpack daemon settings in `~/.appcelerator/appcd/config.json`:
-```json
-{
-  "webpack": {
-    "inactivityTimeout": 600000
-  }
-}
-```
-## 9. Troubleshooting
-Build seems stuck: the Webpack daemon may need a restart.
-```bash
-appcd exec /webpack/latest/stop
-```
-View build logs:
-```bash
-appcd logcat "*webpack*"
-```
-## 10. Known limitations
-- Hyperloop is not compatible with the Webpack pipeline.
-- Alloy.jmk build hooks are not supported. Use Webpack plugins instead.
-- The first build may be slower due to daemon startup.