Difference between revisions of "User:Schindler97/GSoC18/Log"

From BRL-CAD
(Coding Period)
(Coding Period)
Line 29: Line 29:
 
** ''' 18 May '''
 
** ''' 18 May '''
 
*** Introduced primtive : ell1
 
*** Introduced primtive : ell1
*** Going through libged to figure out how the 'in' command works, still can't find it.
+
*** Going through libged to figure out how the 'in' command works. Edit : Found it, thanks to Cezar :)
 
*** Reading through the code of the ell primitive in librt to understand how primitives behave at a ground level. There's a lot going on, might take me a while to figure everything out.
 
*** Reading through the code of the ell primitive in librt to understand how primitives behave at a ground level. There's a lot going on, might take me a while to figure everything out.
 
*** Sean recommended going through the various READMEs scattered across the code, will start on those too and log progress here.
 
*** Sean recommended going through the various READMEs scattered across the code, will start on those too and log progress here.

Revision as of 11:09, 18 May 2018

Development Logs

Community Bonding Period

Progress through the community bonding period

Coding Period

Progress through the coding period. Track changes in the current working repo : https://github.com/Killthebug/python-brlcad-tcl/commits/master

  • Week 1
    • 14 May Introduced bindings and examples for primitives : arb4, arb5, arb7
    • 15 May Introduced bindings and examples for primitives : tec, trc
    • 16 May Introduced bindings and examples for primitives : rhc, rec
    • 17 May Introduced bindings and examples for primitives : ehy, epa
    • 18 May
      • Introduced primtive : ell1
      • Going through libged to figure out how the 'in' command works. Edit : Found it, thanks to Cezar :)
      • Reading through the code of the ell primitive in librt to understand how primitives behave at a ground level. There's a lot going on, might take me a while to figure everything out.
      • Sean recommended going through the various READMEs scattered across the code, will start on those too and log progress here.