Hi, As per previous discussions, it would be nice to support style hierarchies such that the list owners can compose them and defer settings to values higher up, that would allow the core to define some basic styles and then list owners can just tweak a few settings to modify one of those base styles but in this case should the changes in base-styles be propagated to all the styles that inherit it or not. If we allow the propagation of changes to inheriting styles, some list owners might be uncomfortable with this feature as then if any of the base-style changes their inheriting styles will change without any kind of prior notification.

...

In the back-end, we will be using tables for storing style attributes and permission level(read only or editable). This table will basically contain all the "stylable" attributes with "default or predefined" values as contained in the mailing list table and one extra column for permissions.

I think the "Permissions Systems" would have nothing to do with the core. It would be related to Postorius. We will have to create a style model separately in Postorius which would store the style name and the user who created it. Then only the user who has created the style would be granted the permission to edit it.

From UI point of view, there is one more feature that comes to my mind: When the users are presented with an interface to customize the style, we could provide them with two views, one 'simple' and another 'advanced'. The 'simple' one would show only the *frequently* (or most commonly) changed attributes while the 'advanced' one will show all the attributes. This will help them in customizing the styles. I would like to hear some of your comments on it as well.

Thanks, Harshit Bansal.

On 2/11/16, Abhilash Raj <raj.abhilash1@gmail.com> wrote:

On 02/10/2016 10:03 AM, Harshit Bansal wrote:

...

Hi Abhilash, In our previous discussion you mentioned that :

...

Permissions should also consider if the user wants to make his new style public or keep it private. And should public styles be editable by anyone or just read-only?

I am unable to think of a use case in which it will be useful to have private styles.. Can you please suggest a suitable use case?

Well, i agree there is nothing "private" in list styles. We could just make all styles read-only for everyone. But if someone wants to use the style created by other users, it would be better idea to first make them copy the style so that the behavior or their list doesn't change when the owner changes the style.

Barry: If you have some time, I would like to hear some of your thoughts on this thread? I believe you have some ideas of your own on how this is supposed to work.

...

Thanks, Harshit Bansal.

-- thanks, Abhilash Raj