@maccesar/titools 2.0.6 → 2.2.0

package/skills/ti-howtos/references/cross-platform-development.md

@@ -2,42 +2,6 @@
 
 Strategies and techniques for building Titanium apps that work on iOS and Android from a single codebase.
 
-## Table of Contents
-
-- [Cross-Platform Development](#cross-platform-development)
-  - [Table of Contents](#table-of-contents)
-  - [Philosophy](#philosophy)
-    - ["Write Once, Adapt Everywhere"](#write-once-adapt-everywhere)
-    - [Embrace the Platform](#embrace-the-platform)
-  - [Platform Identification](#platform-identification)
-    - [Platform Properties](#platform-properties)
-    - [Best Practice: Cache Platform Checks](#best-practice-cache-platform-checks)
-    - [Anti-Pattern: Don't Assume Binary](#anti-pattern-dont-assume-binary)
-  - [Coding Strategies](#coding-strategies)
-    - [1. Branching (For Mostly Similar Code)](#1-branching-for-mostly-similar-code)
-    - [2. Platform-Specific Files (For Mostly Different Code)](#2-platform-specific-files-for-mostly-different-code)
-    - [3. Single Execution Context (Recommended)](#3-single-execution-context-recommended)
-  - [Platform-Specific Resources](#platform-specific-resources)
-    - [Resource Overrides System](#resource-overrides-system)
-    - [Assets (Alloy)](#assets-alloy)
-  - [5. Webpack Build Pipeline (TiSDK 9.1.0+)](#5-webpack-build-pipeline-tisdk-910)
-    - [`@` Alias](#-alias)
-    - [NPM Support](#npm-support)
-  - [6. Internationalization (i18n)](#6-internationalization-i18n)
-    - [Using Localized Strings](#using-localized-strings)
-    - [Date and Currency Formatting](#date-and-currency-formatting)
-    - [Testing Localizations](#testing-localizations)
-  - [Platform-Specific APIs](#platform-specific-apis)
-    - [Example: Platform-Specific Properties](#example-platform-specific-properties)
-  - [Common Cross-Platform Patterns](#common-cross-platform-patterns)
-    - [Tab Groups](#tab-groups)
-    - [Navigation](#navigation)
-    - [Platform-Specific Event Handling](#platform-specific-event-handling)
-  - [Best Practices](#best-practices)
-  - [Resources](#resources)
-
----
-
 ## Philosophy
 
 ### "Write Once, Adapt Everywhere"
@@ -66,6 +30,19 @@ Best-of-breed apps feel **native** on each platform:
 
 **Develop for both platforms from the start** - much more efficient than porting later.
 
+### Android Platform Key Concepts
+- **Screen sizes**: Classified as small, normal, large, xlarge (measured in dp). Use density-independent resources.
+- **Screen densities**: ldpi (~120 dpi), mdpi (~160 dpi), hdpi (~240 dpi), xhdpi (~320 dpi), xxhdpi (~480 dpi), xxxhdpi (~640 dpi)
+- **Activities**: Each heavy-weight Window maps to an Android Activity. Titanium auto-manages the Activity lifecycle.
+- **Intents**: Used for inter-app and intra-app communication. See [android-platform-deep-dives.md](android-platform-deep-dives.md).
+- **Back button**: Hardware/software back button closes current Window by default. Override with `window.addEventListener('androidback', ...)`.
+
+### iOS Platform Key Concepts
+- **Human Interface Guidelines**: Apple enforces design standards through App Store review. Follow iOS conventions for navigation, tab bars, and gestures.
+- **One-button design**: No hardware back or menu buttons — all navigation must be in the UI (NavigationWindow, back buttons).
+- **Frameworks**: Titanium wraps UIKit, Foundation, MapKit, and other Cocoa Touch frameworks. Access additional frameworks via Hyperloop.
+- **Developer account**: Requires paid Apple Developer Program membership for device testing and App Store distribution.
+
 ---
 
 ## Platform Identification
@@ -149,7 +126,14 @@ const ui = require('ui');
 // Carga: /android/ui.js en Android, /iphone/ui.js en iOS
 ```
 
-### 3. Single Execution Context (Recommended)
+### 3. Execution Contexts
+
+Titanium supports single-context and multi-context applications:
+
+- **Single context (recommended)**: All windows share one JavaScript runtime. Use `require()` for modules and `Alloy.createController()` for views.
+- **Multi-context (legacy)**: Using `Ti.UI.createWindow({ url: 'other.js' })` creates a separate JavaScript context. Variables are NOT shared between contexts.
+
+> **Avoid multi-context apps.** Use CommonJS modules and `require()` instead. If you must communicate across contexts, use `Ti.App.fireEvent()` and `Ti.App.addEventListener()`.
 
 **Avoid multiple contexts:**
 ```javascript
@@ -217,6 +201,30 @@ For more details on optimization, diagnostics, and build Web UI, see:
 
 ## 6. Internationalization (i18n)
 
+### i18n Directory Structure
+```
+i18n/
+├── en/
+│   ├── strings.xml      <!-- Default language -->
+│   └── app.xml          <!-- App name localization (Android) -->
+├── es/
+│   ├── strings.xml
+│   └── app.xml
+└── ja/
+    └── strings.xml
+```
+
+Use ISO 639-1 language codes (en, es, ja) and optionally ISO 3166-1 region codes (en-GB, pt-BR).
+
+### strings.xml Format
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<resources>
+    <string name="welcome_message">Welcome to my app</string>
+    <string name="login_button">Log In</string>
+</resources>
+```
+
 ### Using Localized Strings
 
 **Basic usage:**
@@ -224,6 +232,15 @@ For more details on optimization, diagnostics, and build Web UI, see:
 // Two equivalent methods
 const str1 = L('welcome_message');
 const str2 = Ti.Locale.getString('welcome_message');
+
+// With a default fallback
+const withDefault = L('missing_key', 'Default text');
+```
+
+**In Alloy XML views — use `titleid` instead of `title`:**
+```xml
+<Button titleid="login_button" />
+<Label textid="welcome_message" />
 ```
 
 **String formatting:**
@@ -237,6 +254,18 @@ const formatted = String.format(L('ordered'), 'Jeff', 'Kevin');
 // Result: "Hi Jeff, my name is Kevin"
 ```
 
+### Localizing the App Name
+
+**iOS (SDK 3.2.0+)**: Set `<key>CFBundleDisplayName</key>` in `i18n/LANG/app.xml`
+
+**Android**: Use `<string name="appname">Mi App</string>` in `i18n/LANG/strings.xml`
+
+### Localizing Images and Files
+
+Two approaches:
+1. **Platform folders**: Place localized images in `app/assets/iphone/LANG.lproj/` (iOS) or `app/assets/android/images/` with language qualifiers (Android)
+2. **Code-based**: Load different assets based on `Ti.Locale.currentLanguage`
+
 ### Date and Currency Formatting
 
 ```javascript
@@ -252,6 +281,8 @@ const price = String.formatCurrency(1234.56);
 const amount = String.formatDecimal(1234.56);
 ```
 
+> **Warning (Android)**: `String.formatDate()` may produce incorrect translations or field ordering on some Android versions. Consider using JavaScript's `Date` methods directly as a workaround.
+
 ### Testing Localizations
 
 **iOS:**

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

@@ -2,54 +2,6 @@
 
 Comprehensive guide for debugging Titanium apps, managing memory, finding leaks, and using native debugging tools.
 
-## Table of Contents
-
-- [Debugging and Profiling](#debugging-and-profiling)
-  - [Table of Contents](#table-of-contents)
-  - [Debugging Overview](#debugging-overview)
-    - [Essential Elements of Debugging](#essential-elements-of-debugging)
-    - [Debugging Techniques](#debugging-techniques)
-  - [Memory Management](#memory-management)
-    - [How JavaScript Manages Memory](#how-javascript-manages-memory)
-    - [How Titanium Manages Memory](#how-titanium-manages-memory)
-    - [Releasing Memory Properly](#releasing-memory-properly)
-    - [Parent-Child Relationships](#parent-child-relationships)
-    - [Platform Memory Limits](#platform-memory-limits)
-  - [Memory Leak Detection](#memory-leak-detection)
-    - [Common Leak Sources](#common-leak-sources)
-    - [Debugging Memory on iOS (Instruments)](#debugging-memory-on-ios-instruments)
-    - [Debugging Memory on Android (DDMS)](#debugging-memory-on-android-ddms)
-  - [Android Debugging Tools](#android-debugging-tools)
-    - [DDMS (Dalvik Debug Monitor Service)](#ddms-dalvik-debug-monitor-service)
-      - [Log Output with DDMS](#log-output-with-ddms)
-      - [Simulate Network Conditions](#simulate-network-conditions)
-      - [Simulate Calls/SMS](#simulate-callssms)
-      - [Set GPS Coordinates](#set-gps-coordinates)
-      - [File System Exploration](#file-system-exploration)
-      - [Memory Monitoring](#memory-monitoring)
-    - [ADB (Android Debug Bridge)](#adb-android-debug-bridge)
-      - [Log Output](#log-output)
-      - [File System](#file-system)
-      - [Transfer Files](#transfer-files)
-      - [Access SQLite Databases](#access-sqlite-databases)
-    - [Creating Emulators](#creating-emulators)
-    - [Modifying Emulators](#modifying-emulators)
-  - [iOS Debugging Tools](#ios-debugging-tools)
-    - [Instruments](#instruments)
-    - [Xcode Build Debugging](#xcode-build-debugging)
-    - [Console Logs](#console-logs)
-  - [6. Automation and UI Testing](#6-automation-and-ui-testing)
-  - [Best Practices](#best-practices)
-    - [Memory Management](#memory-management-1)
-    - [Debugging](#debugging)
-    - [Performance](#performance)
-  - [Platform-Specific Notes](#platform-specific-notes)
-    - [Android](#android)
-    - [iOS](#ios)
-  - [Resources](#resources)
-
----
-
 ## Debugging Overview
 
 ### Essential Elements of Debugging
@@ -165,6 +117,8 @@ button = null;  // Now button is destroyed
 - "Jetsam" process can terminate your app
 - "Jetsam" in crash logs = memory issue
 
+> **Important**: Memory ≠ storage. A 16GB device doesn't mean 16GB for your app. These limits may be higher on newer devices but always optimize for the lowest common denominator.
+
 ---
 
 ## Memory Leak Detection
@@ -455,11 +409,12 @@ window scale 0.75
 
 ### Instruments
 
-**Common Templates:**
-- **Allocations** - Memory usage
-- **Leaks** - Detect memory leaks
-- **Time Profiler** - CPU usage
-- **System Trace** - System-level events
+**Key Templates for Titanium Debugging:**
+- **Allocations** — Track object creation and live object counts. Look at "Persistent Bytes" (or "Live Bytes") and "#Persistent" (or "#Living") columns to track memory growth.
+- **Leaks** — Detect memory leaks in real-time. Shows objects that are allocated but never released.
+- **Time Profiler** — Identify CPU-intensive operations and bottlenecks.
+- **System Trace** — System-level events and thread activity.
+- **Zombies** — Detect messages sent to deallocated objects (debug builds only). Useful for tracking over-released objects.
 
 ### Xcode Build Debugging
 

package/skills/ti-howtos/references/extending-titanium.md

@@ -1,56 +1,5 @@
 # Extending Titanium
 
-## Table of Contents
-
-- [Extending Titanium](#extending-titanium)
-  - [Table of Contents](#table-of-contents)
-  - [1. Module Architecture (Core Concepts)](#1-module-architecture-core-concepts)
-    - [Proxy-View Relationship](#proxy-view-relationship)
-  - [2. Module Debugging in Xcode (iOS)](#2-module-debugging-in-xcode-ios)
-  - [3. Upgrading to SDK 9.0.0+ (Android)](#3-upgrading-to-sdk-900-android)
-  - [4. Hyperloop](#4-hyperloop)
-    - [What is Hyperloop?](#what-is-hyperloop)
-    - [Prerequisites](#prerequisites)
-    - [Hyperloop Basics](#hyperloop-basics)
-    - [iOS Hyperloop Examples](#ios-hyperloop-examples)
-      - [Access iOS Frameworks](#access-ios-frameworks)
-      - [Access UIKit](#access-uikit)
-      - [Make Native HTTP Request](#make-native-http-request)
-      - [Access CoreBluetooth (Bluetooth LE)](#access-corebluetooth-bluetooth-le)
-      - [Access AVFoundation (Camera/Video)](#access-avfoundation-cameravideo)
-      - [Access Address Book (Contacts)](#access-address-book-contacts)
-      - [Access CoreLocation (Enhanced)](#access-corelocation-enhanced)
-    - [Android Hyperloop Examples](#android-hyperloop-examples)
-      - [Access Android Frameworks](#access-android-frameworks)
-      - [Access Vibrator](#access-vibrator)
-      - [Access TelephonyManager](#access-telephonymanager)
-      - [Access WiFi Manager](#access-wifi-manager)
-      - [Access PackageManager](#access-packagemanager)
-    - [Hyperloop Best Practices](#hyperloop-best-practices)
-  - [3. Native Module Development](#3-native-module-development)
-    - [When to Create Native Modules](#when-to-create-native-modules)
-    - [Android Module Development](#android-module-development)
-      - [Quick Start](#quick-start)
-      - [Use in Titanium app](#use-in-titanium-app)
-      - [Common Android Module Patterns](#common-android-module-patterns)
-    - [iOS Module Development](#ios-module-development)
-      - [Quick Start](#quick-start-1)
-      - [Common iOS Module Patterns](#common-ios-module-patterns)
-    - [Module Distribution](#module-distribution)
-      - [Packaging](#packaging)
-      - [Installing Module](#installing-module)
-      - [Module Configuration in tiapp.xml](#module-configuration-in-tiappxml)
-  - [4. Choosing Between Hyperloop and Native Modules](#4-choosing-between-hyperloop-and-native-modules)
-    - [Use Hyperloop When](#use-hyperloop-when)
-    - [Use Native Modules When](#use-native-modules-when)
-  - [5. Finding and Using Third-Party Modules](#5-finding-and-using-third-party-modules)
-    - [Ti\_slack Marketplace](#ti_slack-marketplace)
-    - [Popular Third-Party Modules](#popular-third-party-modules)
-    - [Using Third-Party Modules](#using-third-party-modules)
-  - [Best Practices Summary](#best-practices-summary)
-
----
-
 ## 1. Module Architecture (Core Concepts)
 
 Titanium modules are based on a native class hierarchy that communicates with JavaScript:
@@ -63,6 +12,18 @@ Titanium modules are based on a native class hierarchy that communicates with Ja
 ### Proxy-View Relationship
 The `ViewProxy` maintains properties in JS even if the native view does not exist yet. When the view is added to the hierarchy, the Proxy instantiates the native `View` and passes all accumulated properties to it.
 
+### Threading Considerations
+- JavaScript in Titanium is **single-threaded**. All JS callbacks execute on the JS runtime thread.
+- Native modules can use background threads for heavy work, but UI operations must happen on the main/UI thread.
+- On iOS, each Window with a `url` property gets its own JavaScript context and thread — avoid this pattern.
+- Use `@Kroll.method(runOnUiThread=true)` (Android) to ensure a method runs on the UI thread.
+
+### Key Android Kroll Annotations
+- `@Kroll.method` — expose a Java method to JavaScript
+- `@Kroll.getProperty` / `@Kroll.setProperty` — expose getter/setter properties
+- `@Kroll.onAppCreate` — annotate a static method to run when the app process starts
+- `propertyAccessors` element in `@Kroll.proxy` — auto-generate getter/setter methods
+
 ## 2. Module Debugging in Xcode (iOS)
 
 You can debug your native module directly within a Titanium project:

package/skills/ti-howtos/references/google-maps-v2.md

@@ -2,27 +2,6 @@
 
 Guide for implementing native maps on Android using the `ti.map` module (v2).
 
-## Table of Contents
-
-- [Google Maps v2 for Android](#google-maps-v2-for-android)
-  - [Table of Contents](#table-of-contents)
-  - [1. Initial Configuration](#1-initial-configuration)
-    - [Module Installation](#module-installation)
-    - [Obtaining an API Key (Google Cloud Console)](#obtaining-an-api-key-google-cloud-console)
-      - [Get SHA-1 (Debug)](#get-sha-1-debug)
-    - [Configure tiapp.xml](#configure-tiappxml)
-  - [2. Google Play Services Verification](#2-google-play-services-verification)
-  - [3. Using the Map View](#3-using-the-map-view)
-    - [Basic Creation](#basic-creation)
-    - [Map Types](#map-types)
-  - [4. Advanced Annotations (Pins)](#4-advanced-annotations-pins)
-    - [Available Pin Colors](#available-pin-colors)
-  - [5. Routes (Polylines)](#5-routes-polylines)
-  - [6. Critical Events](#6-critical-events)
-  - [7. Limitations and Troubleshooting](#7-limitations-and-troubleshooting)
-
----
-
 ## 1. Initial Configuration
 
 ### Module Installation
@@ -66,16 +45,20 @@ const rc = MapModule.isGooglePlayServicesAvailable();
 
 switch (rc) {
     case MapModule.SUCCESS:
-        Ti.API.info('Google Play services is installed.');
+        Ti.API.info('Google Play Services available');
         break;
     case MapModule.SERVICE_MISSING:
-        alert('Google Play services is missing. Please install it.');
+        Ti.API.error('Google Play Services is missing');
         break;
     case MapModule.SERVICE_VERSION_UPDATE_REQUIRED:
-        alert('Google Play services is out of date. Please update.');
+        Ti.API.error('Google Play Services needs update');
+        break;
+    case MapModule.SERVICE_DISABLED:
+        Ti.API.error('Google Play Services is disabled');
+        break;
+    case MapModule.SERVICE_INVALID:
+        Ti.API.error('Google Play Services is invalid');
         break;
-    default:
-        alert(`Google Play services error: ${rc}`);
 }
 ```
 
@@ -122,6 +105,13 @@ const opera = MapModule.createAnnotation({
 mapView.addAnnotation(opera);
 ```
 
+### Additional Annotation Properties
+- `customView` — a `Ti.UI.View` that replaces the entire annotation (takes precedence over `image`)
+- `centerOffset` — `{x, y}` point to offset the annotation from the coordinate
+- `canShowCallout` — whether tapping shows the info bubble (default: `true`)
+
+> **Precedence**: `customView` > `image` > default pin. For buttons: `leftView`/`rightView` take precedence over `leftButton`/`rightButton`.
+
 ### Available Pin Colors
 `ANNOTATION_AZURE`, `BLUE`, `CYAN`, `GREEN`, `MAGENTA`, `ORANGE`, `RED`, `ROSE`, `VIOLET`, `YELLOW`.
 
@@ -152,10 +142,17 @@ mapView.addEventListener('click', (e) => {
 
 // Detect drag state changes
 mapView.addEventListener('pinchangedragstate', (e) => {
-    if (e.newState === MapModule.ANNOTATION_DRAG_STATE_END) {
-        Ti.API.info(`New position: ${e.annotation.latitude}`);
+    if (e.annotation.dragState === MapModule.ANNOTATION_DRAG_STATE_END) {
+        Ti.API.info(`Dropped at: ${e.annotation.latitude}, ${e.annotation.longitude}`);
     }
 });
+// Drag states: ANNOTATION_DRAG_STATE_START, ANNOTATION_DRAG_STATE_DRAG,
+//              ANNOTATION_DRAG_STATE_CANCEL, ANNOTATION_DRAG_STATE_END
+
+// Detect region changes
+mapView.addEventListener('regionchanged', (e) => {
+    Ti.API.info(`New region: ${e.latitude}, ${e.longitude} (delta: ${e.latitudeDelta}, ${e.longitudeDelta})`);
+});
 
 // Detect complete rendering
 mapView.addEventListener('complete', (e) => {
@@ -163,7 +160,11 @@ mapView.addEventListener('complete', (e) => {
 });
 ```
 
-## 7. Limitations and Troubleshooting
+## 7. Migration from Legacy Titanium.Map
+
+> **Note**: The `ti.map` module replaced the legacy `Titanium.Map` API. Key differences: use `NORMAL_TYPE` instead of `STANDARD_TYPE`, `ANNOTATION_VIOLET` instead of `ANNOTATION_PURPLE`, and routes are created with `Map.createRoute()` instead of abstract data types. Multiple MapView instances are supported.
+
+## 8. Limitations and Troubleshooting
 - **Single Map:** Android (legacy) only allows one MapView instance per application. v2 allows multiple views.
 - **Blank Map:** Verify the API Key is correct and that `android:anyDensity` is NOT set to true in the manifest if using old resolutions.
 - **Simulator:** Google Maps v2 is NOT compatible with the standard emulator without x86 Google Play Services. Real device testing is recommended.

package/skills/ti-howtos/references/ios-map-kit.md

@@ -2,25 +2,6 @@
 
 Guide for implementing native maps on iOS using the `ti.map` module.
 
-## Table of Contents
-
-- [iOS Map Kit](#ios-map-kit)
-  - [Table of Contents](#table-of-contents)
-  - [1. Initial Configuration](#1-initial-configuration)
-    - [Module Installation](#module-installation)
-    - [Location Permissions (Info.plist)](#location-permissions-infoplist)
-  - [2. Using the Map View](#2-using-the-map-view)
-    - [Basic Creation](#basic-creation)
-  - [3. 3D Camera (Perspective)](#3-3d-camera-perspective)
-  - [4. iOS Annotations](#4-ios-annotations)
-    - [System Buttons and Callouts](#system-buttons-and-callouts)
-    - [Center Offset](#center-offset)
-  - [5. Advanced Routes](#5-advanced-routes)
-    - [Overlay Levels](#overlay-levels)
-  - [6. Events](#6-events)
-
----
-
 ## 1. Initial Configuration
 
 ### Module Installation
@@ -46,13 +27,15 @@ Add the mandatory usage descriptions in `tiapp.xml`:
 </ios>
 ```
 
+> **iOS 11+**: You must include both `NSLocationWhenInUseUsageDescription` AND `NSLocationAlwaysAndWhenInUseUsageDescription` in your plist. Users can choose "When in Use" even when your app requests "Always" authorization.
+
 ## 2. Using the Map View
 
 ### Basic Creation
 ```javascript
 const MapModule = require('ti.map');
 const mapView = MapModule.createView({
-    mapType: MapModule.NORMAL_TYPE,
+    mapType: MapModule.NORMAL_TYPE, // Also: SATELLITE_TYPE, HYBRID_TYPE, STANDARD_TYPE (alias for NORMAL_TYPE with labels)
     userLocation: true,
     rotatesEnabled: true, // Allow two-finger rotation
     region: {
@@ -68,6 +51,8 @@ const mapView = MapModule.createView({
 
 iOS allows tilting and rotating the map programmatically for 3D views.
 
+> **Important**: The map view must be visible on screen before using camera APIs. Wait for the map's `complete` event before calling `animateCamera()` or setting camera properties.
+
 ```javascript
 const myCam = MapModule.createCamera({
     altitude: 300, // Meters above ground
@@ -103,7 +88,7 @@ const bridge = MapModule.createAnnotation({
     // iOS system buttons in the callout
     leftButton: Ti.UI.iOS.SystemButton.INFO_DARK,
     rightButton: Ti.UI.iOS.SystemButton.CONTACT_ADD,
-    canShowCallout: true // Default is true
+    canShowCallout: true // Controls whether tapping the annotation shows the callout bubble (default: true)
 });
 
 mapView.addAnnotation(bridge);
@@ -124,15 +109,18 @@ const customPin = MapModule.createAnnotation({
 Control if the route goes above labels or above roads.
 ```javascript
 const route = MapModule.createRoute({
-    points: [...],
-    color: 'blue',
+    points: routePoints,
+    color: '#00f',
     width: 4,
-    // OVERLAY_LEVEL_ABOVE_LABELS or OVERLAY_LEVEL_ABOVE_ROADS
-    level: MapModule.OVERLAY_LEVEL_ABOVE_LABELS
+    level: MapModule.OVERLAY_LEVEL_ABOVE_LABELS  // default
+    // or MapModule.OVERLAY_LEVEL_ABOVE_ROADS (below labels)
 });
 ```
 
 ## 6. Events
+
+Key map events: `click`, `complete` (map loaded), `regionchanged`, `pinchangedragstate`.
+
 Same as Android, but with specialized `clicksource` for system buttons:
 ```javascript
 mapView.addEventListener('click', (e) => {
@@ -140,4 +128,10 @@ mapView.addEventListener('click', (e) => {
         Ti.API.info('Callout button clicked');
     }
 });
+
+mapView.addEventListener('pinchangedragstate', (e) => {
+    if (e.annotation.dragState === MapModule.ANNOTATION_DRAG_STATE_END) {
+        Ti.API.info(`Dropped at: ${e.annotation.latitude}, ${e.annotation.longitude}`);
+    }
+});
 ```