AIR application descriptor elementsThe following dictionary of elements describes each of the legal elements of an AIR application descriptor file. allowBrowserInvocationEnables the AIR in-browser API to detect and launch the application. If you set this value to true, be sure to consider security implications. These are described in Invoking an AIR application from the browser (for ActionScript developers) and Invoking an AIR application from the browser (for HTML developers). For more information, see Installing and running desktop AIR applications from a web page. Parent elements:application Child elements: none Contenttrue or false (default) Example<allowBrowserInvocation>true</allowBrowserInvocation> androidAllows you to add elements to the Android manifest file. AIR creates the AndroidManifest.xml file for every APK package. You can use the android element in the AIR application descriptor to add additional items to it. Ignored on all platforms except Android. Parent elements:application Child elements: manifestAdditions ContentElements defining the Android-specific properties to add to the Android application manifest. Example<android>
<manifestAdditions>
...
</manifestAdditions>
</android>
applicationThe root element of an AIR application descriptor document. Parent elements: none Child elements: AttributesminimumPatchLevel — The AIR runtime minimum patch level required by this application. xmlns — the XML namespace attribute determines the required AIR runtime version of the application. The namespace changes with each major release of AIR (but not with minor patches). The last segment of the namespace, such as “2.5,” indicates the runtime version required by the application. The xmlns values for the major AIR releases are: xmlns="http://ns.adobe.com/air/application/1.0" xmlns="http://ns.adobe.com/air/application/1.1" xmlns="http://ns.adobe.com/air/application/1.5" xmlns="http://ns.adobe.com/air/application/1.5.2" xmlns="http://ns.adobe.com/air/application/1.5.3" xmlns="http://ns.adobe.com/air/application/2.0" xmlns="http://ns.adobe.com/air/application/2.5" For SWF-based applications, the AIR runtime version specified in the application descriptor determines the maximum SWF version that can be loaded as the initial content of the application. Applications that specify AIR 1.0 or AIR 1.1 can only use SWF9 (Flash Player 9) files as initial content — even when run using the AIR 2 runtime. Applications that specify AIR 1.5 (or later) can use either SWF9 or SWF10 (Flash Player 10) files as initial content. The SWF version determines which version of the AIR and Flash Player APIs are available. If a SWF9 file is used as the initial content of an AIR 1.5 application, that application will only have access to the AIR 1.1 and Flash Player 9 APIs. Furthermore, behavior changes made to existing APIs in AIR 2.0 or Flash Player 10.1 will not be effective. (Important security-related changes to APIs are an exception to this principle and can be applied retroactively in present or future patches of the runtime.) For HTML-based applications, the runtime version specified in the application descriptor determines which version of the AIR and Flash Player APIs are available to the application. The HTML, CSS, and JavaScript behaviors are always determined by the version of Webkit used in the installed AIR runtime, not by the application descriptor. When an AIR application loads SWF content, the version of the AIR and Flash Player APIs available to that content depends on how the content is loaded. Sometimes the effective version is determined by the application descriptor namespace, sometimes it is determined by the version of the loading content, and sometimes it is determined by the version of the loaded content. The following table shows how the API version is determined based on the loading method:
When loading a SWF file of a different version than the loading content, you can run into the two problems:
ContentThe application element contains child elements that define the properties of an AIR application. Example<?xml version="1.0" encoding="utf-8" ?>
<application xmlns="http://ns.adobe.com/air/application/2.5">
<id>HelloWorld</id>
<version>2.0</version>
<filename>Hello World</filename>
<name>Example Co. AIR Hello World</name>
<description>
<text xml:lang="en">This is an example.</text>
<text xml:lang="fr">C'est un exemple.</text>
<text xml:lang="es">Esto es un ejemplo.</text>
</description>
<copyright>Copyright (c) 2010 Example Co.</copyright>
<initialWindow>
<title>Hello World</title>
<content>
HelloWorld.swf
</content>
<systemChrome>none</systemChrome>
<transparent>true</transparent>
<visible>true</visible>
<minSize>320 240</minSize>
</initialWindow>
<installFolder>Example Co/Hello World</installFolder>
<programMenuFolder>Example Co</programMenuFolder>
<icon>
<image16x16>icons/smallIcon.png</image16x16>
<image32x32>icons/mediumIcon.png</image32x32>
<image48x48>icons/bigIcon.png</image48x48>
<image128x128>icons/biggestIcon.png</image128x128>
</icon>
<customUpdateUI>true</customUpdateUI>
<allowBrowserInvocation>false</allowBrowserInvocation>
<fileTypes>
<fileType>
<name>adobe.VideoFile</name>
<extension>avf</extension>
<description>Adobe Video File</description>
<contentType>application/vnd.adobe.video-file</contentType>
<icon>
<image16x16>icons/avfIcon_16.png</image16x16>
<image32x32>icons/avfIcon_32.png</image32x32>
<image48x48>icons/avfIcon_48.png</image48x48>
<image128x128>icons/avfIcon_128.png</image128x128>
</icon>
</fileType>
</fileTypes>
</application>
aspectRatioSpecifies the initial aspect ratio of the application Parent elements:initialWindow Child elements: none Contentportrait or landscape Example<aspectRatio>landscape</aspectRatio> autoOrientsSpecifies whether the orientation of content in the application automatically reorients as the device itself changes physical orientation. For more information, see Setting and detecting screen orientation. When using auto-orientation, for best results set the align property of the Stage to the following: stage.align = StageAlign.TOP_LEFT; stage.scaleMode = StageScaleMode.NO_SCALE; Parent elements:initialWindow Child elements: none Contenttrue (default) or false Example<autoOrients>true</autoOrients> contentThe value specified for the content element is the URL for the main content file of the application. This may be either a SWF file or an HTML file. The URL is specified relative to the root of the application installation folder. (When running an AIR application with ADL, the URL is relative to the folder containing the application descriptor file. You can use the root-dir parameter of ADL to specify a different root directory.) Parent elements:initialWindow Child elements: none ContentA URL relative to the application directory. Because the value of the content element is treated as a URL, characters in the name of the content file must be URL encoded according to the rules defined in RFC 1738. Space characters, for example, must be encoded as %20. Example<content>TravelPlanner.swf</content> contentTypecontentType is required as of AIR 1.5 (it was optional in AIR 1.0 and 1.1). The property helps some operating systems to locate the best application to open a file. The value should be the MIME type of the file content. Note that the value is ignored on Linux if the file type is already registered and has an assigned MIME type. Parent elements:fileType Child elements: none ContentThe MIME type and subtype. See RFC2045 for more information about MIME types. Example<contentType>text/plain</contentType> copyrightThe copyright information for the AIR application. On Mac OS, the copyright text appears in the About dialog box for the installed application. On Mac OS, the copyright information is also used in the NSHumanReadableCopyright field in the Info.plist file for the application. Parent elements:application Child elements: none ContentA string containing the application copyright information. Example<copyright>© 2010, Examples, Inc.All rights reserved.</copyright> customUpdateUIIndicates whether an application will provide its own update dialogs. If false, AIR presents standard update dialogs to the user. Only applications distributed as AIR files can use the built-in AIR update system. When the installed version of your application has the customUpdateUI element set to true and the user then double-clicks the AIR file for a new version or installs an update of the application using the seamless install feature, the runtime opens the installed version of the application. The runtime does not open the default AIR application installer. Your application logic can then determine how to proceed with the update operation. (The application ID and publisher ID in the AIR file must match the values in the installed application for an upgrade to proceed.) Note: The customUpdateUI mechanism
only comes into play when the application is already installed and
the user double-clicks the AIR installation file containing an update
or installs an update of the application using the seamless install
feature. You can download and start an update through your own application logic,
displaying your custom UI as necessary, whether or not customUpdateUI is true.
For more information, see Updating AIR applications. Parent elements:application Child elements: none Contenttrue or false (default) Example<customUpdateUI>true</customUpdateUI> descriptionThe description of the application, displayed in the AIR application installer. If you specify a single text node (not multiple text elements), the AIR application installer uses this description, regardless of the system language. Otherwise, the AIR application installer uses the description that most closely matches the user interface language of the user’s operating system. For example, consider an installation in which the description element of the application descriptor file includes a value the en (English) locale. The AIR application installer uses the en description if the user’s system identifies en (English) as the user interface language. It also uses the en description if the system user interface language is en-US (U.S. English). However, if system user interface language is en-US and the application descriptor file defines both en-US and en-GB names, then the AIR application installer uses the en-US value. If the application defines no description that matches the system user interface language, the AIR application installer uses the first description value defined in the application descriptor file. For more information on developing multi-language applications, see Localizing AIR applications. Parent elements:application Child elements:text ContentThe AIR 1.0 application descriptor schema allows only one simple text node to be defined for the name (not multiple text elements). In AIR 1.1 (or above), you can specify multiple languages in the description element. The xml:lang attribute for each text element specifies a language code, as defined in RFC4646 (http://www.ietf.org/rfc/rfc4646.txt). ExampleDescription with simple text node: <description>This is a sample AIR application.</description> Description with localized text elements for English, French, and Spanish (valid in AIR 1.1 and later): <description>
<text xml:lang="en">This is an example.</text>
<text xml:lang="fr">C'est un exemple.</text>
<text xml:lang="es">Esto es un ejemplo.</text>
</description>
descriptionThe file type description is displayed to the user by the operating system. The file type description is not localizable. See also: description as child of the application element Parent elements:fileType Child elements: none ContentA string describing the file contents. Example<description>PNG image</description> extensionThe extension string of a file type. Parent elements:fileType Child elements: none ContentA string identifying the file extension characters (without the dot, “.”). Example<extension>png</extension> extensionIDSpecifies the ID of an extension used by the application. The ID is defined in the extension descriptor document. Parent elements:extensions Child elements: none ContentA string identifying the extension ID. Example<extensionID>com.example.extendedFeature</extensionID> extensionsIdentifies the extensions used by an application. Parent elements:application Child elements:extensionID ContentChild extensionID elements containing the extension IDs from the extension descriptor file. Example<extensions>
<extensionID>extension.first</extensionID>
<extensionID>extension.next</extensionID>
<extensionID>extension.last</extensionID>
</extensions>
filenameThe string to use as a filename of the application (without extension) when the application is installed. The application file launches the AIR application in the runtime. If no name value is provided, the filename is also used as the name of the installation folder. Parent elements:application Child elements: none ContentThe filename property can contain any Unicode (UTF-8) character except the following, which are prohibited from use as filenames on various file systems:
The filename value cannot end in a period. Example<filename>MyApplication</filename> fileTypeDescribes a single file type that the application can register for. Parent elements:fileTypes Child elements: ContentElements describing a file type. Example<fileType>
<name>foo.example</name>
<extension>foo</extension>
<description>Example file type</description>
<contentType>text/plain</contentType>
<icon>
<image16x16>icons/fooIcon16.png</image16x16>
<image48x48>icons/fooIcon48.png</imge48x48>
<icon>
</fileType>
fileTypesThe fileTypes element allows you to declare the file types with which an AIR application can be associated. When an AIR application is installed, any declared file type is registered with the operating system. If these file types are not already associated with another application, they are associated with the AIR application. To override an existing association between a file type and another application, use the NativeApplication.setAsDefaultApplication() method at run time (preferably with the user’s permission). Note: The runtime methods can only manage associations
for the file types declared in the application descriptor.
The fileTypes element is optional. Parent elements:application Child elements:fileType ContentThe fileTypes element may contain any number of fileType elements. Example<fileTypes>
<fileType>
<name>adobe.VideoFile</name>
<extension>avf</extension>
<description>Adobe Video File</description>
<contentType>application/vnd.adobe.video-file</contentType>
<icon>
<image16x16>icons/AIRApp_16.png</image16x16>
<image32x32>icons/AIRApp_32.png</image32x32>
<image48x48>icons/AIRApp_48.png</image48x48>
<image128x128>icons/AIRApp_128.png</image128x128>
</icon>
</fileType>
</fileTypes>
fullScreenSpecifies whether the application starts up in fullscreen mode. Parent elements:initialWindow Child elements: none Contenttrue or false (default) Example<fullscreen>true</fullscreen> heightThe initial height of the main window of the application. If you do not set a height, it is determined by the settings in the root SWF file or, in the case of an HTML-based AIR application, by the operating system. The maximum height of a window changed from 2048 pixels to 4096 pixels in AIR 2. Parent elements:initialWindow Child elements: none ContentA positive integer with a maximum value of 4095. Example<height>4095</height> iconThe icon property specifies one or more icon files to be used for the application. Including an icon is optional. If you do not specify an icon property, the operating system displays a default icon. The path specified is relative to the application root directory. Icon files must be in the PNG format. You can specify all of the following icon sizes: If an element for a given size is present, the image in the file must be exactly the size specified. If all sizes are not provided, the closest size is scaled to fit for a given use of the icon by the operating system. Note: The icons specified are not automatically added
to the AIR package. The icon files must be included in their correct
relative locations when the application is packaged.
For best results, provide an image for each of the available sizes. In addition, make sure that the icons look presentable in both 16- and 32-bit color modes. Parent elements:application Child elements:imageNxN ContentAn imageNxN element for each desired icon size. Example<icon>
<image16x16>icons/smallIcon.png</image16x16>
<image32x32>icons/mediumIcon.png</image32x32>
<image48x48>icons/bigIcon.png</image48x48>
<image128x128>icons/biggestIcon.png</image128x128>
</icon>
idAn identifier string for the application, known as the application ID. A reverse DNS-style identifier is often used, but this style is not required. Parent elements:application Child elements: none ContentThe ID value is restricted to the following characters:
The value must contain 1 to 212 characters. This element is required. Example<id>org.example.application</id> imageNxNDefines the path to an icon relative to the application directory. The following icon images can be used, each specifying a different icon size:
The icon must be a PNG graphic that is exactly the size indicated by the image element. Icon files must be included in the application package; icons referenced in the application descriptor document are not included automatically. Parent elements:application Child elements: none ContentThe file path to the icon can contain any Unicode (UTF-8) character except the following, which are prohibited from use as filenames on various file systems:
Example<image32x32>icons/icon32.png</image32x32> InfoAdditionsAllows you to specify additional properties of an iPhone application. Parent elements:iPhone Child elements: iPhone Info.plist elements ContentContains child elements specifying key-value pairs to use as Info.plist settings for the application. Content of the InfoAdditions element should be enclosed in a CDATA block. See Information Property List Key Reference in the Apple iPhone Reference Library for information about the key value pairs and how to express them in XML. Example<InfoAdditions>
<![CDATA[
<key>UIStatusBarStyle</key>
<string>UIStatusBarStyleBlackOpaque</string>
<key>UIRequiresPersistentWiFi</key>
<string>NO</string>
]]>
</InfoAdditions>
initialWindowDefines the main content file and initial application appearance. Parent elements:application Child elements: All of the following elements can appear
as children of the initialWindow element. However, some elements
are ignored depending on whether AIR supports windows on a platform:
ContentChild elements defining the application appearance and behavior. Example<initialWindow>
<title>Hello World</title>
<content>
HelloWorld.swf
</content>
<systemChrome>none</systemChrome>
<transparent>true</transparent>
<visible>true</visible>
<maxSize>1024 800</maxSize>
<minSize>320 240</minSize>
<maximizable>false</maximizable>
<minimizable>false</minimizable>
<resizable>true</resizable>
<x>20</x>
<y>20</y>
<height>600</height>
<width>800</width>
<aspectRatio>landscape</aspectRatio>
<autoOrients>true</autoOrients>
<fullScreen>false</fullScreen>
<renderMode>auto</renderMode>
</initialWindow>
installFolderIdentifies the subdirectory of the default installation directory. On Windows, the default installation subdirectory is the Program Files directory. On Mac OS, it is the /Applications directory. On Linux, it is /opt/. For example, if the installFolder property is set to "Acme" and an application is named "ExampleApp", then the application is installed in C:\Program Files\Acme\ExampleApp on Windows, in /Applications/Acme/Example.app on MacOS, and /opt/Acme/ExampleApp on Linux. The installFolder property is optional. If you specify no installFolder property, the application is installed in a subdirectory of the default installation directory, based on the name property. Parent elements:application Child elements: None ContentThe installFolder property can contain any Unicode (UTF-8) character except those that are prohibited from use as folder names on various file systems (see the filename property for the list of exceptions). Use the forward-slash (/) character as the directory separator character if you want to specify a nested subdirectory. Example<installFolder>utilities/toolA</installFolder> iPhoneDefines iPhone-specific application properties. Parent elements:application Child elements: For information about iPhone application descriptor settings see Building Adobe AIR Applications with the Packager for iPhone. manifestSpecifies information to add to the Android manifest file for the application. Parent element:manifestAdditions Child elements: Defined by the Android SDK. ContentThe manifest element is not, technically speaking, a part of the AIR application descriptor schema. It is the root of the Android manifest XML document. Any content that you put within the manifest element must conform to the AndroidManifest.xml schema. When you generate an APK file with the AIR tools, information in the manifest element is copied into the corresponding part of the generated AndroidManifest.xml of the application. The manifest element itself must be enclosed in a CDATA block within the AIR application descriptor. Example<![CDATA[
<manifest android:sharedUserID="1001">
<uses-permission android:name="android.permission.CAMERA"/>
<uses-feature android:required="false" android:name="android.hardware.camera"/>
<application android:allowClearUserData="true"
android:enabled="true"
android:persistent="true"/>
</manifest>
]]>
manifestAdditionsSpecifies information to add to the Android manifest file. Every Android application includes a manifest file that defines basic application properties. The Android manifest is similar in concept to the AIR application descriptor. An AIR for Android application has both an application descriptor and an automatically generated Android manifest file. When an AIR for Android app is packaged, the information in this manifestAdditions element is added to the corresponding parts of the Android manifest document. Parent element:android Child elements:manifest ContentInformation in the manifestAdditions element is added to the AndroidManifest XML document. AIR sets several manifest entries in the generated Android manifest document to ensure that application and runtime features work correctly. You cannot override the following settings: You cannot set the following attributes of the manifest element:
You cannot set the following attributes for the main activity element:
You cannot set the following attributes of the application element:
Example<manifestAdditions>
<![CDATA[
<manifest android:installLocation="preferExternal">
<uses-permission android:name="android.permission.INTERNET"/>
<application android:allowClearUserData="true"
android:enabled="true"
android:persistent="true"/>
</manifest>
]]>
</manifestAdditions>
maximizableSpecifies whether the window can be maximized. Note: On operating systems, such as Mac OS X, for
which maximizing windows is a resizing operation, both maximizable
and resizable must be set to false to prevent the
window from being zoomed or resized.
Parent element:initialWindow Child elements: none Contenttrue (default) or false Example<maximizable>false</maximizable> maxSizeThe maximum sizes of the window. If you do not set a maximum size, it is determined by the operating system. Parent elements:initialWindow Child elements: none ContentTwo integers representing the maximum width and height, separated by whitespace. Note: The
maximum window size supported by AIR increased from 2048x2048 pixels to
4096x4096 pixels in AIR 2. (Because the screen coordinates are zero-based,
the maximum value you can use for width or height is 4095.)
Example<maxSize>1024 360</maxSize> minimizableSpecifies whether the window can be minimized. Parent elements:initialWindow Child elements: None Contenttrue (default) or false Example<minimizable>false</minimizable> minSizeSpecifies the minimum size allowed for the window. Parent elements:initialWindow Child elements: none ContentTwo integers representing the minimum width and height, separated by whitespace. Note that the minimum size imposed by the operating system takes precedence over the value set in the application descriptor. Example<minSize>120 60</minSize> nameThe application title displayed by the AIR application installer. If no name element is specified, the AIR application installer displays the filename as the application name. Parent elements:application Child elements:text ContentIf you specify a single text node (instead of multiple <text> elements), the AIR application installer uses this name, regardless of the system language. The AIR 1.0 application descriptor schema allows only one simple text node to be defined for the name (not multiple text elements). In AIR 1.1 (or above), you can specify multiple languages in the name element. The xml:lang attribute for each text element specifies a language code, as defined in RFC4646 (http://www.ietf.org/rfc/rfc4646.txt). The AIR application installer uses the name that most closely matches the user interface language of the user’s operating system. For example, consider an installation in which the name element of the application descriptor file includes a value for the en (English) locale. The AIR application installer uses the en name if the operating system identifies en (English) as the user interface language. It also uses the en name if the system user interface language is en-US (U.S. English). However, if the user interface language is en-US and the application descriptor file defines both en-US and en-GB names, then the AIR application installer uses the en-US value. If the application defines no name that matches the system user interface languages, the AIR application installer uses the first name value defined in the application descriptor file. The name element only defines the application title used in the AIR application installer. The AIR application installer supports multiple languages: Traditional Chinese, Simplified Chinese, Czech, Dutch, English, French, German, Italian, Japanese, Korean, Polish, Brazilian Portuguese, Russian, Spanish, Swedish, and Turkish. The AIR application installer selects its displayed language (for text other than the application title and description) based on the system user interface language. This language selection is independent of the settings in the application descriptor file. The name element does not define the locales available for the running, installed application. For details on developing multi-language applications, see Localizing AIR applications. ExampleThe following example defines a name with a simple text node: <name>Test Application</name> The following example, valid in AIR 1.1 and later, specifies the name in three languages (English, French, and Spanish) using <text> element nodes: <name>
<text xml:lang="en">Hello AIR</text>
<text xml:lang="fr">Bonjour AIR</text>
<text xml:lang="es">Hola AIR</text>
</name>
nameIdentifies the name of a file type. Parent elements:fileType Child elements: none ContentA string representing the name of the file type. Example<name>adobe.VideoFile</name> programMenuFolderIdentifies the location in which to place shortcuts to the application in the All Programs menu of the Windows operating system or in the Applications menu on Linux. (This setting is currently ignored on other operating systems.) Parent elements:application Child elements: none ContentThe string used for the programMenuFolder value can contain any Unicode (UTF-8) character except those that are prohibited from use as folder names on various file systems (see the filename element for the list of exceptions). Do not use a forward slash (/) character as the last character of this value. Example<programMenuFolder>Example Company/Sample Application</programMenuFolder> publisherIDIdentifies the publisher ID for updating an AIR application originally created with AIR version 1.5.2 or earlier. Only specify a publisher ID when creating an application update. The value of the publisherID element must match the publisher ID generated by AIR for the earlier version of the application. For an installed application, the publisher ID can be found in the folder in which an application is installed, in the META-INF/AIR/publisherid file. New applications created with AIR 1.5.3 or later should not specify a publisher ID. For more information, see About AIR publisher identifiers. Parent elements:application Child elements: none ContentA publisher ID string. Example<publisherID>B146A943FBD637B68C334022D304CEA226D129B4.1</publisherID> renderModeSpecifies whether to use graphics processing unit (GPU) acceleration, if supported on the current computing device. Parent elements:initialWindow Child elements: none ContentOne of the following values:
Example<renderMode>gpu</renderMode> resizableSpecifies whether the window can be resized. Note: On operating systems, such as Mac OS X, for
which maximizing windows is a resizing operation, both maximizable
and resizable must be set to false to prevent the
window from being zoomed or resized.
Parent elements:initialWindow Child elements: Contenttrue (default) or false Example<resizable>false</resizable> supportedProfilesIdentifies the profiles that are supported for the application. Parent elements:application Child elements: none ContentYou can include any of these values in the supportedProfiles element:
The supportedProfiles property is optional. When you do not include this element in the application descriptor file, the application can be compiled and deployed for any profile. To specify multiple profiles, separate each with a space character. For example, the following setting specifies that the application is only available in the desktop and extended profiles: <supportedProfiles>desktop extendedDesktop</supportedProfiles> Note: When
you run an application with ADL and do not specify a value for the
ADL -profile option, then the first profile in
the application descriptor is used. (If no profiles are specified
in the application descriptor either, then the desktop profile is used.)
Example<supportedProfiles>desktop mobileDevice</supportedProfiles> systemChromeSpecifies whether the initial application window is created with the standard title bar, borders, and controls provided by the operating system. The system chrome setting of the window cannot be changed at run time. Parent elements:initialWindow Child elements: none ContentOne of the following values:
Example<systemChrome>standard</systemChrome> textSpecifies a localized string. The xml:lang attribute of a text element specifies a language code, as defined in RFC4646 (http://www.ietf.org/rfc/rfc4646.txt). The AIR application installer uses the text element with the xml:lang attribute value that most closely matches the user interface language of the user’s operating system. For example, consider an installation in which a text element includes a value for the en (English) locale. The AIR application installer uses the en name if the operating system identifies en (English) as the user interface language. It also uses the en name if the system user interface language is en-US (U.S. English). However, if the user interface language is en-US and the application descriptor file defines both en-US and en-GB names, then the AIR application installer uses the en-US value. If the application defines no text element that matches the system user interface languages, the AIR application installer uses the first name value defined in the application descriptor file. Parent elements:
Child elements: none ContentAn xml:lang attribute specifying a locale and a string of localized text. Example<text xml:lang="fr">Bonjour AIR</text> titleSpecifies the title displayed in the title bar of the initial application window. A title is only displayed if the systemChrome element is set to standard. Parent elements:initialWindow Child elements: none ContentA string containing the window title. Example<title>Example Window Title</title> transparentSpecifies whether the initial application window is alpha-blended with the desktop. A window with transparency enabled may draw more slowly and require more memory. The transparent setting cannot be changed at run time. Important: You can only set transparent to true when systemChrome is none.
Parent elements:initialWindow Child elements: none Contenttrue or false (default) Example<transparent>true</transparent> versionSpecifies the version information for the application. The version string is an application-defined designator. AIR does not interpret the version string in any way. Thus, version “3.0” is not assumed to be more current than version “2.0.” Examples: "1.0", ".4", "0.5", "4.9", "1.3.4a". In AIR 2.5 and later, the version element is superseded by the versionNumber and versionLabel elements. Parent elements:application Child elements: none ContentA string containing the application version. Example<version>0.1 Alpha</version> versionLabelSpecifies a human-readable version string. The value of the version label is displayed in installation dialogs instead of the value of the versionNumber element. If versionLabel is not used, then the versionNumber is used for both. Parent elements:application Child elements: none ContentA string containing the publicly displayed version text. Example<versionLabel>0.9 Beta</versionlabel> versionNumberThe application version number. Parent elements:application Child elements: none ContentThe version number can contain a sequence of up to three integers separated by periods. Each integer must be a number between 0 and 999 (inclusive). Examples<versionNumber>1.0.657</versionNumber> <versionNumber>10</versionNumber> <versionNumber>0.01</versionNumber> visibleSpecifies whether the initial application window is visible as soon as it is created. AIR windows, including the initial window, are created in an invisible state by default. You can display a window by calling the activate() method of the NativeWindow object or by setting the visible property to true. You may want to leave the main window hidden initially, so that changes to the window’s position, the window’s size, and the layout of its contents are not shown. The Flex mx:WindowedApplication component automatically displays and activates the window immediately before the applicationComplete event is dispatched, unless the visible attribute is set to false in the MXML definition. On devices in the mobile and tv profiles, which do not support windows, the visible setting is ignored. Parent elements:initialWindow Child elements: none Contenttrue or false (default) Example<visible>true</visible> widthThe initial width of the main window of the application. If you do not set a width, it is determined by the settings in the root SWF file or, in the case of an HTML-based AIR application, by the operating system. The maximum width of a window changed from 2048 pixels to 4096 pixels in AIR 2. Parent elements:initialWindow Child elements: none ContentA positive integer with a maximum value of 4095. Example<width>1024</width> xThe horizontal position of the initial application window. In most cases, it is better to let the operating system determine the initial position of the window rather than assigning a fixed value. The origin of the screen coordinate system (0,0) is the top, left-hand corner of the main desktop screen (as determined by the operating system). Parent elements:initialWindow Child elements: none ContentAn integer value. Example<x>120</x> yThe vertical position of the initial application window. In most cases, it is better to let the operating system determine the initial position of the window rather than assigning a fixed value. The origin of the screen coordinate system (0,0) is the top, left-hand corner of the main desktop screen (as determined by the operating system). Parent elements:initialWindow Child elements: none ContentAn integer value. Example<y>250</y> |
|