On 5/6/07 5:00 AM, "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote:
> A.M. Kuchling writes:
>
>> I don't think this choice would work very well; requiring a rebuild
>> would break backward compatibility. I don't know if that breakage
>> would be OK for Mailman 2.2 or 3, but it's surely off-limit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 3, 2007, at 9:03 PM, A.M. Kuchling wrote:
> It presents one big compatibility issue that will probably need to be
> fixed. The patch removes the colour settings (WEB_HEADER_COLOR,
> WEB_ERROR_COLOR, WEB_ADMINITEM_COLOR, etc.) and replaces the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 5, 2007, at 11:24 AM, Terri Oda wrote:
> Have the CSS generated by a CGI (which could then use these variables
> if they're available).
> - extra processing for each web request
> + could lay groundwork to make it possible to change settings on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 6, 2007, at 5:00 AM, Stephen J. Turnbull wrote:
> Going to CSS at all is presumably off-limits for a 2.1 release. I
> think it would be a very bad idea to constrain the design to be
> backwards compatible to a non-CSS solution, but not doing s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2007, at 9:16 AM, Aaron Crosman wrote:
> In general I agree with Ethan and Stephen, designers want CSS to be
> in its
> own file (for good reasons) and don't want to have to work in
> python or XML
> files if they don't have to. Since w
On Tue, May 08, 2007 at 11:06:14AM -0400, Barry Warsaw wrote:
> I'm not so sure. I feel very uncomfortable making /any/ non-bug-fix
> changes to 2.1, perhaps even limiting them to critical bug fixes that
> address security or reliability issues. Better (IMO) to fairly
> quickly get a conser
Barry Warsaw writes:
> Would you make $list.css editable by the list admin, a la
> listinfo.html? Does doing so open any additional security
> vulnerabilities?
Yes to editable, I don't know to security vulnerabilities. View the
CSS Zen Garden (better yet, get the book), and know fear. W
-- Original Message ---
From: "A.M. Kuchling" <[EMAIL PROTECTED]>
> I have an idea for a proposed conservative approach for 2.1:
>
> * Add two mm_cfg settings: CSS_FILES and JS_FILES, while are lists
> (alternatively, whitespace-separated strings):
>
> CSS_FILES = ['/c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2007, at 3:06 PM, [EMAIL PROTECTED] wrote:
> Revision: 8210
> http://svn.sourceforge.net/mailman/?rev=8210&view=rev
> Author: akuchling
> Date: 2007-05-08 12:06:28 -0700 (Tue, 08 May 2007)
>
> Log Message:
> ---
> Add
On 7-May-07, at 11:37 AM, Barry Warsaw wrote:
> Here is my current thinking, and I'd like to know what you all think
> about this. Andrew created the mondernize_21_webui branch and
> applied the xhtml and css patches to it. We could conceivably keep
> these changes very conservative, i.e. just u/
> > CSS_FILES = ['/css/mailman.css', '/css/custom.css']
> > JS_FILES = ['/js/switcher.js', '/js/foo.js']
I like it too. And we can do marvels with jQuery.
-- Fil
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2007, at 3:42 PM, Terri Oda wrote:
> On 7-May-07, at 11:37 AM, Barry Warsaw wrote:
>> Here is my current thinking, and I'd like to know what you all think
>> about this. Andrew created the mondernize_21_webui branch and
>> applied the xhtml
On Tue, May 08, 2007 at 10:43:36AM -0400, Barry Warsaw wrote:
> Andrew, when you created the modernize_21_webui branch, did you set
> it up with svnmerge? I think it would be a good idea to
> systematically merge 2.1 branch changes into the modernize branch.
No svnmerge initialization, but I
13 matches
Mail list logo
