diff --git a/android/cli/commands/_build.js b/android/cli/commands/_build.js
index 2f87474305c..84e869b8b94 100644
--- a/android/cli/commands/_build.js
+++ b/android/cli/commands/_build.js
@@ -2487,7 +2487,7 @@ AndroidBuilder.prototype.copyResources = function copyResources(next) {
copyDir.call(this, {
src: src,
dest: this.buildBinAssetsResourcesDir,
- ignoreRootDirs: ti.availablePlatformsNames
+ ignoreRootDirs: ti.allPlatformNames
}, cb);
},
diff --git a/android/templates/module/default/template/android/timodule.xml b/android/templates/module/default/template/android/timodule.xml
index 6affb2faec1..ae315971a58 100644
--- a/android/templates/module/default/template/android/timodule.xml
+++ b/android/templates/module/default/template/android/timodule.xml
@@ -2,12 +2,10 @@
-
-
diff --git a/apidoc/Global/Global.yml b/apidoc/Global/Global.yml
index 34d92d2a750..2c7ddb8ed5f 100644
--- a/apidoc/Global/Global.yml
+++ b/apidoc/Global/Global.yml
@@ -2,84 +2,84 @@
name: Global
summary: The APIs that reside in the global scope, which may be called without a namespace prefix.
description: |
- Titanium provides a number of global built-in objects, detailed below.
-
+ Titanium provides a number of global built-in objects, detailed below.
+
#### JSON
-
+
Titanium provides a built-in [JSON](Global.JSON) object two functions, `parse` and `stringify`.
#### String Utilities
Titanium includes several extra utility functions for formatting text, attached to the
global [String](Global.String) object.
-
+
#### console
-
+
Titanium provides [console](Global.console) support familiar to many javascript developers
for logging at the toplevel, in addition to the logging facilities.
-
+
#### Timers
-
+
Titanium has built-in support for one-off and repeating timers:
-
+
* Use [setTimeout](Global.setTimeout) to start a one-off timer.
* Use [setInterval](Global.setInterval) to start a repeating timer.
-
+
#### Alert
-
- Titanium has a built-in convenience function [alert](Global.alert) which can be used as an alias
+
+ Titanium has a built-in convenience function [alert](Global.alert) which can be used as an alias
for the [AlertDialog](Titanium.UI.AlertDialog) module.
-
+
#### Locale
-
+
The `L` macro can also be used as an alias for the method.
-platforms: [android, iphone, ipad, mobileweb]
+platforms: [android, iphone, ipad]
methods:
- name: alert
summary: Displays a pop-up alert dialog with the passed in `message`.
description: |
- This function is a shortcut for creating and displaying an
- [alert dialog](Titanium.UI.AlertDialog). For example, the following two statements produce
+ This function is a shortcut for creating and displaying an
+ [alert dialog](Titanium.UI.AlertDialog). For example, the following two statements produce
the same result.
-
+
alert('Danger, Will Robinson!');
-
+
Ti.UI.createAlertDialog({ message: 'Danger, Will Robinson!' }).show();
-
- Note that unlike a web browser-based version of `alert`, the method is asynchronous. However,
+
+ Note that unlike a web browser-based version of `alert`, the method is asynchronous. However,
only one alert dialog will be visible and modal at a time.
-
+
Be aware that this method may be removed in the future.
parameters:
- name: message
summary: Alert message.
type: String
-
+
- name: clearInterval
summary: Cancels an interval timer.
parameters:
- name: timerId
summary: Unique timer identifier returned by [setInterval](Global.setInterval).
type: Number
-
+
- name: clearTimeout
summary: Cancels a one-time timer.
parameters:
- name: timerId
summary: Unique timer identifier returned by [setTimeout](Global.setTimeout).
type: Number
-
+
- name: decodeURIComponent
summary: |
- Replaces each escape sequence in the specified string, created using the `encodedURI`
- method, with the character that it represents.
- description: |
- For more information, see the MDN website for
- [encodeURIComponent](https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/encodeURIComponent)
+ Replaces each escape sequence in the specified string, created using the `encodedURI`
+ method, with the character that it represents.
+ description: |
+ For more information, see the MDN website for
+ [encodeURIComponent](https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/encodeURIComponent)
and [decodeURIComponent](https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/decodeURIComponent).
returns:
summary: Decoded string.
@@ -91,11 +91,11 @@ methods:
- name: encodeURIComponent
summary: |
- Replaces each special character in the specified string with the equivalent URI escape
+ Replaces each special character in the specified string with the equivalent URI escape
sequence. Useful for encoding URIs.
description: |
- For more information, see the MDN website for
- [encodeURIComponent](https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/encodeURIComponent)
+ For more information, see the MDN website for
+ [encodeURIComponent](https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/encodeURIComponent)
and [decodeURIComponent](https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/decodeURIComponent).
returns:
summary: Encoded string.
@@ -114,18 +114,18 @@ methods:
- name: key
summary: Key used to lookup the localized string.
type: String
-
+
- name: hint
summary: Text to return if `key` is not found.
type: String
optional: true
-
+
- name: require
summary: Loads either a native Titanium module or a CommonJS module.
description: |
- The `require` function takes a module identifier as its argument and returns an object with
+ The `require` function takes a module identifier as its argument and returns an object with
references to the module's exported symbols.
-
+
#### Native Titanium Module
To load a native Titanium module:
@@ -138,30 +138,30 @@ methods:
[Using a Module](http://docs.appcelerator.com/platform/latest/#!/guide/Using_a_Module).
#### CommonJS Module
-
+
To load a local CommonJS module, place the CommonJS module in the `Resources` directory of
your project. Pass the `require` method the path to the file without the `Resources`
directory, platform-specific directory and the `.js` extension.
- Note that the appropriate *platform-specific* `Resources` subdirectory is merged into the
+ Note that the appropriate *platform-specific* `Resources` subdirectory is merged into the
main `Resources` directory at build time. For example, suppose the following files exist.
-
+
* `Resources/app.js`
* `Resources/ui/MainWindow.js`
* `Resources/iphone/ui/TaskWindow.js`
* `Resources/android/ui/TaskWindow.js`
-
- The appropriate `TaskWindow.js` file is moved into the `Resources/ui` directory of the
- built application. To include both the MainWindow module and the platform-specific
+
+ The appropriate `TaskWindow.js` file is moved into the `Resources/ui` directory of the
+ built application. To include both the MainWindow module and the platform-specific
TaskWindow module from any JavaScript file in the project:
// load main window module from ui subdirectory
var mainWindow = require('ui/MainWindow');
-
+
// load platform-specific task window module
- var taskWindow = require('ui/TaskWindow');
-
- For more information, see the Official CommonJS website about
+ var taskWindow = require('ui/TaskWindow');
+
+ For more information, see the Official CommonJS website about
[CommonJS Modules/1.1 Specification](http://wiki.commonjs.org/wiki/Modules/1.1).
#### Alloy
@@ -179,13 +179,13 @@ methods:
require('myModule/module');
#### Android
-
+
Additionally, on Android, an absolute path to a module may be specified using a path
separator (`/`) at the beginning of the path.
-
+
For example, a module file `Resources/myModule/module.js` may be required by
`Resources/example/example.js` using either of the following:
-
+
require('../myModule/module')
require ('/myModule/module')
@@ -201,29 +201,29 @@ methods:
- title: Require a Native Module
example: |
To load a native module with the ID `com.mycompany.module`:
-
+
var module = require('com.mycompany.module');
- title: Require a JavaScript Module
example: |
`myModule.js`:
-
+
exports.message = "hello world";
-
+
`app.js`:
-
+
var myModule = require('myModule');
alert(myModule.message);
-
+
- name: setInterval
summary: Executes a function repeatedly with a fixed time delay between each call to that function.
description: |
- Note that although the interval is not guaranteed to be exact, the interval between calls
+ Note that although the interval is not guaranteed to be exact, the interval between calls
will be no less than the specified delay.
-
- Returns a unique timer identifier that can be passed to [clearInterval](Global.clearInterval)
+
+ Returns a unique timer identifier that can be passed to [clearInterval](Global.clearInterval)
to cancel this timer.
-
- For more information, see the MDN website for
+
+ For more information, see the MDN website for
[setInterval](https://developer.mozilla.org/en/DOM/window.setInterval).
returns:
summary: Unique timer identifier.
@@ -232,14 +232,14 @@ methods:
- name: function
summary: Function to call.
type: Callback
-
+
- name: delay
summary: Time in milliseconds to wait between calls to function.
type: Number
examples:
- title: Update a label once every second, and stop at 10 seconds
example: |
-
+
var count = 0;
var timer = setInterval(function(){
count++;
@@ -248,17 +248,17 @@ methods:
clearInterval(timer);
}
}, 1000);
-
+
- name: setTimeout
summary: Executes code or a function after a delay.
description: |
Note that although the timeout is not guaranteed to be exact, the delay before the
function is invoked will be no less than the specified delay.
- Returns a unique timer identifier that can be passed to [clearTimeout](Global.clearTimeout)
+ Returns a unique timer identifier that can be passed to [clearTimeout](Global.clearTimeout)
to cancel this timer.
-
- For more information, see the MDN website for
+
+ For more information, see the MDN website for
[setTimeout](https://developer.mozilla.org/en/DOM/window.setTimeout).
returns:
summary: Unique timer identifier.
@@ -267,14 +267,14 @@ methods:
- name: function
summary: Code or function to call.
type: Callback
-
+
- name: delay
summary: Time in milliseconds to wait before the function is called.
type: Number
examples:
- title: Execute a function in 500 milliseconds
example: |
-
+
setTimeout(function(){
Ti.API.debug('Called using setTimeout');
}, 500);
diff --git a/apidoc/Global/JSON/JSON.yml b/apidoc/Global/JSON/JSON.yml
index cfd1c7f6269..174e7de1409 100644
--- a/apidoc/Global/JSON/JSON.yml
+++ b/apidoc/Global/JSON/JSON.yml
@@ -3,7 +3,7 @@
---
name: Global.JSON
summary: Global JSON object providing the [parse](Global.JSON.parse) and [stringify](Global.JSON.stringify) methods.
-platforms: [android, iphone, ipad, mobileweb]
+platforms: [android, iphone, ipad]
methods:
- name: stringify
@@ -48,7 +48,7 @@ methods:
functions, will not be serialized. Such values in objects are
dropped; in arrays they are replaced with null. You can use
a replacer function to replace those with JSON values.
-
+
JSON.stringify(undefined) returns undefined.
The optional space parameter produces a stringification of the
@@ -57,37 +57,37 @@ methods:
If the space parameter is a non-empty string, then that string is
used for indentation. If the space parameter is a number, then
- each level is indented by the specified number of spaces.
+ each level is indented by the specified number of spaces.
+
+ parameters:
- parameters:
-
- name: value
summary: Any JavaScript value, usually an object or array.
type: Object
-
- - name: replacer
+
+ - name: replacer
summary: |
Determines how object values are stringified for objects. See main text for usage.
type: [Callback, Array]
optional: true
-
- - name: space
- summary: Specifies how nested structures are indented. If it is a number, it specifies the number
- of spaces to indent at each level. If it is a string (such as '\\t' or ' '), it
+
+ - name: space
+ summary: Specifies how nested structures are indented. If it is a number, it specifies the number
+ of spaces to indent at each level. If it is a string (such as '\\t' or ' '), it
specifies the characters used to indent at each level.
type: [Number, String]
optional: true
default: Text is packed without linebreaks or extra whitespace.
-
+
returns:
type: String
-
+
examples:
- title: Formatting with a Replacer Function
example: |
- The following example produces a readable version of a Titanium event object,
+ The following example produces a readable version of a Titanium event object,
omitting the `source` and `type` properties and adding whitespace for readability:
-
+
JSON.stringify(evt, function(key, value) {
if(key === 'source' || key === 'type') {
return undefined;
@@ -106,23 +106,23 @@ methods:
and its return value is used instead of the original value.
If it returns what it received, then the structure is not modified.
If it returns undefined then the member is deleted.
-
+
parameters:
- name: text
summary: JSON text to parse.
type: String
-
+
- name: reviver
- summary: Function to filter and transform the results.
+ summary: Function to filter and transform the results.
type: Callback
-
+
returns:
type: Object
-
+
examples:
- title: Parse with Reviver Function
example:
- The following example parses the text, converting values that look like ISO date
+ The following example parses the text, converting values that look like ISO date
strings into Date objects.
myData = JSON.parse(text, function (key, value) {
diff --git a/apidoc/Titanium/Blob.yml b/apidoc/Titanium/Blob.yml
index fd943622fbf..a2d76332739 100644
--- a/apidoc/Titanium/Blob.yml
+++ b/apidoc/Titanium/Blob.yml
@@ -2,36 +2,36 @@
name: Titanium.Blob
summary: A container for binary data.
description: |
- A `Blob` represents a chunk of binary information, often obtained through
- an [HTTPClient](Titanium.Network.HTTPClient) or by reading a [File](Titanium.Filesystem.File).
+ A `Blob` represents a chunk of binary information, often obtained through
+ an [HTTPClient](Titanium.Network.HTTPClient) or by reading a [File](Titanium.Filesystem.File).
- Blobs are often used to store text or image data.
+ Blobs are often used to store text or image data.
The `Blob` object includes a number of properties and methods specific to image blobs.
- Android and Mobile Web support an [append](Titanium.Blob.append) method, but
- otherwise blobs are immutable.
+ Android supports an [append](Titanium.Blob.append) method, but
+ otherwise blobs are immutable.
- The module provides several utility methods for working with
+ The module provides several utility methods for working with
blobs, including methods for converting between blobs and Base64-encoded strings,
and methods for generating SHA-1 and SHA-256 hashes and MD5 digests from blob data.
-
+
The [Buffer](Titanium.Buffer) object can also contain binary data, and is
more easily mutable. Extracting blob data to a buffer is somewhat roundabout:
var blobStream = Ti.Stream.createStream({ source: myBlob, mode: Ti.Stream.MODE_READ });
var newBuffer = Ti.createBuffer({ length: myBlob.length });
var bytes = blobStream.read(newBuffer);
-
+
Creating a blob from a buffer is much easier:
-
+
var newBlob = myBuffer.toBlob();
-
- In both cases, the conversion involves copying the data from one object to another, so
+
+ In both cases, the conversion involves copying the data from one object to another, so
you should be conscious of the amount of the data being copied.
extends: Titanium.Proxy
since: "0.9"
-platforms: [android, iphone, ipad, mobileweb]
+platforms: [android, iphone, ipad]
createable: false
properties:
@@ -49,7 +49,7 @@ properties:
- name: text
type: String
- summary: UTF-8 string representation of the data in this blob.
+ summary: UTF-8 string representation of the data in this blob.
description: |
If this blob represents pure binary data, the value will be `null`.
permission: read-only
@@ -61,23 +61,17 @@ properties:
- name: height
type: Number
- summary: If this blob represents an image, this is the height of the image in pixels.
+ summary: If this blob represents an image, this is the height of the image in pixels.
description: |
If this blob doesn't represent an image, `height` is 0.
- On Mobile Web, the `height` is not available until the image loads. It is advised
- to set a timeout to wait for the image to load before accessing the `height`.
-
permission: read-only
- name: width
type: Number
- summary: If this blob represents an image, this is the width of the image in pixels.
+ summary: If this blob represents an image, this is the width of the image in pixels.
description: |
If this blob doesn't represent an image, `height` is 0.
-
- On Mobile Web, the `width` is not available until the image loads. It is advised to set a timeout
- to wait for the image to load before accessing the `width`.
permission: read-only
- name: nativePath
@@ -86,7 +80,7 @@ properties:
If this blob represents a [File](Titanium.Filesystem.File), this is the file URL
that represents it.
description: |
- If this blob doesn't represent a file, the value of `nativePath` is `null`.
+ If this blob doesn't represent a file, the value of `nativePath` is `null`.
permission: read-only
- name: size
@@ -96,11 +90,7 @@ properties:
description: |
If this blob represents an image, this is the total number of pixels in the image.
Otherwise it returns the number of bytes in the binary data.
-
- On Mobile Web, always returns the number of bytes of the blob. Note that internally,
- binary data is stored base64 encoded and `size` represents the number of bytes before
- base64 encoding.
- platforms: [iphone, ipad, mobileweb]
+ platforms: [iphone, ipad]
permission: read-only
methods:
@@ -109,12 +99,10 @@ methods:
returns:
type: String
summary: Returns a string representation of this blob.
- description: |
- On Mobile Web, if the blob is binary, `toString` returns a base64 encoded data URI.
- name: append
summary: Appends the data from another blob to this blob.
- platforms: [android, mobileweb]
+ platforms: [android]
parameters:
- name: blob
type: Titanium.Blob
diff --git a/apidoc/Titanium/BlobStream.yml b/apidoc/Titanium/BlobStream.yml
index 96e711ffdff..e2e78f81f7d 100644
--- a/apidoc/Titanium/BlobStream.yml
+++ b/apidoc/Titanium/BlobStream.yml
@@ -7,4 +7,4 @@ description: |
`Blob`.
since: "1.7"
createable: false
-platforms: [android, iphone, ipad, mobileweb]
+platforms: [android, iphone, ipad]
diff --git a/apidoc/Titanium/Buffer.yml b/apidoc/Titanium/Buffer.yml
index cddf3598dd4..3f544344b9a 100644
--- a/apidoc/Titanium/Buffer.yml
+++ b/apidoc/Titanium/Buffer.yml
@@ -1,23 +1,23 @@
---
name: Titanium.Buffer
-summary: Buffer is a mutable, resizable container for raw data.
+summary: Buffer is a mutable, resizable container for raw data.
description: |
A `Buffer` works like a resizable array of byte values.
Use the method to create a buffer.
extends: Titanium.Proxy
since: "1.7"
-platforms: [android, iphone, ipad, mobileweb]
+platforms: [android, iphone, ipad]
properties:
- name: length
type: Number
- summary: Length of the buffer in bytes.
+ summary: Length of the buffer in bytes.
description: |
- When `length` is modified the buffer will be re-sized while preserving existing data where
- possible. If the new buffer length is smaller than the length of the existing data then the
- existing data will be truncated down to the size of the new buffer.
-
+ When `length` is modified the buffer will be re-sized while preserving existing data where
+ possible. If the new buffer length is smaller than the length of the existing data then the
+ existing data will be truncated down to the size of the new buffer.
+
Resizing a buffer by setting its length should be used sparingly due to the associated overhead.
default: 0 unless `value` is specified, in which case the length of the encoded data
is used.
@@ -25,28 +25,28 @@ properties:
- name: value
type: [Number, String]
availability: creation
- summary: Data to be encoded.
+ summary: Data to be encoded.
description: |
- If `value` is a Number, `type` must also be set. (This is simply a convenient way of
+ If `value` is a Number, `type` must also be set. (This is simply a convenient way of
calling or .)
- name: type
type: String
availability: creation
- summary: The type of data encoding to use with `value`.
+ summary: The type of data encoding to use with `value`.
description: |
- Required when `value` is a Number. For numbers, specify a `TYPE` constant
+ Required when `value` is a Number. For numbers, specify a `TYPE` constant
from , for example, .
-
+
When `value` is a String, specify a `CHARSET` constant from .
default: For string values, defaults to .
- name: byteOrder
type: Number
availability: creation
- summary: Byte order of this buffer.
+ summary: Byte order of this buffer.
description: |
- Specify either or .
+ Specify either or .
default: OS native byte order.
methods:
@@ -54,10 +54,10 @@ methods:
returns:
type: Number
summary: The number of bytes appended.
- summary: Appends `sourceBuffer` to the this buffer.
+ summary: Appends `sourceBuffer` to the this buffer.
description: |
This buffer is grown dynamically to accommodate the additional data if need be.
-
+
If `sourceOffset` and `sourceLength` are specified, data from `sourceBuffer` is
copied starting at position `sourceOffset`, and no more than `sourceLength` bytes
are copied.
@@ -87,7 +87,7 @@ methods:
returns:
type: Number
summary: The number of bytes inserted.
- summary: Inserts data from `sourceBuffer` into this buffer at `offset`.
+ summary: Inserts data from `sourceBuffer` into this buffer at `offset`.
description: |
Buffer is grown to accommodate the new data.
@@ -128,7 +128,7 @@ methods:
description: |
Does not expand this buffer if there is not enough room to accomodate the data
from `sourceBuffer`.
-
+
If `sourceOffset` and `sourceLength` are specified, bytes are copied from
`sourceBuffer` starting at `sourceOffset`, and a maximum of `sourceLength` bytes
are copied.
@@ -157,7 +157,7 @@ methods:
type: Number
optional: true
default: Length of source buffer.
-
+
- name: clone
returns:
type: Titanium.Buffer
@@ -165,7 +165,7 @@ methods:
description: |
If called with no arguments, retuns a complete copy of the current buffer.
- If `offset` and `length` are specified, creates a new buffer from the original
+ If `offset` and `length` are specified, creates a new buffer from the original
buffer contents starting at `offset` and ending at `offset`+`length`-1.
parameters:
- name: offset
@@ -187,7 +187,7 @@ methods:
description: |
Fills the buffer by setting byte values to `fillByte`.
- If `offset` and `length` are specified, fills the buffer starting at
+ If `offset` and `length` are specified, fills the buffer starting at
`offset` and ending at `offset`+`length`-1.
If `offset` and `length` are omitted, fills the entire buffer.
@@ -212,7 +212,7 @@ methods:
summary: Clears this buffer's contents but does not change the size of the buffer.
- name: release
- summary: Releases the space allocated to the buffer, and sets its length to 0.
+ summary: Releases the space allocated to the buffer, and sets its length to 0.
description: |
This is effectively the same as `buffer.length = 0`.
diff --git a/apidoc/Titanium/BufferStream.yml b/apidoc/Titanium/BufferStream.yml
index beb1afa73e1..01229c5a990 100644
--- a/apidoc/Titanium/BufferStream.yml
+++ b/apidoc/Titanium/BufferStream.yml
@@ -8,4 +8,4 @@ description: |
`Buffer`.
since: "1.7"
createable: false
-platforms: [android, iphone, ipad, mobileweb]
+platforms: [android, iphone, ipad]
diff --git a/apidoc/Titanium/Codec/Codec.yml b/apidoc/Titanium/Codec/Codec.yml
index c7d7a3319d3..735e24211cc 100644
--- a/apidoc/Titanium/Codec/Codec.yml
+++ b/apidoc/Titanium/Codec/Codec.yml
@@ -3,16 +3,16 @@ name: Titanium.Codec
summary: |
A module for translating between primitive types and raw byte streams.
description: |
- The `Codec` module can be used for encoding strings and numbers into [Buffer](Titanium.Buffer)
- objects, and decoding primitive types from buffers.
+ The `Codec` module can be used for encoding strings and numbers into [Buffer](Titanium.Buffer)
+ objects, and decoding primitive types from buffers.
#### Byte Order
Multi-byte data can be stored in two different byte orders: big-endian or
little-endian. In big-endian byte order, the most significant or highest-value
byte is stored first. For example, the 4-byte integer 0xFEDCBA98 is made up of the
- bytes 0xFE, 0xDC, 0xBA and 0x98, from most-significant to least-significant.
-
+ bytes 0xFE, 0xDC, 0xBA and 0x98, from most-significant to least-significant.
+
If we represent a buffer as an array of byte values, a big-endian encoding of
0xFEDCBA98 would look like this:
@@ -21,7 +21,7 @@ description: |
In little-endian order, the bytes would be stored in this order:
[ 0x98, 0xBA, 0xDC, 0xFE ]
-
+
For 8-bit character encodings, including ASCII, Latin-1 and UTF-8, byte order is not
significant: the text is a sequence of individual bytes.
@@ -37,10 +37,10 @@ description: |
Note that the bytes for each character are stored least-significant byte first, but
the order of the characters is unchanged.
-
+
extends: Titanium.Module
since: "1.7"
-platforms: [android, iphone, ipad, mobileweb]
+platforms: [android, iphone, ipad]
properties:
- name: CHARSET_ASCII
@@ -162,8 +162,6 @@ methods:
).
description: |
See "Byte Order" in the main discussion of for more information.
-
- On Mobile Web, this property always returns .
returns:
type: Number
summary: OS native byte order.
@@ -184,8 +182,6 @@ methods:
* If `byteOrder` is included in the `options` dictionary, the specified byte order
is used -- otherwise, the native byte order is assumed.
-
- On Mobile Web, `position` is not supported.
parameters:
- name: options
summary: Named parameters.
@@ -198,7 +194,7 @@ methods:
example: |
This example encodes a double-precision floating point value in 8 bytes using the OS byte
order.
-
+
var buffer = Ti.createBuffer({ length: 8 });
Ti.Codec.encodeNumber({
source: 1.23456789,
@@ -208,9 +204,9 @@ methods:
- title: Encode an Integer Specifying Start Position and Byte Order
example: |
- This example encodes a 4-byte integer using big endian encoding, and
+ This example encodes a 4-byte integer using big endian encoding, and
writes it to the supplied buffer starting at index position 10.
-
+
var buffer = Ti.createBuffer({ length: 100 });
Ti.Codec.encodeNumber({
source: 0x3456789a,
@@ -231,15 +227,13 @@ methods:
Two optional parameters can also be specified in `options`:
- * If `position` is included in the `options` dictionary, reads data from the
+ * If `position` is included in the `options` dictionary, reads data from the
buffer starting at `position`.
* If `byteOrder` is included in the `options` dictionary, the specified byte order
is used -- otherwise, the native byte order is assumed.
Throws an exception if `source` is null, or `position` is greater than `source.length`
-
- On Mobile Web, `position` and `byteOrder` are not supported.
parameters:
- name: options
summary: Named parameters.
@@ -250,22 +244,22 @@ methods:
examples:
- - title: Decode a Double-Precision Floating Point Number
+ - title: Decode a Double-Precision Floating Point Number
example: |
This sample decodes an 8-byte double-precision floating point number using the
OS byte order.
-
+
var buffer = // a buffer containing (at least) one 8-byte floating-point number
var value = Ti.Codec.decodeNumber({
source: buffer,
type: Ti.Codec.TYPE_DOUBLE
});
-
+
- title: Decode an Integer Specifying Start Position and Byte Order
example: |
This sample decodes a 4-byte integer starting at index position 10 in the
buffer, using big endian encoding.
-
+
var buffer = // a buffer containing a 4-byte integer at position 10.
var value = Ti.Codec.decodeNumber({
source: buffer,
@@ -282,26 +276,24 @@ methods:
Takes a set of named parameters in the `options` argument.
The string is read from `source` and written to the buffer `dest`.
-
+
Several optional parameters can also be specified in `options`:
-
+
* If `charset` is included, the string is encoded using the specified character
encoding.
- * If `destPosition` is included, data is written into the buffer starting at
- the specified position.
-
- * If `sourcePosition` is included, a substring of the source string starting at the
+ * If `destPosition` is included, data is written into the buffer starting at
+ the specified position.
+
+ * If `sourcePosition` is included, a substring of the source string starting at the
specified position is encoded.
- * If `sourceLength` is included, at most the specified numer of characters
+ * If `sourceLength` is included, at most the specified numer of characters
are encoded.
-
+
Throws an exception if `charset` is not a valid character set,
`source` is null, or either `sourcePosition`, `sourceLength`, or
`sourcePosition`+`sourceLength` is greater than `source.length`.
-
- On Mobile Web, the `charset` option is not supported. All strings are treated as UTF-8.
parameters:
- name: options
@@ -316,7 +308,7 @@ methods:
examples:
- title: Encode String with Default Character Encoding
example: |
- This sample encodes a string using the default character encoding (UTF-8), then trims the
+ This sample encodes a string using the default character encoding (UTF-8), then trims the
buffer to the length of the encoded string.
var buffer = Ti.createBuffer({ length: 1024 });
@@ -325,10 +317,10 @@ methods:
dest: buffer
});
buffer.length = length;
-
+
- title: Encode Substring with Specified Character Encoding
example: |
- This sample encodes the first 10 characters of a string using UTF-16 character encoding.
+ This sample encodes the first 10 characters of a string using UTF-16 character encoding.
// (10 * 2) + BOM = 22
var buffer = Ti.createBuffer({ length: 22 });
@@ -353,14 +345,12 @@ methods:
* If `position` is specified, bytes are read from `source` starting at `position`.
* If `length` is specified, no more than `length` bytes are read.
-
+
* If `charset` is specified, it determines the character encoding used to decode the
string. Otherwise, UTF-8 is assumed.
- Throws an exception if `charset` is not a valid character set, `source` is null,
+ Throws an exception if `charset` is not a valid character set, `source` is null,
or either `position`, `length`, or `position`+`length` is greater than `source.length`.
-
- On Mobile Web, `charset` is not supported. All strings are treated as UTF-8.
parameters:
- name: options
@@ -381,7 +371,7 @@ methods:
- title: Decode a String with a Specified Character Encoding
example: |
This sample decodes a string using the UTF-16 character encoding.
-
+
var buffer = // a buffer containing a UTF-16 encoded string
var string = Ti.Codec.decodeString({
source: buffer,
diff --git a/apidoc/Titanium/Filesystem/File.yml b/apidoc/Titanium/Filesystem/File.yml
index 3d97f0668e0..b42f8dab305 100644
--- a/apidoc/Titanium/Filesystem/File.yml
+++ b/apidoc/Titanium/Filesystem/File.yml
@@ -3,13 +3,13 @@ name: Titanium.Filesystem.File
summary: Object representing a path to a file or directory in the device's persistent storage.
description: |
Use the method to get a handle to a `File` object,
- which represents a given path. There does not need to be an existing file or directory
- does not need to exist before `getFile` is called. If the file doesn't exist, and
- the file path identifies a file in a writable directory, writing to the file
- creates the file implicitly.
+ which represents a given path. There does not need to be an existing file or directory
+ does not need to exist before `getFile` is called. If the file doesn't exist, and
+ the file path identifies a file in a writable directory, writing to the file
+ creates the file implicitly.
See for constants identifying commonly-used device directories.
-
+
Use the [exists](Titanium.Filesystem.File.exists) method to test whether the file exists.
A file object can point to an ordinary file, a directory or a symbolic link.
@@ -20,24 +20,24 @@ description: |
The `File` object doesn't provide methods for random access into the file.
The `read` method reads the file's entire contents into a `Blob` object.
The `write` method can either overwrite the entire file or append to an
- existing file.
+ existing file.
- For random access to a file, such as accessing a small portion of a larger file,
- you can open a file as a [FileStream](Titanium.Filesystem.FileStream) object. Use the
+ For random access to a file, such as accessing a small portion of a larger file,
+ you can open a file as a [FileStream](Titanium.Filesystem.FileStream) object. Use the
[open](Titanium.Filesystem.File.open) method to get a `FileStream` for an
- existing `File` object, or use the method
+ existing `File` object, or use the method
to get a `FileStream` directly without calling `getFile` first.
- The module defines a number of properties and methods related to
- filesystem access, including properties that specify paths for application-specific
+ The module defines a number of properties and methods related to
+ filesystem access, including properties that specify paths for application-specific
directories, and methods for creating temporary files and directories.
- On Android, files may be stored on external storage (that is, removable media such as
+ On Android, files may be stored on external storage (that is, removable media such as
SD Cards).
Note that once created with `getFile`, the path associated with a file object is
- immutable. If you move the underlying file using [move](Titanium.Filesystem.File.move)
- or [rename](Titanium.Filesystem.File.rename), you can no longer access it with the
+ immutable. If you move the underlying file using [move](Titanium.Filesystem.File.move)
+ or [rename](Titanium.Filesystem.File.rename), you can no longer access it with the
original `File` object. You must use `getFile` to get a handle to the new path.
#### Resource Files
@@ -49,14 +49,14 @@ description: |
extends: Titanium.Proxy
since: "0.1"
createable: false
-examples:
+examples:
- title: Reading a File
example: |
Data files shipped with the application are stored in the resources directory.
This example reads string data from a text file.
- // resourcesDirectory is actually the default location, so the first
+ // resourcesDirectory is actually the default location, so the first
// argument could be omitted here.
file = Ti.Filesystem.getFile(Ti.Filesystem.resourcesDirectory, "textfile.txt");
var blob = file.read();
@@ -66,15 +66,15 @@ examples:
blob = null;
- title: Creating a Subdirectory
example: |
- Files that the application writes to need to be stored outside of the
+ Files that the application writes to need to be stored outside of the
resources directory, since that directory is read-only.
This example creates a subdirectory to store downloaded images.
The example assumes that two variables are defined elsewhere in the code:
- myImageID, a string containing some kind of ID for the downloaded image,
+ myImageID, a string containing some kind of ID for the downloaded image,
and myImageData, a `Blob` containing JPEG image data.
- var imageDir = Ti.Filesystem.getFile(Ti.Filesystem.applicationDataDirectory,
+ var imageDir = Ti.Filesystem.getFile(Ti.Filesystem.applicationDataDirectory,
'downloaded_images');
if (! imageDir.exists()) {
imageDir.createDirectory();
@@ -99,23 +99,23 @@ methods:
are appended to this file.
Returns `true` if the operation succeeds.
- parameters:
+ parameters:
- name: data
summary: Data to append.
type: [String,Titanium.Blob,Titanium.Filesystem.File]
returns:
type: Boolean
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
- name: copy
summary: Copies the file identified by this file object to a new path.
description: Returns `true` if the copy succeeds.
- parameters:
+ parameters:
- name: destinationPath
summary: Destination path to copy to.
type: String
returns:
type: Boolean
- platforms: [android, mobileweb]
+ platforms: [android]
- name: createDirectory
summary: Creates a directory at the path identified by this file object.
description: |
@@ -128,13 +128,13 @@ methods:
Note that if you write to a file that doesn't exist, the file is created automatically,
so it is not necessary to call this method unless you want to explicitly create the file
(for example, to create an empty file).
-
- Returns `true` if the file was created successfully. Returns `false` if the
+
+ Returns `true` if the file was created successfully. Returns `false` if the
file already exists, or if the file couldn't be created for some other reason.
returns:
type: Boolean
- platforms: [iphone, ipad, android, mobileweb]
- since: { iphone: "0.9.0", ipad: "0.9.0", mobileweb: "2.0.0", android: "6.1.0" }
+ platforms: [iphone, ipad, android]
+ since: { iphone: "0.9.0", ipad: "0.9.0", android: "6.1.0" }
- name: createTimestamp
summary: Returns the creation timestamp for the file identified by this file object.
@@ -152,7 +152,7 @@ methods:
type: Boolean
parameters:
- name: recursive
- summary: Pass `true` to recursively delete any directory contents.
+ summary: Pass `true` to recursively delete any directory contents.
type: Boolean
optional: true
default: false
@@ -174,7 +174,7 @@ methods:
summary: |
Returns a listing of the directory identified by this file object, or `null`
if this object doesn't identify a directory.
- returns:
+ returns:
type: Array
- name: getParent
summary: Returns the path of the parent directory holding the file identified by this
@@ -182,7 +182,7 @@ methods:
description: |
On iOS, this method returns the path of the parent directory as a String.
- Android supports a [parent](Titanium.Filesystem.File.parent) property, which
+ Android supports a [parent](Titanium.Filesystem.File.parent) property, which
is a `File` object representing the parent directory path. The `getParent` method
on Android is a getter for the `parent` property, so it returns a `File` object
rather than a String.
@@ -198,16 +198,16 @@ methods:
type: String
constants: Titanium.Filesystem.IOS_FILE_PROTECTION_*
platforms: [iphone, ipad]
- since: "4.1.0"
+ since: "4.1.0"
- name: isDirectory
- summary: Returns `true` if this file object represents a directory.
+ summary: Returns `true` if this file object represents a directory.
returns:
type: Boolean
since: { iphone: "3.1.0", ipad: "3.1.0" }
- name: isFile
summary: Returns `true` if this file object represents an ordinary file.
- returns:
+ returns:
type: Boolean
since: { iphone: "3.1.0", ipad: "3.1.0" }
- name: modificationTimestamp
@@ -220,7 +220,7 @@ methods:
- name: move
summary: Moves the file identified by this file object to another path.
description: |
- Note that this method moves the stored file, but doesn't update this
+ Note that this method moves the stored file, but doesn't update this
file object to point to the new path. To access the file after moving it,
you must call [getFile](Titanium.Filesystem.getFile) using the destination
path to obtain a new file handle.
@@ -232,16 +232,16 @@ methods:
type: String
- name: open
- summary: Opens the file identified by this file object for random access.
+ summary: Opens the file identified by this file object for random access.
description: |
- You can open the file for reading, writing, or appending by specifying one of the
+ You can open the file for reading, writing, or appending by specifying one of the
`MODE` constants from :
- [MODE_READ](Titanium.Filesystem.MODE_READ), [MODE_WRITE](Titanium.Filesystem.MODE_WRITE),
+ [MODE_READ](Titanium.Filesystem.MODE_READ), [MODE_WRITE](Titanium.Filesystem.MODE_WRITE),
or [MODE_APPEND](Titanium.Filesystem.MODE_APPEND).
- The `FileStream` object returned by this call can be used to read from, write to, or
+ The `FileStream` object returned by this call can be used to read from, write to, or
append to the file, depending on what mode the file is opened in.
- parameters:
+ parameters:
- name: mode
summary: |
Mode to open the file in: `MODE_READ`, `MODE_WRITE`, or `MODE_APPEND`.
@@ -261,7 +261,7 @@ methods:
Fails if the destination is in a different directory than the current file.
Use [move](Titanium.Filesystem.File.move) to move a file to a different directory.
- Note that this method renames the stored file, but doesn't update this
+ Note that this method renames the stored file, but doesn't update this
file object to point to the new path. To access the file after renaming it,
you must call [getFile](Titanium.Filesystem.getFile) using the destination
path to obtain a new file handle.
@@ -296,7 +296,7 @@ methods:
constants: Titanium.Filesystem.IOS_FILE_PROTECTION_*
type: String
platforms: [iphone, ipad]
- since: "4.1.0"
+ since: "4.1.0"
- name: spaceAvailable
summary: Returns the amount of free space available on the device where the file
@@ -309,9 +309,9 @@ methods:
- name: write
summary: Writes the specified data to the file identified by this file object.
description: |
- If the `append` parameter is `false` or not specified, any existing data in
- the file is overwritten.
-
+ If the `append` parameter is `false` or not specified, any existing data in
+ the file is overwritten.
+
If `append` is `true`, the specified data is appended to the end of the file.
returns:
type: Boolean
@@ -329,18 +329,18 @@ properties:
summary: |
`true` if the file is executable.
description: |
- On iOS, Mobile Web, this property exists but is always `false`.
+ On iOS, this property exists but is always `false`.
type: Boolean
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
permission: read-only
- name: hidden
summary:
Set to `true` if the file is hidden.
description: |
- On iOS, Mobile Web, this property exists but is always `false`.
+ On iOS, this property exists but is always `false`.
type: Boolean
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
- name: name
summary: Name of the file.
@@ -350,7 +350,7 @@ properties:
- name: nativePath
summary: Native path associated with this file object, as a file URL.
description: |
- On iOS, use the [resolve](Titanium.Filesystem.File.resolve)
+ On iOS, use the [resolve](Titanium.Filesystem.File.resolve)
method to obtain a plain file path for use with native modules.
type: String
permission: read-only
@@ -358,17 +358,14 @@ properties:
summary: A `File` object representing the parent directory of the file identified by this object.
type: Titanium.Filesystem.File
permission: read-only
- platforms: [android, mobileweb]
+ platforms: [android]
- name: readonly
summary: |
`true` if the file identified by this object is read-only.
- description: |
- On Mobile Web, this property exists but is always `true` for files in the resources directory
- and `false` for application data and temporary files.
type: Boolean
permission: read-only
- platforms: [android, mobileweb]
+ platforms: [android]
- name: size
summary: Size, in bytes, of the file identified by this object.
@@ -384,7 +381,7 @@ properties:
multiple times will not cause problems. For files distributed with your
app, this will need to be set on boot. This flag will only affect iOS
versions 5.0.1 and later, but is safe to set on earlier versions.
-
+
Note that setting this property to `false` will also prevent the
file identified by this object from being backed up to iTunes.
default: true
@@ -394,8 +391,6 @@ properties:
- name: symbolicLink
summary: |
`true` if the file identified by this object is a symbolic link.
- description: |
- On Mobile Web, this property exists but is always `false`.
type: Boolean
permission: read-only
diff --git a/apidoc/Titanium/Filesystem/FileStream.yml b/apidoc/Titanium/Filesystem/FileStream.yml
index 8cd7e0b8b9b..cb388e2d093 100644
--- a/apidoc/Titanium/Filesystem/FileStream.yml
+++ b/apidoc/Titanium/Filesystem/FileStream.yml
@@ -4,8 +4,7 @@ summary: Wrapper around `Titanium.Filesystem.File` that implements the `Titanium
extends: Titanium.IOStream
since: "1.7"
createable: false
-platforms: [android, iphone, ipad, mobileweb]
+platforms: [android, iphone, ipad]
methods:
- name: close
summary: closes file stream, exception is thrown on error
-
diff --git a/apidoc/Titanium/Filesystem/Filesystem.yml b/apidoc/Titanium/Filesystem/Filesystem.yml
index 17cae7df89e..859d54892d1 100644
--- a/apidoc/Titanium/Filesystem/Filesystem.yml
+++ b/apidoc/Titanium/Filesystem/Filesystem.yml
@@ -7,7 +7,7 @@ description: |
as well as the other Filesystem submodule API documentation.
extends: Titanium.Module
since: "0.1"
-examples:
+examples:
- title: Getting a directory for an application group (iOS)
example: |
This example writes a string to a text file in a shared directory
@@ -36,27 +36,27 @@ methods:
arguments.
description: |
Note that `getFile` does not create a file if one does not exist at the specified
- path. It returns a new `File` object referring to the specified file path. The
- application can create a file at that path by calling
+ path. It returns a new `File` object referring to the specified file path. The
+ application can create a file at that path by calling
[write](Titanium.Filesystem.File.write) or create a directory by calling
[createDirectory](Titanium.Filesystem.File.createDirectory) on the `File` object.
-
+
This method takes a variable number of arguments, where each argument is treated
as a path component. All of the arguments are joined together using the
platform-specific path separator to make the final path.
-
+
If a relative path is passed, the full path should be interpreted relative
- to the current file. For example, if the file `Resources/login/login.js`
+ to the current file. For example, if the file `Resources/login/login.js`
contains the following code:
-
+
var icon = Titanium.Filesystem.getFile('icon.png');
-
- The path is interpreted as `Resources/login/icon.png`.
-
+
+ The path is interpreted as `Resources/login/icon.png`.
+
On iOS, all relative paths are currently interpreted as relative to the
`Resources` directory, **not** to the current context. This is a known issue
that will be addressed in a future release.
-
+
On iOS9, if app thinning is enabled, and the file of interest is an image file
that was bundled with the app (not downloaded during runtime), this will not return
the image file since it is already allocated inside the assets catalog. Please
@@ -66,7 +66,7 @@ methods:
type: Titanium.Filesystem.File
parameters:
- name: path
- summary: One or more path components. Path arguments are joined together using
+ summary: One or more path components. Path arguments are joined together using
the platform specific path separator to form the full path.
type: String
@@ -74,25 +74,25 @@ methods:
summary: Returns a `Blob` object representing the asset catalog image identified by the path
arguments.
description: |
- This method is only applicable on images in assets catalogs for apps with app-thinning
- enabled on iOS. Since the bundled image has been reallocated into assets catalog, it is
- no longer accessible via the original file path. To obtain a `Blob` object representing
+ This method is only applicable on images in assets catalogs for apps with app-thinning
+ enabled on iOS. Since the bundled image has been reallocated into assets catalog, it is
+ no longer accessible via the original file path. To obtain a `Blob` object representing
this image, use the original file path as the parameter in this method instead of using it in
[getFile](Titanium.Filesystem.getFile)
-
- Similar to [getFile](Titanium.Filesystem.getFile), this method takes a variable
- number of arguments, where each argument is treated as a path component.
- All of the arguments are joined together using the platform-specific path separator
+
+ Similar to [getFile](Titanium.Filesystem.getFile), this method takes a variable
+ number of arguments, where each argument is treated as a path component.
+ All of the arguments are joined together using the platform-specific path separator
to make the final path.
-
+
If a relative path is passed, the full path should be interpreted relative
- to the current file. For example, if the file `Resources/login/login.js`
+ to the current file. For example, if the file `Resources/login/login.js`
contains the following code:
-
+
var icon = Titanium.Filesystem.getAsset('icon.png');
-
- The path is interpreted as `Resources/login/icon.png`.
-
+
+ The path is interpreted as `Resources/login/icon.png`.
+
On iOS, all relative paths are currently interpreted as relative to the
`Resources` directory, **not** to the current context. This is a known issue
that will be addressed in a future release.
@@ -101,7 +101,7 @@ methods:
type: Titanium.Blob
parameters:
- name: path
- summary: One or more path components. Path arguments are joined together using
+ summary: One or more path components. Path arguments are joined together using
the platform specific path separator to form the full path.
type: String
platforms: [iphone, ipad]
@@ -115,7 +115,7 @@ methods:
Returns `true` on Android if an external storage device, such as an SD card, is
available for reading and writing.
- Returns `false` on iOS and Mobile Web.
+ Returns `false` on iOS.
returns:
type: Boolean
@@ -150,11 +150,11 @@ methods:
Access mode.
constants: Titanium.Filesystem.MODE_*
type: Number
-
+
- name: path
summary: |
- One or more path components. Path arguments are joined together using the
- platform-specific path separator to form the full path.
+ One or more path components. Path arguments are joined together using the
+ platform-specific path separator to form the full path.
type: String
returns:
type: Titanium.Filesystem.FileStream
@@ -162,9 +162,9 @@ methods:
- name: directoryForSuite
summary: Returns the path to the container directory associated with the specified security application group ID.
description: |
- This is a writable directory used on iOS. Groups of sandboxed apps that need to share files
+ This is a writable directory used on iOS. Groups of sandboxed apps that need to share files
and other information can request a container directory as part of their entitlements.
-
+
When called with a valid group identifier, this method returns the location of that directory as a string.
Returns null if the group identifier is invalid; check the app's entitlements.
parameters:
@@ -200,7 +200,7 @@ properties:
type: String
permission: read-only
platforms: [iphone, ipad]
- since: "4.1.0"
+ since: "4.1.0"
- name: IOS_FILE_PROTECTION_COMPLETE
summary: Constant used to set protection key to NSFileProtectionComplete in file attributes.
@@ -210,29 +210,29 @@ properties:
type: String
permission: read-only
platforms: [iphone, ipad]
- since: "4.1.0"
+ since: "4.1.0"
- name: IOS_FILE_PROTECTION_COMPLETE_UNLESS_OPEN
summary: Constant used to set protection key to NSFileProtectionCompleteUnlessOpen in file attributes.
description: |
- File is stored in an encrypted format on disk. Can be created while the device is locked,
- but once closed, cannot be opened again until the device is unlocked. If the file is opened when
- unlocked, you may continue to access the file normally, even if the user locks the device.
+ File is stored in an encrypted format on disk. Can be created while the device is locked,
+ but once closed, cannot be opened again until the device is unlocked. If the file is opened when
+ unlocked, you may continue to access the file normally, even if the user locks the device.
type: String
permission: read-only
platforms: [iphone, ipad]
- since: "4.1.0"
+ since: "4.1.0"
- name: IOS_FILE_PROTECTION_COMPLETE_UNTIL_FIRST_USER_AUTHENTICATION
summary: Constant used to set protection key to NSFileProtectionCompleteUntilFirstUserAuthentication in file attributes.
description: |
File is stored in an encrypted format on disk. Cannot be accessed until after the device has booted.
- After the user unlocks the device for the first time, your app can access the file and continue to
+ After the user unlocks the device for the first time, your app can access the file and continue to
access it even if the user subsequently locks the device.
type: String
permission: read-only
platforms: [iphone, ipad]
- since: "4.1.0"
+ since: "4.1.0"
- name: applicationCacheDirectory
summary: Path to the application's internal cache directory.
@@ -252,18 +252,18 @@ properties:
- name: applicationDataDirectory
summary: Path to the application's data directory.
description: |
- This is a writable directory that can be used to store applications-specific files.
+ This is a writable directory that can be used to store applications-specific files.
On iOS, this directory is specifically designated for user documents, and a
separate directory,
[applicationSupportDirectory](Titanium.Filesystem.applicationSupportDirectory) is
used for other application data.
-
+
On iOS, files in this directory are backed up unless the
[remoteBackup](Titanium.Filesystem.File.remoteBackup) flag is set to false.
- On Android, files in this directory cannot be accessed by other applications, so
- it should not be used for files that must be used by another application
+ On Android, files in this directory cannot be accessed by other applications, so
+ it should not be used for files that must be used by another application
(for example, a video file that will be passed to the system's video player application).
These files should be stored in the
[externalStorageDirectory](Titanium.Filesystem.externalStorageDirectory).
@@ -277,9 +277,9 @@ properties:
- name: applicationSupportDirectory
summary: Path to the application support directory.
description: |
- This is a writable directory used on iOS for application files that are *not*
+ This is a writable directory used on iOS for application files that are *not*
user documents--including settings files, caches, and so on.
-
+
On iOS, files in this directory are backed up unless the
[remoteBackup](Titanium.Filesystem.File.remoteBackup) flag is set to false.
type: String
@@ -290,20 +290,20 @@ properties:
description: |
This directory can be used for storing arbitrary data. It is read/write and files
in this directory can be passed to other applications, such as video
- players--which is not possible with the
+ players--which is not possible with the
[applicationDataDirectory](Titanium.Filesystem.applicationDataDirectory).
This directory may not be subject to as many memory limitations as the
`applicationDataDirectory`, which is stored in the device's internal storage.
Note, however, that the user may remove or replace the removable storage device
- without warning, so the application must be prepared to handle this case gracefully.
-
+ without warning, so the application must be prepared to handle this case gracefully.
+
The application should check
[isExternalStoragePresent](Titanium.Filesystem.isExternalStoragePresent) before
- accessing this location. The application should also handle any exceptions generated
- if the storage device is unmounted during use, or if the files stored on external
+ accessing this location. The application should also handle any exceptions generated
+ if the storage device is unmounted during use, or if the files stored on external
storage are not available.
-
+
type: String
permission: read-only
platforms: [android]
@@ -316,14 +316,14 @@ properties:
summary: Path to the application's resource directory.
description: |
This directory is read-only. If you need to modify any files in this directory,
- they must first be copied to another directory, such as
+ they must first be copied to another directory, such as
[applicationDataDirectory](Titanium.Filesystem.applicationDataDirectory) or
- [tempDirectory](Titanium.Filesystem.tempDirectory).
-
- On iOS,
- writable files can also be placed in the
+ [tempDirectory](Titanium.Filesystem.tempDirectory).
+
+ On iOS,
+ writable files can also be placed in the
[applicationSupportDirectory](Titanium.Filesystem.applicationSupportDirectory).
- On Android, writable files can also be placed in the
+ On Android, writable files can also be placed in the
[externalStorageDirectory](Titanium.Filesystem.externalStorageDirectory).
Note that when running on the simulator, the resources directory may be writable,
@@ -335,19 +335,19 @@ properties:
description: |
On Android, the raw resources directory can be used for resources that need to be
accessed as individual files, not included in the Android resources bundle. For
- example, sound files placed in the raw resources directory can be accessed by
+ example, sound files placed in the raw resources directory can be accessed by
notifications, which cannot access sound files from the resource
directory.
- To use raw resources, place files in the `platform/android/res/raw` folder, where
+ To use raw resources, place files in the `platform/android/res/raw` folder, where
`platform` is at the top level of the project, not inside the `Resources` folder. You
will need to create the `platform` folder and subfolders.
This directory is read-only. If you need to modify any files in this directory,
- they must first be copied to another directory, such as
+ they must first be copied to another directory, such as
[applicationDataDirectory](Titanium.Filesystem.applicationDataDirectory) or
- [tempDirectory](Titanium.Filesystem.tempDirectory).
-
+ [tempDirectory](Titanium.Filesystem.tempDirectory).
+
platforms: [android]
since: "3.0.2"
type: String
@@ -358,15 +358,14 @@ properties:
permission: read-only
- name: tempDirectory
- summary: Path for the application's temporary directory.
+ summary: Path for the application's temporary directory.
description: |
This directory can be used for storing temporary files. Files in this directory
may not persist when the application is shut down and restarted.
type: String
permission: read-only
-
+
---
name: RequestStorageAccessResult
summary: Argument passed to the callback when a request finishes successfully or erroneously.
extends: ErrorResponse
-
diff --git a/apidoc/Titanium/Geolocation/Geolocation.yml b/apidoc/Titanium/Geolocation/Geolocation.yml
index 4b20cf9dfff..e86e814f324 100644
--- a/apidoc/Titanium/Geolocation/Geolocation.yml
+++ b/apidoc/Titanium/Geolocation/Geolocation.yml
@@ -9,16 +9,16 @@ description: |
* Geocoding and reverse geocoding. Converting geographic coordinates into
addresses, and converting addresses into geographic coordinates.
- Using location services can have a significant impact on a device's battery life,
+ Using location services can have a significant impact on a device's battery life,
so it's important to use them in the most efficient manner possible. Power consumption
- is strongly influenced by the accuracy and frequency of location updates required by
- your application.
-
+ is strongly influenced by the accuracy and frequency of location updates required by
+ your application.
+
The location services systems of the underlying platforms are very different, so there
are significant implementation differences between the platforms.
The basic methods of requesting location information and receiving location updates
- are essentially the same on all platforms. However, the method of configuring the
+ are essentially the same on all platforms. However, the method of configuring the
accuracy and frequency of location updates is different for each platform.
#### Getting Location Information
@@ -39,12 +39,12 @@ description: |
In iOS, the accuracy (and power consumption) of location services is primarily
determined by the [accuracy](Titanium.Geolocation.accuracy) setting. This can be set
to one of the following values:
-
+
* [ACCURACY_BEST](Titanium.Geolocation.ACCURACY_BEST) (highest accuracy and power consumption)
* [ACCURACY_HIGH](Titanium.Geolocation.ACCURACY_HIGH)
- * [ACCURACY_NEAREST_TEN_METERS](Titanium.Geolocation.ACCURACY_NEAREST_TEN_METERS)
- * [ACCURACY_HUNDRED_METERS](Titanium.Geolocation.ACCURACY_HUNDRED_METERS)
- * [ACCURACY_KILOMETER](Titanium.Geolocation.ACCURACY_KILOMETER)
+ * [ACCURACY_NEAREST_TEN_METERS](Titanium.Geolocation.ACCURACY_NEAREST_TEN_METERS)
+ * [ACCURACY_HUNDRED_METERS](Titanium.Geolocation.ACCURACY_HUNDRED_METERS)
+ * [ACCURACY_KILOMETER](Titanium.Geolocation.ACCURACY_KILOMETER)
* [ACCURACY_LOW](Titanium.Geolocation.ACCURACY_LOW)
* [ACCURACY_THREE_KILOMETERS](Titanium.Geolocation.ACCURACY_THREE_KILOMETERS) (lowest
accuracy and power consumption).
@@ -81,72 +81,58 @@ description: |
#### Configurating Location Updates on Android
-
+
Prior to Titanium Mobile 2.0, Titanium attempted to follow the iOS model on Android,
but this didn't fit the native Android model well. In Release 2.0, three different
location service modes are supported on Android: *simple*, *manual*, and *legacy*.
- * *Simple mode* provides a compromise mode that provides adaquate support for
+ * *Simple mode* provides a compromise mode that provides adaquate support for
undemanding location applications without requiring developers to
write a lot of Android-specific code. To use simple mode:
- 1. Leave the flag set to `false` (the
+ 1. Leave the flag set to `false` (the
default value).
-
- 2. Set the [accuracy](Titanium.Geolocation.accuracy) property to
- either [ACCURACY_HIGH](Titanium.Geolocation.ACCURACY_HIGH) or
+
+ 2. Set the [accuracy](Titanium.Geolocation.accuracy) property to
+ either [ACCURACY_HIGH](Titanium.Geolocation.ACCURACY_HIGH) or
[ACCURACY_LOW](Titanium.Geolocation.ACCURACY_LOW).
* *Manual mode* gives developers low-level control of location updates, including
enabling individual location providers and filtering updates, for the best
- combination of accuracy and battery life.
+ combination of accuracy and battery life.
Manual mode is used when the flag is set
to `true`. In manual mode, the `accuracy` property is not used, and all
configuration is done through the module.
- * *Legacy mode* is the mode that existed prior to 2.0. Legacy mode is
- used when the `manualMode` flag is `false` and the `accuracy` property is
+ * *Legacy mode* is the mode that existed prior to 2.0. Legacy mode is
+ used when the `manualMode` flag is `false` and the `accuracy` property is
set to one of the iOS `ACCURACY` constants:
* [ACCURACY_BEST](Titanium.Geolocation.ACCURACY_BEST) (highest accuracy and power consumption)
- * [ACCURACY_NEAREST_TEN_METERS](Titanium.Geolocation.ACCURACY_NEAREST_TEN_METERS)
- * [ACCURACY_HUNDRED_METERS](Titanium.Geolocation.ACCURACY_HUNDRED_METERS)
- * [ACCURACY_KILOMETER](Titanium.Geolocation.ACCURACY_KILOMETER)
+ * [ACCURACY_NEAREST_TEN_METERS](Titanium.Geolocation.ACCURACY_NEAREST_TEN_METERS)
+ * [ACCURACY_HUNDRED_METERS](Titanium.Geolocation.ACCURACY_HUNDRED_METERS)
+ * [ACCURACY_KILOMETER](Titanium.Geolocation.ACCURACY_KILOMETER)
* [ACCURACY_THREE_KILOMETERS](Titanium.Geolocation.ACCURACY_THREE_KILOMETERS) (lowest
- accuracy and power consumption).
-
- This mode is deprecated and should not be used for new development.
+ accuracy and power consumption).
+
+ This mode is deprecated and should not be used for new development.
- In this mode, the specified `accuracy` value determines the
+ In this mode, the specified `accuracy` value determines the
*minimum distance between location updates*. If `accuracy` is set to
`ACCURACY_BEST`, no distance filter is used on updates.
-
+
In legacy mode, only a single location provider (GPS, network, or passive) is
- enabled at a time. You can specify a the location provider using the
+ enabled at a time. You can specify a the location provider using the
[preferredProvider](Titanium.Geolocation.preferredProvider) property.
-
+
You can also specifying a desired update frequency using the
[frequency](Titanium.Geolocation.frequency) property. The `preferredProvider`
and `frequency` properties are not used in any other mode.
- #### Configuring Location Updates on Mobile Web
-
- Location services on Mobile Web operate similarly to the *simple mode* operations on
- Android. Setting [accuracy](Titanium.Geolocation.accuracy) property to
- [ACCURACY_HIGH](Titanium.Geolocation.ACCURACY_HIGH) yeilds the best available location
- updates, with the hightest power consumption.
- Using [ACCURACY_LOW](Titanium.Geolocation.ACCURACY_LOW) provides lower-quality location
- updates with lower power consumption.
-
- In addition to the accuracy setting, there are several Mobile Web-specific settings.
- See for details.
-
#### Using the Compass
Both iOS and Android support a receiving heading updates from a hardware compass, if available.
- On Mobile Web, heading updates are supported if the browser supports this feature.
- Currently, this support is only available on Mobile Safari.
Check the [hasCompass](Titanium.Geolocation.hasCompass) property to see if the current
device supports a compass.
@@ -185,7 +171,7 @@ description: |
The module provides two methods, [forwardGeocoder](Titanium.Geolocation.forwardGeocoder) and [reverseGeocoder](Titanium.Geolocation.reverseGeocoder)
to convert between geographic coordinates and addresses. These methods map to MapQuest Open Nominatim Search Service.
- While this API has the advantage that it has no daily usage limits, please note that the data backing this API is crowd sourced and might not return
+ While this API has the advantage that it has no daily usage limits, please note that the data backing this API is crowd sourced and might not return
proper values for valid addresses and geographic coordinates.
If geocoding services are essential component of the application, developers are encouraged to use commercial geocoding providers.
@@ -200,9 +186,9 @@ methods:
summary: address to resolve.
type: String
- name: callback
- summary: Function to invoke on success or failure.
+ summary: Function to invoke on success or failure.
type: Callback
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
- name: getCurrentHeading
summary: Retrieves the current compass heading.
@@ -210,48 +196,48 @@ methods:
- name: callback
summary: Function to invoke on success or failure of obtaining the current heading.
type: Callback
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
- name: getCurrentPosition
- summary: Retrieves the last known location from the device.
+ summary: Retrieves the last known location from the device.
description: |
On Android, the radios are not turned on to update the location, and a cached
location is used.
-
- On iOS the radios **may** be used if the location is too "old".
+
+ On iOS the radios **may** be used if the location is too "old".
parameters:
- name: callback
- summary: Function to invoke on success or failure of obtaining the current location.
+ summary: Function to invoke on success or failure of obtaining the current location.
type: Callback
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
- name: hasLocationPermissions
summary: Returns `true` if the app has location access.
parameters:
- name: authorizationType
summary: |
- Types of geolocation's authorizations. This is an iOS 8 and above only parameter and is ignored on
+ Types of geolocation's authorizations. This is an iOS 8 and above only parameter and is ignored on
Android and iOS 7.
constants: [Titanium.Geolocation.AUTHORIZATION_ALWAYS,Titanium.Geolocation.AUTHORIZATION_WHEN_IN_USE]
- type: Number
+ type: Number
returns:
- type: Boolean
+ type: Boolean
platforms: [iphone, ipad, android]
since: "5.1.0"
-
+
- name: requestLocationPermissions
summary: Requests for location access.
description: |
On Android, the request view will show if the permission is not accepted by the user, and the user did
not check the box "Never ask again" when denying the request. If the user checks the box "Never ask again,"
- the user has to manually enable the permission in device settings. If the user asks for permissions or
- tries to get unauthorized location information, then the app should call the request method to show
- the permission settings. This method requests `Manifest.permission.ACCESS_FINE_LOCATION` on Android.
+ the user has to manually enable the permission in device settings. If the user asks for permissions or
+ tries to get unauthorized location information, then the app should call the request method to show
+ the permission settings. This method requests `Manifest.permission.ACCESS_FINE_LOCATION` on Android.
If you require other permissions, you can also use .
In iOS 8, Apple introduced the Info.plist keys `NSLocationWhenInUseUsageDescription` and `NSLocationAlwaysUsageDescription`
that are used to display an own description while requesting location permissions. In addition to this method, you need to
- include one of these keys (based on how your location updates should behave) or the application will crash if your app does not.
+ include one of these keys (based on how your location updates should behave) or the application will crash if your app does not.
Check the [Apple docs](https://developer.apple.com/library/prerelease/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html) for more information.
parameters:
- name: authorizationType
@@ -281,14 +267,14 @@ methods:
type: Number
- name: callback
- summary: Function to invoke on success or failure.
+ summary: Function to invoke on success or failure.
type: Callback
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
events:
- name: calibration
- summary: Fired when the device detects interface and requires calibration.
+ summary: Fired when the device detects interface and requires calibration.
description: |
When this event is fired, the OS calibration UI is being displayed to the end user.
platforms: [iphone, ipad]
@@ -322,7 +308,7 @@ events:
- name: code
summary: if `success` is false, the error code if available.
type: Number
-
+
- name: success
summary: Indicates if location data was successfully retrieved.
type: Boolean
@@ -343,9 +329,9 @@ events:
- name: locationupdatepaused
summary: Fired when location updates are paused by the OS. Available in iOS 6.0 and later.
description: |
- This event is fired when [pauseLocationUpdateAutomatically](Titanium.Geolocation.pauseLocationUpdateAutomatically)
- is set to `true` and if the OS detects that the device's location is not changing,
- causing it to pause the delivery of updates in order to shut down the appropriate
+ This event is fired when [pauseLocationUpdateAutomatically](Titanium.Geolocation.pauseLocationUpdateAutomatically)
+ is set to `true` and if the OS detects that the device's location is not changing,
+ causing it to pause the delivery of updates in order to shut down the appropriate
hardware and save power.
platforms: [iphone, ipad]
since: "3.1.0"
@@ -353,8 +339,8 @@ events:
- name: locationupdateresumed
summary: Fired when location manager is resumed by the OS. Available in iOS 6.0 and later.
description: |
- When location updates are paused and need to be resumed (perhaps because the user
- is moving again), this event is fired to let the app know that it is about to
+ When location updates are paused and need to be resumed (perhaps because the user
+ is moving again), this event is fired to let the app know that it is about to
begin the delivery of those updates again.
platforms: [iphone, ipad]
since: "3.1.0"
@@ -362,7 +348,7 @@ events:
- name: authorization
summary: Fired when changes are made to the authorization status for location services. Available in iOS 8.0 and later.
description: |
- This event is fired whenever the application's ability to use location services changes.
+ This event is fired whenever the application's ability to use location services changes.
Changes can occur because the user allowed or denied the use of location services for the app or the system as a whole.
properties:
- name: authorizationStatus
@@ -384,7 +370,7 @@ properties:
battery usage.
Using this value on Android enables *legacy mode* operation, which is not
- recommended.
+ recommended.
type: Number
permission: read-only
platforms: [android, iphone, ipad]
@@ -395,7 +381,7 @@ properties:
updates accurate to the nearest 100 meters.
description: |
Using this value on Android enables *legacy mode* operation, which is not
- recommended.
+ recommended.
type: Number
permission: read-only
platforms: [android, iphone, ipad]
@@ -406,7 +392,7 @@ properties:
updates accurate to the nearest kilometer.
description: |
Using this value on Android enables *legacy mode* operation, which is not
- recommended.
+ recommended.
type: Number
permission: read-only
platforms: [android, iphone, ipad]
@@ -417,7 +403,7 @@ properties:
updates accurate to the nearest 10 meters.
description: |
Using this value on Android enables *legacy mode* operation, which is not
- recommended.
+ recommended.
type: Number
permission: read-only
platforms: [android, iphone, ipad]
@@ -428,7 +414,7 @@ properties:
updates accurate to the nearest three kilometers.
description: |
Using this value on Android enables *legacy mode* operation, which is not
- recommended.
+ recommended.
type: Number
permission: read-only
platforms: [android, iphone, ipad]
@@ -441,16 +427,16 @@ properties:
Using this value on Android enables *simple mode* operation.
type: Number
permission: read-only
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
since: "2.0.0"
-
+
- name: ACCURACY_BEST_FOR_NAVIGATION
summary: |
- Use with [accuracy](Titanium.Geolocation.accuracy) to request highest possible
+ Use with [accuracy](Titanium.Geolocation.accuracy) to request highest possible
accuracy and combine it with additional sensor data.
description: |
- Using this value is intended for use in navigation applications that require
- precise position information at all times and are intended to be used only while
+ Using this value is intended for use in navigation applications that require
+ precise position information at all times and are intended to be used only while
the device is plugged in.
type: Number
permission: read-only
@@ -466,12 +452,12 @@ properties:
Using this value on Android enables *simple mode* operation.
type: Number
permission: read-only
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
since: "2.0.0"
- name: AUTHORIZATION_AUTHORIZED
summary: |
- A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
+ A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
indicating that the application is authorized to use location services.
type: Number
permission: read-only
@@ -479,7 +465,7 @@ properties:
- name: AUTHORIZATION_DENIED
summary: |
- A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
+ A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
indicating that the application is not authorized to use location services, *or*
location services are disabled.
type: Number
@@ -488,7 +474,7 @@ properties:
- name: AUTHORIZATION_RESTRICTED
summary: |
- A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
+ A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
indicating that the application is not authorized to use location servies *and*
the user cannot change this application's status.
type: Number
@@ -497,7 +483,7 @@ properties:
- name: AUTHORIZATION_UNKNOWN
summary: |
- A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
+ A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
indicating that the authorization state is unknown.
description: |
This value is always returned if the device is running an iOS release prior to 4.2.
@@ -507,7 +493,7 @@ properties:
- name: AUTHORIZATION_ALWAYS
summary: |
- A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
+ A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
indicating that the application is authorized to start location services at any time. This authorization
includes the use of all location services, including monitoring regions and significant location changes.
type: Number
@@ -518,7 +504,7 @@ properties:
- name: AUTHORIZATION_WHEN_IN_USE
summary: |
- A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
+ A [locationServicesAuthorization](Titanium.Geolocation.locationServicesAuthorization) value
indicating that the application is authorized to start most location services only while running in the foreground.
type: Number
permission: read-only
@@ -579,7 +565,7 @@ properties:
- name: ERROR_TIMEOUT
summary: Error indicating a timeout.
- platforms: [mobileweb]
+ platforms: []
type: Number
permission: read-only
@@ -587,12 +573,12 @@ properties:
summary: |
Specifies the GPS location provider.
description: |
- Used with [preferredProvider](Titanium.Geolocation.preferredProvider),
+ Used with [preferredProvider](Titanium.Geolocation.preferredProvider),
[LocationProvider.name](Titanium.Geolocation.Android.LocationProvider),
[LocationRule.provider](Titanium.Geolocation.Android.LocationRule).
- In general, the GPS provider has the highest power consumption and the
- highest accuracy, but this may vary. In some circumstances, the network
+ In general, the GPS provider has the highest power consumption and the
+ highest accuracy, but this may vary. In some circumstances, the network
provider may be more reliable.
type: String
permission: read-only
@@ -602,7 +588,7 @@ properties:
summary: |
Specifies the network location provider.
description: |
- Used with [preferredProvider](Titanium.Geolocation.preferredProvider),
+ Used with [preferredProvider](Titanium.Geolocation.preferredProvider),
[LocationProvider.name](Titanium.Geolocation.Android.LocationProvider),
[LocationRule.provider](Titanium.Geolocation.Android.LocationRule).
@@ -617,7 +603,7 @@ properties:
summary: |
Specifies the passive location provider.
description: |
- Used with [preferredProvider](Titanium.Geolocation.preferredProvider),
+ Used with [preferredProvider](Titanium.Geolocation.preferredProvider),
[LocationProvider.name](Titanium.Geolocation.Android.LocationProvider),
[LocationRule.provider](Titanium.Geolocation.Android.LocationRule).
@@ -635,12 +621,12 @@ properties:
permission: read-only
platforms: [iphone,ipad]
since: "3.1.0"
-
+
- name: ACTIVITYTYPE_AUTOMOTIVE_NAVIGATION
summary: The location data is used for tracking location changes to the automobile specifically during vehicular navigation.
description: |
- Used with [activityType](Titanium.Geolocation.activityType). This activity might
- cause location updates to be paused only when the vehicle does not move for an
+ Used with [activityType](Titanium.Geolocation.activityType). This activity might
+ cause location updates to be paused only when the vehicle does not move for an
extended period of time. Available in iOS 6.0 and later.
type: String
permission: read-only
@@ -650,8 +636,8 @@ properties:
- name: ACTIVITYTYPE_FITNESS
summary: The location data is used for tracking any pedestrian-related activity.
description: |
- Used with [activityType](Titanium.Geolocation.activityType). This activity might
- cause location updates to be paused only when the user does not move a significant
+ Used with [activityType](Titanium.Geolocation.activityType). This activity might
+ cause location updates to be paused only when the user does not move a significant
distance over a period of time.Available in iOS 6.0 and later.
type: String
permission: read-only
@@ -660,13 +646,13 @@ properties:
- name: ACTIVITYTYPE_OTHER_NAVIGATION
summary: |
- The location data is used for tracking movements of other types of vehicular
+ The location data is used for tracking movements of other types of vehicular
navigation that are not automobile related.
description: |
- Used with [activityType](Titanium.Geolocation.activityType). You would use this
- to track navigation by boat, train, or plane. Do not use this type for pedestrian
- navigation tracking. This activity might cause location updates to be paused only
- when the vehicle does not move a significant distance over a period of time.
+ Used with [activityType](Titanium.Geolocation.activityType). You would use this
+ to track navigation by boat, train, or plane. Do not use this type for pedestrian
+ navigation tracking. This activity might cause location updates to be paused only
+ when the vehicle does not move a significant distance over a period of time.
Available in iOS 6.0 and later.
type: String
permission: read-only
@@ -684,26 +670,26 @@ properties:
* [ACCURACY_LOW](Titanium.Geolocation.ACCURACY_LOW) for lower-quality location
updates with lower power consumption.
- For finer-grained control on iOS, specify one of `ACCURACY_BEST`,
+ For finer-grained control on iOS, specify one of `ACCURACY_BEST`,
`ACCURACY_NEAREST_TEN_METERS`, `ACCURACY_HUNDRED_METERS`, `ACCURACY_KILOMETER`, or
- `ACCURACY_THREE_KILOMETERS`.
+ `ACCURACY_THREE_KILOMETERS`.
- For finer-grained control on Android, use *manual mode*, instead of specifing an accuracy.
- This mode requires more active management on the part of the application, but it
+ For finer-grained control on Android, use *manual mode*, instead of specifing an accuracy.
+ This mode requires more active management on the part of the application, but it
is recommended to maximize accuracy and battery life.
See for details on using manual mode.
- Note that for backwards compatibility, Android supports using the iOS accuracy constants.
+ Note that for backwards compatibility, Android supports using the iOS accuracy constants.
This usage is deprecated. Applications using one of the iOS constants should
migrate to using `ACCURACY_HIGH`, `ACCURACY_LOW`, or Android manual mode.
type: Number
constants: Titanium.Geolocation.ACCURACY_*
-
+
- name: distanceFilter
- summary: The minimum change of position (in meters) before a 'location' event is fired.
+ summary: The minimum change of position (in meters) before a 'location' event is fired.
description: |
- If set to 0, distance filtering is disabled, meaning that location events are
+ If set to 0, distance filtering is disabled, meaning that location events are
generated continuously.
type: Number
default: 0
@@ -723,8 +709,8 @@ properties:
Note that the frequency value is used as a guideline: there are no guarantees
that the device will provide updates at the specified frequency.
-
- A lower frequency value generally increases power consumption.
+
+ A lower frequency value generally increases power consumption.
A value of 0 means that updates should be generated as quickly as possible.
type: Number
@@ -733,11 +719,10 @@ properties:
summary: Indicates whether the current device supports a compass.
type: Boolean
permission: read-only
- platforms: [android, iphone, ipad, mobileweb]
- since: { mobileweb: "2.1.0" }
+ platforms: [android, iphone, ipad]
- name: headingFilter
- summary: Minimum heading change (in degrees) before a `heading` event is fired.
+ summary: Minimum heading change (in degrees) before a `heading` event is fired.
description: |
Set to a value greater than zero to reduce the number of heading events generated.
type: Number
@@ -747,8 +732,8 @@ properties:
- name: locationServicesAuthorization
summary: Returns an authorization constant indicating if the application has access to location services.
description: |
- Always returns `AUTHORIZATION_UNKNOWN` on pre-4.2 devices.
-
+ Always returns `AUTHORIZATION_UNKNOWN` on pre-4.2 devices.
+
If `locationServicesAuthorization` is `AUTHORIZATION_RESTRICTED`, you should not
attempt to re-authorize: this will lead to issues.
type: Number
@@ -782,7 +767,7 @@ properties:
Setting a preferred provider enables legacy location mode on Android.
Note that only a single provider can be active at one time in legacy mode.
- The preferred provider affects power consumption. In general, `PROVIDER_GPS`
+ The preferred provider affects power consumption. In general, `PROVIDER_GPS`
requires the most power, and `PROVIDER_PASSIVE` requires the least.
If `undefined`, the preferred provider is auto-detected.
@@ -796,7 +781,7 @@ properties:
Text to display in the permission dialog when requesting location
services.
description: |
- This property informs the end user why location services are being requested by
+ This property informs the end user why location services are being requested by
the application. This property is **required** starting in iOS 4.0.
deprecated for >= iOS6, include the `NSLocationUsageDescription` key with your
description in tiapp.xml instead.
@@ -808,23 +793,23 @@ properties:
summary: Determines whether the compass calibration UI is shown if needed.
description: |
Set to `false` to disable display of the compass calibration UI. This may result
- in invalid heading data.
+ in invalid heading data.
type: Boolean
default: true
platforms: [iphone, ipad]
- name: trackSignificantLocationChange
summary: |
- Indicates if the location changes should be updated only when a significant change
+ Indicates if the location changes should be updated only when a significant change
in location occurs.
description: |
- The trackSignificantLocationChange service offers a low-power location service for
+ The trackSignificantLocationChange service offers a low-power location service for
devices with cellular radios.This service is available only in iOS 4.0 and later.
- This service offers a significant power savings and provides accuracy that is good
- enough for most applications. It uses the device's cellular radio to determine the
- user's location and report changes in that location, allowing the system to manage
- power usage much more aggressively than it could otherwise. This service is also
- capable of waking up an application that is currently suspended or not running in
+ This service offers a significant power savings and provides accuracy that is good
+ enough for most applications. It uses the device's cellular radio to determine the
+ user's location and report changes in that location, allowing the system to manage
+ power usage much more aggressively than it could otherwise. This service is also
+ capable of waking up an application that is currently suspended or not running in
order to deliver new location data.
type: Boolean
default: false
@@ -835,7 +820,7 @@ properties:
summary: |
Determines if the app can do background location updates.
description: |
- When `UIBackgroundModes` include `location` in tiapp.xml, this property is
+ When `UIBackgroundModes` include `location` in tiapp.xml, this property is
set to `true` by default. Available in iOS 9.0 and later.
type: Boolean
default: true
@@ -847,13 +832,13 @@ properties:
summary: |
The type of user activity to be associated with the location updates. Available in iOS 6.0 and later.
description: |
- The information in this property is used as a cue to determine when location
- updates may be automatically paused. Pausing updates gives the system the
- opportunity to save power in situations where the user's location is not likely
- to be changing. For example, if the activity type is
- [ACTIVITYTYPE_AUTOMOTIVE_NAVIGATION](Titanium.Geolocation.ACTIVITYTYPE_AUTOMOTIVE_NAVIGATION)
- and no location changes have occurred recently, the radios might be powered down
- until movement is detected again.
+ The information in this property is used as a cue to determine when location
+ updates may be automatically paused. Pausing updates gives the system the
+ opportunity to save power in situations where the user's location is not likely
+ to be changing. For example, if the activity type is
+ [ACTIVITYTYPE_AUTOMOTIVE_NAVIGATION](Titanium.Geolocation.ACTIVITYTYPE_AUTOMOTIVE_NAVIGATION)
+ and no location changes have occurred recently, the radios might be powered down
+ until movement is detected again.
type: Number
constants: Titanium.Geolocation.ACTIVITYTYPE_*
default:
@@ -863,12 +848,12 @@ properties:
- name: pauseLocationUpdateAutomatically
summary: Indicates whether the location updates may be paused. Available in iOS 6.0 and later.
description: |
- Allowing the location updates to be paused can improve battery life on the
- target device without sacrificing location data. When this property is set to YES,
- the location updates are paused (and powers down the appropriate hardware) at
- times when the location data is unlikely to change. For example, if the user stops
- for food while using a navigation app, the location manager might pause updates for
- a period of time. You can help the determination of when to pause location updates
+ Allowing the location updates to be paused can improve battery life on the
+ target device without sacrificing location data. When this property is set to YES,
+ the location updates are paused (and powers down the appropriate hardware) at
+ times when the location data is unlikely to change. For example, if the user stops
+ for food while using a navigation app, the location manager might pause updates for
+ a period of time. You can help the determination of when to pause location updates
by assigning a value to the [activityType](Titanium.Geolocation.activityType) property.
type: Boolean
default: false
@@ -928,16 +913,16 @@ properties:
- name: heading
summary: |
- Compass heading, in degrees. May be unknown if device is not moving. On
+ Compass heading, in degrees. May be unknown if device is not moving. On
iOS, a negative value indicates that the heading data is not valid.
type: Number
- name: speed
summary: |
- Current speed in meters/second. On iOS, a negative value indicates that the
- heading data is not valid or the accuracy is configured incorrectly.
- Note: Due to the Apple Geolocation API, set the
- property to in order to properly
+ Current speed in meters/second. On iOS, a negative value indicates that the
+ heading data is not valid or the accuracy is configured incorrectly.
+ Note: Due to the Apple Geolocation API, set the
+ property to in order to properly
measure speed changes and prevent the app from returning negative values.
type: Number
@@ -962,38 +947,38 @@ properties:
- name: level
summary: The logical floor of the building.
description: |
- Level values represent logical levels above or below ground level and are not
+ Level values represent logical levels above or below ground level and are not
intended to correspond to any numbering scheme in use by the building itself.
- The ground floor of a building is always represented by the value 0. Floors
- above the ground floor are represented by positive integers, so a value of 1
- represents the floor above ground level, a value of 2 represents two floors
- above ground level, and so on. Floors below the ground floor are represented
- by corresponding negative integers, with a value of -1 representing the floor
+ The ground floor of a building is always represented by the value 0. Floors
+ above the ground floor are represented by positive integers, so a value of 1
+ represents the floor above ground level, a value of 2 represents two floors
+ above ground level, and so on. Floors below the ground floor are represented
+ by corresponding negative integers, with a value of -1 representing the floor
immediately below ground level and so on.
type: Number
---
name: ForwardGeocodeResponse
summary: |
- Simple object returned in the callback from the
+ Simple object returned in the callback from the
[forwardGeocoder](Titanium.Geolocation.forwardGeocoder) method.
Note that Android includes a number of extra fields.
extends: ErrorResponse
-properties:
+properties:
- name: success
summary: Indicates if the operation succeeded.
description: Returns `true` if request succeeded, `false` otherwise.
type: Boolean
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
- name: error
summary: Error message, if any returned.
description: Will be undefined if `success` is `true`.
type: String
- platforms: [android, iphone, ipad, mobileweb]
-
+ platforms: [android, iphone, ipad]
+
- name: code
summary: Error code. Returns 0 if `success` is `true`.
description: |
@@ -1001,8 +986,8 @@ properties:
was generated by the operating system, that system's error value is used.
Otherwise, this value will be -1.
type: Number
- since: { android: "3.1.0", iphone: "3.1.0", ipad: "3.1.0", mobileweb: "3.1.1" }
- platforms: [android, iphone, ipad, mobileweb]
+ since: { android: "3.1.0", iphone: "3.1.0", ipad: "3.1.0" }
+ platforms: [android, iphone, ipad]
- name: accuracy
summary: Estimated accuracy of the geocoding, in meters.
@@ -1012,14 +997,12 @@ properties:
- name: longitude
summary: Longitude of the geocoded address.
type: String
- since: { mobileweb: "3.1.1" }
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
- name: latitude
summary: Latitude of the geocoded address.
type: String
- since: { mobileweb: "3.1.1" }
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
- name: street
summary: Street name, without street address.
@@ -1047,7 +1030,7 @@ properties:
platforms: [android]
- name: postalCode
- summary: Postal code.
+ summary: Postal code.
type: String
platforms: [android]
@@ -1057,7 +1040,7 @@ properties:
platforms: [android]
- name: countryCode
- summary: Country code.
+ summary: Country code.
type: String
platforms: [android]
@@ -1094,7 +1077,7 @@ properties:
description: Will be undefined if `success` is `true`.
type: String
platforms: [iphone, ipad]
-
+
- name: code
summary: Error code.
description: |
@@ -1116,16 +1099,13 @@ properties:
- name: accuracy
summary: Accuracy of the compass heading, in platform-specific units.
description: |
- On iOS, accuracy is returned as a maximum deviation in degrees,
- the smaller the value, the more accurate the heading is. For example,
- a value of 10 means the heading is plus or minus 10 degrees from the
- actual value. A negative value indicates the compass heading is invalid;
+ On iOS, accuracy is returned as a maximum deviation in degrees,
+ the smaller the value, the more accurate the heading is. For example,
+ a value of 10 means the heading is plus or minus 10 degrees from the
+ actual value. A negative value indicates the compass heading is invalid;
for example, if there is magnetic interference, or if the compass is not calibrated.
-
- On Mobile Web, compass is currently supported only on iOS, and returns
- the same value as iOS native.
-
- On Android, the value is set to either 1 (low accuracy), 2 (medium accuracy)
+
+ On Android, the value is set to either 1 (low accuracy), 2 (medium accuracy)
or 3 (high accuracy). No specific definition of these accuracy values is supplied.
type: Number
@@ -1170,9 +1150,9 @@ properties:
name: LocationProviderDict
summary: Simple object describing a location provider.
description: |
- The `accuracy` and `power` values correspond to constants defined in the
+ The `accuracy` and `power` values correspond to constants defined in the
Android API. See
- [android.location.Criteria](http://developer.android.com/reference/android/location/Criteria.html)
+ [android.location.Criteria](http://developer.android.com/reference/android/location/Criteria.html)
in the Android API Reference.
These values are generalizations. In general, a provider with coarse accuracy will
@@ -1198,7 +1178,7 @@ properties:
---
name: ReverseGeocodeResponse
summary: |
- Simple object returned in the callback from the
+ Simple object returned in the callback from the
[reverseGeocoder](Titanium.Geolocation.reverseGeocoder) method.
extends: ErrorResponse
properties:
@@ -1212,7 +1192,7 @@ properties:
description: Will be undefined if `success` is `true`.
type: String
since: "3.1.0"
-
+
- name: code
summary: Error code. Returns 0 if `success` is `true`.
description: |
@@ -1225,7 +1205,7 @@ properties:
---
name: GeocodedAddress
summary: |
- Simple object representing a place, returned in the callback from the
+ Simple object representing a place, returned in the callback from the
[reverseGeocoder](Titanium.Geolocation.reverseGeocoder) method.
properties:
diff --git a/apidoc/Titanium/Geolocation/MobileWeb/MobileWeb.yml b/apidoc/Titanium/Geolocation/MobileWeb/MobileWeb.yml
deleted file mode 100644
index 172ce7583b6..00000000000
--- a/apidoc/Titanium/Geolocation/MobileWeb/MobileWeb.yml
+++ /dev/null
@@ -1,25 +0,0 @@
----
-name: Titanium.Geolocation.MobileWeb
-summary: The Mobile Web specific geolocation capabilities.
-extends: Titanium.Module
-since: "2.0.0"
-platforms: [mobileweb]
-properties:
- - name: locationTimeout
- summary: The time within which location requests must succeed, in milliseconds.
- default: Infinity
- type: Number
- - name: maximumLocationAge
- summary: The maximum age of cached locations acceptible for location requests, in milliseconds.
- default: 0
- type: Number
- - name: maximumHeadingAge
- summary: The maximum age of cached locations acceptible for heading requests, in milliseconds.
- default: 1000
- type: Number
- - name: forwardGeocoderTimeout
- summary: The time within which forward geocoder requests must succeed, in milliseconds.
- type: Number
- - name: reverseGeocoderTimeout
- summary: The time within which reverse geocoder requests must succeed, in milliseconds.
- type: Number
\ No newline at end of file
diff --git a/apidoc/Titanium/Gesture/Gesture.yml b/apidoc/Titanium/Gesture/Gesture.yml
index 6b85690a229..f37f644d7a4 100644
--- a/apidoc/Titanium/Gesture/Gesture.yml
+++ b/apidoc/Titanium/Gesture/Gesture.yml
@@ -1,7 +1,7 @@
---
name: Titanium.Gesture
summary: |
- The Gesture module is responsible for high-level device gestures such as orientation changes
+ The Gesture module is responsible for high-level device gestures such as orientation changes
and shake gestures.
extends: Titanium.Module
since: "0.8"
@@ -9,19 +9,19 @@ since: "0.8"
methods:
- name: isLandscape
summary: Returns whether current window is considered landscape by the device.
- description: Value returns `true` if in landscape, and `false` otherwise.
+ description: Value returns `true` if in landscape, and `false` otherwise.
deprecated:
since: 6.1.0
- notes: Use for parity instead.
+ notes: Use for parity instead.
returns:
type: Boolean
- name: isPortrait
summary: Returns whether current window is considered portrait by the device.
- description: Value returns `true` if in portrait, and `false` otherwise.
+ description: Value returns `true` if in portrait, and `false` otherwise.
deprecated:
since: 6.1.0
- notes: Use for parity instead.
+ notes: Use for parity instead.
returns:
type: Boolean
@@ -29,44 +29,40 @@ properties:
- name: portrait
summary: Indicates whether current window is considered portrait by the device.
description: |
- Value is `true` if in portrait, and `false` otherwise.
+ Value is `true` if in portrait, and `false` otherwise.
type: Boolean
accessors: false
permission: read-only
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
- name: landscape
summary: Indicates whether current window is considered landscape by the device.
description: |
- Value is `true` if in landscape, and `false` otherwise.
+ Value is `true` if in landscape, and `false` otherwise.
type: Boolean
accessors: false
permission: read-only
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
- name: orientation
- summary: Orientation of the current window.
+ summary: Orientation of the current window.
description: |
- Value may be one of the group of orientation constants,
- ,
- ,
- ,
- ,
- ,
- ,
- or .
-
- On iOS and Windows, returns the current orientation of the *device*,
- regardless of the window orientation. To determine the current window orientation,
+ Value may be one of the group of orientation constants,
+ ,
+ ,
+ ,
+ ,
+ ,
+ ,
+ or .
+
+ On iOS and Windows, returns the current orientation of the *device*,
+ regardless of the window orientation. To determine the current window orientation,
use [Window.orientation](Titanium.UI.Window.orientation).
- On Android and Mobile Web, returns the orientation of the current window, and never reports
- the "reverse" orientations (`LANDSCAPE_RIGHT` and `UPSIDE_PORTRAIT`).
-
- For Mobile Web, the orientation reported by `Gesture.orientation` and
- [Window.orientation](Titanium.UI.Window.orientation) is always the same, and corresponds to
- the orientation of the browser window.
-
+ On Android, returns the orientation of the current window, and never reports
+ the "reverse" orientations (`LANDSCAPE_RIGHT` and `UPSIDE_PORTRAIT`).
+
To set the *allowable* orientations for a window, see .
type: Number
permission: read-only
@@ -75,17 +71,17 @@ events:
- name: orientationchange
summary: Fired when the device orientation changes.
description: |
- On Android, note that the application must have a heavyweight window or tab group open
+ On Android, note that the application must have a heavyweight window or tab group open
in order to receive the `orientationchange` event. It is not necessary for the heavyweight
window to be the topmost window.
-
- Almost all real-world applications will have a heavyweight window or a tab group. This is
- only likely to be an issue if you create a test case or test application that adds an
- orientation change listener from `app.js` without opening a heavyweight window.
-
- Android and Mobile Web do not report the "reverse" orientations,
- `UPSIDE_PORTRAIT` and `LANDSCAPE_RIGHT`. These are reported as
- `PORTRAIT` and `LANDSCAPE_LEFT`, respectively.
+
+ Almost all real-world applications will have a heavyweight window or a tab group. This is
+ only likely to be an issue if you create a test case or test application that adds an
+ orientation change listener from `app.js` without opening a heavyweight window.
+
+ Android does not report the "reverse" orientations,
+ `UPSIDE_PORTRAIT` and `LANDSCAPE_RIGHT`. These are reported as
+ `PORTRAIT` and `LANDSCAPE_LEFT`, respectively.
properties:
- name: orientation
summary: Orientation of the current window.
@@ -97,27 +93,22 @@ events:
summary: Fired when the device is shaken.
description: |
A shake gesture consists of a series of quick accelerations, and is represented by a series
- of shake events.
-
- The `timestamp` property represents the interval between shake events. It is measured in
- milliseconds on Android and Mobile Web, and in seconds on iOS.
-
- Note that Mobile Web detect shake gestures using the device accelerometer, if the device
- and browser support this. This event cannot be generated on Mobile Web in the iOS simulator.
- The simulator's **Shake Gesture** menu item generates a native shake event, but does not
- generate accelerometer events to the browser.
+ of shake events.
+
+ The `timestamp` property represents the interval between shake events. It is measured in
+ milliseconds on Android, and in seconds on iOS.
properties:
- name: timestamp
summary: |
- Time interval since previous shake event. On iOS, this value is 0 for the first shake
+ Time interval since previous shake event. On iOS, this value is 0 for the first shake
event in a series.
type: Number
- name: x
summary: Acceleration along the X axis, in Gs.
type: Number
-
+
- name: y
summary: Acceleration along the Y axis, in Gs.
type: Number
diff --git a/apidoc/Titanium/IOStream.yml b/apidoc/Titanium/IOStream.yml
index d0c835f1964..c61106089d7 100644
--- a/apidoc/Titanium/IOStream.yml
+++ b/apidoc/Titanium/IOStream.yml
@@ -7,14 +7,14 @@ description: |
since: "1.7"
extends: Titanium.Proxy
createable: false
-platforms: [android, iphone, ipad, mobileweb]
+platforms: [android, iphone, ipad]
methods:
- name: read
summary: Reads data from this stream into a buffer.
description: |
- If `offset` and `length` are specified, data is written into the buffer starting at
+ If `offset` and `length` are specified, data is written into the buffer starting at
position `offset`. Data is read from this stream until one of the following occurs:
* the end of this stream is reached
@@ -23,16 +23,16 @@ methods:
If `offset` and `length` are omitted, data is written starting at the beginning
of the buffer.
-
+
Returns the number of bytes read, or -1 if the end of stream was reached before
any data was read.
Throws an exception on error. For example, if the `offset` value is past
- the last byte of `buffer`.
+ the last byte of `buffer`.
This method is synchronous. To perform an asynchronous read on an `IOStream`, use
.
-
+
returns:
type: Number
summary: Number of bytes read.
@@ -69,9 +69,9 @@ methods:
If `offset` and `length` are omitted, all of the data in the buffer is written to
this stream.
-
+
Returns the number of bytes actually written.
-
+
Throws an exception if an error is encountered.
returns:
type: Number
@@ -123,35 +123,35 @@ examples:
var outBuffer = Ti.createBuffer({data: "write me"});
// stream object could be socket, file, buffer or blob
var outStream = Ti.Stream.createStream({mode: Ti.Stream.MODE_WRITE});
-
+
var bytesWritten = outStream.write(outBuffer); // writes entire buffer to stream
Ti.API.info("Bytes written:" + bytesWritten); // should be 8
-
+
bytesWritten = outStream.write(outBuffer, 2, 5); // only writes "ite m" to stream
Ti.API.info("Bytes written:" + bytesWritten); // should be 5
- - title: Read Data From a Stream
+ - title: Read Data From a Stream
example: |
This shows a simple example of reading data from a stream, one buffer full at a
- time.
-
+ time.
+
var size = 0;
// read data one buffer full at a time
while ((size = instream.read(buffer)) > -1) {
// do something with the data here ...
Ti.API.info("Read " + size + " bytes.");
}
-
+
- title: Read Data With Offset and Length
example: |
This example shows how to read data from a stream into a buffer. We assume that
- the `inStream` variable holds a previously initialized stream that contains the
+ the `inStream` variable holds a previously initialized stream that contains the
string, "World Titanium".
var inBuffer = Ti.createBuffer({ value: "Hello [ ]" });
// Read the first 6 bytes from the stream to the buffer, starting at position 10.
- var bytesRead = inStream.read(inBuffer, 10, 6);
+ var bytesRead = inStream.read(inBuffer, 10, 6);
Ti.API.info("Bytes read: " + bytesRead);
Ti.API.info(inBuffer.toString());
@@ -169,4 +169,3 @@ examples:
[INFO] Hello [ World ]
[INFO] Bytes read: 8
[INFO] Hello [ Titanium ]
-
diff --git a/apidoc/Titanium/Locale/Locale.yml b/apidoc/Titanium/Locale/Locale.yml
index 0a720655209..82624935816 100644
--- a/apidoc/Titanium/Locale/Locale.yml
+++ b/apidoc/Titanium/Locale/Locale.yml
@@ -167,7 +167,7 @@ properties:
This property holds a value such as `US` or `GB`. See the
[ISO 3166-1 alpha-2](http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements)
country codes section of wikipedia for reference.
- platforms: [android, iphone, ipad, mobileweb]
+ platforms: [android, iphone, ipad]
type: String
permission: read-only
diff --git a/apidoc/Titanium/Map/Annotation.yml b/apidoc/Titanium/Map/Annotation.yml
index 6375bbe8764..4ae94110e4e 100644
--- a/apidoc/Titanium/Map/Annotation.yml
+++ b/apidoc/Titanium/Map/Annotation.yml
@@ -219,7 +219,7 @@ events:
`title`, or `subtitle`. If the user deselects the annotation by clicking elsewhere
in the map view, `clicksource` is `null`.
- platforms: [iphone, ipad, mobileweb]
+ platforms: [iphone, ipad]
properties:
diff --git a/apidoc/Titanium/Map/Map.yml b/apidoc/Titanium/Map/Map.yml
index 9ee11cefde5..c5e69306105 100644
--- a/apidoc/Titanium/Map/Map.yml
+++ b/apidoc/Titanium/Map/Map.yml
@@ -127,7 +127,7 @@ properties:
summary: Used with [mapType](Titanium.Map.View.mapType) to display the terrain that shows the position of all roads and some road names.
type: Number
permission: read-only
- platforms: [mobileweb]
+ platforms: []
examples:
- title: Map Example
diff --git a/apidoc/Titanium/Map/View.yml b/apidoc/Titanium/Map/View.yml
index 58b992f9f40..3a9f16fe5d3 100644
--- a/apidoc/Titanium/Map/View.yml
+++ b/apidoc/Titanium/Map/View.yml
@@ -1,22 +1,22 @@
---
name: Titanium.Map.View
-summary: Map view is used for embedding native mapping capabilities as a view in your application.
+summary: Map view is used for embedding native mapping capabilities as a view in your application.
description: |
- With native maps, you can control the mapping location, the type of map, the zoom level
+ With native maps, you can control the mapping location, the type of map, the zoom level
and you can add custom annotations directly to the map. Once the map view is
displayed, the user can pan and zoom the map using the native control gestures.
-
+
Use the method to create a map view.
-
+
All latitude and longitude values are specified in decimal degrees. Values in degrees,
minutes and seconds (DMS) must be converted to decimal degrees before being passed to
the map view.
-
+
You can add [Annotation](Titanium.Map.Annotation) objects to the map to mark points of
- interest. An annotation has two states: selected and deselected. A deselected annotation
+ interest. An annotation has two states: selected and deselected. A deselected annotation
is marked by a pin image. When selected, the full annotation is displayed, typically
including a title, an optional subtitle, and one or more images.
-
+
#### Android Platform Notes
On Android, this module requires a Google Maps API v1 key. As of March 3, 2013,
@@ -29,37 +29,20 @@ description: |
If you have a Maps API v1 key, edit your `tiapp.xml` file and add your new key as the
value for the `ti.android.google.map.api.key.production` property.
-
+
A development API key is included in the default `tiapp.xml` file. You can use this
- key for development and testing as long as you are building your application with the
+ key for development and testing as long as you are building your application with the
default Titanium development keystore.
-
+
#### iOS Platform Notes
Since Release 3.2.0, use the [ti.map add-on module](Modules.Map). Support for this module was
removed.
-
+
On iOS, you cannot call any methods on a map view until it has been added to a view.
-
+
In addition to annotations, iOS supports adding routes to a map view, using
[addRoute](Titanium.Map.View.addRoute).
-
- #### Mobile Web Platform Notes
-
- For Mobile Web, the default map provider is Google. Google Maps does not require you to obtain an API key,
- however it is encouraged that you use an API key so that you can monitor your Maps API usage. You can sign
- up for the Maps API key on the Google Code web site:
-
- * developers.google.com/maps/signup
-
- If you get a Maps API key, edit your `tiapp.xml` file and add your new key as the
- value for the `