I think you guys will get a kick out of this:
I decided to crack open iLuaBox and see it’s contents. Here is what I found. Open.zip Go down to all the .lua files. Feel free to copy the code from the “guidemo.lua” or “devicedemo.lua” and paste it into iLuaBox Lite. Those are the only that work in the lite version. Also browse the “gui.lua” or “device.lua” file to see all the functions you can use. And keep in mind, these are the real iOS UI elements… no portable UIs. I think we could get some major fun out of that in Codea. That would be some awesome features. Not to mention the Sockets, SQL, Vox, printing, exporting as a .lua, untouched Lua language (which means file IO is included)… Despite these features, Codea is still by far the best app on the app store. TLL - I think you might want to take a look at these features just because Codea could use these features. Also, you could use this app as an excuse to allow things like sockets in to Codea.
Thanks!
Correction: I’m not sure about the file import… It can also print code over AirPrint which is what I would like from Codea. And did I mention the direct link to downloading external module code from Lua? And the lua system is not alter at all (as far as I can tell). And they update fairly often, so apple notices them… X(
I think Apple may be fine with file I/O if it’s sandboxed (ie. only allowed within the Codea project directory). Not sure how they get away with sockets - but do they do graphics?
Apple is not fair, it s sad :-((
I think you guys will get a kick out of this:
I decided to crack open iLuaBox and see it’s contents. EDIT: REMOVED LINK Go down to all the .lua files. Feel free to copy the code from the “guidemo.lua” or “devicedemo.lua” and paste it into iLuaBox Lite. Those are the only that work in the lite version. Also browse the “gui.lua” or “device.lua” file to see all the functions you can use. And keep in mind, these are the real iOS UI elements… no portable UIs. I think we could get some major fun out of that in Codea. That would be some awesome features. Not to mention the Sockets, SQL, Vox, printing, exporting as a .lua… Despite these features, Codea is still by far the best app on the app store. TLL - I think you might want to take a look at these features just because.
Thanks!
P.S. @Bortels - I know that file IO is allowed… I was a little tired when I wrote that.
I didn’t see this thread the first time. @tskwara I’ve removed the link.
Mr. Zoyt, I believe that iLuaBox’s GUI toolbox was disabled (by order of Apple) last April…
http://www.mobileappsystems.com/forum/viewtopic.php?f=2&t=24#p40
Also the support for “external text editors” (such as Textastic) introduced in version 1.4.1 was removed – again by order of Apple – in the current version 1.5.
Thanks for notifying me about that @Blanchot, but how come the code works then? And how come the GUI and device in-app purchases are still available on the app store? I’m running iLuaBox Lite 1.5, and I can still export as a .lua file and the GUI and device info code still works. You try it… If it’s not in the full version, that’s really annoying. But then that means that apple must have no problem with the sockets. Apple has asked them to remove a few other features, so why didn’t they ask sockets removed?
@Zoyt. I’m not sure why the GUI and Device in-app purchases are still showing as in-app purchases for the standard version. I own the Pro version and for this version they are not available. Perhaps you should buy the standard version and then try to purchase the two tool boxes in question?
Edit: the full description of the standard version does not list the GUI or Device toolboxes. I think the fact that they are still listed as in-app purchases in the side bar is due to some sort of error on the appstore side (or the developer’s negligence).
Did you try the code? Please do. Thanks for letting me know @Blanchot.
Just curious, I assume you prefer Codea over iLuaBox?
@Blanchot - Just curious if the code I was tailing about works.
Ya, those features are not listed. Why did apple want them removed though?
Just curious, I assume you prefer Codea over iLuaBox?
You are indeed one of “those curious fellows” aren’t you? 
Of course I prefer Codea Mr. Zoyt. I find iLuaBox useful as a sort of quick scratch pad for learning (i.e. roughing out functions and quick experiments) but without graphic functions and the brilliant UI it doesn’t hold a candle to Codea.
I absolutely agree… does the code work? Can you please try it? Or do you not have an app like Files Connect in your iPad? I can paste it into here or on my website.
Thanks a lot @Blanchot!
It would appear that the gui.lua and device.lua code require “gui.core” and “device.core” resources which are not present Mr. Zoyt.
Thanks for checking. In curiouse why apple wanted them to remove the GUI and device. I think that the lite version was the only version that didn’t have the GUI, device info, and export as .lua removed, because I can do them all on the lite version.
Thanks!
Feedback is always welcome and appreciated. Lot’s of things get built, reviewed and approved, but later removed at Apple’s request. Guidelines aren’t always clear enough though. iLuaBox will be around for some time, and the roadmap calls for some interesting and unique UI enhancements. While the iLuaBox GUI Toolbox can no longer be offered, it remains in the App Store database in a way that permits hundreds of users who bought the product to continue to restore their purchases. How it is represented in the store however is beyond our control.
If this board’s moderator is moderating, please remove the above link to iLuaBox Lite’s copyrighted contents
TS
MobileApp Systems
@tskwara - Sorry. I did. I find it interesting that apple made you remove the GUI. I’m curiouse why… And how you get to keep file io + sockets…
I removed the link a while ago… Which one did you remove? Feel free to close or delete this conversation. I wasn’t thinking when I did that.
Edit: I see. I missed that one.
Edit #2: IN fact, please do. I really didn’t mean to do this. I’ll look for anywhere else I did this to anything else.