In the companion, this code is interpreted but in APKs it is compiled directly to Java bytecode before running through the normal Android build process. The intermediate code generation is in a language called YAIL, which is a Scheme with additional macros that provide a clean interface for the blocks to translate into. Probably existed before the IDE was constructed anyway in the prototype stages. In fact the IDE would already have that capability. APP Inventor native code with a launcher merged into an APK may be as straightforward as the process of running Python code by an interpreter. If the intermediary code is something else than standard code (again not sure but likely) that could make it problematic to translate outside of that context. My guess is something else that more easily translates the blocks and shapes and such to code, and is understood and easily compiled (C/C++", Python, ?) If this is truly Java under the covers, then perhaps it would be possible to extract code. Here is some idle speculation re: APKs generated by App Inventor, Whether there is something like "middleware" that is attached to an app inventor "code/instructions" to make an APK is your 800lbs gorilla in the corner. Students and learners could see how their objects convert to actual code. Code Generation with App Inventor COULD be a really cool new paradigm. So if it isn't possible, why not? I'd wager that this wasn't a design goal for app Inventor team.
That said, Trends seem to strongly indicate that "Visual Programming" will overtake traditional coding for many areas in the not distant future. Best way to figure it out would be look at the source code if you can., otherwise kind of reminds me of a blackbox problem. Hard to provide an answer to a question you don't understand.
0 kommentar(er)
