Jon Berndt [EMAIL PROTECTED] wrote:
Well, I want to look at it because I sort of hope to migrate the JSBSim XML
definition to a more robust and compliant format at some point in the
future. Even now, it would be nice to make some changes here and there that
allowed us to move towards an
Martin Spott wrote:
Jon Berndt [EMAIL PROTECTED] wrote:
Well, I want to look at it because I sort of hope to migrate the JSBSim XML
definition to a more robust and compliant format at some point in the
future. Even now, it would be nice to make some changes here and there that
allowed us to
[David:]
I tried looking for some docs on EasyXML, but so far the only things I have
been able to find are the auto-generated API docs. That's the second thing
I'd like to see. Is there an EasyXML Quick-start sort of document
somewhere, or do I just need to dig into the code? If the latter is
Jon Berndt wrote:
I tried looking for some docs on EasyXML, but so far the only things I
have been able to find are the auto-generated API docs. That's the
second thing I'd like to see. Is there an EasyXML Quick-start sort
of document somewhere, or do I just need to dig into the code? If
Andy Ross wrote:
I'd strongly suggest using the property tree parser.
Me too, simply because it's at least an order of magnitude easier. However,
I suspect that Jon wants to use EasyXML for parsing the coefficients, and I
have to admit that the property-tree format will be fairly verbose for
I'd strongly suggest using the property tree parser. I wrote YASim
using the easyxml interface, and it worked, but in hindsight it would
have been *much* cleaner to have a parse tree representation than
trying to build the parse tree out of YASim objects from a callback
parser. (In my
Andy Ross wrote:
I'd strongly suggest using the property tree parser.
Me too, simply because it's at least an order of magnitude easier.
However,
I suspect that Jon wants to use EasyXML for parsing the coefficients, and
I
have to admit that the property-tree format will be fairly verbose
