Changes between Version 31 and Version 32 of PySideForAndroid

Timestamp:

Feb 18, 2013, 12:08:26 AM (11 years ago)

Author:

Martin Kolman

Comment:

--

PySideForAndroid

@@ -49 +49 @@
 It first builds Shiboken, followed by !PySide. The script is fully automatic, but waits for the user to ''press any key'':
 * after Shiboken is configured for build
-* after PySide is configured for build
+* after !PySide is configured for build
 Like this you can easily check for any errors during configuration.
 
@@ -59 +59 @@
 The resulting !PySide libraries compiled for Android are located in the ''stage/lib'' folder.
 
-See the ''Example project for the Necessitas Qt Creator'' section for how the PySide libraries can be used as a part of a self-contained Android application.
+See the ''Example project for the Necessitas Qt Creator'' section for how the !PySide libraries can be used as a part of a self-contained Android application.
 
 
@@ -125 +125 @@
 
 ==== How does it work ? ====
-The project contains various components, that together enable the creation of fully standalone Python & PySide application APK, while also allowing to bundle any arbitrary libraries and files needed by the application.
-
-The example project is called ''PySideExample'' and uses the ''org.modrana.PySideExample'' unique name. this means, that when it's APK is installed on and Android device, it gets installed to this directory:
-{{{
-/data/data/org.modrana.PySide.Example/files/
+The project contains various components, that together enable the creation of fully standalone Python & !PySide application APK, while also allowing to bundle any arbitrary libraries and files needed by the application.
+
+The example project is called {{{PySideExample}}} and uses the {{{org.modrana.PySideExample}}} unique name. This means, that when it's APK is installed on and Android device, it gets installed to this directory:
+{{{
+/data/data/org.modrana.PySide.Example/
 }}}
 This path is important, as the application needs to set a couple of environmental variables during startup, pointing to libraries and themes that reside in this directory.
@@ -136 +136 @@
 The {{{main.cpp}}} and {{{main.h}}} files are used to build a C++ Python wrapper. This wrapper is build against the the Android-compiled python libraries in {{{build_dependencies/python}}} by Necessitas. 
 
-Once the APK is deployd to the device and started, this wrapper is run. It initializes it's build-in Python interpreter, which tries to start the {{{/data/data/org.modrana.PySide.Example/files/main.py}}} Python file. This Python code then imports PySide, instantiates a QApplication and starts the main loop.
+Once the APK is deployd to the device and started, this wrapper is run. It initializes it's build-in Python interpreter, which tries to start the {{{/data/data/org.modrana.PySide.Example/files/main.py}}} Python file. This Python code then imports !PySide, instantiates a QApplication and starts the main loop.
 
 Behind the scenes, Necessitas handles wrapping the QApplication to an Android activity and showing it on the screen. It also handles other stuff like keyboard input & Qt Mobility.
@@ -160 +160 @@
 
 #define QML_IMPORT_PATH "/data/data/org.modrana.PySideExample/files/python/imports/"
+
+#define PYSIDE_APPLICATION_FOLDER "/data/data/org.modrana.PySideExample/"
 
 #endif // MAIN_H
@@ -175 +177 @@
 
 ===== The example Python application =====
-The example application is basically a normal !PySide application, it imports !PySide, instantiates QApplication and starts the main loop. There is only one main difference in this piece of code:
+The example in {{{main.py}}} inside {{{my_python_project.zip}}} is basically a normal !PySide application, it imports !PySide, instantiates QApplication and starts the main loop. There is only one main difference in this piece of code:
 
 {{{
@@ -368 +370 @@
 == Ideas for improvement ==
 There is definitely still room for improvement, such as:
-* a script that renames & customizes Necessitas Qt Creator PySide projects
+* customizes Necessitas Qt Creator !PySide projects
 * building APKs from command line only without Qt Creator
 * show a progress bar when the bundled libs are unpacked on first start