Privacy prefs now loads the the consent_types found in the database table dynamically based on the enabled and privacypref flags introduced.
Removed enable_record_optin_consent config settings. Now the 'enabled' field in consent_type takes its place, one a consent_type by consent_type basis.
Added new preferences sub-class for consent table modification.
Added privacy preference form item to record user giving consent to data exports.
User's consent is recorded in the consent table.
- editing resource shared wasn't working
- change sizes of controls to "input-sm"
- show errors correctly in project prefs
- move selection of project prefs from project_specific_prefs.inc
to project.inc.
This means that (unless you've added your own project prefs)
you can update project_specific_prefs.inc from master, with no changes.
NOTE: projects will need to move their project prefs selections, e.g.
define('COLOR_PREFS', false);
from project_specific_prefs.inc to project.inc.
Then copy project.sample/project_specific_prefs.inc to your project/
policy change: when showing lists of name/value pairs in a table,
don't show the names with a different background color or font.
This is what Edward Tufte would call "noise".
Keep the visuals as simple as possible.
See http://boinc.berkeley.edu/trac/wiki/PrefsUnification
Discrepancies:
- "Consider the computer in use" pref isn't disabled when the two
"suspend X when computer is in use" prefs are unset.
Doing this would have greatly complicated things.
- day-of-week prefs aren't implemented
No tooltips yet.
I set out to make project-specific prefs use the same object framework
(PREF_BOOL, PREF_NUM etc.) as other prefs.
This turned out to be infeasible, so I settled for a code cleanup instead.
The reason it's infeasible is that the "other prefs" code
uses a SAX parser (xml_parser_create() etc.),
while the code for project-specific prefs uses the primitive
parse_element() and parse_next_element() functions in util_basic.inc.
If I'm going to change anything, I want to switch to a DOM parser
(e.g. simplexml) for both purposes.
- client: if PREFS::max_ncpus_pct is 0, don't set it to 100;
doing so prevents PREFS::max_ncpus from having any effect.
svn path=/trunk/boinc/; revision=23355
There are now separate flags for
"file_xfers_suspended": don't do file transfers
"network_suspended": don't do any network comm
(scheduler RPCs, RSS fetch, master fetch, etc.)
The policy:
if preferences/settings say no network
(quota exceeded, no-network mode, user active, time, excl. app)
then:
file_xfers_suspended = true
if (no recent network-related RPC) network_suspended = true
- user web: code cleanup for project prefs
svn path=/trunk/boinc/; revision=21299
Shawn Kwang