Hooray wrote in Tue Apr 10, 2012 8:39 pm:The added advantage is that components would be "self-contained", i.e. you could simply copy a whole component folder to a different aircraft, and everything needed/referenced would be automatically there - without having to resolve references. Ultimately, that would also allow people to more easily generalize stuff and move it out of aircraft-specific folders, into the "library" of aircraft resources (such as Instruments, or Instrument-3D, systems etc)
You have describe my initial motivation, for restructuring, better than i've done!
if you go to inside models/instruments folder for example, you could see its self contained. xml-s in the instrument directory and his resources, images and stuff inside "res" folder. the intention was to make instruments easy to move between A/C especialy for Airbuses, sharing equal cockpit.
This way we could even extract and have common systems like FBW on a Airbus-Common repository. On event of updated system Just copy the newly updated system folder and add it to your A/C...
The 320, had a duplicated estructure of the folders inside XML folder. It was crazy for me to develop, having constantly to change from A320neo/Models/Instruments/... to A320neo/XMLs/Models/Instruments/...