Question on launching SWF's with AIR support

I apologize in advance for my ignorance in this, but I am just getting started using Flex/Flash.
The Adobe PDF Driver SDK recommends using Flash for the driver UI. One of the entries in the configuration file for the driver is for specifying the path to the SWF file. It is this SWF file that is shown when the driver UI is displayed.
I have a need in the driver I am creating to access the File system, and so I need to build this SWF as an AIR app (so I can include flash.filesystem.*). But the problem is that I can only specify the name of the SWF file in the configuration file, and can't tell it to run adl.exe nor specify the descriptor file.
Is there any way to build an AIR app (as a desktop app) without it needing adl or the descriptor file?
I am currently using a trial version of Flash Builder, but ultimately the SWFs will need to be created on the fly using the command-line compiler (amxmlc).

Similar Messages

Is this possible to package flash 8 swf file with AIR

Hi All,
Is this possible to package flash 8 swf file with AIR
packager or load flash 8 swf file in AIR?
Any info on AIR would be greatful.
Thanks,
Shailesh

Yes.
-ted

Launching swf files with Director

I recently obtained Adobe Director 11.5 to create a menu for launching a series of Flash CS4 files. I worked through Dean Utian’s excellent tutorial and found the following script to program a button to launch another Director file. However, I can’t figure out how to get it to launch a swf file. If someone could tell this poor soul how to get Director to launch swf files I would really appreciate it. Thatch
on mouseUp me
play movie "FileName”
end

I don’t know if anyone else will ever need to do this, but just in case I thought I should share the final protocol we developed. This will embed a Flash SWF file into a Director DIR, so it can be published in a form that can be opened directly, without the multiple clicks required to open an swf with Windows Explorer (or the MAC equivalent). It has been tested with Director 11.5 and Flash CS4. I hope my shorthand is clear. Dean Utian, Sean Wilson and James Newton all helped me with this, and support their support was far above and beyond the call of duty.
1.) Resize the Director stage to match the Flash stage
Click the Director stage > Windows > Property Inspector > Stage Size > 550 x 400
(alternatively you can compose the Flash file with a stage that matches Director’s.   640 x 480 is the default)
2.) Embed the SWF into Director
File > Import > Browse to File > Import
Drag cast member from cast window to stage
ctrlK > distribute horizontal across stage > distribute vertical across stage
3.) Type a pause script into the script channel of the score
on exitFrame
go to the frame
end
4.) Open the movie script window (Ctrl + Shift + U) and type in stretcher script (this allows the SWF cast member to resize if the final window is maximized)
on resizeWindow
aw = _player.activeWindow
awRect = aw.rect
aw.drawRect = awRect.offset(-awRect.left, -awRect.top)
end
on zoomWindow
resizeWindow()
end
5.) Set publication settings
File > Publish Settings > Projector > Shockwave
                                                      > Center stage in monitor
                                     > Shockwave > Allow movie scaling
                                     > Html > Template > Shockwave Default
                                                > Stretch Style > Preserve Proportions
                                                > Stretch Position > Horizontal Align
                                                > Stretch Position > Vertical Align
                                                > Dimensions > Percentage of Browser Window
                                                > Width > 100
                                                > Width > 100
                                     > Formats > Windows Projector (Creates an exe for Windows)
                                                      > Macintosh Projector (Creates an app for MACs)
                                                      > HTML (Creates an htm and dcr for Windows or MACs)
6.)Publish the movie
File > Publish
The Windows Projector will create a single exe file that can be opened by double clicking the icon. If your SWF has addChild script, it will launch a second SWF, but the second SWF must be in the same folder as the exe.
The Macintosh Projector will create an app application that can be opened by double clicking the icon. However this application actually consists of a folder with several subfolders and files. You will not see this with the MAC file directory, but you will if you try to E-mail the application. If your SWF has addChild script, it will launch a second SWF, but the second SWF must be in the same folder as the app.
The HTM Projector will create a htm file and a dcr shockwave file. Both must be in the same folder, and the user must double click the htm icon to open the dcr. If your SWF has addChild script it will not launch a second SWF.

