On 13-03-05 8:28 PM, Stephen J. Turnbull wrote:
OTOH, would it really be that burdensome to keep styles in the
database and allow styles to be updated with appropriate effects on
the lists? A style *change* that could be applied domain-wide (and
DRY-ly!) without affecting other domains on that
Barry Warsaw writes:
> Note that styles are only applied when a list is created, so it is
> better to think of them as the default set of attributes for a
> list.
I'm unhappy with the name, then. "Style defaults" would be
pedantically correct.
> IOW, if you changed a style after a list is c
On Tue, Mar 5, 2013 at 2:23 PM, Barry Warsaw wrote:
> On Mar 02, 2013, at 10:38 AM, Tom Browder wrote:
...
>>I guess the real question for me is: is there a templating system in MM 3 so
>>that different list types can be defined?
...
> Yes, these are called "list styles". See the IStyle interface
On Mar 02, 2013, at 10:38 AM, Tom Browder wrote:
>Earlier I was pointed to the REST API for programatically generating a new
>list--looks good. However, the docs mention a default set of attributes for
>a new list and I wonder if there are yet any other choices.
>
>I guess the real question for m
