On Wednesday 31 December 1969 06:59 pm, you wrote: > > Contributions for the other init files are very welcome. > > When adapting the Beech99 init file for the Marchetti i encountered that > there appears no real standard on where the panel files do ahve to reside. > C310 panel resides in Aircraft/c310, C182 panel resides in > Aircraft/c182/Panels - and it is only one file. > > quickstep: 16:59:57 /home/fgfsbase> find Aircraft -iname \*panel\* > Aircraft/Instruments/Textures/panel-mini-bg.rgb > Aircraft/Instruments/Textures/panel-trans-mini-bg.rgb > Aircraft/X15/Panels > Aircraft/X15/Panels/X15-panel.xml > Aircraft/c172/Panels > Aircraft/c172/Panels/c172-ifr-panel.xml > Aircraft/c172/Panels/c172-mini-panel.xml > Aircraft/c172/Panels/c172-trans-mini-panel.xml > Aircraft/c172/Panels/c172-vfr-panel.xml > > Aircraft/c172/Panels/c172r-panel.xml > Aircraft/c172/Panels/Textures/panel-bg.rgb > Aircraft/c172/Panels/Textures/panel-c172r-bg.rgb > Aircraft/c172/Panels/Textures/panel-mini-bg.rgb > Aircraft/c172/Panels/Textures/panel-trans-mini-bg.rgb > Aircraft/c182/Panels > Aircraft/c182/Panels/c182s-panel.xml > Aircraft/c182/Panels/Textures/panel-bg.rgb > Aircraft/c310/310-panel-bg.rgb > Aircraft/c310/c310-mini-panel.xml > Aircraft/c310/c310-vfr-panel.xml > > > Is this mixture of any purpose ? > > Martin.
No purpose, just an artifact of a disagreement about what the layout should be. I think the Panels directory is unecessary, David M thinks it should be in a different location altogether. I'd like to do a reorg of the directory structure after the release. I'll go with the flow on whatever the consensus is. It should be noted that my positon is based on a critique of the last release by an unamed party from the position of someone new to FGFS. My position: Aircraft/whatever should contain the Models/ for the airframe, Textures/ Sounds/ , anything *specific to the airframe*. Generic/reusable stuff should be directly under Aircraft/ , ie Aircraft/Instruments Aircraft/Sounds If there is nothing specific to the airframe, the directories are not needed. As far as panels goes, the names are unique, so it doesn't buy us much to have Aircraft/Panels unless there is a large number of alternates and even then it's debatable. 3D models, sounds, textures, et al that are scenery related, as opposed to aircraft related should be in the associated top level directory Anyway, like I said, I'll go with the flow on whatever the consensus is, but I would really prefer a situation where rm -rf Aircraft/whatever would remove an entire plane. Does it make sense? To me, yes. Is there any reason to uninstall a plane? Not for me, but some user (read "not developer")might have a reason. Is it "the right thing"? I'll leave that up to you guys. TTYL John _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
