Template talk:Verdict

Usage

Just fill the following template call:

{{verdict|1|2}}

Where 1 is the verdict given, and 2 is the action taken. If no values are passed to 1 or 2, it automatically fills them as undefined.

Entering "Not Vandalism" for 1 will automatically fill in 2 with "None Required" unless 2 is specified.

Example

{{Verdict}}

Verdict	{{{1}}}
Action taken	{{{2}}}

{{Verdict|Awaiting Clarification}}

Verdict	Awaiting Clarification
Action taken	{{{2}}}

{{Verdict|Vandalism|Warned}}

Verdict	Vandalism
Action taken	Warned

{{Verdict|Not Vandalism}}

Verdict	Not Vandalism
Action taken	{{{2}}}

{{Verdict|Not Vandalism|Warning Retracted}}

Verdict	Not Vandalism
Action taken	Warning Retracted

Modificatins for Verdict

So, because of some tests I decided to run this template's new code through my ProjDev pages, what I ended up with was this. In two edits I managed to remove 394 of 554 bytes from the inclusion size. About a third of that came from documentation with 259 coming from extraneous code. Visually it's roughly the same without red text and with backgrounds behind the verdict texts(due to using precreated classes to save space). The inclusion limit for A/VB is .3 MB. So, basically, if we make my modifications we'll be opening up one hell of a lot of space from this template. --Karek^maps?! 08:17, 15 April 2011 (BST)

Color

So, for those who were rooting for default colors. Just wanted to clarify why I left them out here, partly it's inclusion size, partly it's any method of doing it would add yet another template to the chain here and usually a fairly large block of one. In this case it would have to be Switch or something like the span default used before around the piped variable which, if that were to be included, needs to be done in {{V}} due to the necessity of that to assign default values there for default values to fill. --Karek^maps?! 08:17, 15 April 2011 (BST)

My thinking was that we could simply remove the switch and the coloring that this one has/had (I haven't checked), and use that savings to then put the colors in V. It's not as minimal as it could be, sure, but it's less than what it was, doesn't double up, and really is very useful (as Ross and DDR said over on V's talk). Asking sysops to make alternate smaller sigs for use on the admin pages would result in a much higher savings, however. —Aichon— 08:30, 15 April 2011 (BST)

Oh definitely, which is why I keep bringing it up. I think it'd be reasonable to add the color code to {{V}} if this change set is implemented but it can't be with any sort of template/switch. That'd be about as counter productive as leaving it as is now I suspect. We'd still be making positive reductions. --Karek^maps?! 08:37, 15 April 2011 (BST)

Will making my sig a SUBST sig reduce code in the same way that a smaller sig would?--Yonnua Koponen ^{T G P} ^^^ 11:11, 15 April 2011 (BST)

It reduces template calls so, yes. It won't reduce the size of the A/VB page itself significantly but the A/VB archive page would get more inclusions space there because you're no longer adding a large template every time you sign the page. --Karek^maps?! 04:29, 16 April 2011 (BST)