10 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] [PATCH] Simpler chang...
FromSent OnAttachments
Marcin SemeniukMay 23, 2006 1:02 am.patch
Brian CandlerMay 24, 2006 12:44 am 
Mark ConstableMay 24, 2006 3:14 am 
Pawel TeczaMay 24, 2006 7:29 am 
Brian CandlerMay 24, 2006 8:21 am 
Pawel TeczaMay 29, 2006 3:48 am 
Sam VarshavchikMay 29, 2006 6:19 am 
Brian CandlerMay 29, 2006 1:42 pm 
Pawel TeczaMay 29, 2006 11:15 pm 
Marcin SemeniukJun 13, 2006 1:28 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [sqwebmail] [PATCH] Simpler changing of textarea for singature editingActions...
From:Brian Candler (B.Ca@pobox.com)
Date:May 24, 2006 12:44:51 am
List:net.sourceforge.lists.courier-sqwebmail

On Tue, May 23, 2006 at 10:02:42AM +0200, Marcin Semeniuk wrote:

BTW, don't you think that using styles in *.c files is better than using
hardcoded attributes (for example font names, colors, etc.) ?

I remember this being discussed a while ago. IIRC, at the time Sam wanted to do it that way for compatibility with old browsers which didn't support CSS, or supported it badly.

That was a couple of years ago I think, and these 'old' browsers can be reclassified as 'ancient'. I think it would now be good to completely separate the style from the content, a la www.csszengarden.com. This would allow virtual domain owners to perform almost all the customisation they could want just by adding a cascaded stylesheet, with very low risk that things would break when sqwebmail was upgraded to a new version.

The main issue would be with the rounded corner boxes, but personally I wouldn't mind if they were lost.

If this were to be reworked, there would also be an opportunity to separate out HTML templates from language strings which I'd really like to see done. This would give three parts:

(1) HTML templates, containing tags for strings (2) Language files, mapping tags to strings in that language (3) Style sheets [referred to from the HTML templates]

Doing it this way would allow you to replace or update templates without losing the translations, and vice versa. At worst, if a new HTML template contained a message tag which did not exist in an old translation file, then that particular message would be displayed in English.

It also gives an opportunity to combine the 'login.html', 'invalid.html' and 'expired.html' templates into a single page, where the C code could replace a metatag with one of three tags depending on the situation.

Regards,

Brian.