They take the engine minus the IDE stuff, and glue your stack to it, including substacks. The engine is I believe written primarily in C++ so I suppose you could tell them that. DBase worked similarly. You could either create a standalone app, or you could include a runtime engine and you source code in your distribution. Building a Livecode app with separate stacks included is a kind of mishmash of both approaches.
Bob On Feb 7, 2013, at 11:56 PM, Tiemo Hollmann TB wrote: > Hi, > > I just had a discussion with a (java and objective C) developer of iOS and > android Apps and couldn't really explain what the output of LC is for the > different platforms. This probably is discussed before more than once, but I > didn't found a real answer. > > Does LC has a "native" engine in objective C, java etc. for every platform > and "interprets" our scripts at runtime? Or does LC "compiles" our scripts > for every platform in any native format? Or anything in between? Is the > "apply" of a script just a save or kind of "precompilation" in a faster > "machine code" to be interpreted at runtime? > > If this is answered anywhere, perhaps somebody can give me a pointer? > > Thanks > > Tiemo _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
