Re: [Flightgear-devel] [Flightgear-users] Traffic Manager II

2008-07-28 Thread Jon Stockill
Martin Spott wrote: > Greg Hawkes wrote: > >> One solution to this problem is to create a shared database of every >> (well, every /regularly scheduled/) flight everywhere in the world. This >> idea is similar to FlightGear's world scenery database. That project >> claims to aim for world domin

Re: [Flightgear-devel] [Flightgear-users] Traffic Manager II

2008-07-28 Thread Martin Spott
Greg Hawkes wrote: > One solution to this problem is to create a shared database of every > (well, every /regularly scheduled/) flight everywhere in the world. This > idea is similar to FlightGear's world scenery database. That project > claims to aim for world domination, so why not have the s

Re: [Flightgear-devel] windows.h

2008-07-28 Thread Durk Talsma
On Sunday 27 July 2008 21:24, James Turner wrote: > > Incidentally, a minor rant - even in the past week, I've seen the 'XXX > is being worked on, person YYY has lots of changes which they haven't > committed for arbitrary (justifiable) reason ZZZ'. I'd like to get > involved in hacking on some ac

[Flightgear-devel] Project tracking

2008-07-28 Thread James Turner
(here's a can of worms, please forgive any erroneous assumptions I'm making) As someone new coming to FG, it's pretty tricky to get a handle on what's going on, what's being worked on, what needs fixed and so on. Of course this is an issue for all software projects, and there's different s

Re: [Flightgear-devel] [Flightgear-users] Traffic Manager II

2008-07-28 Thread Greg Hawkes
Durk Talsma wrote: So what is traffic manager II? Well the main difference is that it will become a lot easier for users to develop their own traffic. Instead of going through a complicated procedure of compiling a sequence of flights into an xml file, the new version just requires a plain text

[Flightgear-devel] Header cleanups (was Re: windows.h)

2008-07-28 Thread James Turner
On 28 Jul 2008, at 02:39, Tim Moore wrote: > I'm not sure what's going on in your example, as foo needs to be > defined > somewhere in order for wibble to inherit from it. Otherwise there's > serious bug > there. >> If we're requiring a never MSVC than that, I believe we're fine. And >> perha