[advance question] loading a swf in adobe Air, which loads an image with "componentloader"

Good evening all,
I think this is a complex issue.
I have adobe air application which loads a SWF I made.
Inside this SWF I have used the "component LOADER" to load
something with "ContentPath=image.jpg" for example.
But the swf loaded in the Adobe air works, but does not load
the "ContentPath image"...
(it does load and display it when it this swf is run outside
adobe Air)
I need it to be dynamic like this, so if eventually I Include
it in the package it won't help much...
I just intend to replace an image background from this loaded
swf file!
Thanks!
Edit:
At this time of the editing, I fear and realize
something....I have been using Actionscript2 for the .SWF file,
could it be why it does not works???
If its problematic, is there a simple way like telling it to
read actionscript2, rather than transforming everything??
edit2:
I found this on the official AIR FAQ:
Will Flash version 8 and below SWF files run in Adobe AIR?
Yes. However, the Adobe AIR APIs are only exposed to Flash
content via ActionScript 3 / AVM2, and thus Flash 8 / AVM1 SWFs
will be able to run, but they will not have direct access to the
Adobe AIR APIs.
source:
source
faq Adobe
it seems it should works!!??
Edit3:
nope I confirm at least some code made in Actionscript2
works.
I am sure this code needed to be changed for working in
actionscript3, so "actionscript2" code works in Adobe Air.
The problem of not loading my image must come from something
else!!??

Good Morning all!
Hilarious....
I tried so much to think maybe Adobe Air does not like a SWF
using actionscript2, or it does not load any "external image from a
swf", etc...
None of that!
I just in FLASH in the ComponentLoader....I did put simply
the ContentPath at "myimage.jpg"....
Of course I had to use the absolute path like
"c:\\myfolder\\myimage.jpg"
Of course aswell it works now!!!

Can we resize swf file created with AIR API in AIR application?

Hi,
I created a .swf file with AIR API.
I want to open and resize it in AIR application. This .swf file taking dimensions as default in which it opens.
I want to change its width and height.
Is there any way to change its dimensions?
Please suggest me the solution.
thank you

Loading a Flex WindowedApplication into another is not supported. However,
you might be able to access the WindowedApplication and size it. Sub-Apps
in AIR should be based on Application, not WindowedApplication.

Making an AIR auto launch swf

I have a client asking me to make an auto launch swf for their AIR app, which I did not develop. I modified their current AIRInstallBadge and it works fine, but now they want a swf on a page that will just auto launch it with no interaction. Basically a swf with no UI, invisible. Is that possible? I've tried the following with no success:
var paramObj:Object = LoaderInfo(this.root.loaderInfo).parameters;
var appID:String = validateString(paramObj.appid);
var pubID:String = validateString(paramObj.pubid);
var appLaunchArg:Array = validateString(paramObj.applauncharg) == null ? (null) : ([paramObj.applauncharg]);
var airSWF:Object;
var airSWFLoader:Loader = new Loader();
var AIR_SWF_URL:String = "http://airdownload.adobe.com/air/browserapi/air.swf";
airSWFLoader.load(new URLRequest(AIR_SWF_URL));
airSWFLoader.contentLoaderInfo.addEventListener(IOErrorEvent.IO_ERROR, handleAIRSWFError);
airSWFLoader.contentLoaderInfo.addEventListener(Event.COMPLETE, handleAIRSWFInit);
function handleAIRSWFInit(event:Event) : void
     airSWF = airSWFLoader.content;
      airSWF.launchApplication(appID, pubID, appLaunchArg);
function handleAIRSWFError(event:IOErrorEvent) : void
    Text.text = "unable to load air.swf";
function validateString(param1:String) : String
return param1 == null || param1.length < 1 || param1.indexOf("<") >= 0 || param1.indexOf(">") >= 0 ? (null) : (param1);
I've tested and all parameters get loaded. I'm sure i'm missing some protocols or it's not possible for for security reasons. Any help would be appreciated.
Thanks,
Adam

