13,208
edits
Frequently asked questions: Difference between revisions
Jump to navigation
Jump to search
m
+- template: cite web → forumref
m (+- template: cite web → forumref) |
|||
| Line 253: | Line 253: | ||
|added = Aug 25th, 2011 | |added = Aug 25th, 2011 | ||
|script_version = 0.37 | |script_version = 0.37 | ||
}}</ref><ref>{{ | }}</ref><ref>Soitanen (Aug 28th, 2014). {{forumref |title=Re: Encrypted aircraft dynamics |p=217378}}</ref><ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/34559749/ | |url = https://sourceforge.net/p/flightgear/mailman/message/34559749/ | ||
|title = <nowiki> [Flightgear-devel] External FDM to protect propriety data in a GPL | |title = <nowiki> [Flightgear-devel] External FDM to protect propriety data in a GPL | ||
| Line 286: | Line 279: | ||
the data is parsed from the XML into dynamic look up tables (IE. STL). The only resources used beyond that needed to make the FDM function is the overhead of pulling the data out of the XML into memory. That would have to happen no matter what form the data was in. | the data is parsed from the XML into dynamic look up tables (IE. STL). The only resources used beyond that needed to make the FDM function is the overhead of pulling the data out of the XML into memory. That would have to happen no matter what form the data was in. | ||
Although there may be better ways to store the data than XML if you are unconcerned about human interaction with the data. I think that making the data human readable/editable is the main point of using XML. It may be overly verbose but it works and there are standard libraries for reading/parsing XML files so this makes using it for data input fairly simple. This benefits both FlightGear and JSBSim in terms of limiting the complexity of handling configuration data. In addition there are a limited number of standardied formats for this type of thing such as JSON and all of those that are human readable/editable have many of the same issues as XML. | Although there may be better ways to store the data than XML if you are unconcerned about human interaction with the data. I think that making the data human readable/editable is the main point of using XML. It may be overly verbose but it works and there are standard libraries for reading/parsing XML files so this makes using it for data input fairly simple. This benefits both FlightGear and JSBSim in terms of limiting the complexity of handling configuration data. In addition there are a limited number of standardied formats for this type of thing such as JSON and all of those that are human readable/editable have many of the same issues as XML. | ||
Full function FDMs are complex and understanding the XML used to configure a complex FDM is a very minor issue and anyone who actually understands a full function FDM will have very few issues with the XML part of this.<ref>{{ | Full function FDMs are complex and understanding the XML used to configure a complex FDM is a very minor issue and anyone who actually understands a full function FDM will have very few issues with the XML part of this.<ref>hvengel (Aug 28th, 2014). {{forumref|title=Re: Encrypted aircraft dynamics|p=217408}}</ref> | ||