Quoth Michael Bonar:
Hi David. I get a Forbidden error when I try to reach that link.
Terribly sorry. The link should have been
http://www.more.net/~david/FlightGear-0.9.1/html/
I turned on about every option available, and also built the graphical
class hierarchy.
Regards,
David K. Drum
Quoth David Megginson:
Luke Scharf writes:
Where would I find documentation about code-layout of FGFS? I did a
quick scan of flightgear.org and I didn't see a document that looked
like it addressed this object does this and relates to the other
objects like that question.
Come
Of David Drum
Sent: January 4, 2003 9:00 PM
To: [EMAIL PROTECTED]
Subject: Re: [Flightgear-devel] What's in the job jar?
Quoth David Megginson:
Luke Scharf writes:
Where would I find documentation about code-layout of FGFS? I did a
quick scan of flightgear.org and I didn't see a document
David Megginson writes:
Mike Bonar writes:
I have been mostly interested in AI and terrain rendering, but I am
open to working on anything.
You can also take a look at Dave Luff's ATC code in src/ATC/ -- he
might have some TODO jobs.
Yup, there's a black hole full of TODO jobs in there!
David Luff writes:
With regard to ATC, there's at least one other person working on it
besides myself, but AFAIK no-one is attempting to model centre
control - I might have the terminology wrong there but I'm
referring to control of the airways away from airfield
Norman Vine writes:
Question:
Is there any reason that ALL of the joysticks from the config files are
represented in the 'resident' property tree ??
It's on my TODO list, but it someone else wants to take that over I'll
be very happy.
All the best,
David
--
David Megginson, [EMAIL
Michael Bonar writes:
MSVC6 has a Visio add-on that allows you to reverse engineer C code
into UML diagrams. Anybody have experience with it? I was
thinking of giving that a try to see what it looks like. In the
meantime, I will see what I can find on code documentation.
Many of the
Norman Vine writes:
Thanks. That's pretty handy. I notice that this does not seem
to include all of the property information in some files, eg
sound.xml (and several other .xml files seen when searching
through the props file).
Yes I noticed that this is not a *complete* dump
David Megginson writes:
Norman Vine writes:
Thanks. That's pretty handy. I notice that this does not seem
to include all of the property information in some files, eg
sound.xml (and several other .xml files seen when searching
through the props file).
Yes I noticed
They are very helpful, and that's why the first test of Doxygen turned up such
good results IMHO. If it's decided that this is the way to go, then a simple
code documentation standard would need to be applied to the source to pull
out the information we think is valuable.
Cheers,
Mike
On
Norman Vine writes:
I see that but I thought one of the motivating factors for the
'properties' was to have a central location for all of the 'data'
There are different kinds of data. The property tree is meant to
represent the shared state of the program; when a subsystem happens to
use an
Mike Bonar wrote:
Okay, I have completed step one. I am up and running with the latest cvs
snapshot on Suse 8.1. What's in the job jar? Give me something easy to
start out with since it's been awhile since I have done any coding.
Some background if you are interested, I spent a good chunk
Mike Bonar writes:
Okay, I have completed step one. I am up and running with the
latest cvs snapshot on Suse 8.1. What's in the job jar? Give me
something easy to start out with since it's been awhile since I
have done any coding.
Cleanup is always, always needed -- my only suggestion
David Megginson wrote:
Cleanup is always, always needed --
...
We are slowly trying to get all of the parts of FlightGear to
extend FGSubsystem (defined src/Main/fgfs.hxx) and to simplify the
top-level loop in src/Main/main.cxx.
That sort of top-level stuff really is best done by the
On Sun, 2002-12-22 at 07:09, David Megginson wrote:
We are slowly trying to get all of the parts of FlightGear to
extend FGSubsystem (defined src/Main/fgfs.hxx) and to simplify the
top-level loop in src/Main/main.cxx.
Where would I find documentation about code-layout of FGFS? I did a
quick
Luke Scharf writes:
Where would I find documentation about code-layout of FGFS? I did a
quick scan of flightgear.org and I didn't see a document that looked
like it addressed this object does this and relates to the other
objects like that question.
Come to think of it, that sounds like
David Megginson writes:
Luke Scharf writes:
Where would I find documentation about code-layout of FGFS? I did a
quick scan of flightgear.org and I didn't see a document that looked
like it addressed this object does this and relates to the other
objects like that question.
Come
Norman Vine writes:
A worthy project indeed but IMHO an even worthier project
would be to collect all of the various properties into a single
document that included
1) a short description of what it controlled
2) which xml file it resided in
3) which 'C' file set its default if
David Megginson writes:
Norman Vine writes:
A worthy project indeed but IMHO an even worthier project
would be to collect all of the various properties into a single
document that included
1) a short description of what it controlled
2) which xml file it resided in
3)
Norman Vine writes:
Computer programs are a mix of algorithm and data and just because
you take the data out of the 'C' code and stash it externally does nothing
to alleviate the need to document it !!
Agreed -- I'm simply pointing out the challenges.
All the best,
David
--
David
Michael Selig
As it relates to documenting things, I'd like to ask this again: Is this
file property-api.html still around somewhere? This doc described the
property tree. It was a draft from Curt I believe.
It seems to me like the property stuff is the most important part of
FGFS.
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Megginson
Sent: December 22, 2002 12:01 PM
To: [EMAIL PROTECTED]
Subject: re: [Flightgear-devel] What's in the job jar?
Luke Scharf writes:
Where would I find documentation about code-layout of FGFS? I did a
quick scan
Michael Bonar wrote:
MSVC6 has a Visio add-on that allows you to reverse engineer C code
into UML diagrams. Anybody have experience with it? I was thinking
of giving that a try to see what it looks like.
It probably looks a lot like UML generated automatically from C
code. :)
I've never
On Sun, 2002-12-22 at 13:01, David Megginson wrote:
Luke Scharf writes:
Where would I find documentation about code-layout of FGFS? I did a
quick scan of flightgear.org and I didn't see a document that looked
like it addressed this object does this and relates to the other
objects
Yes, I see where you are coming from, Andy. In the spirit of openness, I
don't think that's the way to go either.
However, I did run doxygen against the source code, and that is very cool.
It's clean, simple, fast, and open. We could run a cron against the cvs
directory each night, and
At 12/22/02, Norman Vine wrote:
Michael Selig
As it relates to documenting things, I'd like to ask this again: Is this
file property-api.html still around somewhere? This doc described the
property tree. It was a draft from Curt I believe.
It seems to me like the property stuff is the
_Interested_ ;-)
On Sunday 22 December 2002 20:48, Mike Bonar wrote:
Yes, I see where you are coming from, Andy. In the spirit of openness, I
don't think that's the way to go either.
However, I did run doxygen against the source code, and that is very cool.
It's clean, simple, fast,
Michael Selig writes:
At 12/22/02, Norman Vine wrote:
Michael Selig wrote:
It seems to me like the property stuff is the most important part of
FGFS. If one does not understand how to use this and code for it (both in
xml and cpp), then you're never going to get anywhere. Ok,
28 matches
Mail list logo
