On Wed, Dec 21, 2011 at 23:45, Christopher Sean Morrison <[email protected]> wrote: > On Dec 21, 2011, at 9:27 PM, Tom Browder wrote: ... >> I also notice the mged bb command does not show with "?" so where >> should I look to fix that? > > src/tclscripts/mged/help.tcl > > Hopefully not for too much longer, though. > The '?' tclscript command has fallen a little out of > sync with more than a few commands missing. > The goal is to move that help documentation over into > src/libged with each respective command defining > their help/usage string. Then the '?' command > becomes a built-in libged command that can > query all registered commands automatically.
1. How will the registration be done? Where will the master command lists be maintained? Right now I know the mged list is in src/mged/setup.c as was pointed out in recent e-mail. And is there any more info on plan for the change? I don't see much in TODO. I will fill in the bb help in the existing system but would like to follow up the same for the new system. Later: I have filled in info for bb and will check it in, but I see the need for expanded help somewhere (I remember this complaint from years ago), i.e., an '-h' or '--help' option for all commands. What is the plan for NOT duplicating help info? I remember some discussion about it versus man versus docbook but is it time for a working model on the trunk? Later: I now see that 'make_bb' is essentially the same as 'bb' but using only one common argument. Are they candidates for aliasing, say, make_bb to bb? 2. Another question ref a TODO project: There is a list of missing man pages. Would generating an almost blank template for each be helpful? I mean so there would at least be a place holder to be expanded by a volunteer. The result would be something like: man missing_cmd DATA TO BE ENTERED HERE--NEED A VOLUNTEER TO COMPLETE [This may be partially OBE if a new help system is started.] Best regards, and Merry Christmas, -Tom ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
