David Megginson writes:
> Now that we're rearranging the /controls/ subtree, it might be a good
> time to clean up the naming.
>
> 1. Consistency
> --------------
>
> Most of the property names use lower case and hyphens ('-') as word
> separators. I suggest that we fix the following to be consistent:
>
> /controls/flight/BLC
> /controls/engines/engine[%d]/WEP
> /controls/fuel/tank[%d]/fuel_selector
> /controls/fuel/tank[%d]/to_engine
> /controls/fuel/tank[%d]/to_tank
> /controls/electric/APU-generator
> /controls/pneumatic/APU-bleed
This sounds reasonable.
> 2. Units
> --------
>
> In flightgear, we use suffixes for most property names to indicate the
> units (such as /position/altitude-ft or /environment/wind-speed-kt).
> Many of the control properties, however, are either normalized values
> (0:1 or -1:1) or boolean flags.
>
> Would it make sense to add suffixes to these as well?
>
> /controls/flight/aileron-norm
> /controls/gear/gear-down-flag
>
> (or something similar)?
This is a bit more verbose, but having the units at the end of the
name is a life saver ... I don't want to think about the number of
times I've had to go digging after a bug that turned out to be a
meters/feet conversion problem or some other units mixup. This won't
make all those problems magically go away, but it will help in many
cases.
> 3. Switches
> -----------
>
> Note that Curt's electrical system has a /controls/switches subtree,
> while the recent rewrite has a /controls/lighting subtree. We need to
> choose one or the other.
Electrical switches and circuit breakers can control a *lot* more
things than just lighting. I vote for /controls/switches/
Regards,
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED]
Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel