Wikipedia:Templates for discussion/Log/2010 July 2

The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review). No further edits should be made to this section.

The result of the discussion was delete. JPG-GR (talk) 07:45, 12 July 2010 (UTC)[reply]

Template:United States Squad 2004 U-19 Women's World Championship (talk · history · transclusions · logs · subpages)

After discussions at

The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review). No further edits should be made to this section.

The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review). No further edits should be made to this section.

The result of the discussion was Merge, using the best features from each template (e.g., layout and pushpin map) Plastikspork _―Œ^(talk) 19:13, 12 July 2010 (UTC)[reply]

Template:Infobox skyscraper (talk · history · transclusions · logs · subpages

)

Template:Infobox building (talk · history · transclusions · logs · subpages)

Redundant to Template:Infobox building. There is also a great deal of inconsistency in what is used, differeint documentation which should be simplified etc. This proposal is to merge given that the parameters are almost identical to infobox building and infobox building has the pushpin map option which ifnobox skyscraper does not. Dr. Blofeld ^{White cat} 18:10, 2 July 2010 (UTC)[reply]

• Delete/merge - the few skyscraper-specific parameters like year_highest and year_end can easily be merged to Infobox building. エムエックスさん 話 00:59, 3 July 2010 (UTC)[reply]
• Delete — Makes no sense to have two different templates that are nearly identical. Also, if those fields can be integrated into Building, then there's no reason to not get rid of it. —Onore Baka Sama^{(speak | stalk)} 01:07, 3 July 2010 (UTC)[reply]

I believe I merged most if not all of the outstanding parameters into infobox building a few weeks back the rest were the same anyway. Also infobox building has a fully functioning pin map facility which this does not have. Any trasition to infobox building naturally will be done without losing any data of course. Dr. Blofeld ^{White cat} 09:21, 3 July 2010 (UTC)[reply]

• Comment {{
  Infobox skyscraper}} has a sectioned layout that I find more aesthetically pleasing than the rather bland {{Infobox building}} There's also a "Status" field that doesn't seem to exist in Infobox building.[1] Perhaps Infobox building should be replaced by Infobox skyscraper instead of the other way around. --AussieLegend (talk) 09:40, 3 July 2010 (UTC)[reply
  ]
• Merge Infobox Skyscraper seems to repeat most of the data found within Infobox building, BUT... it does have some things that Infobox Building does not, and it seems to be laid-out better...perhaps we should merge the data into Infobox Building, and update Infobox Building's layout? Alternately, only have Infobox Skyscraper used on buildings that are 25+ floors? RingtailedFox • Talk • Contribs 14:39, 3 July 2010 (UTC)[reply]

• Keep. Infobox skyscraper has good features and has a better sectioned lay-out design and framing, so that should be kept. The titled detail bars and headings are helpful, and improve understanding and skyscraper template looks better. The ability to incorporate or embed National Register of Historic Places, National Historic Landmark, U.S. Historic District information are highly desireable features that Infobox skyscraper allows after "architect". The flexability is helpful, no need to limit Infobox skyscraper. Its a good tool, make it better don't take it away. Agree that all the good features and lay-out of infobox skyscraper should be kept if there is a merging, since infobox skycraper has the better lay-out.Thomas Paine1776 (talk) 17:41, 3 July 2010 (UTC)[reply]

No it is missing some vital components like pushpin map... It is easy to merge. Dr. Blofeld ^{White cat} 12:04, 7 July 2010 (UTC)[reply]

• Keep per Thomas Paine1776's rationale. Zonafan39 (talk) 00:16, 4 July 2010 (UTC)[reply]
• Merge: 'skyscraper' does look better, but i suppose that's the whole idea of a merging...to retain the best features of both. --emerson7 03:08, 4 July 2010 (UTC)[reply]
• Merge As per others, the functionality and layout of {{
  Infobox skyscraper}} should be included in {{Infobox building}}. --AussieLegend (talk) 03:39, 4 July 2010 (UTC)[reply
  ]
• Keep per Thomas Paine1776's, certainly not redundant, we should make it better than taking away/merged. KuwarOnline ^Talk 06:10, 5 July 2010 (UTC)[reply]
• Keep Per Thomas Paine1776.
  talk) 10:02, 5 July 2010 (UTC)[reply
  ]
• I'm actually planning on adding subclassing to {{infobox building}} which will allow for it to be used for skyscrapers, churches et cetera by adding in "modules" for each, as with {{infobox person}}. Check that template's talk out for further details. Suffice to say that this is still at a relatively early point in development, but in the long run it's better than making {{infobox building}} monolithic and hundreds of LOC long. TP1776's concerns would be better addressed with that approach. Chris Cunningham (not at work) - talk 21:51, 5 July 2010 (UTC)[reply]
• Merge per nearly identical. Subclassing as mentioned by Chris Cunningham is preferred, but not necessary for a merge. jonkerz♠ 00:08, 6 July 2010 (UTC)[reply]

  Not only is it not necessary, it is exclusive to a merge. The point about {{infobox building}} getting monolithic and thus unmanageable stands. Chris Cunningham (not at work) - talk 07:56, 6 July 2010 (UTC)[reply]

• Keep or Merge per Thomas Paine. If it is indeed merged, the functionality and layout must remain intact; however if {{infobox building}} is deemed untweakable (or monolithic, etc), then the two distinct templates are required. -M.Nelson (talk) 23:12, 6 July 2010 (UTC)[reply]
• Keep per Thomas Paine1776. Burpelson AFB (talk) 01:25, 7 July 2010 (UTC)[reply]
• Merge but only if merged properly so that the entire template's function can be preserved. --Deryck C. 07:28, 7 July 2010 (UTC)[reply]

You can be 100% assured that the idea is to merge the whole parameters so nothing is lost. The parameters are mostly identical to infobox building so this template is redundant. So nothing is lost and an obvious redundancy in having dual infoboxes is removed. Dr. Blofeld ^{White cat} 12:03, 7 July 2010 (UTC)[reply]

• Keep per Burpelson. --Extra 999 (Contact ^me + _contribs) 11:31, 7 July 2010 (UTC)[reply]
• Merge I also think that the skyscraper infobox and the building share the same data and parameters, so the skyscraper infobox should be merge into the building infobox. Jim856796 (talk) 21:47, 7 July 2010 (UTC)[reply]
• Merge per all foregoing. -- P 1 9 9 • TALK 00:06, 8 July 2010 (UTC)[reply]
• Merge The skyscraper infobox and the building share almost the same data and parameters.
  Talk 05:30, 8 July 2010 (UTC)[reply
  ]
• Merge I would merge infobox building into infobox skyscraper and delete the building inforbox. --Shorty23sin (talk) 02:55, 9 July 2010 (UTC)[reply]