3 ms·

But it wont be a compatibility layer, it would be no different than using a third party Objective C library. Apple cant really mandate all code for an app be wr

by arpit 17y ago

But it wont be a compatibility layer, it would be no different than using a third party Objective C library. Apple cant really mandate all code for an app be written by the developer team itself. Basically its all Objective C code and some Adobe tool cross compiles it to bytecode that the Flash Player can play

benologist 17y ago
It still has to be "originally written" in x.
- avdempsey 17y ago
  No...you originally write in Objective-C, using an Objective-C framework designed to make cross-compiling to Flash bytecode easier. I think Apple would be a-ok with its competing platforms getting filled with ported apps. You'll still need to program in Objective-C though, and it's hard to see what advantage Adobe's existing apps would bring to Objective-C development.
  - MichaelGG 17y ago
    It's pretty simple for Apple to get around. They can wait until someone does something like this, and then go update their agreement to say cross-platform ui toolkits are not allowed to be used.
gte910h 17y ago
Let's go to what the actual text is: >3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited). For the purpose of your post, the important sentence in all that is: Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited So nee, your solution of a Objective C library written for android would be a compatibility layer, and therefore is forbidden.

by arpit 17y ago

benologist 17y ago

It still has to be "originally written" in x.

avdempsey 17y ago
No...you originally write in Objective-C, using an Objective-C framework designed to make cross-compiling to Flash bytecode easier. I think Apple would be a-ok with its competing platforms getting filled with ported apps. You'll still need to program in Objective-C though, and it's hard to see what advantage Adobe's existing apps would bring to Objective-C development.
- MichaelGG 17y ago
  It's pretty simple for Apple to get around. They can wait until someone does something like this, and then go update their agreement to say cross-platform ui toolkits are not allowed to be used.

gte910h 17y ago

Let's go to what the actual text is: >3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited). For the purpose of your post, the important sentence in all that is: Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited So nee, your solution of a Objective C library written for android would be a compatibility layer, and therefore is forbidden.