What are the options of extending your Lua api ?
If there are some native cocoa library functions that I’d like to use but you don’t support them
is there a way to call them ?
regards
m
p.s. great idea with your SDK we just need native iphone tester
[import]uid: 1540 topic_id: 109 reply_id: 300109[/import]
Which apis do you want to call?
Ansca [import]uid: 24 topic_id: 109 reply_id: 76[/import]
I have a similar question. Corona is very impressive but it’s not clear whether I can use my existing shared libraries within a Corona app. In the regular Lua interpreter I can load them with Lua’s require statement. I haven’t managed to test that out yet in Corona.
Thanks,
Kyle [import]uid: 2543 topic_id: 109 reply_id: 123[/import]
Now I can report that I have in fact been able to test the Lua require() statement. It seems that there are virtual paths internal to the running App itself, that are searched when the require() is evaluated. This is similar to what I’m familiar with from Lua, except that of course I have no access to this kind of virtual path. So I have to assume that part of the build process will involve the populating of a virtual path with whatever shared libraries or whatever else is needed for my app to run.
I can only hope I got that right, and I wouldn’t mind if it provokes some kind of response from those who know more about this than I do.
Thanks,
Kyle
[import]uid: 2543 topic_id: 109 reply_id: 124[/import]
Kyle
Is there a specific path you think Corona should look for? Name/Convention/
Carlos [import]uid: 24 topic_id: 109 reply_id: 125[/import]
Carlos,
I’m just not familiar with the kind of path access that I’m seeing when the require() search paths are displayed. Maybe all iPhone apps are like this? That is, all path accesses, like loading private copies of shared libraries, are limited to a path that has “App.” as its root? If this is standard behavior then I just haven’t studied iPhone architecture enough yet.
Thanks,
Kyle
[import]uid: 2543 topic_id: 109 reply_id: 129[/import]