muekoe wrote:but in the next weeks, I will push some updates and work on the new ND.
design-wise, the ND code still isn't quite there yet, so I would still postpone this a bit - it is better to coordinate things with Gijs and Hyde to keep on improving the existing ND, rather than re-implementing an airbus-specific one at the moment. Simply because things are very much in flux still - there's quite a bit of refactoring pending, and it seems that neither of us is going to tackle this anytime soon.
I can obviously not stop anybody from working with that code, but personally I would prefer to scratch off a handful of items from our todo list first - otherwise, this is going to be a maintenance problem in the mid-term:
http://wiki.flightgear.org/Canvas_ND_Fr ... evelopmentWorking on anything listed there should help prepare the design such that the framework becomes more aircraft agnostic, i.e. to support manufacturer-specific ND types.
Currently, we are simply not there yet - and some of the recent additions aren't exactly making this much easier unfortunately.
Speaking in non-coding terms: When we refactored the ND code, we explicitly wanted to support different makes/models for different aircraft using a single back-end and code base. And that's something that is already prepared in the design in several places, and it may seem straightforward to people not familiar with the code.
Here, you could say that the ND itself is the 3D model, while the "style" is analogous to a "livery" (texture pack).
The way things are implemented, we prepared support for "livery packs", and for easily creating new styles without having to touch the code.
However, currently there's still some work that needs to be done, and Gijs, Hyde and Soitanen have added features that need to be integrated properly first - you could say that they're working on the "3D model" still, so it's not such a good idea to create lots of "liveries" (styles) currently