Such a relocation tends to be more visible from a distance.
New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
61–70 of 495 posts
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#62Is there a legitimate reason for this, or is Apple just thumbing their noses at Adobe (and everyone else)? Is Apple primarily annoyed that Adobe's app and MonoTouch aren't doing it the "Apple" way? Or do they not like that those frameworks present non-standard UI's (I haven't used MonoTouch, so I don't even know if that's the case here)?
I think it's stupid to ban different languages but I can see that writing apps specifically for a platform can make the application better on that platform, rather than having the lowest common denominator between iPhone, Android and Blackberry powered by a scripting language.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#63Getting away from the frenzied rhetoric, my opinion is that what Apple really wants to prevent is people releasing multi-platform compilers. So taking Flash as just one example, if I can build one app and the compiler can make me an iPhone executable, an Android executable, and so forth, Apple don't want that. In my experience so far with such "cross platform compatibility layers," they always produce results that wa…
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#64Earlier quoted context omitted.
Just make a webapp :/ all the freedom you need.
How well does that work for gaming? I like playing around with Unity3D; I have a hard time thinking that HTML5 is going to give the same experience.
http://learningwebgl.com/blog/
=)
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#65I don't really have a politically correct way to say this: What a horseshit maneuver by Apple.
I have been a very loyal mac user for years and love it, but I'm seriously considering going back to Linux. I am not a free software "zealot" and don't mind some closed-ness, but this is getting absolutely insane. Enforcing which LANGUAGES can be used on a platform?!? Insane! Edit: I've been looking at these guys: http://www.system76.com/ (I don't work with or have any vested interest in them, but they look cool.)
https://help.ubuntu.com/community/MacBook
I actually went the opposite route and installed mac os on a netbook.
http://gizmodo.com/5156903/how-to-hackintosh-a-dell-mini-9-i...
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#66Getting away from the frenzied rhetoric, my opinion is that what Apple really wants to prevent is people releasing multi-platform compilers. So taking Flash as just one example, if I can build one app and the compiler can make me an iPhone executable, an Android executable, and so forth, Apple don't want that. In my experience so far with such "cross platform compatibility layers," they always produce results that wa…
I can't see any way that this turns out as remotely positive for developers.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#67So porting from another language is now forbidden? Or is it unoriginal code that is banned?
Either way, the sheer craziness is astounding.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#68> Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine Controlling programmers like this seems positively insane, doesn't it? Does this mean that games can't do scripting in something like Lua either, under the letter of Apple's law?
Games never could do scripting in Lua, since you can't run interpreted or Jitted code on the iPhone anyway. What they are forbidding now is the usage of any third-party compilers that are producing native executables ... Adobe CS5, MonoTouch, Unity.
It's more than that. They are forbidding you from writing it in 'language X,' converting 'language X' into C/C++/ObjC, and then running that through Apple's developer tools. They state that the program must be originally written in C/C++/ObjC.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#692. ???
3. Therefore, if you write native iPhone apps, you must use C derivatives that expose raw pointers and direct memory access.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#70Earlier quoted context omitted.
Just make a webapp :/ all the freedom you need.
Freedom to have no access to the camera or microphone, for example?
idk, I've never thought the appstore was anything but a stop gap personally, and developing for it a crazy risk.