Question: How do you go about getting "written permission from Apple"? What's the standard way of doing this (is there one)?
Written permission probably means / is part of submitting it to the app store and getting it approved. No overhead.
Hello, Lua. (Apple opens door to interpreters on iOS devices)
21–30 of 52 posts
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#22The 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…
Exactly. And the blog's explanation of beign used for game scripting as a minor feature falls short: can anyone imagine what Half Life would be like without scripted events?
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#23Interesting. 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.
It's really just making their current policy explicit.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#24It's nice to see that Apple is starting to warm up to the idea of giving "express written consent" to apps doing things that might be considered to run afoul.
If that got implemented on a larger scale, the concerns of developers who say "I don't want to develop an app, then get it rejected with no warning" could be alleviated.
A step in a more moderate direction benefits everyone.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#25IMHO this doesn't help at all. The core issue is that I can't make an app that runs on multiple platforms. I know that cross platform is against Apple's best interest, but I just don't care. I won't be writing Apple applications.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#26The 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…
Why go to all the work to embed an interpreter when it only has "minor" uses? I can't see any reason to embed something as large as Lua in a mobile app if you aren't going to make good use of it - I would think this would include only something like parsing/interpreting algebraic expressions, e.g. for a calculator. I guess since it's on a case by case basis though, it could mean anything, and they could decide it means something different than it originally did at a later date.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#27Earlier quoted context omitted.
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.
> but what happens when someone creates a foo to objective-c compiler - for eg flash to objective-c or mono to objective-c. They already exist and are specifically forbidden by the license (or were last time I checked): the previous update added the requirements that applications be originally written in a supported language, forbidding the usage of a cross-compiler. Now I'm guessing if it's your own for your own stu…
Stuff like this makes me very unhappy. Everyone programming in the same language and using the same frameworks. Sounds right out of a pink floyd video or an apple commercial from the 80s. To repeat a popular meme - the more I grow up, the more I realise that maybe the Sith were upto something ...
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#28So nowhere explicitly is lua enumerated in the quote from apple.
Is there any particular reason why the posted write up references lua as opposed to i dont know perl or erlang? Are there historical reasons for its preference, as the wiki on lua lists in its use in games?
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#29The 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…
Exactly. And the blog's explanation of beign used for game scripting as a minor feature falls short: can anyone imagine what Half Life would be like without scripted events?
Imagine Half Life without 3d graphics. Now you see why scripting is a 'minor' feature.
Re: Hello, Lua. (Apple opens door to interpreters on iOS devices)
#30So nowhere explicitly is lua enumerated in the quote from apple. Is there any particular reason why the posted write up references lua as opposed to i dont know perl or erlang? Are there historical reasons for its preference, as the wiki on lua lists in its use in games?
You just answered your own question.