FlightGear Newsletter April 2014: Difference between revisions

Jump to navigation Jump to search
→‎Development news: http://sourceforge.net/p/flightgear/mailman/message/32248440/
(→‎Development news: http://sourceforge.net/p/flightgear/mailman/message/32248440/)
Line 6: Line 6:
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].


=== YaSim versioning ===
{{Conversational}}
<pre>Hi all,
as promised, I have just added a versioning scheme to yasim
configuration files.
The <airplane> element of the yasim config file now understands the
"version" attribute that can be currently one of these values:
YASIM_VERSION_ORIGINAL
The original version of YASim as implemented up to FlightGear 3.0.0
(this is the default)
YASIM_VERSION_32
The version of YASim currently implemented in FlightGear 3.1 (current
git HEAD)
YASIM_VERSION_CURRENT
The current and latest version of YASim (which is currently the same as
YASIM_VERSION_32)
Example:
<airplane mass="1344" version="YASIM_VERSION_32">
A missing "version" attribute will cause yasim to use the original
(buggy) implementation without the latest patches. This should restore
the original behavior to all yasim aircraft. Aircraft that were adapted
to the new version of yasim (with the latest patches from Colin Douglas
Howell) should set version=" YASIM_VERSION_32" to re-enable those changes.
The idea is to add a new YASIM_VERSION_xx with every release cycle where
xx is the next to-be-released version number (32 for 3.2 for the current
cycle and 34 for the next cycle etc).
I hope this is somewhat useful and works as described.
Please test some yasim aircraft and provide feedback.
Greetings,
Torsten
</pre>
=== Proof-of-Concept: A TerraGear Web Service (by F-JJTH) ===
=== Proof-of-Concept: A TerraGear Web Service (by F-JJTH) ===
{{WIP}}  
{{WIP}}  

Navigation menu