Hi,
I want to start to integrate an alternative terrain engine with flightgear (http://baron.flightgear.org/pipermail/flightgear-devel/2004-September/030853.html)
That's great, I already wondered what happened to that project. This would really be a great addition for FlightGear.
For this, I need to adapt flightgear to use an abstract terrain API, which
will encapsulate the current and new terrain engine transparently.
As I understood you where using your own SceneGraph engine, what would be the best way to handle this;
1. Adding a SceneGraph API 2. You change your code to use plib 3. FlightGear starts to use your SceneGraph library
As this will involve some (mostly small) changes all over the place, it would be great if I could work on a CVS branch.
Hmm, I've seen work on branches and they have their pro's and con's. I'm not sure I like branches all that much.
Would that be possible? What is the policy for gainining CVS write access to the fgfs repository?
Curtis?
Erik
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
