On Thu, Jun 10, 2004 at 01:14:26PM +0100, Kate L Pugh wrote:
On Wed 09 Jun 2004, Mart?n Ferrari
1. To treat the templates entirely as user
configuration, nobody will
use them as bundled, because we all want to have our own look&feel.
I'm not happy about people using anything other than the templates in
the distro, since they still have some application logic in them. We
have had bugs in the templates; I'm sure there are still some lurking.
Using custom templates is very much done at your own risk.
But it is trivially obvious that people /do/ want to be able to edit
them willy-nilly, and so they should. We shouldn't be enforcing a
particular look and feel unnecessarily, so anything we can do to ease
maintainance of custom template hacks is a good thing. For example, more
splitting up of the logic in the templates; an install/upgrade system
that will detect changes made to the templates in a dpkg-like way that
will prompt you to decide whether you want to keep the locally-modified
version or use a new distributed file.
2. To separate
look&feel from strings and some logic inside the
templates. Look&feel would be config (css + structure), and the strings
could be managed in two ways: language templates, defining variables
(the templating system is *very* powerful); and using gettext (standard
way, but more hacky to implement here)
Locale::Maketext looks interesting:
It's certainly a step in the right direction but it only deals with
string replacement and it's not a complete solution to the above.