Hello, Lua. (Apple opens door to interpreters on iOS devices)
appleoutsider.com
Hello, Lua. (Apple opens door to interpreters on iOS devices)
1–10 of 52 posts
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#2Interesting. I'm surprised this change hasn't been covered at all by the tech press.
So does this 100% clear the way to use tools like Unity or Appcelerator? I'm particularly interested in Appcelerator (starting a droid/iPhone app in a few weeks) and there isn't a clear statement on their website about this change.
Update: I've emailed appcelarator about this change and requested clarification; I'll update again when I hear back.
Update 2: still no word from Appcelerator. I've spent some time digging through their forums and I think they just don't know what's going on either. It seems like they are just waiting to see what happens today when people start to submit iOS 4 Apps. I guess we'll know the answer becaus of this either way, hopefully soon.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#3I have altered the deal. Pray I don't alter it any further.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#4Interesting. I'm surprised this change hasn't been covered at all by the tech press. So does this 100% clear the way to use tools like Unity or Appcelerator? I'm particularly interested in Appcelerator (starting a droid/iPhone app in a few weeks) and there isn't a clear statement on their website about this change. Update: I've emailed appcelarator about this change and requested clarification; I'll update again when…
No, absolutely not. It says in the article that this is not for platforms that completely "take over" the app. This change is for Objective-C applications that want/need to use Lua or other include languages for minor features, like how Tap Tap Revenge uses Lua for its immersive themes.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#5The title and blurb is misleading.
You need permission from Apple on an application by application basis. Interpreted code is to be used in a "minor way" for "minor features". Thus, writing an entire iOS app in an interpreted language (such as Lua) does not seem likely to be allowed.
I'm not a lawyer though. Of course, Apple is fickle and contradicts itself often. Indeed, I would not be surprised to find Titanium gets free reign and Corona does not, or vice versa.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#6Question: How do you go about getting "written permission from Apple"? What's the standard way of doing this (is there one)?
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#7Question: How do you go about getting "written permission from Apple"? What's the standard way of doing this (is there one)?
Email sjobs@mac.com.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#8Interesting. I'm surprised this change hasn't been covered at all by the tech press. So does this 100% clear the way to use tools like Unity or Appcelerator? I'm particularly interested in Appcelerator (starting a droid/iPhone app in a few weeks) and there isn't a clear statement on their website about this change. Update: I've emailed appcelarator about this change and requested clarification; I'll update again when…
No, absolutely not. It says in the article that this is not for platforms that completely "take over" the app. This change is for Objective-C applications that want/need to use Lua or other include languages for minor features, like how Tap Tap Revenge uses Lua for its immersive themes.
Apple will fight a losing battle if they specify mode of execution to limit frameworks. Sure it will slow others down, but what happens when someone creates a foo to objective-c compiler - for eg flash to objective-c or mono to objective-c.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#9Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#10The title and blurb is misleading. You need permission from Apple on an application by application basis. Interpreted code is to be used in a "minor way" for "minor features". Thus, writing an entire iOS app in an interpreted language (such as Lua) does not seem likely to be allowed. I'm not a lawyer though. Of course, Apple is fickle and contradicts itself often. Indeed, I would not be surprised to find Titanium get…
> Thus, writing an entire iOS app in an interpreted language (such as Lua) does not seem likely to be allowed.
Indeed, this is pretty much specifically tailored towards games (which are scripted using e.g. Lua but not entirely written in it) or things like emulators.
Apparently, Apple has decided to go over Jobs's dislike for games and let them grow further on the platform.