Changes between Version 1 and Version 2 of PrefsOverride

Timestamp:

Apr 25, 2007, 1:38:14 PM (17 years ago)

Author:

Nicolas

Comment:

Required manual changes to automatic conversion.

PrefsOverride

@@ -1 +1 @@
 = Preferences override file =
 
-      By default, [GlobalPrefs global preferences] and host venue are maintained on a project server, edited via a web interface, and downloaded from the server.  Some people may want to edit preferences locally, modify preferences on a single host, or hardwire the host venue. To accommodate these requirements, BOINC lets you create a 'preferences override file'. This file is read by the core client after it reads the preferences from the server, and it overrides those preferences.
+By default, [GlobalPrefs global preferences] and host venue are maintained on a project server, edited via a web interface, and downloaded from the server.
+
+Some people may want to edit preferences locally, modify preferences on a single host, or hardwire the host venue. To accommodate these requirements, BOINC lets you create a 'preferences override file'. This file is read by the core client after it reads the preferences from the server, and it overrides those preferences.
 
 The preferences override file is named `global_prefs_override.xml`. Its structure as follows:
-
 
 {{{
@@ -34 +35 @@
 [ <host_venue>venue</host_venue> ]
 }}}
-       If you write a program for editing preferences locally, you'll want to be able to tell a running core client to reread the preferences override file. You can do this using the [http://boinc.berkeley.edu/gui_rpc.php read_global_prefs_override()] GUI RPC. Or you can stop and start the core client.
 
+If you write a program for editing preferences locally, you'll want to be able to tell a running core client to reread the preferences override file. You can do this using the [GuiRpc read_global_prefs_override()] GUI RPC. Or you can stop and start the core client.