* Curtis Olson -- Monday 19 February 2007:
> On 2/19/07, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> > } 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.
> I'm not enthusiastic about ripping this direct procedure call functionality
> out and replacing it with a complicated set of nasal based indirections.
Who said "nasal"?! I said "listener". You know that Nasal listeners
are only wrappers around the real listeners (SGPropertyChangeListener).
I meant such a C++ listener -- they were made exactly for such
purposes.
> I vote for leaving it as is, unless someone can present a really convincing
> argument otherwise.
The arguments are that these commands are
(1) undocumented features for one commercial project (correct?)
(2) limited to the telnet interface (while the listener solution
would also work for GUI dialogs, the httpd interface, etc.)
(3) clutter the interface for no good reason (well, since it's
undocumented, one could say that this doesn't matter, but it
still clutters the source code :-)
m.
-------------------------------------------------------------------------
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
