Exporting LiveCode Projects

[Jon0149]

Allowing us to Export LiveCode Stacks to XCode .iproj.
So we can make little adjustments in XCode and then Deploy.

[richmond62]

I think that is expecting "a bit much".

[Jon0149]

If you can export it to a standalone application in Mac OSX or iOS why not into an Objective-C.
It has to be translated at some point into objective-c for making the application.
Assuming LiveCode translates to Objective-C then deploys?

[FourthWorld]

Assuming LiveCode translates to Objective-C then deploys?

That assumption would be incorrect. LiveCode statically binds its own compiled engine with your scripts, talking to the OS directly in object code. No Objective-C translation happens.

There was a brief period many years ago in which Apple had required that all iOS apps be made with only four languages (C, C++, Objective-C, and JavaScript), but even then translation was not allowed (the "originally written in" clause), and thankfully once the gaming world reminded Apple that most of their products rely on runtime-compiled scripting engines Apple eventually backpedaled on that, opening the door to any system that uses the public APIs regardless of source language.

[richmond62]

If one trusts Livecode one should not need to make "little adjustments" with another set of coding tools.

Currently all I have to do is open the App folder and change the development number (which for some reason is left as that of the IDE in standalones).

[richmond62]

Having just exported a standalone with 6.0.2 for Mac I can report that the thing I wrote about in the previous message is no longer a problem.

This SHOULD mean one does not need to fiddle around with standalones post-build in anything else at all.