Jim Wilson writes: >Actually, on this matrix topic, been thinking about whether we should just >build a few optimized routines (for 3x3 work) into simgear. It would be good >to move all the custom matrix manipulators out to simgear (was it you that >suggested this last week?) so that both the model and the viewer code can use >them.
Since these routines only run once or twice per iteration of the loop They really don't have to be 'super optimized' and I think my method of handling them as 3x3 and just filling in the 4th row and column by 'inspection' is probably good enough. Where these routines help is that I 'know' somethings about each of the matrices ahead of time that I take advantage of that a general purpose 3x3 set of routines would not be able to do. That said I am all for separating the math from the properties interface as much as possible and I think that we could probably create a 'number crunching core' SimGear 'Viewer' that was passed only numbers from the FlightGear 'Viewer' that provided the properties Interface to FGFS This SimGear Viewer would make it easier for other programs to interface to the FGFS scenery esp if and when we move the tile manager code to SimGear Cheers Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
