Changes between Version 3 and Version 4 of ProjectSpecificPrefs


Ignore:
Timestamp:
Dec 24, 2007, 1:23:26 PM (17 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectSpecificPrefs

    v3 v4  
    11= Project-specific preferences =
    22
    3 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].
     3You can provide users with a set of project-specific preferences, controlled via a web interface.
     4These preferences are stored in XML, in a field of the user table.
     5You determine the structure of this XML, and what it's used for.
     6On the client, the XML is passed to your application in the [BasicApi#Communicatingwiththecoreclient APP_INIT_DATA structure].
    47
    58Examples of project-specific preferences include:
     
    811 * [AppFiltering Application selection]: you can allow users to select which of your applications they will be sent work for.
    912
    10 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
     13The PHP code related to project-specific preferences is in `html/project/project_specific_prefs.inc`.
     14When you create your project, this is initialized to sample code.
     15To create your own project-specific preferences, edit this file
    1116(and keep it under SVN or CVS somewhere).
    1217The functions you must supply are:
    1318
     19 * `project_specific_prefs_default()`
    1420 * `project_specific_prefs_edit()`
    1521 * `project_specific_prefs_parse_form()`