I am trying out the demo version and would like to export a "Hello World" as AIR. I have the AIR SDK and ADT installed.
When I export> mobile, it states that this feature is not yet integrated into the KoolMoves GUI. So, I'm not sure how I can export my "Hello World" test file to AIR?
Doing some more reading, it looks like, absent integration of AIR into the KoolMoves GUI, the only way to export AIR would be to separately use AIR SDK/ADT command lines?
Is this integration planned soon in an upcoming release of KoolMoves? Alternately, is there a free/low cost utility/plug-in that can be installed on a Windows computer that can be used to create the AIR file from the SWF?
It does have the mobile export, with reference to the AIR SDK, but it appears that in order to compile the AIR export from the SWF, it would require using command lines for the SDK?
Can the SWF simply be exported and converted using the AIR SDK/ADT without command lines (automated conversion)? Or does the the process require using command lines for the conversion to AIR using the AIR SDK/ADT?
(Maybe the demo version 9.3.0 since it's a demo doesn't have an automated conversion? But my demo's GUI does have the same items as the screenshot you have inserted above.)
The demo version is identical to the full version in export functionality.
That functionality was added several years ago. I don't know if export with AIR has gotten easier. I will have to do some research.
Another possibility (depending on your intended goal) is to export as Html5 from KoolMoves and use PhoneGap to convert the Html5 to mobile apps for all devices. The conversion is done in the cloud for free and is very straight forward.
I think for now this would be on the KoolMoves Wish List:
If at all possible, I would like to use the AIR SDK/ADT to develop AIR including AIR/APK. The command line route has a few steps, for example signing with a certificate, etc. So, if this were automated in KoolMoves, it would be a huge plus. I think it would need KoolMoves to put into the KoolMoves GUI (similar to the much less complicated mobile>preview version which is already automated), the command line steps as checkboxes (intermediate or full export) or fill-in or file search boxes (path to certificate, path to SDK, etc.). But once done, it would form a series of dialog boxes/AIR export wizard that could be hard-wired into the KoolMoves GUI as an added feature.
I don't know if I will be able to implement the gui for the AIR command in the next version. The survey has brought to light some issues that need to be addressed.
I found some useful examples @ Adobe on how to write the command lines and have got it working. If possible, in an upcoming version, would be useful to have it automated through the GUI. But I've figured out a work-around for now.
I did buy the KoolMoves program after seeing today that it will be possible to create AIR and AIR/APK files from the SWF's. (Hopefully, next version will not be extra cost, since I just purchased today. Are updates at no additional cost?)
Here are the links to the useful Adobe help info that aided me in getting it working in Windows:
I am starting to think about a GUI. I am curious where you got the certificate required for the command line. Post here or email me -- support at koolmoves
If you are asking about the signing certificate needed to create AIR apps, I generated my certificate a long time ago, probably using a Adobe Flash AIR app wizard. Once, you have set up a signing certificate you can use it over and over, if you wish. So the one I created a while ago is stored for repeated use, and I simply point to it.
But there are alternate ways to do this, for example, to set up a new one.
I think you can check Adobe AIR help files as a starting point. There may also be info on this in the Apache Flex set up. I believe the command line set-up can also be used to generate this, maybe even on the fly, but I don't know how this works.
If you need something different than the self-signing certificate information I've included above, please advise.
HTH
Last edited by saratogacoach; 05-04-2015 at 03:13 PM.
Wondered if there is a need in the dialog box for a box to enter the certificate password?
From what I remember about modifying the descriptor XML, a key item is matching the SDK version with the namespace: <application xmlns="http://ns.adobe.com/air/application/17.0">. So, if you are using AIRSDK17.0.0.144, the latest version currently, the namespace needs to be set to 17.0. In the Adobe SDK ADT release notes for each new download, I think that they mention the specific namespace needed.
Another item which gets modified is which icons to use for the AIR app. The icon sizes are different for Android and Windows, and specified or commented out accordingly when you create an AIR (Windows) or APK (Android). I have no experience with creating for IOS, but I think this can be done on a MAC.
On pressing Run, the console window prompts for the password.
I will investigate the namespace issue. The different icons are referenced in the xml file.
I am attaching a sample xml file that I have put together. I included all android permissions. The user needs to delete what is not appropriate. If you have modifications, return with your modified file.
So, if the descriptor XML needs to be further customized, like adding the above, hopefully this could be added by editing in/typing into the dialog box.