Wishlist: own output templates

[GoogleCodeExporter]

A future version should have a more dynamic management of output templates, 
allowing users to add their own templates (which might be submitted to a 
central repository later), or modify already existing ones.
In particular for the self-extracting Windows version, this currently isn't 
possible. Also central changes may require admin permissions (Linux), and would 
get lost while upgrading.

Idea:
- Split monolithic templates.py into a sub-directory (similar to fun-factor 
stuff), and replace templates.py by code that simply reads and combines 
individual formats into a single hash.
- Add a folder "templates" to the user's individual config tree (next to 
config.yaml and cookies.yaml), and include that (after the system-wide ones).

Support this idea by "star"ring the issue. Feedback via e-mail or Twitter 
welcome.

Original issue reported on code.google.com by Steve8x8 on 7 Jun 2013 at 10:00

[GoogleCodeExporter]

After a series of commits, split template support is now in branch. This 
finally allows to have tailored templates which don't get overwritten with each 
and every upgrade.
This feature is on the milestone list for 3.18.0 - please test it as thoroughly 
as possible.

Original comment by Steve8x8 on 27 Jun 2013 at 1:00

• Changed state: Started

[GoogleCodeExporter]

Merged into trunk (r1417)

Original comment by Steve8x8 on 24 Aug 2013 at 12:56

• Changed state: FixAvail

[GoogleCodeExporter]

Implemented in 3.17.11 which is meant to be the first pre-release of 3.18.0.
Put your own *.tm files in templates/ below $GEO_DIR (the folder resides just 
side by side with cookies.yaml)

Original comment by Steve8x8 on 12 Sep 2013 at 11:33

• Changed state: Fixed