Changes between Version 6 and Version 7 of PrefsPresets


Ignore:
Timestamp:
09/26/17 23:37:19 (7 months ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PrefsPresets

    v6 v7  
    3939
    4040||                                  || Max  || Standard || Green    ||
    41 || use at most X% of CPUs           || 100  || 85       || 85       ||
     41|| use at most X% of CPUs           || 100  || 85       || 60       ||
    4242|| use at most X% of CPU time       || 100  || 100      || 100      ||
    4343|| suspend when on battery          || yes  || yes      || yes      ||
     
    5656|| when in use, use < X% RAM        || 70   || 50       || 50       ||
    5757|| when not in use, use < X% RAM    || 90   || 90       || 90       ||
    58 || leave non-GPU tasks in mem       || no   || no       || no       ||
     58|| leave non-GPU tasks in mem       || yes  || no       || no       ||
    5959|| use at most X% swap file         || 75   || 75       || 75       ||
    6060|| download rate limit kb/sec       || ---  || ---      || ---      ||
     
    6464== Implementation ==
    6565
    66 If a user selects one of these,
     66If a user selects a preset,
    6767we should store the preset name (max, standard, green) in user.global_prefs,
    6868rather than the prefs themselves.
    69 Examples:
     69Example:
    7070{{{
    7171<global_preferences>
     
    7979This will let us change/extend the meanings of the presets.
    8080
    81 Users can still edit any pref.
    82 But if they change anything, they're not using the preset anymore.
    83 
     81Initial implementation: for simplicity, support only presets.
    8482Enable this by PREFS_PRESETS in project.inc.
    8583
    86 If set:
    87 - default new accounts to "standard"
     84PHP code only needs to know about preset names.
    8885
    89 In any case:
    90 - scheduler: expand <preset>foo</preset> to appropriate XML.
     86C++ code