Never mind, I just found the answer. Nope you can't do it.
The launchApplication() method can only operate when called in the event handler for a user event, such as a mouse click.

Unable to launch swf in standalone player

I'm unable to launch swf's with the standalone player from
within flexbuilder, it will always use the browser.
I've unchecked the option 'Generate HTML wrapper file' from
the 'Actionscript Compliler' settings menu and I've tried to force
it to use the debug player to the best of my knowledge.
I'm on OSX 10.5.1 ( macbook ) and using FlexBuilder 3 beta3.
I've done two reinstalls of the OS, and the problem still comes up.
I've installed FlexBuilder first and then Flash CS3. I've prayed to
the internet search engines with no sign of hope, so please
adobe... you're my only hope :)
-Tony

Hi toknee,
There was a bug related to this problem. The next FB release
should have the fix.
Here is the bug URL:
https://bugs.adobe.com/jira/browse/FB-11228
thanks,
Mihai

I have tried with my ipad air and a friends ipad to mirror the contents to a samsung smart tv via appletv and cannot either to work.I have spent over 2 hours today on live chat with apple support with no resolution.Any ideas please?

i cannot mirror from ipad or ipad air to a samsung smart tv via appletv.Any ideas please?

I have tried with an Ipad Air and Ipad using Op System 8.0.2 to mirror their contents to the screen of my Samsung Flat Screen Flat TV via the latest make of Appletv.I have spent over 2 hours going through all settings etc with Apple Customer Service Live Chat.They cannot find or replicate the problem and says it is all working fine.My TV screen displays, when i go into mirroring, "ready for connection - on your device launch Allshare Cast".Nothing happens although i have agreed with Apple Support that all settings are on and are correct.Can anyone help please, as Apple Support cannot?

Why reloading pure asset SWF with AIR sdk 3.6+ doesn't work?

Hi, I posted this in the AIR beta channel, but I think it suits better here... I'm sorry for double posting.
Hi,
I have a game targeting iOS using AIR sdk that needs to load many swf assets from the disk (packaged with the game). When using AIR sdk 3.5, everything runs just fine. When upgrading the sdk to 3.6 or later (-swf-version=19, 20, 21), we ran into the following problems:
1) The packaging time (making the ipa file for iOS) passes from 15 minutes to 40+ minutes.
2) The game can't load any swf twice (ie. reload a swf).
The first problem is not a big deal. We only have to wait a little bit more. Our guess is that is has to do with new feature introduced by the sdk 3.6, which will go through all packaged secondary swfs and remove the code from it, and since we have lot of swf assets, it takes more time.
The second problem is way more serious, as I have to be able to reload assets according to player's action. Since we have a ton of assets, I can't keep them all in the memory as we could quickly run out of memory.
I know that there's a documented limitation of sdk 3.6 which states:
In AIR apps on iOS running in AOT mode there is a problem when a SWF is reloaded. Therefore reloading a SWF will not be allowed for AIR apps for iOS in AOT mode and attempting to do so will result in following error:
Error 3764: Reloading a SWF is not supported on this operating system
It also says that "Reloading of pure asset SWFs will work with AIR 3.7". However, that's not true, since all my assets are pure asset SWF without any code inside. It won't work, even with AIR 3.8.
While searching on the internet, I came across a forum post that says that the only way to know if a swf is a pure asset swf, is by using swfdump.exe, and searching for the DoABC2 tag. I did it, and effectively, DoABC2 tag was there, but empty.
So my first observation is that:
- Pure asset SWF file containing empty DoABC2 tag can be reloaded using AIR SDK 3.5
- Pure asset SWF file containing empty DoABC2 tag can't be reloaded using AIR SDK 3.6+
It seems to me that AIR SDK 3.6+ doesn't care if the tag is empty or not. If it is there, then it's not ok.
Then I wanted to know why my SWFs have this empty tag. After lot of tests, it turns out that it is because I am using jsfl to automate the export of assets from a FLA file. And there comes my second observation:
- When exporting a swf without code from Flash IDE (Ctrl+Alt+Shift+S), there's no empty DoABC2 tag.
- When exporting a swf from the Flash IDE's library (right click on the library Movieclip -> Export Flash movie...), empty DoABC2 tag is automatically inserted.
Unfortunately, my jsfl script uses thee same Library export functionality, and it produces the same "contaminated" swf. Why doesn't it produce the same SWF from both ways of export? I have no idea.
In the perfect world, the AIR SDK would not only look for the DoABC2 tag, but it should check whether if there's code inside. Also, Flash should use the same export process disregarding if it is being called from the IDE or the Library, and not inserting empty DoABC2 tag when there's no code.
As for now, I can't find any workaround to solve my problem. That means that I'm stuck with swf-version=18, and I can't benefit from all the cool features such as rectangle textures, new Context3DTextureFormat etc.
If anyone has a solution, or simply pointing out what I'm doing wrong here, please share it.
Thanks for reading.
Iojeirg

