Changes between Version 2 and Version 3 of AndroidBoinc

Timestamp:

Mar 16, 2012, 1:35:30 PM (13 years ago)

Author:

davea

Comment:

--

AndroidBoinc

@@ -14 +14 @@
 called BOINCLite, which is able to handle only 1 project attachment and 1 job at a time.
 We considered this as a basis for BOINC on Android but decided it was too limited.
+
+In 2011 someone named Palo M. implemented a BOINC GUI for Android:
+
+http://code.google.com/p/androboinc/
+
+This is intended to control BOINC clients running on remote hosts,
+but in principle it could control a local client.
+I haven't looked at it.
 
 At the 2011 BOINC Workshop, Keith Uplinger, Peter Hanappe and Michael Tarantino
@@ -40 +48 @@
 == What about the GUI? ==
 
-The current BOINC GUI (the Manager) is implemented using WxWidgets,
+The current BOINC GUI (the Manager) is implemented using !WxWidgets,
 for which no port to Android exists.
 Also, though the Manager's "simple view" is similar to what
@@ -50 +58 @@
 to use Unix pipes or some other IPC mechanism).
 
-Note: someone (I'm not sure who) has already implemented a BOINC GUI for Android:
+We maybe able to use some or all of AndroBOINC;
+I've contacted its author asking about the status of its source code.
 
-http://code.google.com/p/androboinc/
+== Packaging ==
 
-This is intended to control BOINC clients running on remote hosts,
-but in principle it could control a local client.
-I haven't looked at it.
+I think that what users see in Android app stores should be
+branded with a particular project's identity,
+rather than a generic BOINC identity.
+When the volunteer first runs the app they're prompted
+for email/password on that project
+(this could be made optional, in which case we'd create
+an anonymous account for them).
 
 == Project plan ==
 
-To be determined
+ * Standardize on the code and scripts for building the BOINC client on Android
+   (probably based on Peter's work).
+   Put these files in the BOINC repository.
+
+ * Get the scripts/makefiles for building SETI@home for Android
+   into the SETI@home repository,
+   and make an Android/ARM app version available on SETI@home.
+   (Jeff, Eric)
+
+ * Persuade some other projects to build Android/ARM apps.
+
+ * Create a template for making a project-specific Android app,
+   with instructions for adding it to spp stores.