Jonathan Polley writes:
I have made an attempt to describe the contents of 'preferences.xml.'
Could someone knowledgeable in the properties list and preferences.xml
file let me know if I am understanding things correctly? Also, is there
any information about what each component of
Just to start, the property tree has nothing to do with Metakit -- we
use Metakit only to hold airport and navaid data.
I will make that change.
path Aircraft/c172/Panels/c172-vfr-panel.xml/ path
This tells FlightGear where it can find the configuration
information for
Some of the other XML files are rather easy to figure out (i.e,. keyboard.
xml), but others are not (i.e., the FDM specific files). Does anyone have
anything written that describes these? The materials.xml file has quite a
nice description at the top.
Can you let us know what is unclear in
Jonathan Polley writes:
Some of the other XML files are rather easy to figure out
(i.e,. keyboard. xml), but others are not (i.e., the FDM specific
files).
YASim and JSBSim each uses its own XML format, which is different from
the XML format used by the rest of FlightGear. For YASim,
On Sunday, March 17, 2002, at 09:53 AM, Jon Berndt wrote:
Some of the other XML files are rather easy to figure out (i.e,.
keyboard.
xml), but others are not (i.e., the FDM specific files). Does anyone
have
anything written that describes these? The materials.xml file has quite
a
I have made an attempt to describe the contents of 'preferences.xml.'
Could someone knowledgeable in the properties list and preferences.xml
file let me know if I am understanding things correctly? Also, is there
any information about what each component of FlightGear needs from the
Wolfram Kuss writes:
The XML files get IMVHO more and more confusing.
I think that it would be more accurate to say that FlightGear is
getting more sophisticated -- there's more to learn if you want to
customize things, but that's only because there's so much more that
you can customize.
The
* [EMAIL PROTECTED] (David Megginson) [2002.03.10 10:47]:
Jim Wilson writes:
Hehe. Yep. Didn't notice that one. Actually I don't know why
that would be in the preferences.xml. Anyone know why that isn't
in the panel or at least aircraft-set xmls?
A cleanup and reorg is long
Cameron Moore writes:
[ Why doesn't Tarzan have a beard? ]
Jane, n'est-ce pas?
All the best,
David
--
David Megginson
[EMAIL PROTECTED]
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
David wrote:
Wolfram Kuss writes:
The XML files get IMVHO more and more confusing.
I think that it would be more accurate to say that FlightGear is
getting more sophisticated -- there's more to learn if you want to
customize things, but that's only because there's so much more that
you can
Wolfram Kuss writes:
BTW, in your list you forgot the *-dpm.xml files, which are of most
interest to me and which are currently the only ones that I really use
:-). With the little time I currently have, I am glad if I manage to
have a nice 3D model at the correct place in fgfs.
Ah, yes
Jonathan Polley writes:
I have some experience with Tkinter. but my GUIs tend to be a bit
functional (OK, ugly), and I will be learning XML at the same
time. Any, and all, help will be greatly appreciated.
If you know LISP (CommonLISP, InterLISP, Scheme, E-LISP, or what-have
you), you're
On Sunday, March 10, 2002, at 07:02 PM, David Megginson wrote:
Jonathan Polley writes:
I have some experience with Tkinter. but my GUIs tend to be a bit
"functional" (OK, ugly), and I will be learning XML at the same
time. Any, and all, help will be greatly appreciated.
If you know LISP
Jonathan Polley [EMAIL PROTECTED] said:
The preferences file is not FDM specific at all. The contents of
preferences.xml in the base package are for the most part self
explanatory,
I have to beg to differ on this one. For those few command line arguments
that I have used, I can
Jim Wilson writes:
Hehe. Yep. Didn't notice that one. Actually I don't know why
that would be in the preferences.xml. Anyone know why that isn't
in the panel or at least aircraft-set xmls?
A cleanup and reorg is long overdue; same for keyboard mappings.
All the best,
David
--
If you know LISP (CommonLISP, InterLISP, Scheme, E-LISP, or what-have
you), you're most of the way there.
Now I am going to have nightmares ). LISP and I were not the best of
friends in college (things like caadaddaddr gives me chills).
Actually, I think they're referring to nested
On Sunday, March 10, 2002, at 08:04 PM, Alex Perry wrote:
Another sneaky bonus of XML over LISP is in the bracketing. Instead of
having fifteen close parentheses stacked up at the end of the function,
you get to say /a/b/c/d/e/f etc. While this is a pain in the
butt to type, at least the
Sounds like a worth while (sp?) project!
The XML files get IMVHO more and more confusing.
Maybe lets do the big reorg that Dave speaks about first, with the
hope that things won't change often afterwards. When doing the python
scripts to generate the very very rudimentary plane xmls on my website
On Monday 11 March 2002 02:32 am, you wrote:
Sounds like a worth while (sp?) project!
The XML files get IMVHO more and more confusing.
Maybe lets do the big reorg that Dave speaks about first, with the
hope that things won't change often afterwards. When doing the python
scripts to generate
On Monday 11 March 2002 02:32 am, you wrote:
snip choose a FDM, panel etc, inputs it into the XMLs, generates a small
batch file to call everything, etc.
The set files do what said batch file would do. They are the
top level aircraft config.
___
20 matches
Mail list logo
