Mark,
Thanks, I think that clarifies things
So GAE works by interpreting Java, Python or Go programs, and only those programs, which means its services can only be used if you write something in
pure Java, Python or Go. If you start from scratch in one of those development environments, then you can deploy the application on GAE.
An alternative would be to extend LiveCode to be able to compile directly into a pure Java/Python/Go application...which is not feasible.
If I'm understanding your explanation correctly, then the code that LiveCode produces as an end-product is in C++ and/or Objective-C (only Android needs some Java). Does that mean it might be possible (leaving aside the question of clean translations) to use a converter to translate LiveCode's standalone application into pure Java/Python/Go? I don't have permission to post links, but I found a couple C-to-Java converters with a quick google search.
Basically these seem like two incompatible toolchains. If I want to end at GAE then I have to start in, say, a Java development environment. I tried to get started in Java a while ago and found it slow going. LiveCode is much more attractive for a variety of reasons. So, if I'm planning to start my toolchain in LiveCode, I have to end somewhere other than GAE.
I haven't gotten to the point in following the resources where they start to describe how to deploy LiveCode applications for servers and/or the web. If I'm understanding this correctly, then when I get to something that can be accessed over the internet I will have a C++/Objective-C application that will have to either be run in a browser plugin or run on a server.
Does that mean I should look at Azure or Amazon's web services instead of GAE? They're just standard servers, not a full platform, so they should be able to run the LiveCode-produced application, right?