Hi makc3d,
Thanks for the response. After all that time I started losing hope.
I would not say that the abvious solution is to remove the tag. I think it should not be put there in the first place if there's no code at all. Moreover, this only happens when exporting a MC from the Library, and it works just fine when exporting normally (publish). It seems more like a bug than an expected behaviour.
Also, AIR should check for actual code in this tag instead of relying only on the tag itself.
Your solution is a nice workaround, and I will certainly try that out. But as I said, it will not fix the original bug, it will only patch it later on in the process.

Hello, my iphoto on my mac OS X Version 10.5.8 will not launch after talking with an apple support tech. She had me sinc my iphone to my mac desktop and my photos downloaded from my iphone and were at the bottom. Now the iphoto will not launch.

My iphoto app will not launch after talking with an apple tech support who had me sync my iphone 4S with my mac desktop. The pictures downloaded from my iphone and after disconnecting from the Apple help, my iphoto had disappeared from the very bottom of the screen and will not launch. Can you help me retrieve my pictures. They are still on the computer.

Any help here:
http://support.apple.com/kb/HT2638?viewlocale=en_US&locale=en_US

AIR 3.4 SDK Beta with iOS6 Support is missing BETA 2 update

We are trying to get our application that uses native extensions working with iO6 and AIR 3.4. I can see from the website that there was an update on August 7th, and the top links show that update in the link date:
Ie: http://labsdownload.adobe.com/pub/labs/flashplatformruntimes/air3-4/air3-4_p2_sdk_mac_080712.tbz2
However the links under “AIR 3.4 SDK Beta with iOS6 Support”, have not been updated. (And that is oviously the build we are most interested in)
http://labsdownload.adobe.com/pub/labs/flashplatformruntimes/air3-4/air3-4_p1_sdk_ios6_mac _071612.tbz2

So I found the problem. I had installed beta 1 in a folder called AIR 3.4 ... I installed beta 2 in a folder called AIR 3.4 Beta2
I did however point Flash CS6 to use the AIR 3.4 Beta2 SDK ... it must not like something about this. Once I deleted both SDK's and then put Beta 2 in a folder simply titled AIR 3.4 everything works again.

Installed Yosemite om my MacBook Air, resulted in no Sound at all. No input devices no output devices. What can do? Have had 2 meetings with Apple support with no results.

Recently, I installed Yosemite on my MacBook Air. After that I had no sound. Not even the start up chime. In Sound preferences there are no input devices and no output devices. I have had three meetings with Apple support with no results. Can anyone help? This seems to be a regular problem.

Try these in order testing your system after each to see if it's back to normal:
1. a. Resetting your Mac's PRAM and NVRAM
    b. Intel-based Macs: Resetting the System Management Controller (SMC)
2. Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
     Boot to the Recovery HD: Restart the computer and after the chime press and hold down the
     COMMAND and R keys until the Utilities menu screen appears. Alternatively, restart the
     computer and after the chime press and hold down the OPTION key until the boot manager
     screen appears. Select the Recovery HD and click on the downward pointing arrow button.
3. Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the Utilities menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.
4. Reinstall Yosemite: Reboot from the Recovery HD. Select Reinstall OS X from the Utilities menu, and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible
            because it is three times faster than wireless.
5. Reinstall Yosemite from Scratch:
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
How to Clean Install OS X Yosemite
Note: You will need an active Internet connection. I suggest using Ethernet if possible
            because it is three times faster than wireless.

Problem packaging AIR app with NativeProcess support!?

My AIR packaged AIR app doent work with NativeProcess
when I package it like
<supportedProfiles>extendedDesktop desktop<supportedProfiles>
or
<supportedProfiles>desktop extendedDesktop<supportedProfiles>
But when I use just <supportedProfiles>extendedDesktop<supportedProfiles>
Packager complains with Error 306!!
What is that suppose to mean?
Help please
I'm using FB4,SDK 4.1

Are you packaging your application as a native application (.exe or .dmg)? I believe applications with extendedDesktop support (and nativeprocesses) can only be packaged as native applications.

HT5312 i am in Iraq right now and i cannot make any schedule for having a call with your support team , however, i forgot the answer for security questions , and also previously i have not summited a rescue Email address is there any way to reset my accou

i am in Iraq right now and i cannot make any schedule for having a call with your support team , however, i forgot the answer for security questions , and also previously i have not summited a rescue Email address is there any way to reset my account?

Please be aware that you are not communicating with Apple when you post in these forums. These are user-to-user support forums, so in almost all cases the only people who will reply to your posts are, like me, your fellow users.
As to whether you can work with Apple via email on this issue I can't say for sure, but you can contact them via this web page:
http://www.apple.com/support/appleid/contact/
and see if they can help. It's mostly going to be an issue of you being able to prove to them that you are the account owner.
Regards.

The three main hurdles to porting existing Flash projects to iOS with AIR

