On 2/19/07, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
And while we are at it, we should get rid of this ugliness:
} else if ( tokens[1] == "set-sea-level-air-temp-degc" ) {
[...]
} else if ( tokens[1] == "set-outside-air-temp-degc" ) {
[...]
} else if ( tokens[1] == "timeofday" ) {
[...]
} else if ( tokens[1] == "play-audio-message" ) {
This does really not belong into the telnet interface (IMHO).
A simple "set /whatever/property value" can do the same, and if special
actions are required, then a listener function should do the job.
Hold on ... the telnet interface allows reading and writing properties, but
it also allows launching specific functions that have been enabled in the
telnet interface. These are two distinct types of actions. You trigger
these with a "run [command] [opts ...]" command.
I'm not enthusiastic about ripping this direct procedure call functionality
out and replacing it with a complicated set of nasal based indirections.
That's just a bunch of extra complication and overhead.
I vote for leaving it as is, unless someone can present a really convincing
argument otherwise.
Regards,
Curt.
--
Curtis Olson - University of Minnesota - FlightGear Project
http://baron.flightgear.org/~curt/ http://www.humanfirst.umn.edu/
http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
