[Flightgear-devel] former project policies

2007-11-21 Thread Melchior FRANZ
I've now written together some rules for aircraft developers that I used to consider official project policies. After recent difficulties to persuade developers to consider them, I will no longer care about them and will only fix buggy aircraft in my local checkout. That's why I put this only on

Re: [Flightgear-devel] former project policies

2007-11-21 Thread Melchior FRANZ
* gerard robin -- Wednesday 21 November 2007: I only wonder about = SGI textures (*.rgb) shall be aggressively since i remember getting trouble with that format Thought i have not tested it recently, [...] There was a problem with compressed splash textures, but that was a bug in fgfs

Re: [Flightgear-devel] former project policies

2007-11-21 Thread AnMaster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 About global settings: this would affect the generic HUD too right? Quite a few aircrafts prevents you from turing on the generic HUD (I agree that it may not be realistic for the aircraft, but it is very useful when you try an aircraft for the

Re: [Flightgear-devel] former project policies

2007-11-21 Thread Melchior FRANZ
* gerard robin -- Wednesday 21 November 2007: AND, the recommendation to use English is less easy when we are not English speaking , this will be an add on of work for the developer. I didn't say that filenames/comments/function-names shall be in perfect English, nor in English better than

Re: [Flightgear-devel] former project policies

2007-11-21 Thread Jon Stockill
Melchior FRANZ wrote: CVS isn't a dumping ground for secrets. Everything there should be open. And being open also means to be understandable by as big an audience as possible. I'm just not able to learn Greek, Chinese, Swahili, ... We all hate English, but it's the lowest common

Re: [Flightgear-devel] former project policies

2007-11-21 Thread Stewart Andreason
I was interested in finding out if my model followed the rules, and came up with a question: If I want to use a generic instrument, but need to modify the xml file slightly, would it be best to place that new instrument.xml file under the generic directory, or copy the entire instrument

Re: [Flightgear-devel] former project policies

2007-11-21 Thread Anders Gidenstam
On Wed, 21 Nov 2007, Stewart Andreason wrote: I am currently following the second option, as the rgb and ac files must be in the same directory to work. If you don't need to change the .ac or the textures you only need to copy the XML file. You'll need to add some '../'s to the path and a

Re: [Flightgear-devel] former project policies

2007-11-21 Thread Maik Justus
Hi, Melchior FRANZ schrieb am 21.11.2007 13:33: (Also, all aircraft should support startup in air, and I must admit that this doesn't even work for the bo105.) This is my fault, not yours. It's on my open point list (since a long time :-( ) Maik