[Mailman-Developers] Skinning Mailman (how to add a customer UI in five minutes or

[Dave Klingler]

> I've completely rewritten the user options page (more on this later,
> tomorrow is checkin day :), and have taken the opportunity to do
> exactly this.  I may have missed some, but the idea is that the colors
> are now overridable in mm_cfg.py.

Wonderful!
  
> Which makes me think more about having a better support for virtual
> domains by having something akin to a different mm_cfg.py per domain.

This would be very cool.  My favorite implementation of virtual domains
is Apache's, and it strikes me that adding the <virtualhost domain> 
directive might be an easy and intuitive way of accomplishing virtual domain 
directives now that you have overridable colors in mm_cfg.py.

Just a thought.  If you did key admin messages in mm_cfg.py you could put
them here this way.

Thanks for all the improvements!  Some day if I could consolidate all my
mailman virtual implementations, all in their separate chrooted environments,
back into one virtual mailman environment, I would die happy and will Barry 
my Star Trek hologram trading cards AND my wool Canadian Army cap.

Dave Klingler


> That's rumbling around in the back of my head.
> 
>     CVR> The other key one for me are some of the admin messages
>     CVR> (Mailman/Handlers/Hold.py). I've modified some of the
>     CVR> messages for various reasons, and it'd be nice if I could
>     CVR> simply override their definitions in the mm_cfg.py file
> 
> I'll have to think about this.  One hackish idea (untested) is to try
> to import Mailman.Hold from mm_cfg.py, and then set the class's
> __doc__ attribute with the message you want.  The fact that
> Mailman/Hold.py imports mm_cfg.py means you might have to play games
> with the importer to get this to work.  Not a great solution, but it
> might help localize your customizations for now.
> 
>     CVR> And the third place I've made custom changes are in some of
>     CVR> the list templates (most radically templates/listinfo.html)
>     CVR> -- but that's why they're template; you simply keep a copy
>     CVR> somewhere and watch out for additions to the updated copy...
> 
> Exactly, and the new template lookup scheme should be much more
> friendly to this approach.
> 
>     CVR> It took me about three days and a couple of exchanges with
>     CVR> the author of mod_layout to get it going the way I wanted
>     CVR> (the documentation is still being fleshed out), but it's a
>     CVR> nice improvement to the old way of doing things -- and since
>     CVR> I know others build custom skins around their installations,
>     CVR> I'd thought I'd pass this one along.
> 
> Yes, thanks!
> 
> -Barry
> 
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
>