[Mailman-Users] Index Listing of mail lists
Reply-To set to Mailman-Users.
Tom Kavanaugh writes:
If there is a way to setup a A-Z index hortizontally above the List name - Description, it would be great.
Any code hacks for this feature?
This feature is already in the Member List page. Since Mailman is free software, reusing that code doesn't even count as stealing!<wink>
Mailman Developers: Is the web code set up so that so that admins could fairly easily assemble these UI widgets into a page that suits their usage? Or would that be a major refactoring? Sorta like reimplementing Plone, I guess, but we really don't want to put "import plone" at the top!
What I was thinking is that there could be a page generator pipeline, similar to the list processor. Of course the objects we want to generate pages from (member lists, moderation queues, etc) would have to grow appropriate interfaces -- sounds like work! but it would be way cool.
At 10:49 AM +0900 10/11/06, stephen@xemacs.org wrote:
Mailman Developers: Is the web code set up so that so that admins could fairly easily assemble these UI widgets into a page that suits their usage?
Nope. It's all hard-coded.
Or would that be a major refactoring? Sorta likereimplementing Plone, I guess, but we really don't want to put "import plone" at the top!
Something like that, or maybe re-implementing Zope.
What I was thinking is that there could be a page generator pipeline, similar to the list processor. Of course the objects we want to generate pages from (member lists, moderation queues, etc) would have to grow appropriate interfaces -- sounds like work! but it would be way cool.
Yeah, way cool.
We can't wait to see the code you're going to contribute to do this. ;)
Mailman-Users trimmed.
Brad Knowles writes:
At 10:49 AM +0900 10/11/06, stephen@xemacs.org wrote:
Mailman Developers: Is the web code set up so that so that admins could fairly easily assemble these UI widgets into a page that suits their usage?
Nope. It's all hard-coded.
Well, at least the hard code is already done! I love it when I get to do the easy part!<wink>
We can't wait to see the code you're going to contribute to do this. ;)
I wouldn't spend effort on waiting if I were you; I'm thinking in terms of Mailman 3.
But if you're in that big of a hurry, you can check out my xre.py from cvs.xemacs.org, the XEmacs/xemacs-builds/stephen module. It was somewhat inspired by this idea. The web announcement part is a little bit pipelined, and the overall structure is a pipeline. But it's a personal tool, so it's **real** crufty.
It's not obvious to me that it would be all that hard to do; what I was hoping for was for some people to chip in with "that's probably going to work, you'll just have to keep finding the stuff that needs to be in the interface, which will be tedious but do-able", or inversely, "you're hosed, because we really can't get away with building these certain pages in a pipeline like that."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Oct 11, 2006, at 2:40 AM, stephen@xemacs.org wrote:
Brad Knowles writes:
At 10:49 AM +0900 10/11/06, stephen@xemacs.org wrote:
Mailman Developers: Is the web code set up so that so that admins could fairly easily assemble these UI widgets into a page that
suits their usage?Nope. It's all hard-coded.
Well, at least the hard code is already done! I love it when I get to do the easy part!<wink>
We can't wait to see the code you're going to contribute to do
this. ;)I wouldn't spend effort on waiting if I were you; I'm thinking in terms of Mailman 3.
I'm definitely interested in improving things here, but I'd like to
try to avoid inventing technology here. There are so many Python web
frameworks and templating systems out there, that there's /got/ to be
at least one that we can adopt. And I'd like to do so in Mailman 2.2
if possible.
BTW, I've been working with Tokio's recent HTTPRunner and wsgiref
interface. I'm making progress, but I'm realizing that there are
quite a few things that have to be fixed to make that a viable
deployment model. One thing I'm trying to eradicate is absolute urls
for internal Mailman links. I've got the listinfo and admin pages
fixed (mostly), but I probably won't check it in until I have most of
the u/i working again. ;)
- -Barry
Barry Warsaw writes:
I'm definitely interested in improving things here, but I'd like to
try to avoid inventing technology here. There are so many Python web
frameworks and templating systems out there, that there's /got/ to be
at least one that we can adopt.
If you want to throw some suggestions my way, I'll take a look.
I wouldn't be surprised if what's available is universally quite poorly adapted to what I'd like to do with it, though.
And I'd like to do so in Mailman 2.2 if possible.
I don't think there's much chance I can help with that, unless it's gonna be a while. :-(
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Oct 11, 2006, at 12:20 PM, stephen@xemacs.org
stephen@xemacs.org wrote:
Barry Warsaw writes:
I'm definitely interested in improving things here, but I'd like to try to avoid inventing technology here. There are so many Python web frameworks and templating systems out there, that there's /got/ to be at least one that we can adopt.
If you want to throw some suggestions my way, I'll take a look.
I wouldn't be surprised if what's available is universally quite poorly adapted to what I'd like to do with it, though.
I know that myself, emf, and others have made several attempts at
adapting various existing templating systems to Mailman, but I don't
think any of us have had rousing success (I certainly haven't). The
ones I know about are ZPT (various implementations exist), Cheetah,
Kid, PTL. I'm sure there are others.
Google gives me this relatively recent comparison:
http://www.simplistix.co.uk/presentations/templating_06/ templating_06.pdf
Here Chris Withers gives a pretty good overview of what's available
and introduces a new package he calls Twiddler (I'm not endorsing any
toolkit).
IWBNI whatever we choose supports i18n without forcing translators to
translate entire templates. IWBNI the templating system were modular
and separate from the web publisher. IWBNI the templates can be
edited by mere mortals.
And I'd like to do so in Mailman 2.2 if possible.
I don't think there's much chance I can help with that, unless it's gonna be a while. :-(
Who knows? :)
- -Barry
stephen@xemacs.org wrote:
We can't wait to see the code you're going to contribute to do this. ;)
I wouldn't spend effort on waiting if I were you; I'm thinking in terms of Mailman 3.
I'm trying to modularize the web code now; I'm using something vaguely like a pipeline. At the very least, all of the code that applies to sequences should work for lists of users/lists/messages.
If you want to play along, check out the soc2006-webui branch :)
~ethan fremen
participants (4)
-
Barry Warsaw -
Brad Knowles -
emf -
stephen＠xemacs.org