213 | | === Running a "hello world" program === |
214 | | |
215 | | |
216 | | |
217 | | |
218 | | |
219 | | |
220 | | |
221 | | |
| 213 | ==== Theory ==== |
| 214 | For a Python program using !PyOtherSide to work it needs these things present on the Android device: |
| 215 | * the application files |
| 216 | * Qt 5 |
| 217 | * a Python 3 bundle |
| 218 | * the !PyOtherSide library |
| 219 | We don't need to care about Qt - its deployment is handled automatically by the Qt SDK Android support (it is either bundled in the APK, automatically copied to the device or provided by the Ministro library manager) and we don't need to care about it. The SDK also handles the deployment of the application files. |
| 220 | |
| 221 | But we need to get Python 3 & !PyOtherSide on the android device our self. For now we will just copy the files to a fixed location on the device with ''adb'' and hardcode a path pointing to them in the example application. This should be enough for getting a proof of concept of (hopefully) working !PyOtherSide on Android. |
| 222 | |
| 223 | In the future it should be possible deploy these files from the APK without a need for manual intervention - either by using the new asset mechanism or the old method (used by the !PySide for Android port) of bundling zip files that are unpacked on first start by modified Java boilerplate. |
| 224 | |
| 225 | ==== Deploying Python 3 & !PyOtherSide to the Android device ==== |
| 226 | |
| 227 | ==== Deploying & running a hello world application ==== |