Changes between Version 17 and Version 18 of PyOtherSideForAndroid


Ignore:
Timestamp:
Nov 6, 2014, 1:17:28 AM (7 years ago)
Author:
Martin Kolman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PyOtherSideForAndroid

    v17 v18  
    221221But 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.
    222222
    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.
     223In the future it should be possible deploy these files from a standalone APK without any need for manual intervention or rooting - 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.
    224224
    225225==== Deploying Python 3 & !PyOtherSide to the Android device ====
     
    256256It is just a normal !QtQuick Controls Android project template modified to load the needed libraries from ''/data/poside'' and with all the needed environmental variables set.
    257257
    258 Now open the project in the !QtCreator provided by the Qt for Android SDK, configure device deployment and press the ''deploy'' button. !QtCreator should do its thing and the application should successfully start on the device. Now look on the main.qml file in !QtCreator and note that while it has the {{{import io.thp.pyotherside 1.0}}} line, the {{{Python {} }}} line that actually instantiates the Python element provided by !PyOtherSide is commented out.
     258Now open the project in the !QtCreator provided by the Qt for Android SDK, configure device deployment and press the ''Run'' button and make sure your device with the deployed libs is selected. !QtCreator should do its thing and the application should successfully start on the device. Now look on the main.qml file in !QtCreator and note that while it has the {{{import io.thp.pyotherside 1.0}}} line, the {{{Python {} }}} line that actually instantiates the Python element provided by !PyOtherSide is commented out.
    259259
    260260Now uncomment {{{Python {} }}} line and try to deploy the application again. This time the deployment fails and the applications crashes as soon as it is started.