Comments on: Working with AIR2.0 beta and nativeProcess – walkthrough http://tomkordys.net/blog/2009/11/30/working-with-air2-0-beta-and-nativeprocess-walkthrough/ freelance flash/flex/air developer Sat, 31 Jul 2010 08:00:16 -0700 http://wordpress.org/?v=2.8 hourly 1 By: admin http://tomkordys.net/blog/2009/11/30/working-with-air2-0-beta-and-nativeprocess-walkthrough/comment-page-1/#comment-184 admin Wed, 09 Dec 2009 10:09:11 +0000 http://tomkordys.net/blog/?p=97#comment-184 Hi Roger, I realised my post might be a bit confusing, let me clarify. You can check the platform the application is running on and conditionally load the right nativeProcess, but you won't be able to ship it as a single app. If you are including a native process you have to package it up as a native OS application: exe for Win, dmz for Mac. To make things even worse, you can only package your app to an exe on Win or to dmz on a Mac. Which means you need to have a machine with each operating system you want to publish to. At least for now. Hi Roger,

I realised my post might be a bit confusing, let me clarify.
You can check the platform the application is running on and conditionally load the right nativeProcess, but you won’t be able to ship it as a single app.
If you are including a native process you have to package it up as a native OS application: exe for Win, dmz for Mac. To make things even worse, you can only package your app to an exe on Win or to dmz on a Mac. Which means you need to have a machine with each operating system you want to publish to. At least for now.

]]> By: Roger Howard http://tomkordys.net/blog/2009/11/30/working-with-air2-0-beta-and-nativeprocess-walkthrough/comment-page-1/#comment-183 Roger Howard Tue, 08 Dec 2009 22:00:29 +0000 http://tomkordys.net/blog/?p=97#comment-183 Since the AIR runtime is cross-platform, I'm surprised/confused that you can't simply check the platform in your AS code and conditionally load the right native binary via nativeProcess - I would have expected to build an AIR app containing both Win and Mac binaries so one could still ship a single, x-platform AIR app. Did I miss something here? Since the AIR runtime is cross-platform, I’m surprised/confused that you can’t simply check the platform in your AS code and conditionally load the right native binary via nativeProcess – I would have expected to build an AIR app containing both Win and Mac binaries so one could still ship a single, x-platform AIR app. Did I miss something here?

]]> By: Theo Denovan http://tomkordys.net/blog/2009/11/30/working-with-air2-0-beta-and-nativeprocess-walkthrough/comment-page-1/#comment-182 Theo Denovan Wed, 02 Dec 2009 22:12:45 +0000 http://tomkordys.net/blog/?p=97#comment-182 It is a shame that the deployment build process isn't cross-platform; however virtualising windows is fairly painless for those of us running macs. I think it's a fair decision by adobe; it's reasonable to assume that you'll be running the OS targetted by the native process if for no other reason than to test it. Great article by the way. It is a shame that the deployment build process isn’t cross-platform; however virtualising windows is fairly painless for those of us running macs. I think it’s a fair decision by adobe; it’s reasonable to assume that you’ll be running the OS targetted by the native process if for no other reason than to test it.

Great article by the way.

]]> By: Sjaakie http://tomkordys.net/blog/2009/11/30/working-with-air2-0-beta-and-nativeprocess-walkthrough/comment-page-1/#comment-181 Sjaakie Wed, 02 Dec 2009 16:10:01 +0000 http://tomkordys.net/blog/?p=97#comment-181 Thanx dude, nice explanation! Thanx dude, nice explanation!

]]>