On May 15, 2011, at 06:15 PM, Benedict Stein wrote:

Did i understand something incorrectly or is the Django UI only a config website ?

That is currently the case, yes.

Why don't we have all UI parts within the Django project (which I'll support during gsoc ;-))

It's a good question. There are two things that will influence design decisions for Pipermail's web ui. First, I would eventually like to split Pipermail into a separate sub-package of Mailman, so that it could be used independently, or easily thrown out if someone wants a different archiver. It would also allow Pipermail to advance on a different schedule than the core engine.

Second, Pipermail has always generated static HTML files, so the "web ui" such as it is, is basically just Apache vending those static HTML files. Now, I've long thought that it would be better, and technically feasible, to generate the archive HTML on the fly, when a message is requested (with appropriate caching for performance). Doing dynamic generation of those pages would allow for some interesting ideas, such as changing content filtering more easily (e.g. address obfuscation, hyperlinking special text like bug numbers, etc.). But that's also a major redesign of the Pipermail architecture.

-Barry

On May 16, 2011, at 10:30 AM, Bill Janssen wrote:

Since UpLib can also process photos, Web pages, Powerpoint decks, Word, PDF, etc., it can display attachments next to the mail message as thumbnails with links to the attachment document. It's a tad tricky to display those documents -- for years I've been using a Java applet, but that's clearly not the wave of the tablet future, so I've been playing with the gnubook code as an alternative.

I think it would be very cool to build an Uplib adapter for the IArchiver interface in MM3. I can imagine it wouldn't be too difficult, and the nice thing is that in MM3, you can have any number of archivers available or enabled.

-Barry

On Monday 16 May 2011 08:06 PM, Barry Warsaw wrote:

The Pipermail archiver in MM3 currently integrates with Apache the same way that Mailman 2.1 did, so it's best to follow those directions for now. This may eventually change, and the instructions are largely untested for MM3, but that's the best way to try to make it work for now. The apache configuration worked for me. Actually, there was one more problem. Pipermail was not generating static html files in the correct way. Each of the static html files just contained the path to the required template files.

In function quick_maketext(), in file Archiver/HyperArch.py: template, filepath = find(templatefile, mailing_list=mlist, language=lang.code)

Here, find() just returns the path of template file to the 'template' variable whereas, it should return the contents of the template file.

In version 2.1, Utils.findtext() works fine. template, filepath = Utils.findtext(templatefile, lang=lang, raw=True, mlist=mlist)

So, after modifying find(), I can see Pipermail archives through a web interface. Now, I'll start looking at Yian's code on UI.

Regards, Dushyant