Changes between Version 2 and Version 3 of AndroidBoinc


Ignore:
Timestamp:
Mar 16, 2012, 1:35:30 PM (12 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AndroidBoinc

    v2 v3  
    1414called BOINCLite, which is able to handle only 1 project attachment and 1 job at a time.
    1515We considered this as a basis for BOINC on Android but decided it was too limited.
     16
     17In 2011 someone named Palo M. implemented a BOINC GUI for Android:
     18
     19http://code.google.com/p/androboinc/
     20
     21This is intended to control BOINC clients running on remote hosts,
     22but in principle it could control a local client.
     23I haven't looked at it.
    1624
    1725At the 2011 BOINC Workshop, Keith Uplinger, Peter Hanappe and Michael Tarantino
     
    4048== What about the GUI? ==
    4149
    42 The current BOINC GUI (the Manager) is implemented using WxWidgets,
     50The current BOINC GUI (the Manager) is implemented using !WxWidgets,
    4351for which no port to Android exists.
    4452Also, though the Manager's "simple view" is similar to what
     
    5058to use Unix pipes or some other IPC mechanism).
    5159
    52 Note: someone (I'm not sure who) has already implemented a BOINC GUI for Android:
     60We maybe able to use some or all of AndroBOINC;
     61I've contacted its author asking about the status of its source code.
    5362
    54 http://code.google.com/p/androboinc/
     63== Packaging ==
    5564
    56 This is intended to control BOINC clients running on remote hosts,
    57 but in principle it could control a local client.
    58 I haven't looked at it.
     65I think that what users see in Android app stores should be
     66branded with a particular project's identity,
     67rather than a generic BOINC identity.
     68When the volunteer first runs the app they're prompted
     69for email/password on that project
     70(this could be made optional, in which case we'd create
     71an anonymous account for them).
    5972
    6073== Project plan ==
    6174
    62 To be determined
     75 * Standardize on the code and scripts for building the BOINC client on Android
     76   (probably based on Peter's work).
     77   Put these files in the BOINC repository.
     78
     79 * Get the scripts/makefiles for building SETI@home for Android
     80   into the SETI@home repository,
     81   and make an Android/ARM app version available on SETI@home.
     82   (Jeff, Eric)
     83
     84 * Persuade some other projects to build Android/ARM apps.
     85
     86 * Create a template for making a project-specific Android app,
     87   with instructions for adding it to spp stores.