| Commit | Date | |
|---|---|---|
|
[r6355]
by
osimons
warning-api branch: Moving `add_warning` to trac.web.chrome and the `chrome` template dictionary, and removing all traces of warnings in the request object (thereby breaking compatibility with any plugins). Updated add_warning to support `*args` and calling for message expansion. |
2007-12-18 01:54:41 | Tree |
|
[r6354]
by
osimons
warning-api branch: Changed all uses of `req.warning(msg)` to use `add_warning(req, msg)` instead. This reflects how similar functions in trac.web.chrome works. Currently the `add_warning()` is located in trac.web.api due to troublesome imports from `trac.versioncontrol.api` and trac.mimeview.api`. Resolve and move to trac.web.chrome? The old `req.warnings()` is not yet removed. Changes so far should therefore not break any behavior for existing plugins. |
2007-12-18 00:46:55 | Tree |
|
[r6353]
by
osimons
warning-api branch: Moved the location of the warnings in layout.html to display below all navigation items. |
2007-12-17 23:11:59 | Tree |
|
[r6352]
by
osimons
Branching off ctxtnav for moving warnings in layout.html and changing to add_warning() api. |
2007-12-17 22:32:30 | Tree |
| 2007-12-17 21:24:27 | Tree | |
| 2007-12-17 21:24:19 | Tree | |
| 2007-12-17 21:15:25 | Tree | |
| 2007-12-17 21:12:04 | Tree | |
| 2007-12-17 21:07:54 | Tree | |
|
[r6346]
by
jruigrok
Using MetaData() ought to be sufficient for our use case. Discussed with: zzzeek (aka Michael Bayer, SA author) |
2007-12-17 20:57:59 | Tree |