Template talk:Infobox aircraft: Difference between revisions

Jump to navigation Jump to search
Line 112: Line 112:


:::: Indeed, that seems like a much better idea - and it would encourage the development/addition of more hangars in the future, which is in line with the hangar related comments recently made on the devel list, i.e. encouraging 3rd party hangars. So, maybe two layers of  templates would make sense: one using repo/fgaddon, and the other assuming a hangar, that maps directly to the corresponding underlying template. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:52, 11 May 2016 (EDT)
:::: Indeed, that seems like a much better idea - and it would encourage the development/addition of more hangars in the future, which is in line with the hangar related comments recently made on the devel list, i.e. encouraging 3rd party hangars. So, maybe two layers of  templates would make sense: one using repo/fgaddon, and the other assuming a hangar, that maps directly to the corresponding underlying template. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:52, 11 May 2016 (EDT)
::::: For now, it might be better to have everything in the same template.  This template is not very big at the moment, and you could simply add the <code>hangar</code> and <code>aircraft</code> parameters and add 2 switches for the <code>hangar</code> parameter - one at the top selecting a banner graphic, and one at the bottom providing automatically constructed download (and development repository) links.  I think the rest of the template should be the same for all aircraft, independent of their source.
::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:03, 11 May 2016 (EDT)

Navigation menu