Erik Hofman wrote:

Well, I object. How could I tell others to postpone their contribution until after the release of FlightGear 1.0 if you are allowed to add this rather comprehensive peace of code?


This is a fair point to make ...

1. Let me say though that this code was ready to go before the 0.9.9 release so it had already been waiting for some time. If you wait too long, the underlyiing structure can change and make it almost impossible to merge in this code later.

2. Ok, a kln89 is no garmin 530, however, a *real* working gps is a *huge* feature we are missing. I really wanted this to make it into the code before 1.0.

3. I have some of my own selfish reasons for wanting to see the gps code get added, because it has the potential to be a big benefit to some of the other projects I'm involved in.

I understand you could build a strong argument in the other direction too, but in this case there was enough advantages in my view to tip the scales in favor of adding it.

Curt.

--
Curtis Olson        http://www.flightgear.org/~curt
HumanFIRST Program  http://www.humanfirst.umn.edu/
FlightGear Project  http://www.flightgear.org
Unique text:        2f585eeea02e2c79d7b1d8c4963bae2d


_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to