Template:Infobox weaponispermanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
This is the talk page for discussing improvements to the Infobox weapon template. |
|
Archives: 1Auto-archiving period: 90 days |
This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||||||||||
|
Self-propelled guns fall into both afv=yes and artillery=yes. Please see the example infobox in T28 Super Heavy Tank.
Can we rearrange the layout a bit so that these two work better together? Specifically, the primary_armament field should be shown at the top of the arty specifications section (within the horizontal rules). I suppose secondary_armament should immediately follow that section, but perhaps armour belongs after that, so it is not separated from the rest of the vehicle specs.
Some of the relevant fields, i.e. barrels, range, max_range, elevation and traverse, might also be useful for tanks or other AFVs in general, and are commonly found in references. Perhaps these should be available when afv=yes? —Michael Z. 2008-10-08 23:12 z
It's always bothered me that the image is just a few pixels narrower than the steel-blue header bars (a compliant 300px image is 5 pixels narrower, and has a visible margin of 2 px on the left and 3 px on the right). The uneven white margins looks like a mistake.
I made up a demo of an improved version—compare:
This requires some minor changes:
cellpadding=0
tomain_box
padding-top:1px; padding-bottom:1px
toimage_box
and image_box_plain
padding:1px;
toheader_bar
For pixel-perfect reproduction of the old style, the simplest solution would be to add padding:1px;
to every tr
, instead of adding it to some table cells. Most efficiently done in a stylesheet rather than in the template.
My demo code is at User:Mzajac/Template:WPMILHIST Infobox style.
Any comments about or objections to this change? —Michael Z. 2008-10-26 21:06 z
This edit request has been answered. Set the |answered= or|ans= parameter to no to reactivate your request. |
I would like to add several elements to this Infobox:
If we take for example the Canadian armoured vehicles LAV, all evolve from each other, and some replace each other. The LAV III replaced the LAV. The LAV 6 replaces the LAV. They also take their origin from the Mowag Piranha family, and were also developed into the ASLAV, the Stryker, the LAV 700.
There are so many weapons that were an evolution from another vehicle, it would help to get with the 4 bullet points a better understanding for the context of the existence of the vehicle in a very concise manner. Fabrice Ram (talk) 08:36, 12 November 2023 (UTC)Reply
This edit request has been answered. Set the |answered= or|ans= parameter to no to reactivate your request. |
Change primary_weapon and secondary_weapon in documentation to primary_armament and secondary_armament . It appears that the code was changed in (hard to believe...) 2011 but the docs were never updated. Zaathras (talk) 03:35, 5 March 2024 (UTC) Zaathras (talk) 03:35, 5 March 2024 (UTC)Reply
{{edit template-protected}}
is usually not required for edits to the documentation or categories of templates using a documentation subpage. Use the 'edit' link at the top of the green "Template documentation" box to edit the documentation subpage. — Martin (MSGJ · talk) 07:22, 5 March 2024 (UTC)Reply