Mars Package Inspector & Air Beta 2
Hi,
We are getting reports that the Mars Package Inspector is not
compatible with the latest version of AIR (Beta 2). However, I have
done some testing on this and it installed on my system (Windows
Vista). Is anyone else having the same problem? Hopefully we can
provide an update soon, but I would like to get an idea as to what
it currently works correctly on and where it fails.
Thanks,
Matt
Thanks for the feedback. If you install Beta 1 first then
Beta 2 (of AIR), the problems seem to be solved. We are in the
process of updating the site with a new version that is 100% Beta 2
compatible and will have that out in the next few days I
hope.
Similar Messages
-
Problem downloading Mars Package Inspector
Due to a server setup problem, the Mars Package Inspector may
download as a .zip file instead of an .air file. If this happens,
save the file to disk, rename it to have the .air suffix, and
double click to install. The problem should be corrected
shortly.Thanks for the feedback. If you install Beta 1 first then
Beta 2 (of AIR), the problems seem to be solved. We are in the
process of updating the site with a new version that is 100% Beta 2
compatible and will have that out in the next few days I
hope. -
Java.lang.NullPointerException is thrown when packaging Adobe AIR application for iOS
Hi All,
https://bugbase.adobe.com/index.cfm?event=bug&id=3071298
As per above link this bug resolve(latest build) but i am facing Java.lang.NullPointerException is thrown when packaging Adobe AIR application for iOS, using the packaging tools.
(for inappPurchase Demo app --- i used below link code)
http://code.google.com/p/in-app-purchase-air-ios/
Thanks,
Sunil RanaHi Everyone,
I'm getting basically the same error. Are there any rules or guidelines that we are suppose follow when writing an app for iOS? Is there a way to know exactly where it is crashing? My apps are not MXML, only actionscript. Also I made sure I have no errors not even warnings in my SWF file, but still no go!
Getting the same error.
Exception in thread "main" java.lang.NullPointerException
at adobe.abc.GlobalOptimizer.sccp_eval(GlobalOptimizer.java:6944)
at adobe.abc.GlobalOptimizer.sccp_analyze(GlobalOptimizer.java:5909)
at adobe.abc.GlobalOptimizer.sccp(GlobalOptimizer.java:4628)
at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:3514)
at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:2215)
at adobe.abc.LLVMEmitter.optimizeABCs(LLVMEmitter.java:526)
at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:336)
at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler
.java:472)
at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:82)
Compilation failed while executing : ADT
regards,
Keith -
hi everyone, i am using a bat file to package an air file ,
this application runs on windows 7 32 bit,
it need to call another windows application , so i google and then find i need to add -target native when package , so i added.
the bat file is like below:
========================================
@echo off
:: AIR application packaging
:: More information:
:: http://livedocs.adobe.com/flex/3/html/help.html?content=CommandLineTools_5.html#1035959
:: Path to Flex SDK binaries
set PATH=%PATH%;C:\AdobeAIRSDK\bin
:: Signature (see 'CreateCertificate.bat')
set CERTIFICATE=yeahCert.pfx
set SIGNING_OPTIONS=-storetype pkcs12 -keystore %CERTIFICATE% -tsa none
if not exist %CERTIFICATE% goto certificate
:: Output
if not exist air md air
set AIR_FILE=air/jonnson.air
:: Input
set APP_XML=application.xml
set FILE_OR_DIR=-C bin .
echo Signing AIR setup using certificate %CERTIFICATE%.
call adt -package %SIGNING_OPTIONS% -target native %AIR_FILE% %APP_XML% %FILE_OR_DIR%
if errorlevel 1 goto failed
echo.
echo AIR setup created: %AIR_FILE%
echo.
goto end
:certificate
echo Certificate not found: %CERTIFICATE%
echo.
echo Troubleshotting:
echo A certificate is required, generate one using 'CreateCertificate.bat'
echo.
goto end
:failed
echo AIR setup creation FAILED.
echo.
echo Troubleshotting:
echo did you configure the Flex SDK path in this Batch file?
echo.
:end
pause
======================================================
after run this bat , the air file is successfully built , but when i want to install this air , it says "sorry ,an error has occured ..... bla bla installer file is damaged....bla bla "
but when i remove the red part -target native in the command above then run it again , the new packaged air file can install successfully, but the application can not call other windows apllication anymore, nativeprocess.issupported always returns false when running
so seems like the problem is all about -target native , deos anyone know whats wrong ?
this problem really bothers me long time , any help will be appreciated. thanks in advance!Nice! I swear I tried that URL (substituting "mac" for "win" and "MAC" for "WIN" in the one relaxatraja posted), but I guess I missed something.
Ironically, it doesn't include a binary either, but a simple alias works:
alias pfi='java -jar /path/to/PFI/lib/pfi.jar'
And it did indeed produce an ipa without error. I don't have my hardware with me, but I'll be able to test it tonight. Meanwhile, I think I'm in business. Thank you all! -
I'm running v1 of TCS on a Dell Optiplex 755 w/4GB RAM. When
I run RoboHelp Packager for AIR on any output, repeat "any output,"
after I review the output and exit the packager, I get a BSoD. This
is dependable and replicable...10 times so far today trying to
diagnose it. Test has rulled out a RAM issue. Any advise?I may have found the issue:
When I spin an AIR application from WebHelp output and
preview the AIR application, or
when I Preview an application from the AIR Packager Generate
dialog,
if I Cancel the dialog before I close the AIR application,
the OS will BSoD every time;
if I Cancel the Generate dialog without first closing the AIR
application, the AIR Packager exits and returns control to me
without error, every time.
This sounds like a memory management bug of a garbage
collection bug.
When I close the fresh AIR application before I exit the AIR
Packager, apparently the AIR Packager attempts to clear memory,
finds that <some address> is already clear, and barfs with
"PAGE_FAULT_IN_NONPAGED_AREA" every time. -
I used the RoboHelp Packager for AIR on a WebHelp file
created RoboHelp 7. The WebHelp file works fine. However, when I
open the AIR version, many of the individual help topics do not
display. All of the TOC entries are present. And, all the files
display correctly when I use the Preview function.
Does anyone know where I can look to fix this?
ThanksHi Peter and thanks for reply. I know that there is an
article on my site about AIR help. It's useful and explanatory but
i din't find any useful tip regarding the issue. Any other idea?.
Thanks. -
How can I run Adobe AIR beta until my application is ready to be upgraded?
How can I run Adobe AIR beta until my application is ready to be upgraded? How can I get around being forced to upgrade? Everything was working fine until the upgrade was forced. This is a huge problem for me
You can use the Installation Tuner for Reader to customize the UI elements provided to the user. Details on the Adobe web site.
-
Packaging Linux AIR app as a native package (.deb)?
Ok, so I've been tasked with packaging an AIR app in a system package. We got a redistrubution license for AIR so I think we are good in that respect but I run into an unfortunate predicament when trying to do a silent install from a deb:
Both AIR runtime and AIR applicaiton generate a native package (.deb in this case) during install. So even though I can run silent install from my own deb, it fails to install as it cannot install a deb during installation of a deb. I am assuming that even if I could somehow grab the generated deb file, it would be against the license agreement to do so.
So, any thoughts as to how to get this accomplished? Is there an alternative distribution of an app that comes as a native ".deb" file? Or is there a command line option that disables a native package management install? ( I can seem to find no information on any command line options for the bin installer)
Thanks.
-MOk, so I've been tasked with packaging an AIR app in a system package. We got a redistrubution license for AIR so I think we are good in that respect but I run into an unfortunate predicament when trying to do a silent install from a deb:
Both AIR runtime and AIR applicaiton generate a native package (.deb in this case) during install. So even though I can run silent install from my own deb, it fails to install as it cannot install a deb during installation of a deb. I am assuming that even if I could somehow grab the generated deb file, it would be against the license agreement to do so.
So, any thoughts as to how to get this accomplished? Is there an alternative distribution of an app that comes as a native ".deb" file? Or is there a command line option that disables a native package management install? ( I can seem to find no information on any command line options for the bin installer)
Thanks.
-M -
Packaging an AIR application in a .EXE file using ADT
Hi All,
I have to package a .AIR file in .exe file with ADT.
Is it possible setting a default installation path in exe file using ADT tool?
I would like to create a .exe file where user can't interact with installation wizard to set a particular path.
Does it exist a particular option?
Would you suggest an example?
(...adt -package -target native ??? myApp.exe myApp.air)
Thanks in advance
GianniHi All,
I have to package a .AIR file in .exe file with ADT.
Is it possible setting a default installation path in exe file using ADT tool?
I would like to create a .exe file where user can't interact with installation wizard to set a particular path.
Does it exist a particular option?
Would you suggest an example?
(...adt -package -target native ??? myApp.exe myApp.air)
Thanks in advance
Gianni -
Possible Solution: Allow native code packaging with AIR using ADT?
Packager / ADT are providing huge benefits for AS3 developers targetting mobile as we all know. We also know that we'd like as much access to the native libs for the various platforms as we can possibly get. Two cases in point, in-app purchasing and access to Apple's iAd network. Discussions about these requirements over the last few days with a colleague of mine have resulted in him coming up with a very strong idea for providing adhoc access to native libraries. He has posted his suggestion, (which involves a feature request to Adobe), on Adobe AIR Ideas at Labs. I really encourage as many people as possible to read his suggestion to get the discussion warmed up. If you think the proposal is worthy, please make sure you vote it up so that it registers on Adobe's radar. I believe this would really benefit all of us working with AIR for mobile. Here is the link.
Peter Robertsonmanicjames wrote:
I have packaged my AIR app into a Native .exe installer using ADT. If the user does not have air installed and they are connected to the internet, the AIR runtime is automatically installed.
Is it possible to package the AIR runtime into the exe so that if the user is not online the AIR runtime is installed?
I have experimented with the sidecar install and .air file but ideally I want to only have the one file(.exe). I already have a distribution licence from Adobe.
This isn't available at this time, but I think it's a great idea. You might want to add a feature request for this over at ideas.adobe.com and bugbase.adobe.com, or review and vote for these current feature requests if they provide for what you're looking for:
Portable AIR Apps
Create portable AIR apps
If you decide to add a new request, please post back with the URL so others can cast their votes and add comments.
Chris -
Hi Everyone,
I need to package the Air run time in my air application
When i am installing the my air application in a system if the system doest have Air runtime environment .My air application has to install run time and then application.
How to do this ?I dont want badge.swf approach..Please tell me any another way to do that..
Thanks in advance.
Thanks,
TinuDon't use Jinitiator, use Sun JRE.
Then, be sure that you have the correct Java version in your formsweb.cfg.
If you google for "oracle forms sun jre" you will find plenty of postings on how to set up the config file for IE and Mozilla.
A tip: if you are sure all the clients have the correct jre version (e.g. 1.6.*), skip the version altogether in the Mozilla section:
--jpi_mimetype=application/x-java-applet;jpi-version=1.4.2_06
jpi_mimetype=application/x-java-applet -
RoboHelp Packager for Adobe AIR (BETA)
It is so exciting. It been just a few months since we
released Adobe RoboHelp 7 and a brand new Technical Communication
Suite, and today we are ready to share with you guys what we
perceive as the future of Online Help. All I can say is that Time
flies like an arrow. With this, I welcome you all to this new world
of Web 2.0 and the future of Online Help - check out the Public
Beta of
RoboHelp
Packager for Adobe AIR
The tool is available for Free of Cost and can be used by
customers who have either Adobe RoboHelp 6 or Adobe RoboHelp 7 or
the Technical Communication Suite.
The RoboHelp Packager for Adobe® AIR™ allows you
to convert your existing WebHelp files generated using Adobe
RoboHelp® to an Adobe AIR application. Help and knowledge
bases delivered as Adobe AIR application will have a consistent
look and feel across all platforms.
RoboHelp Packager for Adobe AIR can:
Generate a single distributable file
similar to a .chm file.
Provide a variety of skins from which a user can choose from.
In addition, for any skin a user can choose different themes, which
control the look and feel in terms of colors and button/icons
images.
Provide a consistent look and feel on all platforms and
operating systems.
Enable you to comment, in addition to using other advanced
features such as Breadcrumbs, Mini TOC and Security (Digital
Signatures).
The output generated after running this tool is an .air file.
This is a single file that has built-in logic to install itself.
The same file can be installed on any platform that has Adobe®
AIR installed. Installing the Adobe AIR runtime is as seamless as
installing the Adobe Flash® Player for your browsers.
Another important aspect of the Adobe AIR installer file is
that it is a single file that contains all of the information
regarding the look and feel of the Help along with the content. It
is one package with no separate viewer required.
To read more about the benefits of packaging your help as
.air file, please visit the following link:
http://labs.adobe.com/technologies/robohelp/aboutoutput.htmlWhen you are comparing this to Flash, does this comparison
extend to the requirement for each end user to install the Air
runtime on their PCs before they can access our RoboHelp system?
And that they will also get reminders to update to the latest
version of Air runtime? -
RoboHelp Packager for Adobe AIR - Beta 2 Announced
RoboHelp Packager for Adobe AIR is now updated. You can
download the new version for FREE from Adobe labs -
http://labs.adobe.com/technologies/robohelp/.
It has added a long list of novel features - first time for a HATT.
Now, besides multiple tabs, favorites, commenting and multiple
skins like Multi-Tab Accordion and Uni-pane Help, you have another
set of new features.
Designed for End Customers - Adobe AIR based Help templates
have been designed keeping in view the end customer. They have some
high-end navigation features like Mini TOC, Breadcrumbs, etc. Apart
from these capabilities, the new Adobe AIR based Help also empowers
the end customers to customize the Help. An end customer can set
their own preferences and customize Help as desired.
Compelling Rich Branded Experience- RoboHelp Packager for
Adobe AIR provides a compelling rich user experience. It includes
templates that help authors package the same content into three
completely different styles – Multi-Tab Accordion, Uni-Pane
or the Classic Tri-Pane Help. Apart from this it also helps the
Authors brand the Help as per Corporate Branding Guidelines. It
provides support for the addition of a Company Logo and a Punch
line in the main Help window. Apart from this it also provides an
About Box in the Help that details the version, description,
copyrights, logos etc.
Auto Update -Adobe AIR based Help applications provide an
Auto Update feature using which updates can be pushed to all
installed connected versions of Help. Usually, the Help content
bundled with the application is never updated, while the web
content is updated with current feature enhancements and additional
resources. Adobe AIR based Help provides you with the option to
publish updates for your end users at a common server location. The
Adobe AIR based Help is intelligent enough to check for updates and
prompts users to apply updates when it detects a new version is
available.
Review Workflows / Personalization of Help
Adobe AIR based help files can be configured in such a way
that you can add comments to topics and publish those comments at a
common location. This feature enables a complete review workflow,
whether or not the reviewer is a part of your group/organization.
* Reviewers within your network: Reviewers can publish their
comments to an XML file on a shared folder. They can also
synchronize the comments from other reviewers on the same network.
This enable multiple reviewers to simultaneously view the comments
being made by other reviewers as they review.
* Reviewers outside your network: You can send the .air file
to these reviewers who can then export their comments to an XML
file and send it to you. You can import these comments into your
Adobe AIR application.
Apart from the rewire workflow, the feature is designed to
help an end customer personalize Help by adding comments on the
same. These comments will not be uploaded to the server, however
can be exported to a file and shred with friends over email.
New Classic help Template - A new template called Classic
Help has been added. It is named Classic because it is a Tri-Pane
Help. Apart from that it has got all the power of any other Adobe
AIR based Help template. This template has a new feature called
“How do I” that lists all the browse sequences defined
in the WebHelp. We recommend that authors design their browse
sequences in such a way that they provide complete workflow
information to end customers.
Supports Packaging of Merged WebHelp- RoboHelp Packager for
Adobe AIR now supports merged WebHelp. If an author specifies the
WebHelp folder of a Master project, the Packager is intelligent
enough to detect and convert all referenced projects in the Master
Project. However, one needs to be careful while using this feature.
It doesn’t provide as much flexibility as Merged WebHelp. A
new Package needs to be created every time even when you update any
of the sub projects.
In Beta 2, zoom works flawlessly and search results has been
further improved.
If you have not tried the RoboHelp Packager for Adobe AIR,
you can download it now for FREE (Adobe RoboHelp 7 required).
Thanks and regards
Vivek Jain
Group Product Manager, Adobe Systems
Adobe Technical Communication Suite, FrameMaker and RoboHelp
www.adobe.com/products/technicalcommunicationsuite/
blog-
http://blogs.adobe.com/techcomm/
RoboHelp Packager for Adobe AIR-
http://labs.adobe.com/technologies/robohelp/When you are comparing this to Flash, does this comparison
extend to the requirement for each end user to install the Air
runtime on their PCs before they can access our RoboHelp system?
And that they will also get reminders to update to the latest
version of Air runtime? -
Failed to package iOS AIR app with Air 3.6 beta
Hi
I was hoping I could get help with those error messages
Configuration to package for an iOS device
Here is the adt command
c:\program files (x86)\jetbrains\intellij idea 12.0\jre\jre\bin\java.exe -Dapplication.home=D:\flex_sdk_4.6 -Xmx384m -Dsun.io.useCanonCaches=false -Dfile.encoding=UTF-8 -Djava.awt.headless=true -Duser.language=en -Duser.region=en -Xmx512m -jar D:\flex_sdk_4.6\lib\adt.jar -package -target ipa-test-interpreter -storetype PKCS12 -keystore D:\Headr\trunk\headr-app\headr-mobile\app\ios_profiles\certificate.p12 -storepass xxxxx -provisioning-profile D:\Headr\trunk\headr-app\headr-mobile\app\ios_profiles\development.mobileprovision D:\Headr\trunk\headr-app\headr-mobile\app\bin-debug\iOS_device.ipa D:\Headr\trunk\headr-app\headr-mobile\app\bin-debug\HeadrApplication-app.xml -extdir D:\Headr\trunk\headr-app\headr-mobile\app\ane -C D:\Headr\trunk\headr-app\headr-mobile\app\bin-debug iOS_device.swf -C D:\Headr\trunk\headr-app\headr-mobile\app\src data -C D:\Headr\trunk\headr-app\headr-mobile\app\src icons -C D:\Headr\trunk\headr-app\headr-mobile\app\src [email protected] -C D:\Headr\trunk\headr-app\headr-mobile\app\src Default.png
And error
Failed to package AIR application iOS_device.ipa:
D:\Headr\trunk\headr-app\headr-mobile\app\bin-debug\HeadrApplication-app.xml: error 302: Root content HeadrApplication.swf is missing from package
Configuration for the emulator
Here is the adt command
c:\program files (x86)\jetbrains\intellij idea 12.0\jre\jre\bin\java.exe -Dapplication.home=D:\flex_sdk_4.6 -Xmx384m -Dsun.io.useCanonCaches=false -Dfile.encoding=UTF-8 -Djava.awt.headless=true -Duser.language=en -Duser.region=en -Xmx512m -jar D:\flex_sdk_4.6\lib\adt.jar -package -target ipa-test-interpreter -storetype PKCS12 -keystore D:\Headr\trunk\headr-app\headr-mobile\app\ios_profiles\certificate.p12 -storepass xxxxxx -provisioning-profile D:\Headr\trunk\headr-app\headr-mobile\app\ios_profiles\development.mobileprovision D:\Headr\trunk\headr-app\headr-mobile\app\bin-debug\HeadrApplication.ipa D:\Headr\trunk\headr-app\headr-mobile\app\bin-debug\HeadrApplication-app.xml -extdir D:\Headr\trunk\headr-app\headr-mobile\app\ane -C D:\Headr\trunk\headr-app\headr-mobile\app\bin-debug HeadrApplication.swf -C D:\Headr\trunk\headr-app\headr-mobile\app\src data -C D:\Headr\trunk\headr-app\headr-mobile\app\src icons -C D:\Headr\trunk\headr-app\headr-mobile\app\src [email protected] -C D:\Headr\trunk\headr-app\headr-mobile\app\src Default.png
And error
Failed to package AIR application HeadrApplication.ipa:
unexpected failure: null
java.lang.NullPointerException
at com.adobe.air.ipa.IPAPackager.processExtensions(IPAPackager.java:314)
at com.adobe.air.ApplicationPackager.createPackage(ApplicationPackager.java:65)
at com.adobe.air.ipa.IPAPackager.createPackage(IPAPackager.java:257)
at com.adobe.air.ADT.parseArgsAndGo(ADT.java:572)
at com.adobe.air.ADT.run(ADT.java:419)
at com.adobe.air.ADT.main(ADT.java:469)Hi Pahup
My application.xml does say 3.6 at the moment.
First couple of lines from application.xml
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://ns.adobe.com/air/application/3.6">
But I am using 2 ANEs (one is ours but one is a third party that 'm afraid I can't change)
Their extension.xml look like below
My ANE
<extension xmlns="http://ns.adobe.com/air/extension/3.1">
<id>com.headr.HeadrNativeExtensions</id>
<versionNumber>1</versionNumber>
<platforms>
<platform name="iPhone-ARM">
<applicationDeployment>
<nativeLibrary>libHeadrNativeExtensionsIOS.a</nativeLibrary>
<initializer>ExtInitializer</initializer>
<finalizer>ExtFinalizer</finalizer>
</applicationDeployment>
</platform>
<platform name="default">
<applicationDeployment/>
</platform>
</platforms>
</extension>
Third party ANE
<extension xmlns="http://ns.adobe.com/air/extension/3.5">
<id>com.milkmangames.extensions.GoViral</id>
<versionNumber>2</versionNumber>
<platforms>
<platform name="iPhone-ARM">
<applicationDeployment>
<nativeLibrary>libGoViralAPI.a</nativeLibrary>
<initializer>MmgGoViralApiExtInitializer</initializer>
<finalizer>MmgGoViralApiExtFinalizer</finalizer>
</applicationDeployment>
</platform>
<platform name="Android-ARM">
<applicationDeployment>
<nativeLibrary>GoViralExtensionAPI.jar</nativeLibrary>
<initializer>com.milkmangames.extensions.android.GoViralExtension</initializer>
<finalizer>com.milkmangames.extensions.android.GoViralExtension</finalizer>
</applicationDeployment>
</platform>
<platform name="default">
<applicationDeployment>
</applicationDeployment>
</platform>
</platforms>
</extension>
Please let me know if there is any other workaround or if you see anything else that might be wrong in my above files.
Melissa -
Packaging an AIR application in a native installer
Hi! I'm trying to create a native installer of my AIR Application, because (I think) it's the only way make the native processes working. But I have a problem: I used the following command to pack: "adt -package -storetype pkcs12 -keystore myCert.pfx -target native -storetype pkcs12 -keystore myCert.pfx myApp.exe myApp-app.xml", but I get the error: "File myApp-app.xml is not a valid AIRI or AIR file". In the Flash Builder I use as additional compiler arguments: "-locale=pt_PT,en_UK,fr_FR,de_DE,ro_RO,es_ES -allow-source-path-overlap=true -source-path=assets" and I add the source path "src/locale/{locale}/". What is the sintax for packing my AIR application in a native installer? Thanks in advance.
Hi again! Thanks for the reply. I based myself on the link to see what command syntax I should use to pack my Air Windowed Application and it was the command that I presented in the previous post.
adt version "2.0.1.12090"
My Descriptor File
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<application xmlns="http://ns.adobe.com/air/application/2.0">
<!-- Adobe AIR Application Descriptor File Template.
Specifies parameters for identifying, installing, and launching AIR applications.
xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.0
The last segment of the namespace specifies the version
of the AIR runtime required for this application to run.
minimumPatchLevel - The minimum patch level of the AIR runtime required to run
the application. Optional.
-->
<!-- A universally unique application identifier. Must be unique across all AIR applications.
Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
<id>com.MyCompany.Application</id>
<!-- Used as the filename for the application. Required. -->
<filename>Production Control System</filename>
<!-- The name that is displayed in the AIR application installer.
May have multiple values for each language. See samples or xsd schema file. Optional. -->
<name>Production Control System</name>
<!-- An application version designator (such as "v1", "2.5", or "Alpha 1"). Required. -->
<version>2.1.3</version>
<!-- Description, displayed in the AIR application installer.
May have multiple values for each language. See samples or xsd schema file. Optional. -->
<!-- <description></description> -->
<!-- Copyright information. Optional -->
<!-- <copyright></copyright> -->
<!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
<!-- <publisherID>My Company</publisherID> -->
<!-- Settings for the application's initial window. Required. -->
<initialWindow>
<!-- The main SWF or HTML file of the application. Required. -->
<!-- Note: In Flash Builder, the SWF reference is set automatically. -->
<content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
<!-- The title of the main window. Optional. -->
<!-- <title></title> -->
<!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
<systemChrome>none</systemChrome>
<!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
<transparent>true</transparent>
<!-- Whether the window is initially visible. Optional. Default false. -->
<!-- <visible></visible> -->
<!-- Whether the user can minimize the window. Optional. Default true. -->
<!-- <minimizable></minimizable> -->
<!-- Whether the user can maximize the window. Optional. Default true. -->
<!-- <maximizable></maximizable> -->
<!-- Whether the user can resize the window. Optional. Default true. -->
<!-- <resizable></resizable> -->
<!-- The window's initial width in pixels. Optional. -->
<!-- <width></width> -->
<!-- The window's initial height in pixels. Optional. -->
<!-- <height></height> -->
<!-- The window's initial x position. Optional. -->
<!-- <x></x> -->
<!-- The window's initial y position. Optional. -->
<!-- <y></y> -->
<!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
<!-- <minSize></minSize> -->
<!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
<!-- <maxSize></maxSize> -->
</initialWindow>
<!-- We recommend omitting the supportedProfiles element, -->
<!-- which in turn permits your application to be deployed to all -->
<!-- devices supported by AIR. If you wish to restrict deployment -->
<!-- (i.e., to only mobile devices) then add this element and list -->
<!-- only the profiles which your application does support. -->
<!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
<supportedProfiles>extendedDesktop</supportedProfiles>
<!-- The subpath of the standard default installation location to use. Optional. -->
<!-- <installFolder></installFolder> -->
<!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
<!-- <programMenuFolder></programMenuFolder> -->
<!-- The icon the system uses for the application. For at least one resolution,
specify the path to a PNG file included in the AIR package. Optional. -->
<!-- <icon>
<image16x16></image16x16>
<image32x32></image32x32>
<image48x48></image48x48>
<image128x128></image128x128>
</icon> -->
<!-- Whether the application handles the update when a user double-clicks an update version
of the AIR file (true), or the default AIR application installer handles the update (false).
Optional. Default false. -->
<customUpdateUI>true</customUpdateUI>
<!-- Whether the application can be launched when the user clicks a link in a web browser.
Optional. Default false. -->
<!-- <allowBrowserInvocation></allowBrowserInvocation> -->
<!-- Listing of file types for which the application can register. Optional. -->
<!-- <fileTypes> -->
<!-- Defines one file type. Optional. -->
<!-- <fileType> -->
<!-- The name that the system displays for the registered file type. Required. -->
<!-- <name></name> -->
<!-- The extension to register. Required. -->
<!-- <extension></extension> -->
<!-- The description of the file type. Optional. -->
<!-- <description></description> -->
<!-- The MIME content type. -->
<!-- <contentType></contentType> -->
<!-- The icon to display for the file type. Optional. -->
<!-- <icon>
<image16x16></image16x16>
<image32x32></image32x32>
<image48x48></image48x48>
<image128x128></image128x128>
</icon> -->
<!-- </fileType> -->
<!-- </fileTypes> -->
<!-- iPhone/iPad -specific capabilities -->
<!-- <iPhone> -->
<!-- A list of plist key/value pairs to be added to the application Info.plist -->
<!-- <InfoAdditions>
<![CDATA[
<key>UIDeviceFamily</key>
<array>
<string>1</string>
<string>2</string>
</array>
<key>UIStatusBarStyle</key>
<string>UIStatusBarStyleBlackOpaque</string>
<key>UIRequiresPersistentWiFi</key>
<string>YES</string>
]]>
</InfoAdditions> -->
<!-- </iPhone> -->
</application>
Maybe you are looking for
-
I'd like to be able to view these events from the monthly and yearly overviews.
-
cant have satellite dish in my apt complex, and Id like to be able to watch a Sports channel thats on Direct TV, surfing the web foind some soft that works for PC that allows you to watch TV in your computer, wondering if theres anything for MAC or i
-
My cloud says I have photoshop but it is not on my computer! I clicked download & it says it downloaded & updated but there isn't any file on my computer to open or install.
-
Problème de mise à jour avec photoshop cs6
le programme s'est chargé à 50%.message rencontré extraction fichier (U44M1I210) faut il désistaller le programmeet le recharger
-
Restore only works on Mac?!
Until last week I had a perfectly happy primary connection (since Nov.) to iTunes on my PC, and had also successfully added songs to the iPod from a first gen iMac (running OS 10) that I also have, with no troubles. I know Apple does not encourage th