by Hooray » Sat Jul 06, 2019 12:14 pm
Actually, that's exactly right: fgcommands are documented in README.commands, which unfortunately hasn't been updated in a while.
Like you say, these days many subsystems register their own fgcommands, so that it would make sense to expose the SGCommandMgr to Nasal to obtain a list of commands dynamically, possibly in conjunction with fields documenting purpose and syntax/usage.
This would be a really simply C++ modification that would nicely fit the addcommand/removecommand APIs, i.e. an API to retrieve a list of available fgcommands, along with a help string, and an example.
That way, the list of fgcommands could be dynamically retrieved and shown on-screen, directly inside FlightGear, e.g. as part of the Nasal Console.
This would be superior to anything involving README files or wiki articles, because FlightGear fgcommands would become self-documenting