On Jun 25, 2013, at 3:25 PM, Nyah Chck wrote: > Hello everyone, > > I am currently studying the libged, libbn, and librt libraries to > identify routine which would be useful in implementing the pull > routine.
I suggest starting with a simple easy goal just to get started coding. Stub in a pull function that does nothing. This requires creating a new src/libged/pull.c, adding it to src/libged/CMakeLists.txt, and you can hook the command into the command table in src/mged/setup.c so it can be tested with mged. Archer requires more, but you can get to that later. That empty function will get you set up to have the command .. do something. > However, looking at my design document(Link) I would like to get some > suggestions on some possible routines( saw interesting routines in > /src/librt/transform.c,tree.c, dbwalk.c which would be invaluable or > more..) I can add or take from the brlcad source which would be really > useful in implementing the complete pull routine. Also, I would also > like some more ideas on possibly a better approach in implementing the > pull.c subroutines and the complete pull routine. User-centered design is very powerful. Look at it from a usability perspective instead of thinking about the implementation. How is a user running mged going to use your new command? What might a usage statement look like? What might an example usage look like on the command line if you saved a transcript? Cheers! Sean ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
