> On Feb 28, 2017, at 7:15 PM, Benson Chepkwony <bchepk...@att.net> wrote: > > Hi Sean, > I came across this MGED Command removals and I would like to participate > with the process. > Also is it possible to create a set of add on or a Plugin which can be > used to add this commands by users themselves.
Benson, That’s great to hear, thanks for speaking up! While it has always been in the plan for LIBGED commands to be modular with most loadable at runtime, there is currently no code or system in place that does this. All commands are basically run via a main-style argc/argv global function. Perhaps that’s a place where you could start? One thought is to create a command registration system where each “plugin” declares a set of commands that it will be registering and their respective callbacks. You can see a start of this in the ‘zoom' and more recent ‘help/apropos/info/?’ commands. It’s not done, not great, nor set in stone by any stretch, but the basic gist is to simply register a command with all it’s code and docs in one src/libged subdir. This implies moving all the doc/docbook/system/ manual pages into those respective subdirs eventually. It also implies rewriting the src/tclscripts/help*.tcl logic to utilize registered help instead of having command implementations spread throughout the source tree. EVERYTHING for a command should be in its subdir. Maybe see if you can figure out a pattern that gets us towards that? Cheers! Sean p.s. Note that we must follow the CHANGES policy for actually removing those commands. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