The purpose of this discussion is to identify significant problems currently preventing AIR for iOS from being a viable solution for porting existing Flash apps. These issues have been largely ignored by Adobe, so I hope that everyone will add to this discussion if you have also run into these roadblocks in targeting iOS with the AIR SDK. I hope that Adobe staff will address and provide some much needed information with regard to fixing these problems.
There are 3 main problems with targeting iOS currently, which are probably affecting anyone who is trying to port a project that is both medium to large in size and makes use of SWF loading. Pretty much any project that has a MVC architecture is going to load SWF assets that are compiled against a view class, so this is likely affecting many people.
1. Bug - ADT packager runs out of memory when packaging "large" numbers of SWF assets
https://bugbase.adobe.com/index.cfm?event=bug&id=3511656
This is a blocking bug that prevents packaging projects with a large number of SWF assets. It is preventing me from being able to package all the needed assets for my project. I provided Adobe with my project to package a couple months ago so this bug can be reproduced in house and fixed. The Adobe employee who was handling this never tried to reproduce the issue and has stopped responding to email and comments in the bug. Adobe, please have someone take charge of testing and fixing this bug. It seems like it would be a straightforward fix once the failure is reproduced within a debugger.
Has anyone who has encountered this problem determined the number of files or classes where it starts to fail. I've spent some time trying to reverse engineer what the packager is doing when it runs out of memory, so think I can determine how many classes it's working with, but obviously the size of the classes will be variable and so this number will probably be more of a range where we start to get into the failure state.
Please let me know if you can reproduce this issue with your project with many SWF assets and upvote the bug if you are already aware of this one.
2. Bug - SWF reloading when doing a "real" (AOT) compile
https://bugbase.adobe.com/index.cfm?event=bug&id=3636385
There is already a forum post that covers the history of this issue (http://forums.adobe.com/message/4920638) but that also covers some issues in older AIR builds with loading of any SWF asset (previously fixed), where this bug deals specifically with reloading of SWF assets that include compiled bytecode (ABC).
The expectation here is that all versions of the Flash runtime should handle SWF reloading with ABC in the same way, so that a single codebase can be used to target web and iOS (or any other platform). This is the only issue of the 3 that has a legitimate work around, in my opinion, because the assets can be cached within the app within a loading manager layer. All the application code that makes loading calls can stay the same, and a compiler flag can be used to enable this caching for iOS builds, with subsequent requests returning a new instance of the cached asset. This can potentially lead to a very bloated memory footprint for the running app after a period of time, though, which could make some apps perform poorly, so a bugfix is ultimately needed.
3. Unimplemented feature (?) - The constraint that a single ApplicationDomain is used when running AIR for iOS
I did ask about this in the same forum post as SWF reloading but didn't get an Adobe response. Why does this constraint exist? My guess is that the AIR runtime for iOS simply hasn't implemented multiple ApplicationDomain support at this point, and that this was done to focus resources on other high priority features for the iOS runtime. It's possible that there is some aspect of the iOS operating system that makes it difficult or impossible to implement this feature, which may be why it's been avoided to this point, but obviously this is all conjecture without hearing from Adobe on it.
This is a major issue that needs to be addressed. For us, the problem is that our SWFs for multiple instances of the same type of asset use the same name for the AS export. For example, each item an avatar can equip is a single SWF with multiple sub assets -- the parts which comprise the item. Each of the parts will have an AS export name based on the avatar facing and where it is equipped, like "fv_head". This naming is consistent across all items, so we will load a lot of assets containing "fv_head" simultaneously. This normally works fine because the default behavior for Flash has always been that each SWF is loaded into a new ApplicationDomain instance, but for iOS a single ApplicationDomain must be used, causing these names to collide. The last SWF loaded containing a given AS export name overwrites the previous ones of that name.
The work around for this, and I use that term loosely, is to go through and uniquely name every AS export in every asset where sets of assets with the same export name is used. For us that is hundreds of items with multiple exports. Maintaining unique naming across all these parts is also a very error prone process, not to mention all the code that manipulates the parts needs to be modified to handle the new naming and make sure it's referring to the now uniquely named assets.
The expectation here is that all versions of the Flash runtime should handle asset loading in the same way and place each loaded asset into its own ApplicationDomain container as the default behavior. I'd like an Adobe employee to address my assumption that this is an unimplemented feature of AIR for iOS at this point, and let the community know if a solution for this will be implemented.
Summary
All three of these issues in combination are a major roadblock to porting existing Flash games to iOS with AIR. Issues with one can make it hard to test and try to work around others. All need to be fixed, but If I could only pick one of these to fix, it would have to be issue 3 -- that lack of proper ApplicationDomain support when loading assets. This issue is completely inconsistent with standard Flash behavior and creates a major roadblock to ports of existing applications with no viable solution for a workaround.
I look forward to Adobe's feedback on each of these issues and hopefully fixes that will allow those of us working with AIR for iOS to get our products to market.

About the 3rd issue being an AoT design limitation, I'm not sure I understand why it's necessary to know during AoT packaging what the domain is that a child will be loaded into to be able to have SWF loading work as on the browser.
Isn't the ApplicationDomain an internal construct in the AIR runtime that you guys define in order to manage namespaces of loaded SWFs? To be clear, when I say "runtime" I know that the resulting code isn't being interpreted within the iOS app, but clearly you have a set of AIR libraries that get compiled into the IPA that provides support for all the Flash APIs. If that's the case, then wouldn't it be possible for the iOS version of the AIR libraries to define a new ApplicationDomain on the fly when code that has been cross-compiled to iOS native code loads a packaged SWF?
I don't have a clear picture of how ApplicationDomains are managed internal to the runtime of course, but a little more detail would be very helpful. Thanks.

Question on launching SWF's with AIR support

Similar Messages

Maybe you are looking for