RE: [Flightgear-devel] properties documentation
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 values, short descriptions, long descriptions, etc. I've seen Doxygen mentioned here previously, IIRC. I can vouch for its effectiveness as a documentation aid. Doxygen can produce a pretty detailed index. This would be a start, if nothing else. I also wonder if there shouldn't be a way to - dump at run time - the listing you ask for (for instance in a debug compile, one could have this capability). Jon smime.p7s Description: application/pkcs7-signature
RE: [Flightgear-devel] properties documentation
Jon Berndt [EMAIL PROTECTED] said: 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 values, short descriptions, long descriptions, etc. I've seen Doxygen mentioned here previously, IIRC. I can vouch for its effectiveness as a documentation aid. Doxygen can produce a pretty detailed index. This would be a start, if nothing else. I also wonder if there shouldn't be a way to - dump at run time - the listing you ask for (for instance in a debug compile, one could have this capability). Yes and I think Doxygen sounds like a good thing. To be honest I don't really have much trouble figuring out what the properties are and if I need to know what sets/reads them, grep works fine. But it does seem as though a central dictionary (for lack of a better term) to which xml configs refer might yield some benifit for new programmers as well as simplifying the coding of xml files. Maybe even error checking. Again this is a topic I'm not familiar with...just asking the question. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] What's in the job jar?
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 PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] What's in the job jar?
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 code modules I've written have JavaDoc-like comments attached in the *.hxx files -- those might be helpful. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] What's in the job jar?
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 too :-( I find that massaging this file a little is even handier, for example the attached script creates this from the file the above patch produces and can be easily modified to do other things with the properties Not everything that is read from an XML file resides in the main property tree; some subsystems also use XML files for initial configuration information. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] copying properties
Jim Wilson writes: 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. See simgear/misc/props_io: /** * Copy properties from one node to another. */ bool copyProperties (const SGPropertyNode *in, SGPropertyNode *out); All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] properties documentation
Jim Wilson writes: Is this the sort of thing that a standard DTD document provides? Or could we develop our own dictionary of sorts? I'm suggesting that this could provide the documentation we need (if it is centralized). No, DTDs are strictly structural -- think of it as a specialized version of BNF. If it assumed an active role in the property system, then it could be used as a resource to simplify coding individual xml files, since default values, types, and other properties could be sourced from the central dictionary. We can create a dictionary in XML, but then we have the problem of maintaining properties in multiple locations. Another alternative is to allow documentation attributes for all properties: controls doc=aircraft control inputs aileron doc=aileron position: left=-1, neutral=0,right=10/aileron /controls and so on. That's the inelegant, English-only solution; the more elegant solution is to document in external files, but then we get maintenance issues again. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] copying properties
Norman Vine writes: 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 No, that's wrong -- all of the nodes are created on demand except for the root node. This will work just fine: SGPropertyNode * saved_props = new SGPropertyNode(); copyProperties(props, saved_props); All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
David Megginson wrote: [EMAIL PROTECTED] writes: FWIW, I found 1 a bit quiet, although audiable over the idling engine, so I set it to 2, which was audiable over the full throttle engine. Thats on windows though, although I could certainly make it out over the idling engine when I tested on Linux at 2. Hmm. I wonder what the issue is. At 10, I can hear, perhaps, 75% of it over the idling engine, but I still have to strain to make it out. It's also a matter of what you want to simulate. I think up until now we simulate the situation where the pilot doesn't wear headphones. With ATC that is becoming inpractical. So it might be time to tune down engine, squeel, noise at all. I don't know enough about the audio side to troubleshoot this easily. This might be a driver issue (either kernel or plib). It sounds like your volume scales linear instead of logarithmic ... Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
Erik Hofman writes: This might be a driver issue (either kernel or plib). It sounds like your volume scales linear instead of logarithmic ... That's a reasonable guess. What would the next step be? All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
David Megginson wrote: Erik Hofman writes: This might be a driver issue (either kernel or plib). It sounds like your volume scales linear instead of logarithmic ... That's a reasonable guess. What would the next step be? What kernel driver do you use: OSS or ALSA? And which hardware? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] What's in the job jar?
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 that this is not a *complete* dump too :-( I find that massaging this file a little is even handier, for example the attached script creates this from the file the above patch produces and can be easily modified to do other things with the properties Not everything that is read from an XML file resides in the main property tree; some subsystems also use XML files for initial configuration information. 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' Hence shouldn't the subsytems also stem from global-get_props() too ? Are there reasons that it isn't done this way ? Efficiency isn't a problem as the subsytem can just cache a node to serve as it's local root. Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Distributed Interactive Simulation Interface
Hi, I'm just looking for a few pointers to start off. I see that the DIS interface has been mentioned as a 'would like to have' feature. I have had a quick look at the code and I guess the interface would be similar, in a way, to the net_send.cxx code for the OLK stuff, in that it receives state data from over the network and creates an entity within FG to allow it to be rendered. I guess some of you will have thought about this before aswell. If anyone has any ideas / suggestions / or if you've already done it or are working on it, I would love to hear what you have to say. Best regards, Dave = Tel: +44 (0) 7092 250 375 Fax: +44 (0) 7092 250 375 __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] properties documentation
Doxygen would need to be tweaked a bit, since it is not set up for XML I started hunting for an XML documentation engine last night. All the ones I have found so far do only one page at a time. We want it to do the same thing that Doxygen does, which is to read through all the subdirectories, dump the XML into html files and build an index.html I'll put the Doxygen output from the C code up on my site as soon as I clean it up. It read the entire SimGear into a single 5MB html file ;-) Mike On Monday 23 December 2002 08:17, Jim Wilson wrote: Jon Berndt [EMAIL PROTECTED] said: 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 values, short descriptions, long descriptions, etc. I've seen Doxygen mentioned here previously, IIRC. I can vouch for its effectiveness as a documentation aid. Doxygen can produce a pretty detailed index. This would be a start, if nothing else. I also wonder if there shouldn't be a way to - dump at run time - the listing you ask for (for instance in a debug compile, one could have this capability). Yes and I think Doxygen sounds like a good thing. To be honest I don't really have much trouble figuring out what the properties are and if I need to know what sets/reads them, grep works fine. But it does seem as though a central dictionary (for lack of a better term) to which xml configs refer might yield some benifit for new programmers as well as simplifying the coding of xml files. Maybe even error checking. Again this is a topic I'm not familiar with...just asking the question. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] What's in the job jar?
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 Monday 23 December 2002 08:16, David Megginson wrote: 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 code modules I've written have JavaDoc-like comments attached in the *.hxx files -- those might be helpful. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] properties documentation
Doxygen would need to be tweaked a bit, since it is not set up for XML I Right. I was looking at it from another angle. That is, from the source code side. JSBSim uses properties and in the header we can probably document all the properties for a particular class. When Doxygen builds the docs from header comments, those will be included. Jon smime.p7s Description: application/pkcs7-signature
Re: [Flightgear-devel] ATC Sound
Erik Hofman writes: What kernel driver do you use: OSS or ALSA? OSS (kernel 2.4.20). And which hardware? Maestro3. Thanks, and all the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] What's in the job jar?
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 XML file to set up its internal state -- information that is of no use to the rest of the program and that cannot be changed without a reinit (i.e. use this texture with these UV coordinates for layer 3 of the instrument) -- it doesn't make sense to clutter the property tree with it. Those trees are usually deleted as soon as the subsystem is set up (i.e. they exist for perhaps 0.1 sec). We could just as easily use another format for internal initialization, but since the XML support is already available, it was the easiest route. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] properties documentation
Jon Berndt writes: Right. I was looking at it from another angle. That is, from the source code side. JSBSim uses properties and in the header we can probably document all the properties for a particular class. When Doxygen builds the docs from header comments, those will be included. Absolutely right; we just need a recommended way to document that. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
David Megginson wrote: Erik Hofman writes: What kernel driver do you use: OSS or ALSA? OSS (kernel 2.4.20). And which hardware? Maestro3. Hmm, according to this article the OSS drivers for the Meastr3 had problems on a Dell Latitude C800, but it is fairly old (speaking about Linux 2.4.9). I think I can rule out plib, but I couldn't find much more about it. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
David Megginson wrote: Erik Hofman writes: What kernel driver do you use: OSS or ALSA? OSS (kernel 2.4.20). And which hardware? Maestro3. Article: http://www.zabbo.net/pipermail/maestro-users/2001-August/000433.html Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
Erik Hofman writes: Hmm, according to this article the OSS drivers for the Meastr3 had problems on a Dell Latitude C800, but it is fairly old (speaking about Linux 2.4.9). The article suggests that the maestro3 driver uses a lookup table. The thing is, I'm not having problems with the relative volumes of other sounds, only the ATIS. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
David Megginson wrote: Erik Hofman writes: Hmm, according to this article the OSS drivers for the Meastr3 had problems on a Dell Latitude C800, but it is fairly old (speaking about Linux 2.4.9). The article suggests that the maestro3 driver uses a lookup table. The thing is, I'm not having problems with the relative volumes of other sounds, only the ATIS. It's very difficult to tell then. Are you sure there aren't any other problems (I know the lads who used to develop the Gravis UltraSound drivers at first didn't notice they used linear volume either), it's not that obvious all the time. Another question, do you use esd or something like that? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
Erik Hofman writes: Another question, do you use esd or something like that? No -- I keep it disabled (or else FlightGear wouldn't work at all). It could well be that my driver is using linear volume, but then wouldn't the other relative volumes for FlightGear be wrong as well? All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
David Megginson wrote: Erik Hofman writes: Another question, do you use esd or something like that? No -- I keep it disabled (or else FlightGear wouldn't work at all). It could well be that my driver is using linear volume, but then wouldn't the other relative volumes for FlightGear be wrong as well? Yes, but like I said, it's hard to know unless you are aware of wha you're looking for. The mixer volume *sounds* linear to you? If so, then it's actually logarithmic. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
David Megginson wrote: Erik Hofman writes: Yes, but like I said, it's hard to know unless you are aware of wha you're looking for. The mixer volume *sounds* linear to you? If so, then it's actually logarithmic. Yes, as far as I can tell, it sounds linear. You are not making it easy for me ... To be honnest, I can't think of an explaination anymore. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
Erik Hofman writes: You are not making it easy for me ... To be honnest, I can't think of an explaination anymore. OK, as long as no one else is reporting the same problem, we can leave it for now. Thanks, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
David Megginson wrote: Erik Hofman writes: You are not making it easy for me ... To be honnest, I can't think of an explaination anymore. OK, as long as no one else is reporting the same problem, we can leave it for now. Just one more thing: Make sure bass and treble aren't amplified in the mixer panel. Speech will fall in the section that isn't amplified and because of the amplification of bass and treble one will automatically turn down the master volume, cause the speech section to be very soft! Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
Erik Hofman writes: You are not making it easy for me ... To be honnest, I can't think of an explaination anymore. OK, as long as no one else is reporting the same problem, we can leave it for now. Just one more thing: Make sure bass and treble aren't amplified in the mixer panel. Nope. Thanks, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
On Monday, December 23, 2002, at 02:14 pm, David Megginson wrote: Hmm. I wonder what the issue is. At 10, I can hear, perhaps, 75% of it over the idling engine, but I still have to strain to make it out. I don't know enough about the audio side to troubleshoot this easily. I would just like to corroborate David's results, I thought ATC was broken until I realized I could *just* hear it over the engine noise. This is on Linux with ALSA, all the other FG sounds have a 'normal' volume. HH James -- The lack of planning on your part does not constitute to an emergency on mine ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC Sound
James Turner writes: I would just like to corroborate David's results, I thought ATC was broken until I realized I could *just* hear it over the engine noise. This is on Linux with ALSA, all the other FG sounds have a 'normal' volume. So we're seeing the problem with both ALSA and OSS. Now, I'm using a fairly recent CVS plib -- could this be simply a plib versioning problem? All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Patch to property-assign command
Here is a patch that allows assignment from one property in the tree to another property. Also put a check in there so that FG no longer segfaults if the value to be assigned is not defined in the XML. Usage Example: commandproperty-assign/command property/sim/destination-property-value/property property/sim/source-property-value/property http://www.spiderbark.com/fgfs/property-assign-patch.gz Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
