Check out Jerry's new videos -- REV to ObjC -> iPhone

Josh Mellicker josh at
Sun May 9 18:31:56 EDT 2010

I was just speaking of a simple text parser and term search and  
replace. Certainly not worth the effort, it would be easier to just  
write in Xcode!

While you're correct about the dangers of writing for Apple, some  
developers continue to risk it because the potential  is in some cases  
quite large.


On May 9, 2010, at 11:32 AM, Chipp Walters <chipp at> wrote:

> Not true. There was much web talk about this on various dev blogs  
> and the consensus was Apple would definitely be able to create a  
> tool to identify Flash apps created from C ported to Xcode.
> The reason is simple. even though Flash (and Rev) generates C code,  
> they have to use their own C libraries to work with it. And these C  
> libraries have unique footprints which can easily be detected. Once  
> detected, it is easy to conclude they are in violation of SDK 4.0.
> And even if a better workaround was found, we're only a Apple  
> license dot dot revision away from being excluded once again. I  
> don't understand why this concept is so hard for folks to grasp? If  
> Apple doesn't want you to develop on their platforms, then do like  
> Adobe did and give up.
> Instead, focus on creating killer apps on other platforms. Sooner or  
> later someone is bound to create another must have software product  
> with a dev environment which is not Xcode. It just won't be able to  
> be run on iPhones and ipads.
> My advice would be it's risky to do business with Apple. Earlier, I  
> couldn't believe you could spend a year writing an iPhone app, just  
> to have it rejected based on arbitrary conditions. At least with  
> game consoles, they can pre-accept your idea and the final check is  
> only a QA one.
> Now, with the latest 4.0 (not 3.0,2.0,1.0) SDK, it's obvious Apple  
> can change their mind, midstream of your million dollar investment,  
> and kill your company plan with an unprecedented dot dot license  
> change limiting you to what "original programming language is used."  
> Who ever heard of such draconian development terms?
> Yes, to put trust in Apple as a partner these days is a risky  
> business indeed.
> On May 9, 2010, at 12:11 PM, Josh Mellicker <josh at>  
> wrote:
>> Of course, if you pasted the C code into Xcode and built your app  
>> there, there would be no way Apple could tell the code was not  
>> written in Xcode. Text is text.
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:

More information about the Use-livecode mailing list