Hello Daniel!

On Fri, Mar 13, 2015 at 10:15 PM, Daniel Roßberg <danielmrossb...@gmail.com>
wrote:

> Kalpit,
>
> Sorry for the late response.  I was busy at work.
>

Ah, that's totally fine. Actually, it was good you replied a bit late; I
looked up on Mark's task as well. :P



> > I'm sorry I forgot to mention in my changes that you need to include
> > "raytrace.h".
> > The error will go away then and source will be succesfully compiled.
> > Here are the final changes, that I have done and successfully compiled
> the
> > source and run the tests :
> >
> > http://pastebin.com/Y0Aqy7ht
> >
> > I have attached the test log generated by ctest.
> >
> >>
> >> Maybe you should
> >> make a patch file from what you have really compiled and upload it to
> >> sourceforge.
> >
> >
> >  Should I upload a patch now and add you as the owner?
>
> Exactly.  This is usually what will be evaluated.  Otherwise you could
> forget to mention something ;)


Right! Got it. I'll be clear and precise from now onwards!



> >> > Everything else is good and running properly and fits the coding
> style.
> >> >
> >> > So, what's up next? :)
> >>
> >> Where do you think are the building sites of the core interface?
> >
> >
> > I didn't quite get you.
>
> There are many areas where the C++ interface can be improved.  E.g.
> - Adding new primitives
> - Adding new features, e.g.
>     - Primitives' features like centroid etc..  But they have to work
> for combinations too.
>     - Shader-colors from ray-trace
> - Improving the tests/test framework
> - Fixing oddness in BRL-CAD found during C++ interface development
> to list some of them.  On which area do you want to work?  Whith which
> would you feel comfortable?
>

I want to do the following tasks before starting implementing new things :
1. Get the coding style in existing files in coreInterface in conformation
with the guidelines mentioned in the HACKING file.
2. Finish reviewing the remaining 2 tests written by Mark, in GCi '14, for
Cone and Torus.
3. Talk to Andrei about his work and have a good understanding on what has
been already done!
(I aim to do this before I start working on the actual project targets)

About the things I would like to do in the project :
1. Adding new primitives (Writing their tests along the way)
2. Adding new features for the primitives in coreInterface (Writing their
tests along the way)

If time permits, I would be more than willing to add features for the
combination of primitives and test them.

I might be too ambitious here, but I assure you that I will complete each
and every single thing that I mention in my targets.
No looking back.



> Regards,
>     Daniel


With Regards,
Kalpit Thakkar

------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> BRL-CAD Developer mailing list
> brlcad-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to