Question re project organization

William Prothero prothero at earthednet.org
Sat Feb 7 06:46:05 CET 2015


Kay:
Thanks for offering your expertise. What I’m thinking is to have a main application stack. then the user will be able to add stacks to enhance the software. I’m thinking of a mySQL database that is queried, that lists available enhancements and their location. The user would get a menu of enhancements and choosing one or more would download and connect them into the main application. I’m thinking the main app will be the “engine” that supports peripheral activities. It’s an educational app, so various activities, writing exercises, challenges, explanations and videos, etc would be added. The way the program develops will depend on feedback from teachers and what they will actually use.

Is this practical in the iOS style of app? I’m really tired of rewriting my software for new authoring systems and would like to get this right. From what I understand, Apple will not let you write apps that download code that they haven’t approved of. Is there a way I could accomplish what I want, within the current iOS rules, which will probably eventually be applied to the desktop too? In fact, will Apple allow the app to connect to my mySQL database for configurations and content downloads? I guess I should spend some time going over Apple’s documentation on this. 

Best,
Bill


> On Feb 6, 2015, at 3:57 PM, Kay C Lan <lan.kc.macmail at gmail.com> wrote:
> 
> On Fri, Feb 6, 2015 at 3:40 AM, William Prothero <prothero at earthednet.org>
> wrote:
> 
>> I expect the splash app model is the way to go.
>> 
> 
> Only if you never ever plan on deploying to iOS or you don't believe that
> OS X's iOSification will get to the point that the same restrictions that
> prevent splash stacks from being approved by Apple for iOS will be applied
> to desktop. The latter obviously assuming that you are working within the
> Mac App Store not an unknown developer.
> 
> If on the other hand an iOS version is a possibility then you may as well
> cross the bridge now and find a non-splash stack solution - as you already
> seem to be working with a server side db a local sqlite db might be a
> possibility; stored in specialFolderPath("documents") for iOS and
> specialFolderPath("support") for OS X and Win (not sure for Linux).
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode




More information about the use-livecode mailing list