Prakhar Joshi
DA-IICT,Gandhinagar
On Sat, Mar 21, 2015 at 9:10 PM, Stephen J. Turnbull
wrote:
> I think we're pretty much in agreement on most things. Please update
> your proposal on melange to reflect this discussion. (The quoting has
> gotten too fragmented to be very useful in understandin
I think we're pretty much in agreement on most things. Please update
your proposal on melange to reflect this discussion. (The quoting has
gotten too fragmented to be very useful in understanding what progress
has been made.)
___
Mailman-Developers mai
Prakhar Joshi
DA-IICT,Gandhinagar
On Sat, Mar 21, 2015 at 4:53 PM, Stephen J. Turnbull
wrote:
> prakhar joshi writes:
>
> > So you want to store only changed attributes under a specific list
> > style in the table ? Isn't that make the table dynamic in width as
> > sometimes only one attribut
prakhar joshi writes:
> So you want to store only changed attributes under a specific list
> style in the table ? Isn't that make the table dynamic in width as
> sometimes only one attribute is stored and sometimes 3-4 attributes
> are stored ?
That's a feature of object-relational managers (
Prakhar Joshi
DA-IICT,Gandhinagar
On Sat, Mar 21, 2015 at 9:03 AM, Stephen J. Turnbull
wrote:
> Abhilash Raj writes:
>
> > > Admin can change there values.
> >
> > You meant 'their' here and not 'there'.
>
> (-: Lighten up on the spelling stuff. *I* make that typo regularly
> (I think I most
Abhilash Raj writes:
> > Admin can change there values.
>
> You meant 'their' here and not 'there'.
(-: Lighten up on the spelling stuff. *I* make that typo regularly
(I think I mostly manage to correct it before posting, I hope :-).
You're right about reviewing the language, though. I had
On Mar 19, 2015, at 03:31 PM, Stephen J. Turnbull wrote:
>Also, I suspect it would be useful to allow very incomplete templates so that
>you could apply template A to get the basic character, then apply template B
>(which is very incomplete and only changes two attributes) to get the effect
>you w
hi Abhilash,
Thanks for all these corrections.
Prakhar Joshi
DA-IICT,Gandhinagar
On Fri, Mar 20, 2015 at 7:03 PM, Abhilash Raj
wrote:
> Hi Prakhar,
>
> I see that you mentioned below the details of our conversation, but the
> language looks confusing to me. Please look out for simple mistakes
Hi Prakhar,
I see that you mentioned below the details of our conversation, but the
language looks confusing to me. Please look out for simple mistakes in
your English before sending the mail, not just here but anywhere.
On Friday 20 March 2015 12:37 PM, prakhar joshi wrote:
> hi,
> For the
hi,
For the storage of list we will have table for list styles and when
the admin creates a new list he/she will edit some attributes of particular
list. By attribute I mean the options under each mailing list style like
announce list have "allow list post". Admin can change there values. The
prakhar joshi writes:
> what if we create separate tables for each class in the
> mailman/src/mailman/styles/base.py and store the name and their attributes
> in it with user_name with it.
Who are these "users" (subscribers? admins?) and why do you want to
associate styles with users? Please
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 g
what if we create separate tables for each class in the
mailman/src/mailman/styles/base.py and store the name and their attributes
in it with user_name with it. I think the attributes for the classes
defined already will be fixed? So now if we feel the requirement of
including new things to style (
hi,
so we should have templates already created in a folder with default
values of the attributes in it. the templates will be of "BASIC OPERATION",
"BOUNCES" etc. and under each of the template we will gonna have
attributes for it and then we can apply these templates on the list and
even us
prakhar joshi writes:
> I am thinking of storing the styles in the database by creating a
> table for the styles in the db
Mailman's databases are not relational dbs, they're object-oriented.
Underneath the objects are stored in relational dbs and managed by an
ORM (SQLAlchemy), of course,
hi,
I am thinking of storing the styles in the database by creating a
table for the styles in the db and this table will contain all the
attributes of a style and these entries can be null too. So a table which
will contain a style name with all its attributes. Now as we have table for
mailing
16 matches
Mail list logo
