Hi Raj,

On Mi, 2014-03-19 at 23:08 +0530, K RAJ KOUSHIK REDDY wrote:

>         2) My goodness, we don't use CVS! :) [snip]
> Ok. I meant the Controlled Version System but looks like there isn't
> such a term. ;) And CVS is an old obsolete SCM. I will correct that in
> a while

I'm pretty sure you meant VCS = Version Control System ;-)

>         4) I see no mention of documentation ... [snip]

That's actually a good point, adding examples with good explanation of
the parameters is something which could be helpful for the whole BRL-CAD
project, not just python-brlcad in particular...

>         6) Weeks 10-12 are "high risk".  That's a lot of time and no
>         detail to account for it.  Note that "brep" and "nurb" are
>         synonymous.  Maybe try to find a way to break that work up
>         into smaller subtasks.

The BREP primitive is definitely the hardest of all - to be able to get
an informed road-map of what to do there, you should study at least
shortly the open-nurbs library and plan how to map that to python !

Wrapping open-nurbs would actually be a project on it's own, but the
BREP primitive is likely only needing wrapping the data structures
(which is hard enough). It would however provide a good starting point
for further work to completely wrap that library !

>         As for primitives, these should probably be skipped:  grip, pg
>         (poly), hf, and bspline (which you don't list, good).

> Do you mean I should completely avoid them ? So do we have
> alternatives for them. or they are old ways of CAD drawing. I am just
> curious.

These are mostly not very useful or not maintained or have other
problems I guess...
 
>         These are of lesser priority and shouldn't have much time
>         invested in them due to their status: cline, constraints,
>         annotation.  
> Ok, I will take care of that. But I believe implementing them will
> still be my goal.

These are just stubs, not functional (even with native BRL-CAD tools),
so really not high priority...

>         I'd rather see a nice wiki page example showing an example
>         (with images) of how to use the python interface than to focus
>         on any of those old primitives.  However, I defer to your guru
>         mentors on that decision.

> Yeah, that is a nice idea. In fact I would think about this plan to
> follow a way to document the wrapped primitives. Also, I will be
> creating examples framework. And taking a feedback from Csaba and
> Bryan (who are already involved with the project) will be a good idea.

Totally agree, I always wanted to have a place where I can check for
examples of usage of each primitive. This page is a good start:

http://brlcad.org/wiki/BRL-CAD_Primitives

... but some primitives should be expanded, and pictures on the same
page, plus code examples (or links to them) on the same page would be
really nice !

Maybe mentioning expanding that page with (links to) code
examples/rendered images would be good.

In principle I trust you are ready to go, for the final touches Sean
please help Raj with suggestions if needed !

Cheers,
Csaba




------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to