<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Marc,<br>
<br>
Am 12.03.2010 12:41, schrieb Marc Delisle:
<blockquote cite="mid:4B9A2872.6070204@infomarc.info" type="cite">
<pre wrap="">Michael Keck a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
We'll have to see what kind of performance we get without caching.
</pre>
</blockquote>
On things, wich are not changed every time, caching increase performance.<br>
Please take a look at: <a class="moz-txt-link-freetext" href="http://www.ohrensessel-filme.de">http://www.ohrensessel-filme.de</a>. This page loads
10 times faster with cache.<br>
Templates are only written, if any thing has been changed, means
html-files are written and then included.<br>
Otherwise, the cache file is used, it means php includes a html-file.<br>
<blockquote cite="mid:4B9A2872.6070204@infomarc.info" type="cite">
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
This is why I asked a question, in a previous message. Templates are
done for who?</pre>
</blockquote>
The compiled for all, the sources for developers and interested peoples
only.<br>
A compiled version of a template is like a procedural php-file with
some functions and is written by the template-engine from the sources.<br>
<blockquote cite="mid:4B9A2872.6070204@infomarc.info" type="cite">
<pre wrap="">The developers?</pre>
</blockquote>
Yes.<br>
<blockquote cite="mid:4B9A2872.6070204@infomarc.info" type="cite">
<pre wrap="">Would they be beneficial also to anyone
who wants to contribute/modify the code?
</pre>
</blockquote>
Yes, they only need to modify the skin (sources), not the functional of
phpMyAdmin. That's the pro.<br>
<blockquote cite="mid:4B9A2872.6070204@infomarc.info" type="cite">
<pre wrap="">What is the real goal of going to templates?
</pre>
</blockquote>
<ul>
<li>Separate php-code from html output</li>
<li>Making layouting and theming (I call this skins) more flexible.</li>
<li>User can download the source of a base skin and build there own:<br>
They don't need anything know about functional things in phpMyAdmin.<br>
</li>
<ul>
<li>If in user's environment, permission is set to write files and
directories they can directly use their skin</li>
<li>If a user want to share his skin, he can upload his
skin-sources in theme tracker.</li>
<li>Then we can check and compile and release it.<br>
</li>
</ul>
</ul>
<ul>
<li>Less security problems, cause only skins are changed, phpmyadmin
core functions are excluded from this.<br>
Things wich are not supported, allowed or restricted are ignored by the
template engine.<br>
</li>
<li>Better bugfixing: we know directly where the bug is, in skin or
in pma-functions</li>
</ul>
I get this idea of template-based phpMyAdmin, cause I have some
problems to fix the current themes (which are at the moment done only
with cascading stylesheet) of changed html-code in php-functions:<br>
<ul>
<li>ID's are changed,</li>
<li>clases are changed</li>
<li>new icons</li>
<li>new features</li>
</ul>
This is not flexible enough (see i.e. artic-ocean, I've to write a
terribble fix to make navigationbar fixed).<br>
<br>
<blockquote cite="mid:4B9A2872.6070204@infomarc.info" type="cite">
<blockquote type="cite">
<pre wrap="">For developers we can distribute a default template source.
For us we should perhabs store all template sources in an etxra trunk?
</pre>
</blockquote>
<pre wrap="">
I don't have experience with templating systems to offer insight about
this question.
</pre>
</blockquote>
I mean, we have in svn/git a '/themes' folder? Perhabs I would add new
one: '/skins' with the subdirs '/skins/sources/' and '/skins/compiled/'.<br>
<blockquote cite="mid:4B9A2872.6070204@infomarc.info" type="cite">
<blockquote type="cite">
<pre wrap="">
Regards
Michael
</pre>
</blockquote>
</blockquote>
</body>
</html>