Talk:McDonnell Douglas F-15 Eagle

From FlightGear wiki
Jump to navigation Jump to search

Is this the FGAddon version?

I have updated the aircraft infobox template usage in preparation for a migration to a new template: Template talk:Infobox aircraft#Proposal for a new aircraft infobox template design (2016/06). However I am not 100% sure if this article describes the aircraft as found in FGAddon, as the download link pointed to Richard's version at Though I believe this has been fully merged into FGAddon. Could someone please confirm this? Cheers! Note, I have set the development repository link to

Bugman (talk) 12:06, 9 June 2016 (EDT)

It is currently merged as at the last release version, although I think the development version may be slightly revised, merging into FGAddon is something that I've been meaning to do for a while, I'm planning to get it properly merged for 2016.3 and there are also specific versions to match with FG versions so it makes sense to keep the links to my site, but I'm happy to be swayed by arguments to the contrary.The links for development and beta versions will still be valid.
Richard H (talk) 12:44, 9 June 2016 (EDT)
What do you think of the current template McDonnell Douglas F-15 Eagle/info as used on the main page and French translation? I've linked to for the development icon (I just reverted the name from "Repository" to "Development" to be clearer). For FGAddon aircraft in the new template, clicking on the download icon will download the official zip file for the latest tagged stable release. If you can think of anything new that could be added to User:Bugman/Infobox Aircraft that might be of general interest, I would be interested in hearing some more opinions. For example would a link for a second, non-FGAddon download be of use here? Now would be a great time to expand the capabilities of this template ;)
Bugman (talk) 13:27, 9 June 2016 (EDT)
The development and associated icon aren't clear (to me) as to what they are (without hovering); would suggest some sort of indication that this is a website, or a download link. I'd also like to see some more icons (for all aircraft) to indicate what is simulated and what isn't, and also where the aerodynamic data came from for the FDM (maybe a JSBSim windtunnel, JSBSim aeromatic, JSBSim DATCOM, JSBSim). The F-15 (and F-14) have representative Hyds, electrics, ECS. Also ALS Interior (and glass) effects would be neat to show in the list.
Richard H (talk) 11:57, 11 June 2016 (EDT)
It is not clear to me either ;) These are more historic constraints. There is also the single word constraint of the infobox. Let me break this into different points:
  • Development: This parameter was supposed to be for the development repository URL. But this has been used for other URLs in 3rd party hangars. Maybe new parameters are required for the different use cases, but I would need to work out all the different cases.
  • Credit for hangars: This might be where your URL could fit in? These could be listed at the end, and use the same logo or text as the hangar parameter.
  • FDM info: This could be a new parameter after the fdm parameter, and have a fixed set of values that automatically add categories.
  • More ready icons: Could you expand the table at {{ready}}? Maybe we should use text until icons are created?
Bugman (talk) 06:26, 12 June 2016 (EDT)
For the development parameter, I am experimenting by splitting this into devel-repo for the SCM repository and devel-website for a website, and grouping both of these under the one title of Development. The F-15 infobox has been updated so that the link to website is now under devel-website. I hope this clears the confusion between repository URLs and often used website links.
Bugman (talk) 12:21, 14 June 2016 (EDT)