http://gorillajawn.com/wordpress/2008/01/29/adobe-air-native-os-integration-problem/ Enterprise Software Consultant Mon, 15 Mar 2010 20:02:48 +0000 http://wordpress.org/?v=2.9.1 hourly 1 http://gorillajawn.com/wordpress/2008/01/29/adobe-air-native-os-integration-problem/comment-page-1/#comment-20859 jonr Sat, 18 Apr 2009 23:06:35 +0000 http://ectropic.com/wordpress/?p=20#comment-20859 I understand the dilemma for Adobe. However, the choice to limit the ability to integrate with the native OS limits the number of applications that developers will be able to build on the AIR platform. For example, if you require peer-to-peer integration, you either have to find ways to break out of the sandbox (like Merapi) or use a different platform. Either way, you end up with the same challenges ... you just are unable to use the native AIR platform for building your application. I understand the dilemma for Adobe. However, the choice to limit the ability to integrate with the native OS limits the number of applications that developers will be able to build on the AIR platform. For example, if you require peer-to-peer integration, you either have to find ways to break out of the sandbox (like Merapi) or use a different platform. Either way, you end up with the same challenges … you just are unable to use the native AIR platform for building your application.

]]> http://gorillajawn.com/wordpress/2008/01/29/adobe-air-native-os-integration-problem/comment-page-1/#comment-20858 Michael Sat, 18 Apr 2009 22:41:57 +0000 http://ectropic.com/wordpress/?p=20#comment-20858 It you start integrating with the native OS, the AIR platform stops being truely cross platform, and you are back to "write once, test and revamp everywhere". Adobe obvously made the decision to avoid that. It you start integrating with the native OS, the AIR platform stops being truely cross platform, and you are back to “write once, test and revamp everywhere”. Adobe obvously made the decision to avoid that.

]]>