On Fri, 2011-02-11 at 15:38 +0000, Martin Spott wrote: > Curtis Olson wrote: > > > On the subject of nasal and the property system. What this gives us is the > > ability to create all kinds of specific aircraft functionality or > > functionality specific to [...] > > I agree for the cases you're outlining in your statement. On the other > hand I think I understand what Alasdair is concerned about: > > Taking the ground surface material into account is a 'feature', a > requirement which clearly belongs into the responsibility of the > gear-department of the FDM. Thus if Nasal hacks to circumvent FDM- or > other core-deficiencies are becoming standard in the long run, then > this development is very likely going to bite you sooner or later. > > Maintaining a healthy level of distinction between core features and > add-on's is, to put it straightforward, a matter of 'education'. > > Cheers, > Martin.
Well said that man. Thank you, Martin. I could not have put it more succinctly myself. As I said in my original message, this was intended to be considered as a programming philosophy question, rather than a criticism of the NASAL sub-system, per se. And certainly _not_ a criticism of the property tree, which I think is rather cute in conception, but horribly prone to violation via run-time mechanisms. I, myself fell foul to thIs problem while researching more realistic allocation of a collection of festival voices for ATIS/TWR/GND/AI-Pilots etc. where a message was sent to /sim/messages/... in trafficcontrol.cxx and turns up immediently in voice.cxx as /sim/sound/voices/voice [n] Now, while I find this disagreeable as a theorist, I find disturbing as a pragmatist, in the sence that the executable fgfs will _not_ run if I choose to disable the NASAL (see below) ?plugin. Now, how do knowledgeable guys like AJ suggest who is the boss and who is the slave in this particular tug-of-love? As an aside, I would love to hear from the creator of the current git developer of fgdata/ATC/default.[vce,wav] with a view making ATIS announcements a little more human. For my own part, I found (voice_nitech_us_slt_arctic_hts) provided the most audible and closest approximation to sweetest female voice we had previously. Grrr... the lady's name is buried deep in my archives, so apologies to said lady's husband with whom I have communicated in the past You will note in all further dicussions that I will refer to "nasal" as NASAL (Not Another Scripting Language), which denies its very existentence through a lie in its own nomenclature. cf "GNU" which makes no such assertion, but was probably dreamed up by a brainy recursionist like Csaba. I suggest that this topic has diverged sufficient from the current "Subject" matter. I suggest "To Kludge or not_to use_NASAL, that is my Q". Sorry William S I, myself, as I am sure as AJ will attest to, am far too stupid to undertake this procedure on my own -- Kind regards, Alasdair ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
