prakhar joshi writes: > One thing how these templates will be stored for the user is still a doubt > for me ? Can you please help me with that ?
Not until late next week. I haven't thought about the problem at all. Anyway, designing the implementation is really your job. Here's how I would go about thinking about it. First, let's try to reuse existing structure in Mailman. What's most similar to a template for a list? Probably a list. So consider using the same structure. Next question is whether a template should be a list with inputs to things like list name disabled, or whether the list record/object should be refactored into a template copy plus list-specific components like name and membership list. Next problem for you is to find where the list object is defined, and find out what all is in there. Regards, _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://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: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
