Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4
On lun 2 juin 2008, Tim Moore wrote: Update of /var/cvs/FlightGear-0.9/source/src/FDM/JSBSim/models/flight_control In directory baron:/tmp/cvs-serv2999/src/FDM/JSBSim/models/flight_control Modified Files: FGActuator.cpp FGFCSComponent.h Log Message: Clean up header file use of iostream and using declarations Replace include iostream with istream, ostream and/or iosfwd as appropriate. Remove using namespace std and using std::foo from header files. Does this will be compatible with actual JSBSim development ? -- Gérard http://pagesperso-orange.fr/GRTux/ J'ai décidé d'être heureux parce que c'est bon pour la santé. Voltaire - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4
* gerard robin -- Thursday 05 June 2008: Does this will be compatible with actual JSBSim development ? No, it will get overwritten with the next JSBSim update. There's a reason why commits to externally maintained parts of fgfs (nasal, jsbsim) used to be taboo, just like commits to parts which are strictly maintained by a single person or small group (YASim). (UIUC may no longer belong to either group, as it seems to be unmaintained.) The right thing would have been to ask the responsible maintainers, to have them make the changes in their repositories, and then to forward port that. But then again, times change, and maybe all that is no longer true ... m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4
- Curtis Olson [EMAIL PROTECTED] a écrit : On Thu, Jun 5, 2008 at 10:22 AM, Melchior FRANZ wrote: * gerard robin -- Thursday 05 June 2008: Does this will be compatible with actual JSBSim development ? No, it will get overwritten with the next JSBSim update. There's a reason why commits to externally maintained parts of fgfs (nasal, jsbsim) used to be taboo [snip] The right thing would have been to ask the responsible maintainers, to have them make the changes in their repositories, and then to forward port that. [snip] Tim has already been made aware that changes to JSBsim need to be submitted upstream or they will be lost the next time we sync with their code. I assume he has made contact there so these changes (if important) aren't lost in the future. It's good to see a few others besides myself watching to catch things like this. These changes are very unfortunate. Like it or not, cin, cerr and cout are defined in iostream under MSVC. FG is no longer compilable for me :-( -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery - album photo http://fgsd.sourceforge.net/ FlightGear Scenery Designer - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Scotland Scenery
Hi All, For my own amusement, I generated some scenery for Scotland using the GSHHS coastline and OpenStreetMap for roads. Scotland greatly benefits from using GSHHS coastline, as the VMAP0 data doesn't include many of the small islands on the west coast. There are sufficiently few roads that the OSM dataset works quite well also - you can even see some roundabouts! For those who might be interested in doing some flying in Scotland, it is available here: http://flightgear.mxchange.org/stuart/scotland.tar.gz (35MB) Many thanks to Roland Haeder for hosting it. Note that the scenery package is only the Terrain part, and doesn't include any Objects. It should be uncompressed into the Terrain sub-directory of your $FG_SCENERY (e.g. data/Scenery). As always, objects should be downloaded from http://scenemodels.flightgear.org/. For those unfamiliar with Scotland, there is a small suggested flight around my home city of Edinburgh here: As suggested flight for those who have downloaded both the scenery and objects is this: http://wiki.flightgear.org/flightgear_wiki/index.php?title=Suggested_Flights#Scotland_-_Edinburgh_to_Dundee I'd also highly recommend taking off from Oban and As suggested flight for those who have downloaded both the scenery and objects is this: flying in the mountains in a fast military jet. After all, that's what the RAF do! The fact that I was able to generate scenery using TerraGear for amusement is a testament to the effort that the Custom Scenery team (http://www.custom-scenery.org/) have made to make TerraGear easier to use. Many thanks to Martin and Ralf for their work. -Stuart __ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] automated response
Vielen Dank fuer Ihre Nachricht. Ich bin zur Zeit nicht im Buero und habe erst ab dem 09.06.2008 wieder Gelegenheit, meine E-Mails abzurufen. Bitte wenden Sie sich daher an meine Kollegen, die Ihnen gerne weiterhelfen werden. Dies ist eine automatisch generierte E-Mail. Sie erhalten diese Nachricht nur einmal, selbst wenn Sie waehrend meiner Abwesenheit mehrere E-Mails an mich richten. Thank you for your mail. I am abroad until the 09th of June 2008. This is an automatic reply, you will receive it only once. Mit freundlichen Gruessen/ yours sincerely Tim Kober - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fw: [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4
Begin forwarded message: Date: Thu, 5 Jun 2008 22:27:25 +0200 From: Tim Moore [EMAIL PROTECTED] To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4 On Thu, 5 Jun 2008 22:15:41 +0200 (CEST) Frederic Bouvier [EMAIL PROTECTED] wrote: - Curtis Olson [EMAIL PROTECTED] a écrit : On Thu, Jun 5, 2008 at 10:22 AM, Melchior FRANZ wrote: * gerard robin -- Thursday 05 June 2008: Does this will be compatible with actual JSBSim development ? No, it will get overwritten with the next JSBSim update. There's a reason why commits to externally maintained parts of fgfs (nasal, jsbsim) used to be taboo [snip] The right thing would have been to ask the responsible maintainers, to have them make the changes in their repositories, and then to forward port that. [snip] Tim has already been made aware that changes to JSBsim need to be submitted upstream or they will be lost the next time we sync with their code. I assume he has made contact there so these changes (if important) aren't lost in the future. It's good to see a few others besides myself watching to catch things like this. These changes are very unfortunate. Like it or not, cin, cerr and cout are defined in iostream under MSVC. FG is no longer compilable for me :-( -Fred I know that cin, cerr and cout are defined in iostream; they're defined that way in every conforming C++ implementation. But they are only used in a very few places and don't need to be sucked into every file. Can you be more specific about the problems you are seeing? Tim - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4
On Thu, 5 Jun 2008 17:22:33 +0200 Melchior FRANZ [EMAIL PROTECTED] wrote: * gerard robin -- Thursday 05 June 2008: Does this will be compatible with actual JSBSim development ? No, it will get overwritten with the next JSBSim update. There's a reason why commits to externally maintained parts of fgfs (nasal, jsbsim) used to be taboo, just like commits to parts which are strictly maintained by a single person or small group (YASim). (UIUC may no longer belong to either group, as it seems to be unmaintained.) The right thing would have been to ask the responsible maintainers, to have them make the changes in their repositories, and then to forward port that. But then again, times change, and maybe all that is no longer true ... m. I never got the memo that large parts of the tree were off limits. I agree that a substantive change should be vetted by owners first, but I don't really see the point for fairly cosmetic changes. On the other hand, why is JSBSim in our CVS at all if new versions are brought in in this way? Tim - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4
Frederic Bouvier schrieb am 05.06.2008 22:15: These changes are very unfortunate. Like it or not, cin, cerr and cout are defined in iostream under MSVC. FG is no longer compilable for me :-( -Fred Hi Fred, don't know what is different here, but yesterday evening I compiled fresh cvs osg-fg on MSVC-express without problem (based in Olaf Flebbes project files). I have the problem, that some parts of the static scenery isn't found (alcatraz, stadium near KSFO and many others, but not all). The fg-root path is added twice, so I changed my starting directory, that fg-root can be added twice (fg-root=../../fg-cvs/data). I don't know, when this problem started, my last build was rather old... Maik - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4
On Thu, 5 Jun 2008 22:15:41 +0200 (CEST) Frederic Bouvier [EMAIL PROTECTED] wrote: - Curtis Olson [EMAIL PROTECTED] a écrit : On Thu, Jun 5, 2008 at 10:22 AM, Melchior FRANZ wrote: * gerard robin -- Thursday 05 June 2008: Does this will be compatible with actual JSBSim development ? No, it will get overwritten with the next JSBSim update. There's a reason why commits to externally maintained parts of fgfs (nasal, jsbsim) used to be taboo [snip] The right thing would have been to ask the responsible maintainers, to have them make the changes in their repositories, and then to forward port that. [snip] Tim has already been made aware that changes to JSBsim need to be submitted upstream or they will be lost the next time we sync with their code. I assume he has made contact there so these changes (if important) aren't lost in the future. It's good to see a few others besides myself watching to catch things like this. These changes are very unfortunate. Like it or not, cin, cerr and cout are defined in iostream under MSVC. FG is no longer compilable for me :-( -Fred I know that cin, cerr and cout are defined in iostream; they're defined that way in every conforming C++ implementation. But they are only used in a very few places and don't need to be sucked into every file. Can you be more specific about the problems you are seeing? Tim - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4
* Tim Moore -- Thursday 05 June 2008: I never got the memo that large parts of the tree were off limits. In the old days one didn't need memos for that. One had to be around long enough before one even got CVS access. Enough time to learn the rules. Not your fault, of course, that this has changed now. I don't really see the point for fairly cosmetic changes. The point is: what you consider an improvement might not be seen as such by the code *owner*. And the owner's wish usually trumps a contributor's. On the other hand, why is JSBSim in our CVS at all if new versions are brought in in this way? What way would you prefer? Some projects are on other servers, and CVS has no way to import them directly. They need to be copied in. This hasn't been a problem in the past. You just have to know that making changes in those copies is totally pointless. m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Scotland Scenery
Hi Stuart, thank you for sharing this as I am especially interested in all scenery which uses OSM data. Last year I bought a cheap handheld GPS device and collected some local data for OSM and uploaded them - but what a rapid development here around Bremen until now, very very busy people improving the data every day. Even forrests and rivers are represented in a very nice way in the local dataset. That is why I hope that in some years - regarding the poor man-power, only 2 developers - we can use OSM data at good data-represented areas. Stuart Buchanan schrieb: Hi All, For my own amusement, I generated some scenery for Scotland using the GSHHS coastline and OpenStreetMap for roads. Scotland greatly benefits from using GSHHS coastline, as the VMAP0 data doesn't include many of the small islands on the west coast. There are sufficiently few roads that the OSM dataset works quite well also - you can even see some roundabouts! Yes, saw them - and the difference between normal streets and motorways (double lines). Moreover those streets are smoother than the ones we have now. For those who might be interested in doing some flying in Scotland, it is available here: http://flightgear.mxchange.org/stuart/scotland.tar.gz (35MB) Many thanks to Roland Haeder for hosting it. .. The fact that I was able to generate scenery using TerraGear for amusement is a testament to the effort that the Custom Scenery team (http://www.custom-scenery.org/) have made to make TerraGear easier to use. Many thanks to Martin and Ralf for their work. -Stuart Thanks a lot to all who are working for or supporting getting OSM data (not only streets) into FlightGear. Georg EDDW (Beside this, simflying this scenery is a real joy as the landscape is fascinating, especially the contrast between sea and mountaineous areas. I hope you'll spend some more nice models for this area, the scenery deserves it :-) ) - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4
On jeu 5 juin 2008, Melchior FRANZ wrote: On the other hand, why is JSBSim in our CVS at all if new versions are brought in in this way? What way would you prefer? Some projects are on other servers, and CVS has no way to import them directly. They need to be copied in. This hasn't been a problem in the past. You just have to know that making changes in those copies is totally pointless. m. And i fear, that process will increase the distance between JSBSim and FG, and probably going to a JSBSim use in a stand alone way ONLY, working with FG through an external communication. Today the users who are using JSBSim with FG could include the most recent original code of it into FG, in to get a running updated FG+JSBSim (last version) What will happen now with that update from Tim which is not, to me, only cosmetic. Cheers -- Gérard http://pagesperso-orange.fr/GRTux/ J'ai décidé d'être heureux parce que c'est bon pour la santé. Voltaire - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp
I don't have all of this conversation, but here are a few items: 1) I'll be glad to make changes in JSBSim as needed. This is the first I've read of the changes. Which of the posts here is the pertinent one? 2) Dave Culp (and others?) have actually been using the latest JSBSim in FlightGear for a while, now, for testing. I've compiled it in here at home, too, but haven't really used it much. I have access to the FlightGear CVS tree in the JSBSim directory. It's really my fault that the current JSBSim is not in FlightGear CVS, and I apologize for the foot-dragging. Jon - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4
On Thu, 5 Jun 2008 23:11:03 +0200 Melchior FRANZ [EMAIL PROTECTED] wrote: * Tim Moore -- Thursday 05 June 2008: I never got the memo that large parts of the tree were off limits. In the old days one didn't need memos for that. One had to be around long enough before one even got CVS access. Enough time to learn the rules. Not your fault, of course, that this has changed now. I don't really see the point for fairly cosmetic changes. The point is: what you consider an improvement might not be seen as such by the code *owner*. And the owner's wish usually trumps a contributor's. I understand, and I didn't really understand the situation wrt to JSBSim. On the other hand, why is JSBSim in our CVS at all if new versions are brought in in this way? What way would you prefer? Some projects are on other servers, and CVS has no way to import them directly. They need to be copied in. This hasn't been a problem in the past. You just have to know that making changes in those copies is totally pointless. If we really have no capability or desire to make local changes to JSBSim (for example), then I'd prefer that we'd say get JSBSim from the JSBSim CVS server like we do with plib. At the very least it should have imported on a vendor branch into our CVS so that local changes could be easily maintained. Tim - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
