2,561
edits
Recommended Property Tree Enhancements: Difference between revisions
Jump to navigation
Jump to search
Recommended Property Tree Enhancements (view source)
Revision as of 14:45, 30 October 2008
, 30 October 2008→Additional Ideas
| Line 112: | Line 112: | ||
* "default-working-dir" - default cwd if only filename specified without path info | * "default-working-dir" - default cwd if only filename specified without path info | ||
== | == Introducing Variables in PropertyList XML Files == | ||
* introducing the concept of "base/frame pointers" for property nodes (and possibly attributes) as described in [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg11307.html] would surely simplify PropertyList XML files tremendously and make them much more intuitive to work with (this is in fact conceptually pretty much identical to another suggestion, to provide basically the same facility for (non-relative, file system) paths and filenames provided in aircraft/PropertyList XML files, as posted in response[http://mail.flightgear.org/pipermail/flightgear-devel/2004-November/032299.html] to a request by C. Olson to enable aircraft to become more easily relocatable [http://mail.flightgear.org/pipermail/flightgear-devel/2004-November/032294.html] [http://mail.flightgear.org/pipermail/flightgear-devel/2004-November/032295.html]). This could for example be achieved by generalizing the current concept of aliases or by introducing a possibility to set file-specific (or possibly just global) variables in XML files that can later on be referenced and resolved in attributes or nodes in the XML file, i.e. along the lines of (the details might still need to be discussed, though): | * introducing the concept of "base/frame pointers" for property nodes (and possibly attributes) as described in [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg11307.html] would surely simplify PropertyList XML files tremendously and make them much more intuitive to work with (this is in fact conceptually pretty much identical to another suggestion, to provide basically the same facility for (non-relative, file system) paths and filenames provided in aircraft/PropertyList XML files, as posted in response[http://mail.flightgear.org/pipermail/flightgear-devel/2004-November/032299.html] to a request by C. Olson to enable aircraft to become more easily relocatable [http://mail.flightgear.org/pipermail/flightgear-devel/2004-November/032294.html] [http://mail.flightgear.org/pipermail/flightgear-devel/2004-November/032295.html]). This could for example be achieved by generalizing the current concept of aliases or by introducing a possibility to set file-specific (or possibly just global) variables in XML files that can later on be referenced and resolved in attributes or nodes in the XML file, i.e. along the lines of (the details might still need to be discussed, though): | ||