Thursday, September 19, 2002, 7:58:53 PM, you wrote:
> On 19 Sep 2002 at 13:36, Luis Augusto Coutinho Sauerbronn wrote:
>> Is there a template to create new pages in jawmail??? I need to include
>> some configurations for the anti-virus software in my server to the
>> users, and I wanted to maintain the Themes and stuff...
> I ran into the issue of creating a new template. I come from Perl and
> Template::Toolkit and I thought that there would be a
> but instead I found *hooks* into the views in many different places. I
> never did appreciate it which may be because I did not spend enough
> time banging my head or because the system I use is so much simpler or
> any number of other reasons. The Jaw template system seems to be like
> most of the PHP systems I've seen and not like what I do (where ALL
> templates are under one common path and so it's very easy to change the
> template). One drawback to my system is that you really have to create
> new templates (and not just change a style sheet).
Well, we have seperated templates (PHP/HTML code) and themes (images &
CSS stylesheets)... Is that good? :)
> I'm currently using the smarty.php.net template system and it allows me
> to emulate what I do in Perl. Here is an example of an application
> which uses a template system I'm accustomed to:
Well, I was thinking about using Smarty, but I always found something
- do we really need it? Plain PHP files are simply the fastest
templating system that there is.
- Smarty is most probably additional 50kb (dunno) of PHP code to
parse for every page request ... not really efficient, the current
framework is quite big anyhow.
- IIRC Smarty has to be seperately and has to have a configured
temporary directory where the pre-compiled template files will be
kept ... More installation fun?
But since I never really used it... I don't know :-)
> Anyhow, I just forced the template path to my set of templates (copied
> the existing then renamed my folder) and I did this in the X number of
> places that this must be done. And I think I was wrong in doing this. I
> think I either should have told the customer that they could only
> change that which was changeable, or I should have kept coming back to
> the list to understand how I could create a *completely new set of
> templates without doing what I did .. I hacked some scripts to force
> the use of my templates as I never saw where to do that dynamically*.
> I got what I wanted working ... but I would not do this again as I've
> just ruined any upgrade. I may also have jumped to a solution that was
> not necessary if I had fully understood the app. I'm used to creating
> my own apps and not working within another framework.
Well, you really missed it :-) conf/prefs.php ... Yet I really don't
know if it works.
I was thinking: Maybe we should be able to define pairs of templates
and themes: like, template X can be used with theme A, so display it
as a preference to user "Theme X A" ... Or should we just have two
pulldown menus with theme and a seperated template?
Anyhow, a nice idea for RC3. It's just that I'm rather busy right
Rudi Benkovič rudi@...
Just Another Web mail http://www.jawmail.org/