Changes between Version 25 and Version 26 of SeattleOnAndroid

Changes between Version 25 and Version 26 of SeattleOnAndroid

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 25 and Version 26 of SeattleOnAndroid

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 25 and Version 26 of SeattleOnAndroid

Show
Ignore:
Timestamp:
11/05/12 05:32:24 (7 years ago)
Author:
albert
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SeattleOnAndroid

    v25 v26  
    11= Seattle on Android = 
    22 
    3 This page discusses our port of Seattle to the Android platform. You will be able to download a native Android installer (APK) Real Soon Now from our clearinghouse web site. 
     3This page discusses our port of Seattle to the Android platform. You will be able to download a native Android installer (APK) Real Soon Now from our clearinghouse web site. In the meantime, find instructions how to install Python, the Seattle runtime, and the Seattle Node Manager below. 
    44[[BR]] 
    55---- 
     
    1313 
    1414= Overview = 
    15 Here is a general outline of steps to be performed. 
    16  1. Setting up Python. (I found this the hardest part.) 
    17  1. Patching Seattle's {{{nix_common_api.py}}} so you can run scripts locally, and/or 
    18  1. Patching Seattle's {{{nix_common_api.py}}} and {{{runonce.py}}} so you can run the installer which will configure the node manager (for donating resources). 
    19  1. Running the node manager. 
    20  
    21 We can't setup Seattle for running at boot time using Python, but our native installer can. 
    22  
     15Here is a general outline of steps to be performed. You will get access to Python, Repy (Seattle's runtime), and the Seattle Node Manager, respectively. 
     16 1. Set up [http://code.google.com/p/android-scripting/wiki/InstallingInterpreters Python for Android (Py4A)]. 
     17 1. [wiki:RepoAccess#Anonymousaccess Check out] the latest version of Seattle from SVN (r5656 and later should work). 
     18 1. Install Seattle on the command line. This won't give you autostart capabilities, though. 
    2319 
    2420= Setting up Python = 
    2521 
    26 As far as I know, you cannot install Python as a standalone app right now. Therefore, these steps cover the installation of the Scripting Layer for Android, into which the actual Python interpreter will be installed. ''(Note to self: Restore our phone from a plain image and try out all the steps. I'm pretty sure I'm forgetting something.) (Another note to self: Include links to the official installation instructions for SL4A and [http://code.google.com/p/android-scripting/wiki/InstallingInterpreters Py4A].)'' 
    27  
    2822 1. On the home screen, press ''Menu''. Go to ''Settings > Applications'' and make sure ''Unknown Sources'' is checked. This is needed for installing non-Market APKs right after downloading them. 
    29  1. Download the Scripting Layer for Android ([http://code.google.com/p/android-scripting/ SL4A]) from [http://android-scripting.googlecode.com/files/sl4a_r4.apk here]. Tap on the download notification to install. 
    30  1. Download the Python 2.6.2 interpreter for Android ([Py4A]) from [http://code.google.com/p/android-scripting/downloads/detail?name=PythonForAndroid_r4.apk&can=2&q= here]. Again, tap on the download notification to install. Congratulations! You can now run Python code from within SL4A, either using scripts from files or an interactive interpreter. 
     23 1. Download the Python 2.6.2 interpreter for Android ([Py4A]) from [http://code.google.com/p/python-for-android/downloads/list= here]. Tap on the download notification to install. Congratulations! You can now run Python code from within the Py4A GUI, either using scripts from files or an interactive interpreter. 
    3124 1. Undo Step 1 for obvious security reasons. 
    3225 
    33 For running Repy programs locally, SL4A is not the optimal choice, but shell access to the Python interpreter is tricky to add because the shell knows nothing about Python's paths yet. Depending on which shell you have, there are different routes to take from here. 
     26 
     27 
     28= Setting up Repy = 
     29 
     30Repy is the restricted version of Python Seattle supports. For running Repy programs locally, Py4A is not the optimal choice, but shell access to the Python interpreter is tricky to add because the shell knows nothing about Python's paths yet. Depending on which shell you have, there are different routes to take from here. 
    3431 
    3532For {{{sh}}} (which is the default shell also greeting you via [http://developer.android.com/guide/developing/tools/adb.html adb]'s {{{shell}}} command), I don't know yet where it takes its run commands (.shrc) from. If you have [https://github.com/jackpal/Android-Terminal-Emulator/wiki Jackpal's AndroidTerm2] installed, you could write an rc script and configure !AndroidTerm to run it on startup: Press ''Menu'', go to ''Settings > Start command'' and enter /path/to/your/script.