If that were the case, then OpenPlug wouldn't be able to to it with Elips Studio, but they are. They basically are providing a modified Flex 3.x SDK to use within Flex Builder. Then their IDE extensions output an XCode project that even will give you hooks so you can tie into native services, like the camera, address book, etc.
On Tue, Apr 13, 2010 at 9:23 AM, Gregor Kiddie < gregor.kid...@channeladvisor.com> wrote: > > > That amounts to open sourcing the player, as anyone could take a look at > the XCode project (or reverse engineer the player from it), which is a no-no > from Adobe’s perspective. Turning the player into ARM code was about the > only way they could get round the licensing problems associated with the > player. > > > > Gk. > > > > *From:* flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] *On > Behalf Of *valdhor > *Sent:* 13 April 2010 15:15 > *To:* flexcoders@yahoogroups.com > *Subject:* [flexcoders] Re: With the latest eula agreement from Apple > > > > > > Yes, I know that. > > What I was suggesting is that Adobe change the output from ARM code to to > an XCode project. Wouldn't that get around the new Apple agreement? > > > > > >
