Michael Keck a écrit :
  

Okay,

I see the points. Then by default caching is disabled.
I can distribute the compiled templates, but cached templates makes no
sense,because theese are genereted by the installed environment. It means the
cached files includes servers, databases, language specific things etc.
Caching would be only a feature to improve perfomance.
    

We'll have to see what kind of performance we get without caching.
  

Compiled templates are mainly php files. Perhabs, the we don't need to
distribute the template sources, only the compiled version of them is required.
    

This is why I asked a question, in a previous message. Templates are 
done for who?

The developers?

Would they be beneficial also to anyone 
who wants to contribute/modify the code?
  

What is the real goal of going to templates?
  

• Separate php-code from html output
• Making layouting and theming (I call this skins) more flexible.
• User can download the source of a base skin and build there own:
  They don't need anything know about functional things in phpMyAdmin.
  
• If in user's environment, permission is set to write files and directories they can directly use their skin
• If a user want to share his skin, he can upload his skin-sources in theme tracker.
• Then we can check and compile and release it.
  

• Less security problems, cause only skins are changed, phpmyadmin core functions are excluded from this.
  Things wich are not supported, allowed or restricted are ignored by the template engine.
  
• Better bugfixing: we know directly where the bug is, in skin or in pma-functions

• ID's are changed,
• clases are changed
• new icons
• new features

For developers we can distribute a default template source.
For us we should perhabs store all template sources in an etxra trunk?
    

I don't have experience with templating systems to offer insight about 
this question.
  

Regards
Michael