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
signature.asc
Description: PGP signature
_______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9