Do I need to load an object c script at run time and run it against classes / methods / objects / functions in the current iPhone application?
BASIC NOTE: The main reason I would like to do this is to allow me to quickly prototype the application, and then, after I finished the main prototyping phase, take the scripts I wrote and compiled them instead during build. I never plan on sending an application using an object c-interpreter.
I ask that I played with the iPhone wax , a lua interpreter that can be embedded in the iPhone application, and it works very well, in the sense that any object / method / function that is publicly available in Objective-C code automatically connects and available in lua.
This allows you to quickly prototype applications by simply creating the core of your application as lua files that are in the user docs directory. Just reload the application and you can test the changes in your lua files without rebuilding the application in Xcode - a big time saver!
But, having Apples at its disposal the latest 3.1.3 SDKs, it seemed to me that the safest way to do this type of rapid prototyping would be if you could use Objective-C as interpreted code ... Thus, the worst case scenario, you could just compile it into your application before its release. I heard that the lua source can be compiled into bytecode and linked at build time, but I think the safest thing would be if the source script was in lens c, not lua. So your source is always in lens c, whatever.
This makes me wonder (I searched, but didn't come up with anything) if there are examples of how to embed Objective-C Interpreter in an iPhone app? This will allow you to quickly prototype your application against the current classes that are embedded in your binary, and when you are going to deploy your application, instead of running the classes through the application interpreter, you compile them.
With iPad and OS 4, bluetooth and virtual keyboards can work with iPhones and iPads ... This will make this type of rapid prototyping something more useful, at least for dev time. If you have an interpreter built into your application and, for example, it is on an iPad, you can encode the interpreter during the journey without Xcode. And to me, the most useful way to return the source code to the state approved by the "apple" would be if the scripts were Objective C.
objective-c objective-c-runtime iphone interpreter runtime
Brad parks
source share