Mercurial > p > roundup > code
comparison doc/customizing.txt @ 909:ef9c759c243e
Fix to hasPermission, thanks Stefan Seefeld.
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Mon, 29 Jul 2002 21:53:29 +0000 |
| parents | 38a74d1351c5 |
| children | 299f4890427d |
comparison
equal
deleted
inserted
replaced
| 908:a8d80ffe37cc | 909:ef9c759c243e |
|---|---|
| 1 =================== | 1 =================== |
| 2 Customising Roundup | 2 Customising Roundup |
| 3 =================== | 3 =================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.12 $ | 5 :Version: $Revision: 1.13 $ |
| 6 | 6 |
| 7 .. contents:: | 7 .. contents:: |
| 8 | 8 |
| 9 | 9 |
| 10 What You Can Do | 10 What You Can Do |
| 11 --------------- | 11 --------------- |
| 12 | 12 |
| 13 Customisation of Roundup can take one of three forms: | 13 Customisation of Roundup can take one of four forms: |
| 14 | 14 |
| 15 1. `instance configuration`_ file changes | 15 1. `instance configuration`_ file changes |
| 16 2. `instance schema`_ changes | 16 2. database, or `instance schema`_ changes |
| 17 3. "definition" class `database content`_ changes | 17 3. "definition" class `database content`_ changes |
| 18 4. behavioural changes, through detectors_ | |
| 18 | 19 |
| 19 The third case is special because it takes two distinctly different forms | 20 The third case is special because it takes two distinctly different forms |
| 20 depending upon whether the instance has been initialised or not. The other two | 21 depending upon whether the instance has been initialised or not. The other two |
| 21 may be done at any time, before or after instance initialisation. Yes, this | 22 may be done at any time, before or after instance initialisation. Yes, this |
| 22 includes adding or removing properties from classes. | 23 includes adding or removing properties from classes. |
| 513 "definitional" classes like "priority" and "status". | 514 "definitional" classes like "priority" and "status". |
| 514 | 515 |
| 515 | 516 |
| 516 Detectors - adding behaviour to your tracker | 517 Detectors - adding behaviour to your tracker |
| 517 -------------------------------------------- | 518 -------------------------------------------- |
| 518 .. _`detectors`: | 519 .. _detectors: |
| 519 | 520 |
| 520 The detectors in your instance fire before (*auditors*) and after (*reactors*) | 521 The detectors in your instance fire before (*auditors*) and after (*reactors*) |
| 521 changes to the contents of your database. They are Python modules that sit in | 522 changes to the contents of your database. They are Python modules that sit in |
| 522 your instance's ``detectors`` directory. You will have some installed by | 523 your instance's ``detectors`` directory. You will have some installed by |
| 523 default - have a look. You can write new detectors or modify the existing | 524 default - have a look. You can write new detectors or modify the existing |
| 535 ``unread`` on new nodes if the status isn't explicitly defined. | 536 ``unread`` on new nodes if the status isn't explicitly defined. |
| 536 | 537 |
| 537 See the detectors section in the `design document`__ for details of the | 538 See the detectors section in the `design document`__ for details of the |
| 538 interface for detectors. | 539 interface for detectors. |
| 539 | 540 |
| 540 __ spec.html | 541 __ design.html |
| 541 | 542 |
| 542 Sample additional detectors that have been found useful will appear in the | 543 Sample additional detectors that have been found useful will appear in the |
| 543 ``detectors`` directory of the Roundup distribution: | 544 ``detectors`` directory of the Roundup distribution: |
| 544 | 545 |
| 545 **newissuecopy.py** | 546 **newissuecopy.py** |