Mercurial > p > roundup > code
comparison plugins/README.md @ 4943:7920d700e580 routing
Add support for extensions to provide custom pages to Roundup
and update CHANGES.txt
1. Added registerHandler() extension point to instance.Tracker
to register URL handlers for specific routes
2. Added processing of extension routes to client.cgi
3. Added example plugins/extensions/custompage.py
| author | anatoly techtonik <techtonik@gmail.com> |
|---|---|
| date | Tue, 25 Nov 2014 17:29:38 +0300 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 4942:ba1ec6d13e76 | 4943:7920d700e580 |
|---|---|
| 1 | |
| 2 This directory contains useful `detectors` and `extensions`, which | |
| 3 are both Roundup `plugins`. | |
| 4 | |
| 5 | |
| 6 ### Plugins or Extensions | |
| 7 | |
| 8 Historically, Roundup plugins were called `extensions`, then at some | |
| 9 point appeared specialized class of extensions called `detectors`. | |
| 10 | |
| 11 `extensions` extend tracker instance adding new utils, actions and | |
| 12 (since 1.6.0) URL handlers for web part. `detectors` allow to change | |
| 13 the behavior of data model by adding reactors to data change events. | |
| 14 | |
| 15 The API difference between `detector` and `extension` is that first | |
| 16 gets `db` argument for its `init()` function and the second gets | |
| 17 `tracker` instance. Both extend Roundup if placed into corresponding | |
| 18 directories of tracker home, so they both can be called in a more | |
| 19 familiar manner as `plugins`. |