Joachim:

Yes, that's the intended architecture.
The installers may have the names and icons of particular projects
(e.g. Einstein@home) or account managers (e.g. GridRepublic).
However, they should install the BOINC client and the GUI
in a project-independent place (like /usr/bin/boinc).
*It's critical that there be only one BOINC data directory,
and one copy of the software*.

We need to decide how things should appear to the user
if they add N projects.
Should it look like they're running N apps?

My inclination is: no.  It should look like 1 app,
and the icon for it should be project-neutral (e.g. the BOINC icon).

This suggests that at install time,
we show the user a splash screen saying that
1) Einstein@home (or whatever the project is) is based on BOINC;
2) click on the BOINC icon to control Einstein@home
3) you can add other projects if you want.

-- David



On 04-Jan-2013 8:00 AM, Joachim Fritzsch wrote:
> Hi!
>
> I want to propose an architecture change for BOINC on Android.
>
> The initial design combines Client and Manager in the same Android 
> application.
> Which, due to the isolation of application on Android, leads to problems when 
> a
> volunteer installs several BOINC-based applications - which seems not 
> unlikely.
>
> A possible solution is, to split Client and Manager back into different 
> Android
> apps:
>
> - generic Client as a rudimentary Android app. Does not need to have a user
> interface, i.e. background service. A few lines of Java code, that trigger
> ARM-compiled Client at boot time.
>
> - (potentially multiple) project-branded and -maintained Managers, that check
> for presence of Client upon installation (package dependency)
>
> @David,Rom: What are your thoughts on this? Is it possible for you to take
> charge of such an Android Client in the long-term?
>
> Joachim
>
>
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to