Template talk:Fgaddon aircraft source: Difference between revisions

Jump to navigation Jump to search
(→‎The move from fgaddon url to fgaddon file: Looks good so far + Some ideas)
Line 51: Line 51:
::* Moving that template to {{tl|fgaddon aircraft url}} to make its use less ambiguous
::* Moving that template to {{tl|fgaddon aircraft url}} to make its use less ambiguous
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 09:26, 9 March 2016 (EST)
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 09:26, 9 March 2016 (EST)
::: Thinking more about the organisation of the [[:Category:Repository link templates|{{obr}}repo link{{cbr}} family of templates]], I might have a better idea :)  If you have a look at the other FlightGear {{obr}}* source{{cbr}} templates, you'll see that the usage of the current set of templates is an identical match (for example {{tl|fgaddon source}} vs. {{tl|flightgear source}}).  This is the same with the {{obr}}* url{{cbr}} set of templates, for example {{tl|fgaddon url/sandbox}} vs. {{tl|flightgear url}}.  The only set of templates that are not consistent are the [[:Category:Repository link templates|{{obr}}* file{{cbr}} templates]].  The idea of the {{param|aircraft}}, {{param|path}}, and {{param|file}} parameters, as used in {{tl|fgaddon file/sandbox}} to construct the {{tl|repo link}} master parameters {{param|path}}, {{param|text}}, and {{param|full}}, could be expanded to match the other templates sets.  Maybe we could have:
:::* {{tl|fgaddon aircraft source}} - as the content of {{tl|fgaddon file/sandbox}}, which matches the behaviour of your original {{tl|fgaddon url}} template, but with many new {{tl|repo link}} options.
:::* {{tl|fgaddon aircraft url}} - this is the same as {{tl|fgaddon aircraft source}} but with the parameter value {{param|full|1}}, and all text construction parameters dropped.  It produces pure URLs and no Mediawiki links.  It could transclude {{tl|fgaddon aircraft source}} to allow that template to do the parameter remapping, rather than transcluding {{tl|repo link}} and duplicating the parameter mapping.
::: This might be nicer for organisation and consistency, rather than dumping this into the [[:Category:Repository link templates|{{obr}}* file{{cbr}} mixed bag category]].  This would allow the {{param|file}} parameter to be dropped.  So where you would like {{param|file|yes}}, you would use {{tl|fgaddon aircraft source}}.  And for {{param|file|no}}, you would use {{tl|fgaddon aircraft url}}.  For such an organisation, it would be good to preserve the history as {{tl|fgaddon url}} → {{tl|fgaddon file}} → {{tl|fgaddon aircraft source}}.
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:13, 9 March 2016 (EST)

Navigation menu