Hi David! I do like the idea of having a couple of predefined sets of settings that one can easily select.
Something that bothers me since the early days of BOINC is the inconsistency of which preferences can be set via web / manager / client (command-line or files) and possibly account manager. If you're touching the preferences code anyway, you might consider the following proposal: * create an XML blob that specifies the available settings (sections, names, explanation, possible values). This would be rather easy in full-featured XML, but it should be possible with BOINC's idea / implementation of XML, too. * have web code, code in the manager etc. that dynamically creates an options dialog of this specification This would * ensure consistency of the different possibilities on how to modify settings * make it easy for projects to add project-specific preferences without maintaining additional settings code * make it possible to configure project-specific settings locally in the manager (or account manager) * be trivial to extend the settings for future use, e.g. if new coprocessors become available Best, Bernd On 08.12.10 23:35, David Anderson wrote: > http://boinc.berkeley.edu/trac/wiki/PrefsRemodel > > This isn't something we're going to do anytime soon, > but we may as well discuss it. > > -- David _______________________________________________ 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.
