Board Thread:Support Requests - Getting Technical/@comment-24739709-20151102183832/@comment-11733175-20151105084001

I think this is a step in the right direction, but I feel it's a confusing mix of extensions/tags. I also feel it should have been implemented at the tag level, i.e. in the template itself, rather than at the argument level as the template is really where any logic or complication should be handled. A template should offer a simple, powerful and intuitive API that can be used by anyone irrespective of how little experience they have. I find it unlikely someone using VE will be able to edit a field set up in this way.

I think it would have been cleaner to offer a something more inline with what's already offered. For example:  ...

However, that example doesn't support a default. So, how about this instead: ...

Which could be used as:

The good thing about integrating this with the  tag is that it allows other parameters to have multiple values too, while adding one more attribute to the API thus keeping it relatively simple instead of having to lookup other syntax to achieve what you want.

I'd agree with Lord TBT that a large amount of tabs is aesthetically unpleasant. So what about limiting the number of buttons to 2-3 &mdash; just limit it to the what fits within a single line of the infobox &mdash; and then using a dropdown instead?