[Phpmyadmin-devel] Transition to template-based framework

Michal Čihař michal at cihar.com
Fri Mar 12 13:20:57 CET 2010


Dne Fri, 12 Mar 2010 12:33:09 +0100
Michael Keck <sfnet at michaelkeck.de> napsal(a):

> 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.

Okay, then this needs to be disabled by default (and can be for example
enabled by distros).

> 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.
> For developers we can distribute a default template source.
> For us we should perhabs store all template sources in an etxra trunk?

It should be same as is with current themes - basic set (or maybe
just default one) will be in main repository and contributed ones will
be stored in other.

When doing release, the compiled ones will be created and stored in
release file (same needs to be done with Gettext).

	Michal Čihař | http://cihar.com | http://blog.cihar.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20100312/6b4bfcba/attachment.sig>

More information about the Developers mailing list