Changes between Version 3 and Version 4 of ProjectSpecificPrefs

Timestamp:

Dec 24, 2007, 1:23:26 PM (17 years ago)

Author:

davea

Comment:

--

ProjectSpecificPrefs

@@ -1 +1 @@
 = Project-specific preferences =
 
-You can provide users with a set of project-specific preferences, controlled via a web interface. These preferences are stored in XML, in a field of the user table. You determine the structure of this XML, and what it's used for. On the client, the XML is passed to your application in the [BasicApi#Communicatingwiththecoreclient APP_INIT_DATA structure].
+You can provide users with a set of project-specific preferences, controlled via a web interface.
+These preferences are stored in XML, in a field of the user table.
+You determine the structure of this XML, and what it's used for.
+On the client, the XML is passed to your application in the [BasicApi#Communicatingwiththecoreclient APP_INIT_DATA structure].
 
 Examples of project-specific preferences include:
@@ -8 +11 @@
  * [AppFiltering Application selection]: you can allow users to select which of your applications they will be sent work for.
 
-The PHP code that allows users to edit their project-specific preferences is in `html/project/project_specific_prefs.inc`. When you create your project, this is initialized to sample code. To create your own project-specific preferences, edit this file
+The PHP code related to project-specific preferences is in `html/project/project_specific_prefs.inc`.
+When you create your project, this is initialized to sample code.
+To create your own project-specific preferences, edit this file
 (and keep it under SVN or CVS somewhere).
 The functions you must supply are:
 
+ * `project_specific_prefs_default()`
  * `project_specific_prefs_edit()`
  * `project_specific_prefs_parse_form()`