[Flightgear-devel] Did anyone ever do a simple psuedo code roadmap of the major flightgear program sections and an index to the modules they are compiled from?
Did anyone ever do a simple psuedo code roadmap of the major flightgear program sections and an index to the modules they are compiled from? If so where can I download it or would someone post it to this list as a text message? Thanks geopilot www.GlobalBoiling.com for daily images about hurricanes, globalwarming and the melting poles. www.ElectricQuakes.com daily solar and earthquake images. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Chaos in FG development [was: Bomb patch for vulcanb2]
* leee -- Saturday 14 July 2007: Perhaps FG has reached the point where it positively needs some sort of oversight management and planning, as seems to happen with many, if not most, large-scale Open-source projects e.g. Apache, Wine etc. I think that projects where this works always have a few sponsored (paid) developers. Of course, you can tell those on what to work. But you can't tell unpaid developers. What if some project manager says the next point on our plan is to beef up weather modeling -- do you think that Andy, Fred, Mathias, Maik, etc. will then all work on weather stuff? Even though they have no interest in that region (other than having it work nicely when they run fgfs themselves)? I have insight in a few F/OSS projects, and everywhere it's the developers who make their plans. Each on their own. Except paid developers, where it's sometimes the sponsor. I for one don't really have a TODO list, though I often say I'd put something there. :-) I decide on which things to work on next as I run into them. Segfaults are often a motivation to look into some code. Sometimes I need/want a feature and find that it doesn't work as I think it should, and work on that. Today I just thought that I'd like to do something nice, something with Nasal and placing models. (False alarm -- I haven't done anything. Well, not for FlightGear that is. But it's not too late ... :-) m. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Chaos in FG development [was: Bomb patch for vulcanb2]
Well defining ranges of reserved attachable variables and hooks would help to keep things backward compatable. Define chunks of variables in chunks of 50 (allways define more than you think you need for the future.) To much MANAGEMENT though will slow down contributions. On Sat, 14 Jul 2007 10:00 am, leee wrote: On Friday 13 July 2007 21:39, Melchior FRANZ wrote: [snip...] Coders are all the time adding new code, which can sometimes be chaotic. On the other hand, coders are also fixing chaotic code. All the time. Yes, there is some, but as long as you aren't actually working on the code, it shouldn't really concern you much. Are you aware of people who were scared away by the chaos, and decided not to contribute because of it? Which files or subsystems do you find most chaotic? I'm sure we can work on those. m. I think this is a very important observation by Melchior, although he and I might disagree on both the degree and effects of the 'chaos' in FG :) The earliest FG mailing list posts I have archived date from late 2002 so I reckon that is when I started contributing to FG and since then there has been a huge amount of development in FG, all to it's benefit and leading to a much more capable and effective package. However, as well as the software developers who are developing the FG platform/framework itself there are those who use and develop _for_ the FG platform, for example aircraft developers who make aircraft for FG and development research projects that use FG as their environmental framework. For this group of people/users I would say that the FG platform has become much more chaotic and difficult to use or to develop for unless they 'freeze' a local version and don't try to keep track of FG development after the freeze. Doing this though, will make their work incompatible with future versions of FG, which cannot be a good thing. It is difficult to see a good answer to this issue. On the one hand, planning ahead and setting specific objectives for the FG developers to work towards would give known objectives and a clear development path but at the same time would constrain developers to working on what the plan requires, which may not be what the individuals concerned are interested in. On the other hand, if FG development carries on as it is now, with developers able to follow any line of development they find interesting there will be many new valuable developments but it will continue to be unpredictable and chaotic. Perhaps FG has reached the point where it positively needs some sort of oversight management and planning, as seems to happen with many, if not most, large-scale Open-source projects e.g. Apache, Wine etc. I personally hate to be even a little bit critical of FG and it's community of developers because FG is a tremendous achievement by a lot of very skilled and talented individuals but it's because I do care about FG that I feel obliged to comment when I believe I see something that could harm the project. LeeE - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel www.GlobalBoiling.com for daily images about hurricanes, globalwarming and the melting poles. www.ElectricQuakes.com daily solar and earthquake images. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgcom
Hi Emmanuel, On Fri, Jul 13, 2007 at 09:15:23PM +0200, BARANGER Emmanuel wrote: I'm sorry but the mail of fgcom programmer is not avaible. I post my message here. uuups... this should be mentioned on the web site. I will double check this on monday. My mail address ist [EMAIL PROTECTED] Hello, First of all to ask you forgiveness for my bad English. Actually I use Google to translate for me because I do not speak English. Oh. And I do not speak french so I hope google will forgive me for my bad english :-) Thanks for your testing! I will take a look at this on monday, too. Until now the code is really alpha code and my C knowledge is not very well. Due to my 32bit Linux I cannot test why the problem exists but I think it is a simple problem in themake process... try to compile without -L/usr/lib64 -L/usr/lib64 (by hand?). The -L/usr/lib64 -L/usr/lib64 are inserted by the macro XMLRPC_LIBS:=$(shell xmlrpc-c-config libwww-client --libs) which automaticly generates the lines for the library dependencies for libxmlrpc. I think I should use my own simple implementation instead og libxmlrpc. Regards, Holger [EMAIL PROTECTED] src]$ make gcc -O2 -DDEBUG -D'SVN_REV=18M' -c fgcom.c gcc -O2 -DDEBUG -D'SVN_REV=18M' -I/usr/include -c xmlrpc.c gcc -s fgcom.o xmlrpc.o -o fgcom -lm -liaxclient -lportaudio -lspeex -lgsm -L/usr/lib64 -L/usr/lib64 -lwwwssl -lwwwxml -lxmltok -lxmlparse -lwwwzip -lwwwinit -lwwwapp -lwwwhtml -lwwwtelnet -lwwwnews -lwwwhttp -lwwwmime -lwwwgopher -lwwwftp -lwwwfile -lwwwdir -lwwwcache -lwwwstream -lwwwmux -lwwwtrans -lwwwcore -lwwwutils -lmd5 -ldl -lz -L/usr/lib64 -lssl -lcrypto -L/usr/lib64 -lcurl -L/usr/lib64 -lxmlrpc_client -lxmlrpc -lxmlrpc_util -lxmlrpc_xmlparse -lxmlrpc_xmltok -Wl,--rpath -Wl,/usr/lib /usr/bin/ld: warning: libportaudio.so.0, needed by /usr/lib64/libiaxclient.so, may conflict with libportaudio.so.2 [EMAIL PROTECTED] src]$ In spite of that compilation is finished and FGCOM is present. But with the launching of FGCOM here the result: [EMAIL PROTECTED] src]$ ./fgcom ./fgcom - a communication radio based on VoIP with IAX/Asterisk (c)2007 by H. Wirtz [EMAIL PROTECTED] Version 0.9 build 18M Using iaxclient library Version CVS-2006/09/17-16:59 JACK tmpdir identified as [/tmp] Erreur de segmentation [EMAIL PROTECTED] src]$ Last precision, my system: [EMAIL PROTECTED] src]$ uname -a Linux localhost 2.6.21-4mdvRT #1 PREEMPT Sun Jul 8 01:19:20 CEST 2007 x86_64 AMD Sempron(tm) Processor 3100+ GNU/Linux [EMAIL PROTECTED] src]$ gcc --version gcc (GCC) 4.2.1 20070704 (prerelease) (4.2.1-3mdv2008.0) Copyright © 2007 Free Software Foundation, Inc. Ce logiciel est libre; voir les sources pour les conditions de copie. Il n'y a PAS GARANTIE; ni implicite pour le MARCHANDAGE ou pour un BUT PARTICULIER. [EMAIL PROTECTED] src]$ By hoping that these indications could be useful. Best regards. Emmanuel -- BARANGER Emmanuel http://helijah.free.fr http://helijah.free.fr/Pack_3D http://helijah.free.fr/flightgear/flightgear.htm http://helijah.free.fr/flightgear/H4-Hercules.htm http://helijah.free.fr/flightgear/hangar.htm - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- # ## ## Holger Wirtz Phone : (+49 30) 884299-40 ## ## ## ### ## DFN-Verein Fax : (+49 30) 884299-70 ## ## ## Stresemannstr. 78E-Mail: [EMAIL PROTECTED] ## ## ## ## ### 10963 Berlin # ## ## ## GERMANY WWW : http://www.dfn.de GPG-Fingerprint: ABFA 1F51 DD8D 503C 85DC 0C51 E961 79E2 6685 9BCF - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear data
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-08_06:52:37 (helijah) /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/COPYING -New plane to test particles OSG =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-08_06:52:38 (helijah) /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/pa100-base-fire.xml /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/pa100-base.xml /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/pa100-fire-set.xml /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/pa100-splash.rgb /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/pa100-yasim-set.xml -New plane to test particles OSG =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-08_06:52:39 (helijah) /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Read-Me.txt /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/pa100-yasim.xml /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/thumbnail.jpg -New plane to test particles OSG =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-08_06:52:40 (helijah) /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/FJ3_03.rgb /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/color.rgb /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/glass.rgb /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/pa100.ac -New plane to test particles OSG =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-08_06:52:41 (helijah) /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/pa100-fire.xml /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/pa100.xml /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/prop.rgb /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/wheels.rgb -New plane to test particles OSG =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-08_06:52:42 (helijah) /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/fire/fire.osg /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/fire/fire.xml /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Models/fire/smoke.rgb /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Nasal/doors.nas /var/cvs/FlightGear-0.9/data/Aircraft/payen-pa100/Nasal/pa100-keyboard.xml -New plane to test particles OSG =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-08_13:15:02 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/ufo/cam.nas /var/cvs/FlightGear-0.9/data/Aircraft/ufo/mibs-set.xml /var/cvs/FlightGear-0.9/data/Aircraft/ufo/Dialogs/Attic/campanel.xml /var/cvs/FlightGear-0.9/data/Aircraft/ufo/Models/Attic/camera.ac /var/cvs/FlightGear-0.9/data/Aircraft/ufo/Models/Attic/camera.xml Syd's MIBS: A camera tool for making fgfs videos (heavily used by Michelle) and for tracking MP and AI aircraft. It's planned to include this into the regular ufo, but for now it's better to keep them separated. Comes with its own panel, which (hopefully) is self-explaining. Shouldn't be announced on the fgfs page as separate aircraft (if that's possible). Work in progress ... =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-08_19:14:55 (sydadams) /var/cvs/FlightGear-0.9/data/Aircraft/Citation-Bravo/Models/Attic/Bravo1.rgb Remodelling Bravo ... attempting to cut down on textures... Added opening cabin door , seats , windows ... Added chrome again since it works in OSG ... panel lettering will be back shortly ... =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-08_19:14:57 (sydadams) /var/cvs/FlightGear-0.9/data/Aircraft/Citation-Bravo/Models/Attic/chrome.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Citation-Bravo/Models/Attic/chrome1.rgb Remodelling Bravo ... attempting to cut down on textures... Added opening cabin door , seats , windows ... Added chrome again since it works in OSG ... panel lettering will be back shortly ... =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-09_11:16:52 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/A-10/README.armament Alexis BORY: Added some Willy Pete rockets =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-07-09_11:16:54 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/ext-stores.xml /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/GAU-8A/gau-8a-submodels.xml /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/GAU-8A/puff-impact.ac /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/GAU-8A/puff-new.rgb /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/GAU-8A/smoke-impact.xml /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/GAU-8A/subsubmodels.xml /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/LAU-68/LAU-68-submodels.xml /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/LAU-68/fire-impact.ac /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/LAU-68/fire-impact.xml /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/LAU-68/puff-impact.ac
