I give up. Let's just have the nonsensical directory layout.
It's not the only bad design in fgfs, and I'm the only one
who cares about it, anyway. But here's a final comparison
for your entertainment (and for the archive, so that I can
occasionally point to it ;-):



Solution 1 -- proposed and defended by Ralf and Martin:
-------------------------------------------------------

    Airports/L/O/X/LOXA.ils.xml
                  /LOXA.parking.xml
                  /LOXA.rwyuse.xml
                  /LOXA.twr.xml
                  /LOXA.threshold.xml
                  /LOXN.ils.xml
                  /LOXN.parking.xml
                  /LOXN.rwyuse.xml
                  /LOXN.twr.xml
                  /LOXN.threshold.xml
                  /LOXT.ils.xml
                  /LOXT.parking.xml
                  /LOXT.rwyuse.xml
                  /LOXT.twr.xml
                  /LOXT.threshold.xml
                  /LOXZ.ils.xml
                  /LOXZ.parking.xml
                  /LOXZ.rwyuse.xml
                  /LOXZ.twr.xml
                  /LOXZ.threshold.xml

Characteristics:
 - lots of files per level (messy)
 - natural grouping done by prefixes, rather than directories (the latter
   of which were invented for that purpose and come at *no* costs)
 - tower abbreviated as twr (not saving *any* space)

Technical argument:
 - "it's too late, we don't want to change it anymore"




Solution 2 -- proposed by /me:
------------------------------

    Airports/L/O/X/A/ils.xml
                     parking.xml
                     rwyuse.xml
                     tower.xml
                     threshold.xml
    Airports/L/O/X/N/ils.xml
                     parking.xml
                     rwyuse.xml
                     tower.xml
                     threshold.xml
    Airports/L/O/X/T/ils.xml
                     parking.xml
                     rwyuse.xml
                     tower.xml
                     threshold.xml
    Airports/L/O/X/Z/ils.xml
                     parking.xml
                     rwyuse.xml
                     tower.xml
                     threshold.xml


Characteristics *and* technical arguments:
 - directory per airport for natural grouping and clear layout
 - consistent and logical: all ICAO/ID letters are treated the same way
 - easy path creation e.g. in Nasal



Or maybe we should use prefixes instead of directories at other
occasions as well, if that concept is considered superior.
Let's see:

  $FG_ROOT/Aircraft/bo105.splash.rgb
  $FG_ROOT/Aircraft/bo105.thumbnail.rgb
  $FG_ROOT/Aircraft/bo105.fdm.xml
  $FG_ROOT/Aircraft/b1900d.splash.rgb
  $FG_ROOT/Aircraft/b1900d.thumbnail.rgb
  $FG_ROOT/Aircraft/b1900d.fdm.xml
  $FG_ROOT/Aircraft/concorde.splash.rgb
  $FG_ROOT/Aircraft/concorde.thumbnail.rgb
  $FG_ROOT/Aircraft/concorde.fdm.x ml

Yummy.  :-)

m.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users

Reply via email to