Talk:FlightGear version check: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(Dequoted)
Line 3: Line 3:
We should grep through $FG_ADDON to see if there are any other aircraft processing /sim/version in *.nas files, and check what is done/needed there. So far, the JA37 has the best-developed system in place, and it does not just silently fail/exit, but will do dynamic-feature scaling by disabling stuff, i.e. true backward compatibility. So that seems to be much better in comparison. It would only need to be generalized, e.g. to support SGConditions via props.nas and custom message/code blocks to enable/disable features
We should grep through $FG_ADDON to see if there are any other aircraft processing /sim/version in *.nas files, and check what is done/needed there. So far, the JA37 has the best-developed system in place, and it does not just silently fail/exit, but will do dynamic-feature scaling by disabling stuff, i.e. true backward compatibility. So that seems to be much better in comparison. It would only need to be generalized, e.g. to support SGConditions via props.nas and custom message/code blocks to enable/disable features
=== terminating ===
=== terminating ===
{{FGCquote
should take into account the aircraft centre and in-sim switching<ref>{{cite web
|1= It also would need to be designed to take the aircraft centre into account, and switching in-sim.
| url    = http://forum.flightgear.org/viewtopic.php?p=264829#p264829
|2= {{cite web
| title  = <nowiki>Re: version checking for matching fgfs and -set.xml files</nowiki>
  | url    = http://forum.flightgear.org/viewtopic.php?p=264829#p264829
| author = <nowiki>bugman</nowiki>
  | title  = <nowiki>Re: version checking for matching fgfs and -set.xml files</nowiki>
| date  = Nov 17th, 2015
  | author = <nowiki>bugman</nowiki>
}}</ref>
  | date  = Nov 17th, 2015
  }}
}}
=== disable version-check ===
=== disable version-check ===
should introduce a property to disable the whole thing for power users using a prop switch
should introduce a property to disable the whole thing for power users using a prop switch
Line 19: Line 16:
should use $FG_ROOT/Translations as a workaround for non-English errors messages
should use $FG_ROOT/Translations as a workaround for non-English errors messages
=== GUI independent ===
=== GUI independent ===
{{FGCquote
should work independently of the used frontend (PUI, Phi, Canvas, Qt)<ref>{{cite web
|1= It should also be GUI independent (i.e. it works in a non-GUI mode with no PUI, no Phi, no Canvas, no Qt, etc.).
| url    = http://forum.flightgear.org/viewtopic.php?p=264823#p264823
|2= {{cite web
| title  = <nowiki>Re: version checking for matching fgfs and -set.xml files</nowiki>
  | url    = http://forum.flightgear.org/viewtopic.php?p=264823#p264823
| author = <nowiki>bugman</nowiki>
  | title  = <nowiki>Re: version checking for matching fgfs and -set.xml files</nowiki>
| date  = Nov 17th, 2015
  | author = <nowiki>bugman</nowiki>
}}</ref>
  | date  = Nov 17th, 2015
  }}
}}
=== logprint ===
=== logprint ===
should be used to ensure that everything shows up in the log file
should be used to ensure that everything shows up in the log file
Line 34: Line 28:
=== conditions ===
=== conditions ===
props.nas
props.nas
{{appendix}}

Revision as of 19:33, 5 May 2016

features

JA37

We should grep through $FG_ADDON to see if there are any other aircraft processing /sim/version in *.nas files, and check what is done/needed there. So far, the JA37 has the best-developed system in place, and it does not just silently fail/exit, but will do dynamic-feature scaling by disabling stuff, i.e. true backward compatibility. So that seems to be much better in comparison. It would only need to be generalized, e.g. to support SGConditions via props.nas and custom message/code blocks to enable/disable features

terminating

should take into account the aircraft centre and in-sim switching[1]

disable version-check

should introduce a property to disable the whole thing for power users using a prop switch

modal error dialog

should we disable/hide the menubar and use Draw masks to hide everything else?

localized

should use $FG_ROOT/Translations as a workaround for non-English errors messages

GUI independent

should work independently of the used frontend (PUI, Phi, Canvas, Qt)[2]

logprint

should be used to ensure that everything shows up in the log file

properties

we could make this much more generic by allowing arbitrary properties to be checked and warnings/errors to be shown, which would allow aircraft developers to provide custom messages to clarify if/how an aircraft is going to be affected by mismatching versions--Hooray (talk) 08:33, 17 November 2015 (EST)

conditions

props.nas

References