Roundup Tracker - Issues

Issue 2550930

classification
Title: add support for local_replace to classic template
Type: Severity: normal
Components: Web interface Versions: devel
process
Status: new Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: ThomasAH, ber
Priority: Keywords: patch

Created on 2016-10-26 11:17 by ber, last changed 2018-12-11 14:30 by ThomasAH.

Files
File name Uploaded Description Edit Remove
local_replace_for_classic.patch ber, 2016-10-26 11:17
local_replace.py ber, 2016-10-26 11:19 more advanced example local_replace.py as mailed to users list in Sept 2016
Messages
msg5916 Author: [hidden] (ber) Date: 2016-10-26 11:17
Because the classic template is most complete,
I suggest to add support for the local_replace.py
extension to it.

Here is a patch doing so.
(And I am also adding an example for a more advanced local_replace.py)
msg6306 Author: [hidden] (ThomasAH) Date: 2018-12-11 14:17
The patches add functionality to the extensions directory and
additionally makes this extension required by using it in the html
templates.

If it is required by the classic template, I'd rather see it integrated
into the core.

Additionally the configuration for the extension will happen in the
extension itself. Having a configuration mechanism similar to 
schema.py or interfaces.py (in the tracker root directory, in the case
of interfaces.py even an optional file) might be preferable.
msg6307 Author: [hidden] (ThomasAH) Date: 2018-12-11 14:30
One additional thought: Adding it as a default extension might be OK, if
the extension code and the configuration code can be separated and the
extension provides a sane default when running without further
configuration.
History
Date User Action Args
2018-12-11 14:30:50ThomasAHsetmessages: + msg6307
2018-12-11 14:17:41ThomasAHsetnosy: + ThomasAH
messages: + msg6306
2016-10-26 11:19:40bersetfiles: + local_replace.py
2016-10-26 11:18:15bersetcomponents: + Web interface
2016-10-26 11:17:58bersetversions: + devel
2016-10-26 11:17:54bercreate