Difference between revisions of "User:Bhinesley"

From BRL-CAD
m (Edit command: better title)
(GSoC 2012 Project)
 
Line 13: Line 13:
  
 
== GSoC 2012 Project ==
 
== GSoC 2012 Project ==
TBA
+
See my [[User:Bhinesley/gsoc2012|GSoC 2012 proposal drafts]].
  
 
== Misc ==
 
== Misc ==

Latest revision as of 01:43, 28 March 2012

Who I am[edit]

My name is Brandon Hinesley. I'm a 27 year old, unemployed, full-time student in my junior year of a Bachelor of Science in Computer Science. I live in Bakersfield, CA. My preferred coding environment is in any *nix operating system, while using Vim and screen/tmux.

Contact[edit]

Experience[edit]

I participated in GSoC 2011 with BRL-CAD, under Cliff, my official mentor. I have 5 years of experience designing commercial plumbing systems in 3d, using AutoCAD. I've also fooled around a bit in Blender. I have experience in C/C++, and Tcl/Tk/Itcl/Itk. For 3 years I was a system administrator for a Linux/Windows based small business network.

GSoC 2011 Project[edit]

See the log and timeline or the official GSoC project summary for details. I migrated MGED commands to Archer/libged, and cleaned up existing commands. Later in the program, my focus shifted towards adding new capabilities to the libged oed commands, rather than simply migrating them.

GSoC 2012 Project[edit]

See my GSoC 2012 proposal drafts.

Misc[edit]

Edit command, TODO[edit]

  1. Getting help for the edit subcommands is confusing. ex: 'help translate' doesn't work, since translate is really just a subcommand of edit. The current workaround is to use 'edit help translate' or 'translate help'.
  2. It is not possible to use the batch operator '.' as a particular coordinate, i.e. 'translate -k -y . -a cube.s sph1.s sph2.s sph3.s' will not work. It would increase orthogonality if this were supported, although it's not strictly necessary. A workaround for the aforementioned example is 'translate -k . -a -y cube.s sph1.s sph2.s sph3.s'. It would take some doing to get this working, but it could be viewed as an opportunity to refactor some poor design decisions along the way.
  3. All testing has been done by hand. There are so many possible combinations of options/args, surely some have been overlooked.
  4. Cleanup logic per TODO/FIXME's in edit.c. Minor impact.
  5. The basic commands rotate and scale are not yet implemented
  6. Other subcommands could be written, for example:
    • swap - switch one object out with another
    • align - line several objects up with points on one or two axes (besides an intuitive name, it's not clear if this would be any better than using translate to perform this task, for ex: 'translate -k . -a -y cube.s sph1.s sph2.s sph3.s' moves sph[1-3].s to the same y-coordinate as cube.s, without changing x/z positions.)
    • other ideas?