Paul Deppe wrote:
Paul Deppe wrote:
When compiling CVS simgear/sky/clouds3d I am getting numerous warnings:
WIN32 redefined, initialization from int to float, ... is
implicitly a
typename, and many others, and finally the following error
when compiling
SkyTextureState.cpp:
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
Someone on the Piper mailing list had a chance to crawl into a couple
of AT6's visiting his home field and snap some pics. Here they are,
for anyone interested in the modelling:
http://xcski.com/gallery/album02
All the best,
David
--
David Megginson, [EMAIL PROTECTED],
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
Any chance we could get back cvs logs from prior to the changeover? The lack
of them is making it hard to track down regressions introduced prior to.
Best,
Jim
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Last night I did an update to three of the Wright Flyer files, but only two
showed up in the log. The one that did not show up in the log was the file:
~/fgfsbase/Aircraft/UIUC/wrightFlyer1903-v1-nl/aircraft.dat
For the record, the message for it:
Wright Flyer update: Reduced wing warp to
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)
Paul Deppe writes:
When compiling CVS simgear/sky/clouds3d I am getting numerous warnings:
WIN32 redefined, initialization from int to float, ... is
implicitly a
typename, and many others, and finally the following error
when compiling
SkyTextureState.cpp:
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
David Megginson writes:
The new ATIS sound is great,
Thanks!
but I'm having volume problems with it.
Oh dear :-(
It's not possible to make it out at all at the default volume; when I change
the volume from 2 to 10 in ATCmgr.cxx simple-set_volume(10.0); I can
just make it out over the idling
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.
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.
Cheers!
Mike
-Original Message-
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,
I think the problem stems from GL/gl.h being included before extgl.h
Note GL/glu.h and GL/glut.h both include GL/gl.h so extgl.h must
precede these also
Norman
I inserted the following in SkyTexture.hpp at line 36:
#ifdef WIN32
# include extgl.h
#endif
... and it worked - thanks. But I
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,
Paul Deppe writes:
I think the problem stems from GL/gl.h being included before extgl.h
Note GL/glu.h and GL/glut.h both include GL/gl.h so extgl.h must
precede these also
Norman
I inserted the following in SkyTexture.hpp at line 36:
#ifdef WIN32
# include extgl.h
#endif
Is there a way to copy a block of properties (ie an equivelent to cp -ax dir1
dir2)? IIRC this was discussed at one time, and I'm wondering if it has been
implemented yet.
Best,
Jim
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
This may sound like a lame idea. I am not all that versed on xml technology,
but it seems to me that there is a standard form for something like this. In
the database world there is something called a Data dictionary that works as
a central repository for data items, their types, default
Jim Wilson writes:
Is there a way to copy a block of properties
#include simgear/misc/props_io.hxx
copyProperties (const SGPropertyNode *in, SGPropertyNode *out)
But AFAIK this requires that the 'out' nodes exist
i.e. this copies but does not construct the nodes
I think the easiest way to
28 matches
Mail list logo
