Csaba Halász wrote:
> Finally, there could be other programs that need scenery data, would
> you embed terrasync in each one? I view this as bad design.
By having a closer look at Thorsten's patches you'd realize that his
primary work was to turn the standalone program with hard-coded host-
and pathnames into a neatly configurable library. The interface
between this lib and FlightGear is pretty slim, it doesn't add much
overhead and you're free not to use it.
BTW, while I'm very much in favour of having FlightGear's various
subsystems split into distinct parts, I think the "bad design" claim
coming from you is pretty weak. Where was your voice when the Local
Weather subsystem was added ? There could be other programs that need
the same local weather, let's say multiple viewer instances on the same
FlightGear scenario.
Adding another 'wrapper' around libsgtsync, let's say a configurable
HLA interface, and removing the current one from FlightGear is
extremely cheap compared to making local weather multi-viewer
compatible. Just a random example, think about it ....
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
