Re: [Flightgear-devel] RFD: /controls/engine/ reorg

2002-11-08 Thread julianfoad
David Megginson wrote: Julian Foad writes: No - we have that in some places, but I was thinking recently that it's not the right way to go. I think the only practical purpose is to reduce clutter in the browser; but the property browser could and should do this for us if we

[Flightgear-devel] RFD: /controls/engine/ reorg

2002-11-07 Thread David Megginson
A while ago, Curt suggested moving from /controls/afterburner[0] /controls/afterburner[1] /controls/afterburner[2] /controls/afterburner[3] /controls/mixture[0] /controls/mixture[1] /controls/mixture[2] /controls/mixture[3] /controls/propeller-pitch[0]

Re: [Flightgear-devel] RFD: /controls/engine/ reorg

2002-11-07 Thread Jon S Berndt
On Thu, 7 Nov 2002 14:03:54 -0500 David Megginson [EMAIL PROTECTED] wrote: A while ago, Curt suggested moving from /controls/afterburner[0] This looks like a good idea, but one thing I'll throw out here and maybe Tony has any idea on how we can handle this. I am still planning in

Re: [Flightgear-devel] RFD: /controls/engine/ reorg

2002-11-07 Thread Julian Foad
David Megginson wrote: A while ago, Curt suggested moving from ... and so on, to something more sane: /controls/engine[0]/ /controls/engine[1]/ /controls/engine[2]/ /controls/engine[3]/ Yes, lovely. Excellent. We could even go to /controls/engines/engine[0/ and so on to

Re: [Flightgear-devel] RFD: /controls/engine/ reorg

2002-11-07 Thread David Megginson
Julian Foad writes: No - we have that in some places, but I was thinking recently that it's not the right way to go. I think the only practical purpose is to reduce clutter in the browser; but the property browser could and should do this for us if we want it to. It also makes life