- client: on startup, if new version, arrange to get new project list
- alphabetize fields in prefs structure
- client emulator: simulate project-requested backoff after work fetch
- remove uFluids and Virtual Prairie from the projects file
- XML parser: return error if string exceeds buffer size.
- client: when parsing MD5, use 64 instead of 33 char buffer.
    When the XML parser reads a string,
    it enforces the buffer size limit BEFORE it strips whitespace.
    So if a project put whitespaces before or after the MD5,
    it would fail to parse.
MGR: fix crash bug in Simple View preferences dialog
Updates for 7.0.60
- remove dead projects
- client: don't prefix <task> messages with [task]
- client: major overhaul of work-fetch logic based on suggestions
    by Jacob Klein.
    The new policy is roughly as follows:
    - find the highest-priority project P that is allowed
        to fetch work for a resource below buf_min
    - Ask P for work for all resources R below buf_max
        for which it's allowed to fetch work,
        unless there's a higher-priority project allowed
        to request work for R.
    If we're going to do an RPC to P for reasons other than work fetch,
    the policy is:
    - for each resource R for which P is the highest-priority project
        allowed to fetch work, and R is below buf_max,
        request work for R.
- client: work fetch message tweaks: show state before actions
- tabs -> spaces
- Client: detect new Win versions and AMD GPUs; from [P3D] Crashtest
Fix for "make clean" not removing .a files in lib/
Merge branch 'master' of ssh://boinc.berkeley.edu/boinc-v2
- client emulator: parse <max_concurrent> in <app> in client_state.xml.
    This gives you a way to simulate the effects of app_config.xml
- client: piggyback requests for resources even if we're backed off from them
- client: change resource backoff logic
    Old: if we requested work and didn't get any,
        back off from resources for which we requested work
    New: for each resource type T:
        if we requested work for T and didn't get any, back off from T
        Also, don't back off if we're already backed off
            (i.e. if this is a piggyback request)
        Also, only back off if the RPC was due to an automatic
            and potentially rapid source
            (namely: work fetch, result report, trickle up)
- client: fix small work fetch bug
- client: fix bug in work fetch that prevented resource backoff
- scheduler: fix bug in plan class XML spec,
    when it uses a project-specific pref element that's
    missing from a user's prefs.
    From Michael Goetz via Rytis.
-android: acquisition of WakeLock to prevent CPU throttling when display is off.
-android: multiple layout improvements
- client: AMD GPU names; from Jord